Safa — Privacy Policy
Effective date: 22 October 2026
This policy explains how Safa handles personal information when you use the Safa web app at safa-ai.com, the Safa connectors in Claude, Slack, Microsoft Teams and Microsoft 365 Copilot, our website, or our waiting list, or when you contact us. It covers Safa's VAT service.
If you use Safa from Claude, Slack, Microsoft Teams or Microsoft 365 Copilot, the Safa Connectors Privacy Policy also applies. It adds what each connector receives, stores and sends back. Safa Ads has its own privacy policy.
1. Who is responsible for your information
Safa is a trading name of the holder of Dubai DET Licence No. 1156573, Dubai, United Arab Emirates. We are responsible for the personal information we process to provide Safa.
Contact us about privacy at hello@safa-ai.com.
We process personal information in line with UAE Federal Decree-Law No. 45 of 2021 on the Protection of Personal Data.
Your company decides what it uploads. Two kinds of information pass through Safa:
- Account information is about the people who use Safa: names, email addresses, sign-in records, team roles and billing contacts. We decide how it is used.
- Business data is what a company uploads and what Safa produces from it: invoices, ERP exports, TRN certificates, the details read from them and the results. The company decides what to upload and why, and we process it to provide Safa to that company, as our terms of service describe.
Invoices often name people who do not use Safa, such as a sole trader or a supplier's employee. If you are one of them, contact the company that uploaded the invoice. We will help that company answer your request.
2. Information we collect
Your account. Your name, email address and, if you give it, your company name. If you sign up for the web app, we also collect your TRN certificate, which we read to record your TRN, the registered name, trade name and registration date. Each person signs in with an authenticator app, so we store the secret that pairs your account with that app, and a hashed copy of each backup code. If you invite colleagues, we store their names, email addresses and roles.
Your invoices and your books. The invoices you send us (PDFs, images and ZIP files), the ERP exports you upload, the details Safa reads from them (such as supplier, TRN, amounts, VAT and dates), and the results Safa produces: the VAT treatment, tax code, account, verdicts and reasons. Invoices can contain information about other people, such as a supplier's contact details. Send only what is needed for the check, and do not upload passwords, identity documents or payment-card details.
Your companies and settings. The companies you add, with their name and TRN, and their VAT settings, such as how Safa should treat motor vehicles, entertainment and kitchen purchases, and your business sector.
Your connector accounts. When you connect Safa to Claude or Microsoft 365 Copilot, we store the sign-in tokens that let the app call Safa for you; refresh tokens are stored as hashes. When you connect Slack, we store your workspace and Slack user identifiers and the workspace's Safa app token, encrypted. When you connect Microsoft Teams, we store your tenant and user identifiers and the chat details Safa needs to reply. We also keep a record of each request you make through these apps. The Connectors Privacy Policy sets out the details.
Payments. Card payments are made on Stripe's checkout page. Safa never receives your full card number or security code. We keep your Stripe customer reference, your plan, its status, your invoice credits, your payment history and the billing details you enter: company name, billing email, phone number, tax number and address.
The waiting list. Your email address and, if you give it, your company name.
Security and technical records. When you sign up, sign in or join the waiting list, we record a keyed hash of your IP address for an hour to limit repeated attempts; we do not store the IP address itself for this. Our hosting provider keeps technical logs of requests to our service, such as the time, the address requested and the response, so we can run the service and fix problems. When it helps us diagnose a problem, these logs can also include your email address, the names of files you upload, TRNs and short extracts of what Safa read from a document. These logs are kept for 30 days.
When you contact us. Your emails or WhatsApp messages and our replies.
3. How we use it
We use your information to:
- create and secure your account, and let you sign in;
- read your invoices and give you the VAT treatment, tax code and account to book, and check them against your ERP export;
- run Safa in the apps you connect;
- take payments, manage your plan and count your invoices;
- send service emails, such as sign-up codes, team invitations, billing messages and the notices described in section 6;
- answer your questions and give support;
- tell you when Safa opens to you, if you joined the waiting list;
- keep the service secure and prevent misuse; and
- meet our legal obligations.
We do not sell your personal information. We do not use your invoices or results to advertise to you, and we do not send marketing emails.
About AI results. Safa uses AI to read documents and suggest the VAT treatment. AI can make mistakes. Safa flags uncertain results for review, and your team makes the final decisions. Safa does not use AI to make decisions about individuals that have legal effects on them.
4. Who we share it with
We share information only with the providers that run parts of Safa for us, and only what each one needs:
| Provider | What they do for Safa |
|---|---|
| Microsoft Azure | Hosts the Safa service in its data centres in the UAE, with your invoice files, ERP exports, TRN certificates and the details read from them, your companies' names and TRNs, and Safa's results. |
| MongoDB Atlas (MongoDB, Inc.) | Hosts account records in Ireland, in the European Union: your name, email address and sign-in details, your company memberships and roles, billing records, the links between your Slack or Teams account and Safa, and the waiting list. |
| Anthropic | Reads invoices and TRN certificates for Safa and helps produce the VAT treatment. See section 5. |
| Stripe | Processes payments and manages subscriptions. |
| SendGrid (Twilio) | Sends Safa's emails, such as the codes that confirm your email address. |
| Vercel | Hosts our website. Requests you make on safa-ai.com, including uploads, pass through Vercel on their way to Safa. |
| Slack, Microsoft and Anthropic (Claude) | Carry your messages and files between you and Safa when you choose to use Safa in those apps. Their own terms and privacy policies also apply to what you share in their apps. |
Members of your Safa team see your company's business data, according to their role. Authorised Safa staff access business data only when needed to support you, fix a problem, keep Safa secure or meet a legal duty.
We may also share information with professional advisers, or with authorities when the law requires it.
5. How AI reads your documents
Safa uses Anthropic's Claude models to read invoices and TRN certificates and to classify what is on them. For each document, Safa sends Anthropic the document and what Safa has read from it, and Anthropic returns the details and a suggested treatment. Safa uses no other AI provider.
Under Anthropic's commercial terms with Safa, invoice data sent for extraction is not used to train models. Anthropic keeps it for up to 30 days and then deletes it, unless the law requires it to keep it longer or the content is flagged for breaking Anthropic's usage policy. Anthropic processes it outside the UAE, mainly in the United States.
6. Where your information is stored
| Information | Where |
|---|---|
| Invoice files, ERP exports, TRN certificates and the details read from them, your companies' names and TRNs, and Safa's results | Microsoft Azure in the UAE: UAE North. Stored files are also copied to UAE Central. |
| Account records: your name, email address and sign-in details, company memberships and roles, billing records, and Slack and Teams links | MongoDB Atlas in Ireland, in the European Union. |
| Reading invoices and certificates | Anthropic, outside the UAE, mainly in the United States. |
| Payments, email and our website | Stripe, SendGrid and Vercel, which process information in other countries, including the United States. |
| Messages in Claude, Slack, Teams and Copilot | Anthropic, Slack and Microsoft, under their own terms. Microsoft's Bot Service, which carries Teams messages to Safa, runs worldwide and is not limited to the UAE. |
We use these providers under contracts that require them to protect the information. Contact us for details of the safeguards for a particular provider.
7. How long we keep it
| Information | How long |
|---|---|
| Invoices, files and results sent through Claude, Slack, Teams or Copilot | 90 days, then deleted. You can delete an analysis sooner from Recent analyses. |
| Records of connector requests | Up to 90 days. See the Connectors Privacy Policy. |
| Invoices, ERP exports and results in the web app, including the original invoice files you upload | While your account is open, unless you ask us to delete them sooner. |
| A company you remove | Removing a company deletes its records and its files straight away: its TRN certificate, invoice files, uploads and exports. |
| Excel exports | Safa builds the file when you ask for it and keeps no copy after sending it to you. |
| Your account | While your account is open. Ask us to close it and we delete it, apart from records we must keep by law. |
| Sign-ups that never finish the authenticator step | Deleted after 7 days, with the certificate and company they created. |
| Connector accounts that never paid | Deleted after six months without activity. We email you 14 days before. |
| Email codes for signing up | 10 minutes. |
| Waiting list | Until we invite you, or sooner if you ask us to remove you. |
| Hashed IP records that limit repeated attempts | 1 hour. |
| Payment records | As long as the law requires us to keep accounting records. |
When we delete an analysis, we keep only a count of how many invoices it used each month, so your plan's usage stays correct. That count contains no invoice details. Deleted information can remain in backups until they expire: 7 days for our storage and database in the UAE, and 8 days for the account database in Ireland.
8. Cookies
Safa uses only the cookies it needs to work. They are set by our service, cannot be read by scripts on the page, and are not used for advertising:
- session_token keeps you signed in, for up to 24 hours;
- company_token remembers which company you are working in, for up to 24 hours;
- pending_token holds a sign-in in progress, for up to 30 minutes; and
- slack_install_nonce protects the step where you add Safa to Slack, for up to 10 minutes.
The web app also stores small settings in your browser, such as the company you last selected and whether you have seen a tip. They stay on your device, and clearing your browser data removes them. We do not use analytics or advertising cookies, and we load no third-party trackers.
9. Your rights
You can ask us to:
- tell you what personal information we hold about you and give you a copy;
- correct information that is wrong;
- delete your information or close your account;
- stop or restrict how we use your information; or
- send your information to you in a portable format.
Some of this you can do yourself: export results to Excel, delete an analysis from Recent analyses, remove a company in Settings, and disconnect Slack or Teams. For anything else, email hello@safa-ai.com. We reply to support emails within 24 hours and answer privacy requests within 30 days. We may need to confirm your identity first, and we may keep information the law requires us to keep. Requests about business data that a company controls are handled with that company.
If you are not satisfied with our answer, you can complain to the UAE Data Office.
10. Security
Files and results are encrypted in transit and at rest. Every request is limited to one company. Each person signs in with an authenticator app, and sessions expire after 24 hours. Slack app tokens are stored encrypted, and Claude refresh tokens are stored as hashes. Staff access to production systems is limited to those who need it. No system is perfectly secure; if we learn of a breach that affects you, we will tell you as the law requires.
11. Children
Safa is a business service and is not meant for anyone under 18.
12. Changes to this policy
We will update this policy when our practices change and show the new effective date at the top. If a change is significant, we will tell you by email or in the app before it applies.
13. Contact
Email hello@safa-ai.com. Read our terms of service for the rules of using Safa.