Privacy Policy: AZR Intelligence Platform browser extension and service
At a glance
| Field | Value |
|---|---|
| Version | 1.0, 14 November 2026 |
| Effective date | 14 November 2026 |
| Provider | AZR SOFTWARE SOLUTIONS W.L.L., Commercial Registration 234601 |
| Address | 10th Floor, Hleatan Tower, Al Safliya Street, Doha, Qatar |
| Privacy contact | Data Protection Officer, AZR SOFTWARE SOLUTIONS W.L.L., privacy@azr.com.qa |
| Covers | The AZR Intelligence Platform browser extension, the sign-in it uses, the hosted evidence service ("the Core") it talks to, and the administration console ("Studio") |
| Language | Both the Arabic and English texts form part of the agreement; if they differ, the Arabic text prevails. |
1. In short
- The extension reads the text of a web page on your computer and looks for words that have the shape of a business reference (an identifier, for example a payment or invoice number). It does this only on sites your organization's administrator has approved, and only after you have allowed the extension to work on that site in your browser.
- It does not send page text or the page address to us. It sends only the identifiers it found (for example
PMT-700102), together with your Microsoft sign-in token, to your organization's AZR service (the Core), so the service can return the evidence card for that record. When you save a decision, the decision and the reason you typed go to the same service. - The evidence shown on a card belongs to your organization (the "customer"). We process it for the customer.
- We do not sell personal data, show advertising, build advertising profiles, or use customer data to train any model. The extension has no analytics or telemetry code.
- The product is read-only toward your business systems in this release.
- The Service is offered to organizations outside the European Union. Before we offer it in the European Union we will appoint a representative and sign standard contractual clauses.
2. Who is responsible
| Role | Who | For which data |
|---|---|---|
| Processor | AZR SOFTWARE SOLUTIONS W.L.L. | Customer data: records and documents from the customer's connected sources, the cards and decision receipts built from them, the identifiers the extension sends, and the people the customer invites. The customer is the controller and decides which sources, sites and patterns are used. |
| Controller | AZR SOFTWARE SOLUTIONS W.L.L. | Account and billing contact data of the customer's administrators, sign-up and trial records, support messages, security records, and the minimal operating logs of the service. |
"Controller" and "processor" have the meaning given in Article 1 of Law No. 13 of 2016 on protecting the privacy of personal data ("the Qatar law").
A data processing agreement between AZR and each customer governs the processor role. It is shown with the order form and accepted electronically with it by a recorded "I accept" action, and we send a copy on request. No customer data or credential is accepted before it is in place.
People named inside a customer's records (for example supplier contacts or payees) were never enrolled by AZR, and AZR cannot notify them. Telling them what the law requires is the customer's duty as controller. AZR uses that data only to build the card: no reuse, and no index or copy for any other purpose.
3. What the extension and the service process
3.1 On your computer (the extension)
| What | Detail | Stored where | Kept until |
|---|---|---|---|
| Page text | Read in memory on approved sites to find reference-shaped words. Only tokens of letters, digits and . _ - /, at most 64 characters, can be kept as candidates. Never stored, never sent. |
Not stored | The scan ends |
| Sign-in token | Issued by Microsoft Entra after you sign in with your organization account. The extension never sees a password. | Browser session storage | Sign-out or end of the browser session |
| Sign-in name and account id | Lets the extension sign you in again after a browser restart without asking, only for the same account. Not a token. | Browser local storage | Sign-out |
| Signed organization configuration | Approved sites, reference patterns, card templates, branding, and the public key that verified them. | Browser local storage | Replaced, expired, or the extension is removed |
| Extension settings | Language, digit style, site pauses. Your browser may synchronize these through your browser account. | Browser sync storage | You remove them |
| Evidence values | Not cached on disk. Shown only inside the extension's own side panel and isolated card frame, never written into the web page. | Memory | The panel or card closes |
The extension has no analytics or telemetry code. It asks the browser for access to a site only after your administrator approves it; you can withdraw that access in the browser settings at any time.
3.2 What is sent to the service
| Request | What it carries | Why |
|---|---|---|
| Look up references | The list of identifiers (reference-shaped words) found on the page (at most 200 per message, at most 1,000 distinct per page), your Microsoft sign-in token, a request id | To find which records exist and which you may see |
| Open a card | The identifier of the record and the display language (en or ar) |
To return the card |
| Save a decision receipt | Outcome, the reason you typed, the record identifier, the module id of the surface | To keep a record of your decision and its reasons |
| Refresh the organization configuration | Your sign-in token | To receive the signed configuration, every 20 minutes and at start-up and sign-in |
| Sign in | Standard sign-in exchange with Microsoft Entra (login.microsoftonline.com) |
To prove who you are |
The extension is allowed by its security policy to connect only to the customer's AZR service address (the Core) and to Microsoft sign-in. Page text and the page address are not part of any request.
3.3 What the service stores
| Category | Content | Source | Purpose |
|---|---|---|---|
| Identity and access | Microsoft Entra tenant id, your directory object id, display name and role claims in the token; seat assignments | Your organization's Microsoft Entra sign-in; administrator | Sign you in, decide your organization and role, enforce seats and plan limits |
| Evidence data | Facts from the customer's connected sources with source, time and the parties allowed to see them; entity names and aliases; document text or its hash where the source provides it. May contain financial and personal data in the customer's records. | Customer connectors | Build the evidence card |
| Reference lookups | The identifiers sent by the extension are used to find records and are not kept as a browsing history. | The extension | Look up the card |
| Decision receipts | Outcome, your typed reason, facts and gaps at that time, rule version, a snapshot with its hash and signature, who acted | You, in the side panel | Keep the reason behind a decision and show it was not changed |
| Configuration | Approved sites, patterns, templates, branding, connection settings, agent registrations, webhook endpoints | Administrators | Run the product as the customer set it up |
| Secrets | Connection passwords and tokens that an administrator enters | Administrators | Let a connector read a source; encrypted, held in Azure Key Vault where configured, never shown again |
| Usage records | Meter name, quantity and time (for example a receipt saved). No content. | The service | Plan limits and billing |
| Audit log | Who made an administrator change, what, when, the target, and the result. No bodies, secrets or card values. Entries cannot be edited or deleted through the product. | The service | Accountability |
| Subscription and billing | Plan, seats, status, term dates, invoice contact. Billing is by invoice from AZR (yearly, in Qatari riyals, by bank transfer). The extension and the service take no card numbers in this release. | Sign-up, order | Provide the plan and invoice it |
| Sign-up and support | Name, work email, organization name, what you write to us | You | Create the account, run the trial, answer you |
| Operating logs | Time, route, status, request id, error type. Authorization headers, cookies, values, amounts, reasons and bodies are removed before a log line is written. | The service | Keep the service running and secure |
Any index, cache, export or derived copy of personal data is itself personal data, and this policy treats it as such.
3.4 What we do not do
We do not read pages that are not approved. We do not send page text or page addresses to the service. We do not sell or rent personal data, show advertising, or use customer data to train a model. Optional AI explanations are off; if they are ever turned on for a customer, the provider is added to section 5 first and the customer chooses.
4. Why we process it
Under Article 4 of Qatar Law No. 13 of 2016 we process the data we control as controller because it is necessary for a legitimate purpose: providing, securing and billing the service the customer ordered. We send marketing only with prior consent (Article 22). Customer data is processed on the customer's instructions; the customer is responsible for its own legal basis.
| Purpose | Data | Ground |
|---|---|---|
| Provide the service the customer ordered | Identity, evidence, identifiers, receipts, configuration, secrets | Legitimate purpose of providing the contracted service (Article 4); for customer data we act on the customer's instructions |
| Security, abuse prevention, audit log | Audit log, operating logs, identity | Legitimate purpose of keeping the service secure (Article 4) |
| Billing and plan limits | Subscription, usage, invoice contact | Legitimate purpose of billing the contracted service (Article 4); legal duty to keep accounting records |
| Support and service messages | Sign-up and support data | Legitimate purpose of answering you (Article 4) |
5. Who else processes data (subprocessors)
| Provider | What it does | Data | Location |
|---|---|---|---|
| Microsoft Corporation, Microsoft Azure (Container Apps and Database for PostgreSQL) | Runs the Core and the database | All service data | Microsoft Azure UAE North (United Arab Emirates) |
| Microsoft Corporation, Microsoft Azure (Key Vault, Container Registry, Storage) | Holds connection secrets, the container images and the Studio console files; service logs are also kept there | Secrets, software, console files, operating logs | Microsoft Azure Qatar Central |
| Microsoft Corporation, Microsoft Entra ID | Signs people in; we receive the token claims in section 3.3 | Sign-in tokens and claims | As set by the customer's Microsoft agreement |
| Microsoft Corporation, Microsoft 365 (Exchange Online) | Email we send and receive from our azr.com.qa mailboxes (trial, invoice, service and support messages). We use no other email provider. | Name, email address, message content | The data location of AZR's Microsoft 365 organization: Qatar (Doha), for mailbox content stored at rest (Exchange Online), under Microsoft's product terms |
| Cloudflare, Inc. | Hosts the product website (extension.azrapps.qa), including these policy pages, on Cloudflare Pages | Website request logs: IP address, browser type, page requested, time | Cloudflare's global network; Cloudflare, Inc. is a United States company that stores information mainly in the United States and the European Economic Area |
| The browser store from which the extension was installed | Distributes the extension; independent of us, under its own policies | Install data it holds | Its own |
Our product website (extension.azrapps.qa) is hosted on Cloudflare Pages by Cloudflare, Inc., a United States company with a global network. When you visit it, Cloudflare receives your IP address, browser type, the page you asked for and the time. Cloudflare stores information mainly in the United States and the European Economic Area, can access it from other countries where it operates, and keeps its request records under its own terms; it does not state to us how long it keeps them. This website holds no account data or customer data.
This table is the current list of our subprocessors and hosting regions. We update it before any change takes effect, and the version date at the top of this page shows when it last changed.
We give customer administrators 30 days' written notice before a new subprocessor starts, before a change of hosting region, and before a material change to this policy. A customer may object to a new subprocessor, or to a move of its data to a country not already listed in this table; if the objection is not resolved, it may end the affected service and receive a pro-rata refund of prepaid fees. If a move is needed at once to protect the data, we move it only to a region already listed and tell customer administrators within 72 hours.
Systems that the customer chooses (its own ERP, document library, webhook destinations, tool servers) are not our subprocessors. Data goes there only because the customer set them up. We disclose personal data to authorities only when a binding legal request requires it, and we tell the customer first where the law allows.
6. Security
- Customer data is separated by organization: the database enforces row-level security on every tenant table, and the organization is taken from the verified sign-in token, never from what the client sends.
- Sensitive values appear only inside the extension's own side panel and isolated card frame, never in the page's code, tooltips or events.
- Roles and field permissions decide who sees which value; a value you may not see is shown as unavailable.
- Connection secrets are encrypted or held in a key vault. Tokens are kept in memory-backed session storage and removed at sign-out.
- The organization configuration the extension receives is signed (Ed25519) and checked before use.
- Decision receipts are hashed and signed; opening one checks your access again.
- AI agents are separate principals: they read and request, only people approve.
- We run a security and version check on every build and keep third-party components current.
No system is perfectly secure. We make no uptime, speed or certification claim here.
7. How long we keep data
| Data | Kept for |
|---|---|
| Page text | Not kept |
| Sign-in token | Until sign-out or end of the browser session |
| Signed configuration in the extension | Until replaced, expired, or the extension is removed |
| Evidence data, entities, versions, source state, decision receipts, uploaded files, audit log | While the subscription is active. Exported on request for 30 days after it ends. Deleted from our live systems, with every derived copy, within 30 days after that (day 60 at the latest). We delete by hand, following a written procedure that we have tested, and we record each deletion. Copies in backups, logs and the key vault expire afterwards on the schedules in the rows below. |
| Export file we prepare for you | Deleted when you confirm you received it, or 14 days after we send it, whichever is first. Microsoft Azure keeps a deleted copy for 30 days. |
| Trial data | Deleted 30 days after the trial ends unless the customer subscribes |
| Secrets | Until the connection is replaced or deleted, and no later than the deletion above. We delete them from the key vault. Microsoft Azure keeps a deleted secret for 90 days (soft delete, with purge protection). During that time only people with administrator rights on the vault can recover it, and the service cannot read it. |
| Operating logs | No more than 90 days. Log lines cannot be selected by customer, so deleting a customer's data does not remove them; they expire within this period. |
| Webhook delivery records | 30 days |
| Usage records, subscription and invoice records | 10 years after the financial year they belong to (Decision No. 39 of 2019, Article 36 item 1), or longer while a dispute is open |
| Sign-up and support messages | While the account exists plus 12 months |
| Backups | Microsoft Azure makes database backups inside the same region as the database (UAE North). They are not copied to any other region. They are kept for 7 days, the value set on the database server today. We cannot remove one customer from a backup, so deleted data stays in a backup until it expires, which today is at most 7 days after the deletion. After any restore we re-apply the deletions recorded since, before the restored database serves anyone. If the period changes we update this section first. |
| Our record that a deletion took place | Kept. One entry with the organization identifier, the time and the fact of the deletion, with no names and no customer content (section 9). |
Deletion reaches search indexes, caches and exports. Backups, logs and key vault copies expire on the schedules above.
Records we must keep. A legal obligation or an order of a competent court may require us to keep specific records, and an open dispute between us and a customer may require us to keep the records it concerns. We then keep only those records, only for as long as the need lasts, tell the customer's administrator which records and why unless the law forbids it, and delete them when the need ends (Articles 10 and 19 item 2 of Law No. 13 of 2016). The accounting records in the table above are kept for the reason stated there.
8. Breaches
We notify the customer immediately when we become aware of a breach of our safeguards or of any threat to personal data, and in any case within 24 hours, then update the customer as facts are confirmed. The 24 hours is an outer limit only; it is never a reason to wait. For data we control as controller, we also tell the affected individuals and the competent department where the breach is likely to cause serious harm (Article 14 of the Qatar law).
9. The audit log
Every administrator change (sites, patterns, templates, branding, connections, datasets, agents, seats, webhooks, audit export) is recorded: who, what, when, the target and the result. Refused attempts are recorded too. At the database, entries cannot be updated, deleted or truncated by the service role. Administrators can filter and export it in Studio; the export is itself recorded. When a customer's data is deleted (section 7), its audit log entries are deleted with it, because they hold the names and directory identifiers of the customer's administrators. Only a deletion run under the procedure in section 7, by our technical team, removes them. We keep one entry that records that the deletion took place: the organization identifier, the time and the fact, with no name and no content.
10. Cross-border data flow
The Service is hosted in the Microsoft Azure regions named in the subprocessor list in section 5, which is always the current list. At the version date of this policy, data is stored in Microsoft Azure UAE North (United Arab Emirates), and connection secrets, the container registry, the console files and service logs are in Microsoft Azure Qatar Central (State of Qatar). We keep no copy of customer data outside the regions in that list. Qatari law permits these flows (Article 15 of Law No. 13 of 2016); we protect the data with the safeguards in section 6 and Microsoft's data processing terms. Before data moves to a different region, we update section 5 and give the 30 days' notice it describes. We move data to another country otherwise only when the customer connects a source or destination in another country.
11. Your rights
Under Law No. 13 of 2016 you may: withdraw consent, object to processing, ask for deletion or erasure, and ask for correction (Article 5); and access your data, be told of its processing and receive a copy (Article 6).
- If your data is in your organization's records, ask your organization's administrator first; the organization is the controller, and we help it answer.
- For data we hold as controller, write to the Data Protection Officer at privacy@azr.com.qa. We may need to confirm who you are first.
- We answer within 30 days of receiving the request, free of charge.
- You may complain to the competent department for personal data protection in the State of Qatar under Article 26 of Law No. 13 of 2016. The National Cyber Security Agency is charged with implementing the laws and decisions on personal data privacy (Amiri Decision No. 1 of 2021, Article 3 item 21), and at the version date of this policy its website takes individual complaints (ncsa.gov.qa, page "Individual Complaints").
12. Children and sensitive data
The product is for working adults in organizations. It is not directed to children and we do not knowingly collect their data.
Special-nature personal data is barred. Do not connect sources or fields holding personal data of a special nature (Article 16 of Law No. 13 of 2016: ethnic origin, children, health or physical or psychological condition, religious belief, marital relationship, criminal offences). AZR holds no permit to process them, and no agreement can cover them.
13. Laws
- Qatar. Law No. 13 of 2016 on protecting the privacy of personal data (Official Gazette, issue 15, 29 December 2016) is the law in force that regulates the processing of personal data in the State of Qatar. This policy cites Articles 1, 4, 5, 6, 9, 10, 13, 14, 15, 16, 22 and 26.
- European Union. The Service is not offered in the European Union at this time, and AZR has no representative there. The General Data Protection Regulation (Regulation (EU) 2016/679) is therefore not relied on in this policy. If we offer the Service in the European Union we will first appoint a representative and sign standard contractual clauses, and publish an updated policy.
14. This website and changes
The product website uses no cookies and no script and stores nothing in your browser. Cloudflare, Inc., which hosts it (section 5), records each request in logs that it keeps under its own terms, for a period it does not state to us, to serve and secure the site. We post changes here, change the version and date, and give customers' administrators 30 days' notice before a material change takes effect. Both the Arabic and English texts form part of the agreement; if they differ, the Arabic text prevails.
15. Contact
AZR SOFTWARE SOLUTIONS W.L.L., Commercial Registration 234601, 10th Floor, Hleatan Tower, Al Safliya Street, Doha, Qatar. Privacy contact: Data Protection Officer, AZR SOFTWARE SOLUTIONS W.L.L., privacy@azr.com.qa. Support: support@azr.com.qa. European Union representative: none.
16. Statement for the Chrome Web Store (Limited Use)
Google's Chrome Web Store User Data Policy requires an affirmative statement, on a website that belongs to the extension, that the use of data complies with the Limited Use requirements. We make that statement in the words of Google's own example:
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
In plain words, for this extension:
- We use user data only to provide or improve the extension's single purpose: showing the evidence behind a business record on sites the organization's administrator approved, and keeping decision receipts.
- We transfer user data to third parties only where necessary to provide that purpose (the subprocessors in section 5), to comply with law, to protect against malware, spam, phishing, fraud or abuse, or in a merger, acquisition or sale of assets after the user's explicit prior consent.
- We do not allow humans to read user data unless the user gives explicit consent for specific data, the data is aggregated and anonymized for internal operations, it is necessary for security (for example investigating abuse), or the law requires it.
- We do not use or transfer user data for personalized advertising, we do not sell it to advertising platforms, data brokers or other information resellers, and we do not use it to determine credit-worthiness or for lending.
- The extension uses no web browsing activity except the reference-shaped words found on pages of approved sites, for the user-facing card feature described in the store listing and in the extension's first-run screen.
Source: Chrome Web Store program policies, "Protecting User Privacy", sections Privacy Policy and Limited Use (developer.chrome.com/docs/webstore/program-policies/limited-use and /privacy, read 13 November 2026).