Evidence. Decisions. Capital.
Privacy notice
This notice explains what personal data Athar collects on atharbio.ai and in the Athar workspace, why, where it is kept, and what you can ask us to do with it. Athar is a controlled alpha for institutional design partners; it is not a consumer service.
Last updated: 2026-10-20
Who is responsible
Athar Bio, of Riyadh, Saudi Arabia, operates atharbio.ai and the Athar workspace and decides how the personal data described here is used. To reach us about this notice or your data, email info@atharbio.ai, or use the access form on the home page and say that your message is a privacy request. We answer from the same team that reviews access requests.
What we collect, and why
We collect only what each step needs.
- Access form: your full name, organization, organization type and work email, and whether you are an existing partner. We use them to review your request, reply to you and, if we agree to work together, to set up your organization's access. The form is for business contact details; please do not put confidential research in it.
- Sign-in: approved users sign in with a Google account through Google Identity Platform. We receive the account's email address and display name and keep a server-side list of approved organizations and members. We set a signed session cookie (HttpOnly, Secure, SameSite=Lax) so you stay signed in, and we check it on every protected request.
- Workspace records: what your organization imports into its workspace (portfolio and asset records, documents and the questions you ask) is stored for that organization only. Before release acceptance, workspaces are for evaluation with non-confidential test data, such as published patents.
- Operational logs: request identifiers, timestamps, the route called and the outcome, and an audit record of workspace actions (who imported, approved or changed what, and when). Logs do not record your questions or documents.
- Emails we send: a receipt for an access request when enabled, sign-in and access emails, and replies from the team. We record whether a message was accepted by our email provider, not whether you opened it.
What we do not do
We do not sell personal data, we do not use advertising or tracking cookies on the public pages, and we do not profile visitors. The public pages set no cookie other than your language choice. We do not use your organization's records to train models.
Language models
Deterministic engines compute every number. When an organization's workspace has live AI enabled, a language model reads the relevant records to draft the words of an answer, and the answer is checked against those records before it is shown. The providers we may use for this are Anthropic (the Claude API) and Google Cloud (Vertex AI); records are sent to them only for that request and under terms that forbid training on them. Live AI is off unless it has been enabled for your organization.
Where data is kept, and who processes it
Athar runs on Google Cloud in the us-central1 region of the United States: Cloud Run for the website and the API, Cloud SQL (PostgreSQL) for workspace records, Secret Manager for credentials, and Google Identity Platform for sign-in. Public traffic to atharbio.ai passes through Cloudflare's network before it reaches Google Cloud. Transactional email is sent through Resend. Each provider processes data on our instructions under its own data-processing terms.
If you are in Saudi Arabia or elsewhere in the GCC, this means your personal data is transferred to and stored in the United States. Hosting in Saudi Arabia is planned and is not active. Institutional data residency is agreed in writing before real or confidential data is accepted; until then, workspaces hold non-confidential evaluation data only.
How long we keep it
Access requests are kept while we review them and while a design-partner conversation continues; ask us and we delete yours. Sign-in records last while your organization's access lasts. Workspace records belong to your organization and are kept until the organization asks for their removal or its access ends; the evidence a valuation relied on is kept with its audit record until then. Operational logs are kept for a limited period for security and troubleshooting. Backups follow the same rules with a delay.
Your rights
You can ask what personal data we hold about you, ask us to correct it, ask us to delete it, object to a use of it, or withdraw a consent you gave. If you are in Saudi Arabia, these rights are set out in the Personal Data Protection Law (PDPL) and its regulations; if you are in another jurisdiction, in its data-protection law. Contact us as described above; we confirm your identity through the email address we hold for you and reply within the period the applicable law allows. You may also complain to the competent data-protection authority.
Security
Access is restricted to approved organizations and checked on the server before a session is created. Protected pages are served with private, no-store caching and anti-framing headers, and all traffic uses HTTPS. Workspace records are separated per organization in the database. These are product controls, not a certification claim; the FAQ lists which controls are deployed and which are planned.
Changes to this notice
This notice is dated 2026-10-20. When the product changes in a way that affects personal data, we update this page and the date; for a material change we also tell approved organizations by email.
Still have a question?
Request access to speak with the team.
Request access