Privacy policy for Berkati
Last updated 4 November 2026
This policy covers Berkati, the invitation-only service that connects your Google accounts to your AI assistant (see what Berkati is). It is operated by Abdelbaki Berkati, personally. Contact: [email protected].
Google API Services User Data Policy
In practice, this means:
- Berkati uses Google user data only to provide the features you ask your assistant for.
- It does not transfer Google user data to anyone, except as needed to provide those features (to your assistant, at your request), to comply with the law, or as part of a merger or sale with your consent.
- It does not use Google user data for advertising, and does not sell it.
- No human reads your Google user data, except with your explicit permission, for security or to comply with the law.
- Google Workspace and Google user data is not used to develop, improve or train generalized AI or machine learning models. Berkati has no AI model of its own.
What data Berkati accesses
Sign-in. The first sign-in asks Google only for your email address and a stable account identifier. It gives no access to mail, files or calendar, and the Google tokens from this step are discarded.
Linked Google accounts. When you link a Google account, Google shows a consent screen listing the permissions requested. Berkati can then call Google APIs on your behalf for the services you allowed: Gmail, Drive, Calendar, Docs, Sheets, Tasks, Contacts, Search Console and Meet by default, plus any extra services you choose on the consent screen (for example Slides, Forms, Chat, Classroom, Gmail settings, Apps Script, Analytics). Full Google Admin access (users and groups management) cannot be linked.
The content of your Google data (emails, files, events, contacts and so on) is fetched only when your assistant asks for it.
How the data is used
Only to carry out the request your assistant makes: read, search, create or change something in the Google account you linked. Berkati does not analyse, profile, index or browse your Google data on its own.
What is stored
| What | Where and how | Why |
|---|---|---|
| Google OAuth tokens for each linked account (access token, refresh token, granted permissions, expiry) | Encrypted at rest (AES-256-GCM), with a separate key per workspace, file readable only by the service account | To call Google on your behalf without asking you to sign in every time |
| Your sign-in email address and Google account identifier | Encrypted registry | To recognise you and to keep one account in one workspace |
| Addresses of the Google accounts you linked, and which permission set each has | Configuration file on the server, not encrypted by Berkati, readable only by the service account | To know which account is which |
| Your write setting (read only, safe writes, full writes) | Encrypted | To apply your choice |
| Invitation record: your address, when the invite was used, and who issued it | Encrypted | To prove the invitation was used and by whom |
| Sessions between your assistant and Berkati | Encrypted store; 90 days at most, 30 days if unused, 10 per workspace | To keep your assistant connected |
| Audit log: tool name, allowed or refused, workspace identifier, time | Plain file on the server | To investigate misuse and failures. It contains no email addresses, no tokens and none of your Google data |
| Usage statistics: counts per tool, error types, latency ranges, assistant name and version | Plain daily files, no workspace identifier, kept 180 days | To see which features work. No email address, no content |
Berkati does not store the content of your Google data: no copy of your emails, files, calendar entries or contacts is written to disk by the service. Server logs record the tool name, the outcome and the duration of a call, never its arguments or results, and mask email addresses.
Security
- Tokens and the registry are encrypted at rest, and each workspace's tokens use their own derived key.
- The service runs without a login page of its own. Its web pages are static, load no scripts, fonts or trackers, and use only short-lived security cookies to bind a sign-in step to your browser. These cookies are not used for analytics.
- Actions that change data are, by default, flagged so your assistant asks you before running them. This approval happens in your assistant, not on the server, so it depends on the assistant honouring it.
- I run the server, so I technically hold the keys that decrypt the stored tokens. My admin tools can list workspaces and invitations (including email addresses), but they have no command that displays tokens or the content of your Google data.
Who data is shared with
- Google: Berkati sends API requests to Google on your behalf and receives the responses.
- Your AI assistant (Claude, provided by Anthropic): receives what the tools return, for example the text of an email you asked about. This transfer is made at your request. Anthropic handles the data under your own agreement with it, not under this policy.
- Hosting provider: the service runs on a virtual server at a cloud hosting provider, which processes data on my behalf as infrastructure.
Berkati does not share data with advertisers, data brokers or any other third party, and has no analytics or error-reporting service.
How long data is kept
- Google tokens: until you remove the account, I delete your workspace, or you re-link.
- Sessions: 90 days at most, 30 days if unused.
- Invitations: expire after 7 days, pruned 7 days later; the record of a used invitation stays as long as the workspace.
- Usage statistics: 180 days.
- Audit log: no fixed deletion date at present. It contains no email address and no Google data.
Deleting your data and revoking access
Revoke access at Google. At any time, go to myaccount.google.com/permissions, pick Berkati and remove access. The stored token then stops working, and your assistant will report that the account needs to be linked again. Berkati does not revoke the grant at Google for you.
Delete your data. There is no self-service delete button. Email [email protected] from the address you signed in with and I will delete your workspace. This removes your tokens, linked-account list, sessions, registry entry and invitation records. Audit log lines (workspace identifier, tool name, outcome, time; no email, no content) and the anonymous usage statistics remain. Please also revoke access at Google, as above, so that the grant itself is removed.
This website
This policy is hosted on berkati.xyz, my personal website, which uses Google Analytics to count visits. That is separate from the Berkati service, which loads no analytics.
Changes
If this policy changes, I will update the date above. If a change affects how Google user data is used, I will tell invited users before it takes effect.
Contact
Abdelbaki Berkati, [email protected].