> ## Documentation Index
> Fetch the complete documentation index at: https://docs.antarah.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Privacy Policy

> What Antara Industries collects, why, how long it keeps it, and your rights.

*Last updated: November 10, 2026*

Antara Industries ("Antara", "we") operates the Antara console, API, and documentation. This policy explains how we handle personal data. It follows the Saudi Personal Data Protection Law (PDPL). Questions or requests: [maan@antarah.dev](mailto:maan@antarah.dev).

## The short version

* **We don't store your prompts or the model's responses.** They're processed in memory to serve your request and then discarded, with the two short-lived exceptions below.
* We keep account, billing, and usage records (tokens, cost, timing) to run and bill the service.
* We don't sell personal data. The console uses no analytics or advertising cookies; this documentation site counts page views with an anonymous ID.

## What we collect and why

| Data | Examples | Why |
| - | - | - |
| Account | Name, email address, the identity of your Google, GitHub, or Microsoft sign-in, two-factor settings, onboarding progress | To create your account and sign you in |
| Organization | Organization and project names, members and roles, invitations (the invitee's email), spend limits and alert settings | To run shared workspaces |
| Policies and integrations | Policy names, descriptions, and rule text; decision-export destinations (URLs and bucket settings, with their secrets encrypted) | To run your policies and send decisions where you choose |
| API keys | A one-way hash of each key, its name, its last 4 characters, and when it was last used | To authenticate requests. The full key exists only in the response that creates it and in that request's encrypted 24-hour retry record (see [Your content](#your-content)) |
| Billing | Payment records, card brand and last 4 digits, plan and auto-reload settings | To take payments. Our payment processor receives your email, your organization's name, and your phone number if you give it. Card numbers go directly to the processor; we never see or store them |
| Usage | Per request: model, token counts, cost, latency, status, request ID, project, and key | Billing, rate limits, the usage pages in the console, and support |
| Policy decisions | Which policy ran, its result and action, and its latency | Your decision log and exports. Decisions contain no content |
| Audit log | Who changed what in your organization, and when | Security and accountability |
| Technical | IP addresses and request metadata | Rate limiting, abuse prevention, and keeping the service secure |
| Documentation visits | Pages viewed and searches, with an anonymous ID; questions you ask the documentation's AI assistant | To understand which docs help and to answer your questions |

## Your content

Prompts, files, images, and model outputs ("content") are sent to the model to produce your response and are **not stored** by Antara. Our logs and metrics never contain content. The only exceptions:

| Exception | Kept for |
| - | - |
| The response to a request you sent with an `Idempotency-Key` (including the response that shows a newly created API key), stored encrypted so a retry returns the same answer | About 24 hours |
| Images you upload in the console's Playground | About 24 hours |

To spot a reused `Idempotency-Key`, we keep a one-way fingerprint of the request, not its content, for 7 days.

To produce responses, content is processed by our model infrastructure provider, which we require not to retain content or use it for training. When you use [policies](https://docs.antarah.dev/guides/policies.md), content and your policy's rule text are also checked by a classifier model through the same provider. Nothing in your content is used to train models.

If we ever change how we handle content, we'll update this policy and tell you before the change takes effect.

## Who processes data for us

| Provider | Purpose | Location |
| - | - | - |
| Supabase | Sign-in, Playground image storage | Germany (Frankfurt) |
| Railway | API servers, databases, and logs (without content) | Netherlands (Amsterdam) |
| Vercel | Hosting the console's web pages | Global content delivery network |
| Resend | Sign-in codes, invitations, and account and billing emails | Ireland |
| Tap Payments | Card payments | Tap's own infrastructure |
| Grafana Cloud | Operational metrics, without content | European Union |
| Mintlify | Hosting this documentation, its page-view analytics, and its AI assistant | Mintlify's own infrastructure |
| Model infrastructure provider | Generating responses | Under a zero-retention agreement |

Some of these providers store or process data outside the Kingdom of Saudi Arabia. We use them under contracts that require them to protect it and to use it only to provide their service to us.

## How long we keep data

| Data | Kept for |
| - | - |
| Account and profile | Until you delete your account |
| Usage records | Per-request records: 13 months. Hourly totals per project, key, and model: as long as the organization's records are kept |
| Policies | With the organization. Past versions of a policy aren't deleted, because decisions refer to them |
| Policy decisions | 90 days |
| Audit log | 1 year. Entries keep the name of the person who acted and the email addresses of people invited, also after an account is deleted |
| Invitations | 30 days after they're accepted, expire, or are revoked |
| Email delivery records (the recipient's address) | 7 days after the email is sent |
| Payment and accounting records | As long as the law requires |

## Deleting your account

When you delete your account, we delete your profile and your sign-in identity, and you leave every organization you belong to. Organizations where you were the only member are closed: their keys are revoked, their integrations are deleted, any plan stops, and their remaining balance is forfeited. Their billing, usage, and audit records are kept for accounting and security.

We also keep a one-way hash of your email address, so the free signup credit can't be claimed twice, and audit entries that name you, until they expire. Our payment processor keeps its own records under its own policy.

## Cookies and browser storage

The console stores in your browser's local and session storage: your sign-in session, the sign-in step (including the email address you entered), a pending invitation while you accept it, and display preferences such as the theme, the sidebar, the last organization and project you used, and dismissed announcements. These are needed for the console to work. The console doesn't use analytics, advertising, or tracking cookies.

This documentation site, hosted by Mintlify, stores an anonymous visitor ID and a session ID in your browser to count page views and searches.

## Your rights

Under the PDPL you can ask us to:

* tell you what personal data we hold about you and how we use it;
* give you a copy of it;
* correct it;
* delete it, when we no longer need it for the purposes above or a legal obligation;
* stop processing based on your consent, by withdrawing it.

You can change your profile and delete your account in the console yourself. For anything else, email [maan@antarah.dev](mailto:maan@antarah.dev). If you're not satisfied with our answer, you can complain to the Saudi Data & AI Authority (SDAIA).

## Security

Data is encrypted in transit. API keys are stored as one-way hashes, and the short-lived retry records that hold a full key or a response are encrypted, as are integration secrets. Access to production systems is limited to the people who run the service.

## Children

Antara isn't for anyone under 18, and we don't knowingly collect their data.

## Changes

We'll post changes here and update the date above. If a change is significant, we'll tell you by email or in the console before it takes effect.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.