Privacy Policy
Last updated: 6 November 2026
This policy explains what personal data Counted collects, why we collect it, who can see it and the choices you have. It covers our website, the Counted app and the accounting services we provide.
The short version
- We connect to your bank, accounting system, mailbox or cloud storage only after you or someone at your company authorises it.
- AI reads your documents, transactions and messages to prepare your books. Our accountants review the exceptions and sign off.
- We do not sell personal data, use it for advertising, or use it to train general-purpose AI models.
- Your data is stored mainly in the Netherlands, and some of the providers we use process it in the United States.
- Disconnecting a source stops new data coming in, but does not delete what we already hold. To ask us to delete data, email privacy@getcounted.ai.
This summary is for convenience. The full policy below is what applies.
1. Who we are
Counted L.L.C-FZ (“Counted”, “we”, “us”) is a licensed accounting firm based in Dubai, United Arab Emirates.
Meydan Grandstand, 6th Floor, Meydan Road, Nad Al Sheba, Dubai, UAE
Trade licence: 2650616.01 (Meydan Free Zone)
Privacy contact: privacy@getcounted.ai
We handle personal data in line with the UAE Personal Data Protection Law (Federal Decree-Law No. 45 of 2021, the “PDPL”) and any other data protection law that applies to us.
We are the controller of data about website visitors, app accounts and our own business records. When we keep a client’s books, the client decides why its records are processed and we mainly act on its instructions as a processor. We act as a controller of client data where we set the purpose ourselves, for example to meet our own professional, tax or anti-money-laundering duties, or to keep our systems secure.
2. Who this policy covers
This policy covers:
- Website visitors, including anyone who sends an enquiry, completes the health check or books a call.
- App users, including founders, finance staff, anyone they invite, and Counted staff.
- People we contact for a client, for example by WhatsApp or email to collect a missing document or answer a question.
- People named in a client’s records, such as suppliers, customers and employees who appear on invoices, bank transactions or payroll. The client is usually your first point of contact, but you can also contact us.
Services you connect to Counted, such as your bank, Google or Zoho, have their own privacy policies. This policy does not cover them.
3. The data we collect
From our website
- Enquiries and the health check: your name, company, email, phone number, the plan you are interested in, your message and your health check answers.
- Where you came from: campaign tags, the page you landed on and the referring site, which we attach to your enquiry.
- Technical details: your IP address and browser details when you send an enquiry, and for analytics the pages you view, what you click, the referring site, your device type and your approximate location.
- Call bookings: Calendly collects the details you enter when you book a call and shares them with us.
Your account and sign-in
- From Google or Microsoft: your name, email address, profile photo and account identifier. Microsoft sign-in can also give us the phone number on your Microsoft profile.
- From you: your profile details, including your phone number.
- Session records: a hashed session token, the sign-in method, IP address, browser details, and when you signed in and were last active.
- Authorisation records: who connected a source, what access they granted, when, and from which IP address and browser.
Your company
- Legal name, website domain, logo, country, base currency and tax registration number.
- Your contact directory: names, email addresses, phone numbers, photos and notes about the people we may contact for your company.
- Identity and ownership documents, where we need them for client due diligence under anti-money-laundering rules.
Accounting and bank data
- From your accounting system: chart of accounts, contacts, tax codes, invoices, bills, expenses, payments, journals, bank feeds and reports.
- From your bank or uploaded statements: account names and numbers, balances where the bank provides them, transactions, counterparties and saved beneficiaries, including their IBANs.
- Bank login details: if you connect a bank with your online banking login, the username, password and device details needed to sign in. See Section 5.
Emails and files
From the mailboxes, folders and drives you connect, we look for emails with attachments and for files that may be accounting documents. For each one we may store its sender, subject, date, file name and a content fingerprint.
- Accounting documents (invoices, bills, receipts, supporting documents and payment confirmations): we keep a copy of the original and the details we extract, such as supplier, amounts, dates and VAT information.
- Other files: we do not keep a copy of the original. We keep a reference to it, a short summary and the extracted text, so we can reassess it later without reading the file again.
WhatsApp and other messages
When you message Counted, or we message you, we keep your phone number or email address, your messages, voice notes and their transcripts, images and documents you send, and delivery and read status. We also record your consent to be contacted on each channel.
Payroll and payments
Where your plan includes them, we process payroll details such as employee names, salaries, gratuity and bank details, and supplier payment details such as the recipient, IBAN, amount, purpose and who confirmed the request.
Automatic data from the app
We collect diagnostic logs about requests, errors and background work. See Section 8 for what these can contain and Section 11 for cookies.
Sensitive information
We do not ask for health data or other sensitive categories of personal data. They can still appear in documents you connect or send, such as a medical bill or a payroll record. We handle them with the same controls as the rest of your records.
4. How we use data and our legal grounds
| Purpose | What this involves | Legal ground |
|---|---|---|
| Provide accounting, tax and payroll services | Preparing books, reconciling transactions, preparing returns and reports, running payroll and supplier payments | Contract with you or your organisation |
| Connect your sources | Signing in to the services you authorise and importing data from them | Your consent, and the contract |
| AI-assisted preparation | Reading documents, categorising and matching transactions, checking for duplicates, transcribing voice notes and drafting questions | The contract, and your consent to connect sources |
| Message you | Asking for a missing document or answer, sending service updates and handling requests on WhatsApp or email | Your consent, and the contract |
| Run accounts and keep them secure | Sign-in, access control, preventing misuse and investigating problems | The contract and legal obligations, and legitimate interests where the law applying to you recognises them |
| Reply to enquiries | Answering your enquiry or health check and following up | Your consent, and steps you ask for before a contract |
| Understand and fix our website and app | Site analytics, debugging and reliability work | Your consent where required, and legitimate interests where the law applying to you recognises them |
| Meet legal duties and handle claims | Tax and accounting records, anti-money-laundering checks and reports, responding to authorities, and bringing or defending legal claims | Legal obligation, and establishing or defending legal claims |
Where we rely on consent, you can withdraw it at any time. This does not affect what we have already done, but it may stop us providing some or all of the service.
Where we process data for a client, that client is responsible for its own legal ground and for telling its employees, suppliers and other people that it shares their data with us.
5. Connected sources
We access these sources only after someone authorised at your company connects them. Each one gives us the following access:
| Source | What we can do | Why |
|---|---|---|
| Gmail | Read messages and attachments, organise messages, including labelling and moving them to the bin, and send email | Capture accounting documents and handle accounting correspondence for you |
| Outlook, including shared mailboxes | Read messages and attachments, organise messages and send email | Capture accounting documents and handle accounting correspondence for you |
| Google Drive | Read files (read-only) | Capture accounting documents |
| OneDrive and SharePoint | Read files | Capture accounting documents |
| Zoho Books and QuickBooks | Read, create, change and delete accounting records | Keep your books, post entries and reconcile |
| Your bank | Sign in, read accounts and transactions, and, where your plan includes it, submit payment requests for your approver to release | Keep your books current and prepare supplier payments |
Online banking logins. Some bank connections use your own online banking login. We store those details encrypted and use them to sign in on your behalf, and the bank may ask you for a one-time code. These connections cannot release a payment. Release stays with the approver at your bank.
Disconnecting. You can disconnect a source on the Integrations page in the app, or by asking us. This stops new data coming in and removes the stored login or access token. It does not delete data we already hold. See Section 14.
6. How we use AI
We use AI models to read documents, extract details, categorise and match transactions, check for duplicates, transcribe voice notes and hold conversations on WhatsApp. To do this, we send document files and text, transaction details, messages and voice notes to our AI provider, currently OpenAI.
Training. We do not use your data to train general-purpose AI models. We have not opted in to OpenAI using our data for training, and OpenAI’s published policy is that API data is not used for training without that opt-in. OpenAI generally keeps API inputs and outputs for around 30 days for abuse monitoring and to run the service, and longer where the law requires. Patterns we learn from your books, such as how you categorise a supplier, are used only for your organisation.
Staff AI assistants. Counted staff can also use Claude (Anthropic) and ChatGPT (OpenAI) through a restricted connection to work with a client’s connected accounting system, mailboxes and files. Content they retrieve this way is processed by that assistant’s provider. This connection is limited to staff with an active Counted account and a Counted email address, and actions that would change data ask the staff member to confirm first.
Human review. AI proposes and accountants decide. High-confidence items can be applied automatically under rules our accountants approve. Everything else goes to an accountant, who also signs off your books. We do not make decisions that have legal or similarly significant effects on individuals by automated means alone, and you can ask for a person to review any AI output that affects you.
AI can make mistakes. If something looks wrong, tell us and we will correct it.
7. Google and Microsoft account data
This section explains how we handle data from Google APIs. We handle data from Microsoft accounts in the same way.
What we access
- Google sign-in: your name, email address and profile photo.
- Gmail: messages, attachments and labels in a mailbox you connect, and the ability to organise messages and send email.
- Google Drive: read-only access to files in a Drive you connect.
How we use it
We use this data only to provide the features you see in Counted: finding, reading and storing accounting documents, matching them to transactions, showing accountants the evidence behind an entry, and sending email for your organisation.
How we store and share it
We store this data as described in Section 9, and encrypt access tokens. We share it only with the providers that help us deliver those features (Railway, OpenAI, Anthropic and Pydantic), for security, or to comply with the law. We would transfer it in a merger, acquisition or sale of assets only after asking for your explicit consent.
Who can read it
By connecting your account, you agree that our accountants can open specific messages, attachments and files when they need to for your accounting work. Otherwise, people can read this data only to investigate a security issue or bug, or to comply with the law.
What we do not do
- We do not sell Google user data or transfer it to advertisers or data brokers.
- We do not use it for advertising, including retargeting.
- We do not use it to assess creditworthiness or for lending.
- We do not use it to train general-purpose AI models.
Counted’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
8. Who can see your data
We do not sell personal data or share it for advertising. The people who can see it are:
- People in your organisation with an account, according to their access.
- Counted staff. Our accountants and operators use named staff accounts that are not limited to one client, because they work across clients. We keep audit records of financial actions and of staff access to conversations.
- The services you connect, such as Google, Microsoft, Zoho, Intuit and your bank, as needed to read from them or act in them for you.
- Professional advisers, such as lawyers, auditors and insurers, under duties of confidentiality.
- Authorities, such as the Federal Tax Authority, regulators and courts, where the law requires it, including anti-money-laundering reporting.
- A buyer or successor, if we are part of a merger, acquisition or sale of assets, subject to Section 7 for Google user data.
We also use these service providers:
| Provider | What they do | Main location |
|---|---|---|
| Railway | Hosts the app, database and file storage, and the gateway used for some bank connections | Netherlands; United States for the bank gateway |
| OpenAI | AI models, transcription and a staff AI assistant | United States |
| Anthropic | Staff AI assistant | United States |
| Pydantic (Logfire) | Diagnostic logs and traces. These can include the content of AI requests and replies, such as text from documents and messages. We design logging to leave out passwords and access tokens | United States |
| Meta (WhatsApp) | Sends and receives WhatsApp messages | Global |
| Resend | Sends invitation and sign-up emails | United States |
| Notion | Stores website enquiries in our sales records | United States |
| Calendly | Books calls | United States |
| Lovable and Cloudflare | Host and protect our website and provide its analytics | Global |
| Google Fonts | Delivers website fonts and receives your IP address | Global |
| Logo.dev and Brandicons | Find your company logo using your website domain | Global |
We will update this list when these providers change in a material way.
9. International transfers
Our main database and file storage are in the Netherlands. Some processing happens in the United States, including AI processing, diagnostic logs and the gateway used for some bank connections. Other providers listed in Section 8 may process data elsewhere.
Where we transfer personal data out of the UAE, we rely on what the PDPL allows: a destination with adequate protection, contract terms with the recipient, a transfer needed to perform a contract with you, or your consent. Contact us for more detail.
10. Security
- Data travels over encrypted connections.
- Stored logins and access tokens are encrypted with a dedicated key, and the app never shows them back to anyone.
- Session tokens are stored only as hashes, and the session cookie cannot be read by scripts in the browser.
- Each client’s data is kept separate. We do not reuse one client’s data, credentials or learned patterns for another.
- Client users can reach only the areas of the app their role allows.
- We keep records of connection authorisations, financial actions and accountant decisions.
No system is completely secure. If a breach is likely to put your rights at risk, we will tell you and the relevant authorities as the law requires. Please keep your Google or Microsoft account secure and tell us straight away if you suspect misuse.
11. Cookies and browser storage
| Name | Where | Purpose | How long |
|---|---|---|---|
| counted_session | App | Keeps you signed in | 7 days |
| Sign-in and sign-up cookies | App | Protect sign-in, sign-up and connection steps | 10 to 30 minutes |
| sidebar_state | App | Remembers whether the sidebar is open | 7 days |
| __cf_bm | Website | Cloudflare bot protection | 30 minutes |
| __dpl | Website | Routes you to the right version of the site | 24 hours |
| session-id | Website | Groups page views into one visit for analytics | 30 minutes |
| counted_src (browser storage) | Website | Remembers where your visit came from, to attach to an enquiry | Until you close the tab |
| Browser storage | App | Remembers your selected organisation and sign-in steps | Until cleared |
We do not use advertising cookies. If you open the booking widget, Calendly may set its own cookies. You can block or delete cookies in your browser, but the app cannot keep you signed in without them.
12. How long we keep data
| Data | How long we keep it |
|---|---|
| Accounting and tax records, source documents, matches and audit trail | During our engagement and for at least seven years after the end of the tax period they relate to. Some records must be kept longer, such as real estate records or those linked to an open refund claim |
| Files that are not accounting documents | We keep no original. The reference, summary and extracted text stay with the organisation’s records until deleted |
| Messages and voice notes | With the organisation’s records, for the same period as the accounting records they support |
| Bank logins and access tokens | Until you disconnect the source or access is revoked, when we remove them |
| Accounts, sessions and authorisation records | While the account is active, and afterwards for as long as needed for security and audit purposes |
| Website enquiries | Until you ask us to remove them or we no longer expect to work together |
| Diagnostic logs | For a limited period set with our logging provider |
| Backups | Deleted data may remain in backups until they are overwritten |
When we no longer need data, we delete or anonymise it. Our team currently carries this out on request and at the end of an engagement, rather than on an automatic schedule. We may keep data for longer if the law requires it or for an active dispute.
13. Your rights
Subject to the law that applies, you can ask us to:
- tell you what personal data we hold, why, and who receives it;
- give you a copy, including in a form you can pass to another provider;
- correct inaccurate or incomplete data;
- delete your data;
- restrict or stop processing, including for marketing; and
- have a person review a decision made by automated means alone.
You can also withdraw consent at any time, and you can complain to the UAE Data Office or another competent authority.
To use these rights, email privacy@getcounted.ai. We may need to verify your identity. We aim to reply within 30 days. If your data is part of a client’s records, we may need that client’s authorisation or may pass your request to them. We may also have to refuse part of a request, for example where tax law requires us or the client to keep a record.
If you are somewhere with other data protection laws, such as the EU, the UK or Saudi Arabia, you may have further rights where those laws apply to us.
14. Deleting your data and revoking access
Ask us to delete your data
- Email privacy@getcounted.ai from the address linked to your account. If we know you through WhatsApp, include your phone number.
- Tell us what you would like deleted. We may ask you to confirm your identity.
- We aim to reply within 30 days, confirming what we deleted, what we must keep and why.
This process is open to anyone whose data we hold, including people we know only through WhatsApp. An authorised person at a client can also ask us to delete the organisation’s data when our engagement ends.
Revoke our access
- In Counted: disconnect the source on the Integrations page, or ask us to.
- Google: remove Counted at myaccount.google.com/permissions.
- Microsoft: remove Counted at account.live.com/consent/manage or ask your Microsoft 365 administrator.
- Your bank: disconnect the bank in Counted and change your online banking password.
Revoking access stops new data coming in, but does not delete what we already hold. To delete it, follow the steps above as well.
15. Marketing messages
We may follow up on your enquiry and send you information about Counted. To stop, reply to the message or email privacy@getcounted.ai. We do not send marketing on WhatsApp unless you have agreed to it. To stop WhatsApp messages from Counted, tell us in the chat and we will record your choice. Service messages may still reach you by another channel while your organisation uses Counted.
16. Children
Counted is a service for businesses and is not directed at anyone under 18. We do not knowingly collect children’s data directly from them. A child’s details could appear in a client’s records, for example on a school invoice. Contact us if you have a concern.
17. Changes to this policy
We may update this policy and will change the date at the top when we do. If a change is material, we will tell clients by email or in the app before it takes effect. We will ask for your consent first where the law or a provider’s rules require it.
18. Contact us
Counted L.L.C-FZ
Meydan Grandstand, 6th Floor, Meydan Road, Nad Al Sheba, Dubai, UAE
Privacy: privacy@getcounted.ai
Website: getcounted.ai
Our Terms of Service apply to your use of Counted.