Safa — Connectors Privacy Policy

Effective date: 22 October 2026

Safa Connectors let you get the UAE VAT treatment of your invoices without opening the Safa app. You send invoices to Safa from Claude, Slack, Microsoft Teams or Microsoft 365 Copilot, and Safa replies there.

This policy adds what is specific to the connectors. The Safa Privacy Policy still applies in full: who is responsible, how AI reads your documents, our providers, where information is stored and your rights.

Safa is a trading name of the holder of Dubai DET Licence No. 1156573, Dubai, United Arab Emirates. Privacy email: hello@safa-ai.com.

1. What every connector has in common

A Safa account. Each connector works through a Safa account with the Safa Connectors plan. To create one, you give your full name and email address, and optionally a company name. We email you a code to confirm the address, and you set up an authenticator app. You can later add companies, each with a name, an optional TRN and a business sector, and set each company's VAT settings.

Access is limited for now. Only invited accounts can use the connectors. If you join the waiting list, we keep your email address, the company name if you give one, and where you joined from. To limit abuse, we keep a scrambled form of your IP address for one hour. We never store the address itself.

Linking. Before Slack or Teams can send invoices to Safa, you link your chat identity to your Safa account once. Safa sends you a one-time link that expires after 30 minutes. You confirm with your Safa email and authenticator code, and approve what the chat identity may do.

Analysis. The invoices you send go through the same checks as in the Safa app, using your company's VAT settings. Safa stores the files, the fields it reads from them and the results as an analysis in your account. You can see them under Recent analyses in the Safa app.

Results in the chat. Safa sends each result back to the chat. That includes the file name, supplier, invoice number and date, amounts, supplier TRN, the expected VAT treatment, the reason and the recommended action. Once it is in the chat, the provider of that chat service holds it under your agreement with them, as described below.

Excel workbooks. Safa builds the workbook when you ask for it and keeps no copy after sending it. A download link works once and expires after five minutes.

Limits. Each message or upload can hold up to 20 files of up to 25 MB each, and up to 50 invoices. Safa accepts PDF, PNG, JPG and ZIP files.

Billing. Invoices you send through a connector count against your free invoices, plan or credits. We keep those counts with our billing records, even after you delete an analysis.

Accounts that never paid. If a connector account has never paid and has had no activity for six months, we delete it. We email you 14 days before.

2. Claude

You add Safa to Claude as a connector, then sign in to Safa and approve the connection. Claude receives a key that lasts 60 minutes and a renewal key that lasts 30 days. Safa stores only a scrambled form of the renewal key, so it cannot be read back.

What Safa receives. Safa does not see your conversation with Claude. It receives only the requests Claude makes to Safa's tools, such as which company to use, a name for the analysis, a change to a VAT setting or a new company's details. Files reach Safa only when you drop them into Safa's upload panel inside the chat. Files you attach to the chat itself do not reach Safa.

What Claude receives. Safa returns results, your companies and their VAT settings, and your recent analyses. Anthropic processes them as part of your Claude conversation, under your own Claude account terms and settings.

Disconnecting. Disconnect in the Safa app under Connectors, or remove the connector in Claude. Disconnecting in Safa cancels every renewal key at once; a key already issued stops working within 60 minutes.

3. Slack

A workspace admin installs Safa in a Slack workspace. Safa asks Slack for these permissions: read messages that mention Safa and direct messages sent to Safa, post messages, read and upload files shared with Safa, add reactions, run the /safa command and look up the sender's display name.

What Safa receives. Safa receives only direct messages to Safa and messages that mention @Safa. It never reads channel history or other conversations. It does not read email addresses from Slack. With each message, Safa receives Slack's IDs for the workspace, channel, message and sender, and the files attached. Safa reads the message text to find a company name and a name for the analysis. It keeps only those two and discards the rest of the text.

What Safa stores. For each workspace, the installation record and Safa's Slack access key, which is encrypted. For each linked person, their Slack ID, display name and workspace name. Each channel's default company. For each request, the IDs, file names, the company and analysis names, and its status.

What Slack receives. Safa posts its replies in the direct message, or in the thread of the message that mentioned Safa. In a channel, every member of that channel can see the results. Use a direct message for invoices the channel should not see. If you ask for the Excel workbook, Safa uploads it to the same thread. Answers to the /safa command are shown only to you.

Unlinking and uninstalling. Send unlink to Safa, or unlink in the Safa app under Connectors. This removes the link and your default companies. When an admin uninstalls Safa, we delete the workspace's installation, access key, links, pending choices and default companies. Analyses already made stay in your Safa account until they are deleted (section 6). Messages and files Safa posted stay in Slack under your workspace's retention settings. Safa does not delete them.

4. Microsoft Teams

Your organisation's Teams admin adds Safa to your organisation's app catalogue. Safa works only in a personal chat between you and Safa. It does not join channels or group chats. Safa does not ask for any Microsoft Graph permissions.

What Safa receives. Microsoft's Bot Framework delivers the messages you send in your chat with Safa. Each one carries your organisation's tenant ID, the chat ID, your Teams and Microsoft Entra IDs, your display name, the message text and its attachments. Safa does not receive your email address. Safa reads the text to find a company name, a name for the analysis or a command. It keeps only those and discards the rest of the text.

Files. Teams gives Safa a download link for each file you send. Safa downloads the file and then deletes the link from its records. Safa downloads files before you choose a company. If no company is chosen within 30 minutes, Safa deletes those files.

What Safa stores. For each chat, the technical details Safa needs to reply: your organisation's tenant ID, the chat ID, your Teams IDs and Microsoft's service address. For each linked person, their Teams IDs and display name. Your default company for the chat. For each request, the IDs, file names, the company and analysis names, and its status.

What Teams receives. Safa replies with cards in your personal chat. If you ask for the Excel workbook, Teams asks for your permission first. If you allow it, Safa saves the workbook to your OneDrive. If you decline, nothing is saved. Messages and files stay in Teams and OneDrive under your organisation's retention settings. Safa does not delete them.

Unlinking and removing the app. Send unlink to Safa, or unlink in the Safa app under Connectors. This removes the link and your default companies. When you or your admin removes the app, we delete the chat's technical details, your link, pending choices and default companies at once, and stop sending messages to the chat. If you block Safa instead, we stop sending messages and delete the chat's technical details within 90 days. Analyses already made stay in your Safa account until they are deleted (section 6).

5. Microsoft 365 Copilot

Safa is available in Copilot as an agent that your organisation adds. You sign in to Safa and approve the connection, as with Claude. Microsoft keeps the connection keys in its own secure store.

What Safa receives. Safa receives only the requests the agent makes to Safa's tools. It does not see your Copilot conversation. Files reach Safa only through Safa's upload panel, which Microsoft displays and which sends the files straight to Safa. Files attached to the chat itself do not reach Safa.

What Copilot receives. Safa returns the same results as for Claude. Microsoft processes them as part of your Copilot conversation, under your organisation's Microsoft 365 agreement.

Disconnecting. Remove the agent in Copilot, or ask your admin to remove it for your organisation. You can also email us and we cancel the connection. Cancelling it in Safa signs out every connected app, including Claude.

6. How long we keep connector data

Results Safa sent to a chat stay with that chat service under your own settings. Deleting an analysis in Safa does not delete them.

7. The chat services' own processing

Anthropic, Slack and Microsoft run their services under your agreements with them. They decide how they handle your conversations, including Safa's replies and any files Safa posts or saves for you. Their privacy notices apply to that processing:

• Anthropic: anthropic.com/legal/privacy
• Slack: slack.com/trust/privacy/privacy-policy
• Microsoft: privacy.microsoft.com

Microsoft's Bot Service, which carries Teams messages to Safa, is global and is not limited to the UAE. Safa's connector servers run in Microsoft Azure, UAE North, and the files and results of your analyses are stored on Microsoft Azure in the UAE. Anthropic reads the invoices for Safa outside the UAE, keeps them for up to 30 days and does not use them to train models, as described in the Safa Privacy Policy.

8. Questions and requests

Email hello@safa-ai.com for questions or to exercise your rights. We reply to support emails within 24 hours and answer privacy requests within 30 days. Your rights are set out in the Safa Privacy Policy. We date every update to this policy and tell account admins about material changes before they take effect.