Privacy Policy

Effective date: July 21, 2026 · Version 1.3

1. Who we are

Azrivo ("Azrivo", "we", "us") is a service operated by Azrivo LLC, a limited liability company registered in Georgia. Azrivo lets you consult a team of AI specialists, convene them as a panel, set them debating, and turn the result into a plan.

This Privacy Policy explains what personal data we process, why, who we share it with, and the rights you have. We act as the controller of the personal data described here.

Company details (data controller):

• Legal name: Azrivo LLC
• Registration / tax identification number: 405868324 (Georgian National Agency of Public Registry)
• Registered address: Kandelaki str. 6, Tbilisi 0160, Georgia
• Contact: privacy@azrivo.com (data-protection matters) · hello@azrivo.com (general)

If you have any question about this policy or your data, contact us at privacy@azrivo.com.

2. The data we process

You give us, or we create as you use Azrivo:

• Account data — when you sign in with Google, we receive your name, email address, and basic profile information from your Google account; we do not receive your Google password. When you register with an email address and password, we store your name, email address, and a one-way hash of your password (never the password itself), and we send a confirmation link to verify the address. We also keep a record that you accepted our terms (which document versions, and when), and — where applicable — of any invitation.
• Trial use without an account — if you try Azrivo from our home page without signing up, we do not ask for or receive your name, email address, or any other identifier. We create a provisional record with no identity attached to it, keep it linked to your browser through our session cookie (§8), and store what you do in that trial: the messages you send, the responses generated for you, and the chats, debates, and plans you create. These messages and responses are sent to the same categories of providers listed in §4 as an account holder's are. We also record that the notice below the prompt box was shown to you (which document versions, and when), and your browser's user-agent string with it, as our record that you accepted our terms. That record does not include your IP address. We do use the address your request comes from to limit how many trials can be started from one place at once — held in the server's memory for about fifteen minutes and never written to our database — and, like any website, our web server keeps short-lived access logs. A trial does not use memory and cannot attach files. If you later create an account, that provisional record becomes your account and everything in the trial carries over to it.
• Access requests — if you ask for access on our homepage (where that option is shown), we store the email address you give us and, if you include one, your note about what you'd use Azrivo for, so we can follow up. We use this only to respond to your request.
• Conversations and content — the messages you send; the responses generated for you; files and images you attach; images and documents generated at your request; and the chats, projects, and plans you create.
• Memory — facts you ask the assistant to remember, or that it saves to serve you better across sessions. You can view and remove these at any time on your Memory page.
• Public shares — if you choose to make a finished debate public (the Share action, off by default), we store a public copy of that debate's shareable content — its question, the specialists' arguments, the verdict, and cited sources — together with a record that it is shared and your search-engine choice. Your follow-up messages and uploaded files are not included. You can un-share it at any time.
• Programmatic access — if you create an access key to use Azrivo from a developer tool, we store a one-way hash of that key (never the key itself) and a short non-secret prefix to help you identify it.
• Messaging connections — if you connect a messaging app to use Azrivo from your phone, we store the link between your Azrivo account and your messaging identity (your messaging user id and display handle) so we can route your messages to the right account. You can disconnect it at any time.

We collect automatically:

• Usage and operational data — technical and session information needed to run the service, keep it secure, and measure cost (for example, request timing, model-usage counts, and error logs).
• Share-page activity — for a debate you have made public, we keep simple, non-identifying counts of how its page and downloads are used (how many views and downloads, whether a request looks like a person or a crawler, and the domain of the site a visit came from), so you and we can see how a shared debate is doing. We do not store visitors' IP addresses, set any cookie on the public page, or otherwise identify individual visitors.
• Cookies — a single essential cookie that keeps you signed in, or keeps a trial you started attached to your browser. We do not use advertising or third-party tracking cookies. See §8.

We do not ask for or intentionally collect special-category data (such as health, religion, or political views). Please avoid putting such information into your prompts unless necessary, and never put others' personal data into Azrivo without a lawful basis to do so.

3. How and why we use your data

Content review. To run Azrivo reliably, keep it secure, prevent fraud and abuse, and improve quality, we — and, over time, automated systems — may review conversation content. This applies to conversations started in a trial, without an account, in the same way it applies to account conversations — the notice below the prompt box links here, on screen, before you send your first message, so the position is stated up front rather than assumed. A trial is private from other users, not from us. Where we use your content to improve the service through model training or tuning, we rely on the choices you give us (for example, the per-reply "share this prompt and response" box), not on this general review — and those choices are not offered during a trial, so nothing from a trial is used that way. You can ask us about how your content is used at privacy@azrivo.com.

4. Who we share it with

To run Azrivo we rely on a small number of service providers (processors) acting on our instructions. We share only the data needed for each function, and we disclose them here by category of recipient:

• Authentication provider — Google, to let you sign in with your Google account.
• Analytics provider — Google (Google Analytics), only if you consent to analytics cookies, to count visits and page views. Page addresses are trimmed before they are sent, and your conversations, prompts, files, name, and email address are not sent to it. Advertising features are disabled. See our Cookie Policy for the detail and for how to turn this off.
• Email delivery provider — to send you account emails such as your invitation and password-reset links.
• AI and inference providers — to generate responses, embeddings, and generated media from your prompts and attachments.
• Cloud hosting and storage providers — EU-based infrastructure that hosts the application, database, and your stored files and images.
• Search providers — when a specialist performs a web search on your behalf, your search query (not your account identity) is sent to a search provider.
• Messaging channel providers — if you connect a messaging app to chat with Azrivo from your phone, your messages and Azrivo's replies (including any generated images or documents) pass through that messaging provider to reach your device, as any message on that app would.

We do not sell your personal data, and we do not use it for third-party advertising. We may disclose data where required by law, to protect our rights, or in connection with a corporate transaction (with notice where required).

5. International transfers

We are registered in Georgia, and some of our service providers may process data outside the European Economic Area. Where personal data of EU/EEA users is transferred outside the EEA, we rely on appropriate safeguards (such as the European Commission's Standard Contractual Clauses or an adequacy decision). You can ask us for more detail at privacy@azrivo.com.

6. How long we keep it

• Account data — your name, email address, and password hash are retained while your account is active; deleted when you close your account. Invitation records and proof-of-acceptance are kept as long as needed for that audit.
• Access requests — if you asked for access on our homepage, kept only so we can respond to your request; deleted on request at any time (privacy@azrivo.com).
• Conversations, projects, plans, attachments, and generated media — retained while your account is active, until you delete them or close your account.
• Trial use without an account — if you try Azrivo without an account, your trial conversations and the provisional record behind them are deleted automatically about 14 days after the trial starts, whether or not you ever came back to it: the conversation, any debate or plan in it, and the record that the notice was shown all go together. If you began creating an account but never confirmed your email address, that unconfirmed account and its trial content are deleted about 30 days after the trial starts — until then you can still finish signing up by requesting a new confirmation link. We say about rather than giving a guaranteed deadline because the deletion runs as a nightly job. Either way, the exception is that you finish creating an account — then it becomes your account data, and the account rules above apply instead.
• Public shares — a debate you make public is kept as a public page (with its non-identifying visit counts) until you un-share it, and is deleted when you delete that debate or close your account. Un-sharing stops us serving the page immediately; search engines and others may keep cached copies we cannot recall.
• Memory — retained until you remove it; removed items are deactivated and no longer used.
• Messaging connections — the link between your account and a connected messaging app is kept while the connection is active; removed when you disconnect it or close your account.
• Operational and cost logs — retained for a limited period for security, debugging, and accounting, then deleted or aggregated.

When you ask us to delete your account, we delete or irreversibly anonymise your personal data, cascading the deletion across our systems, except where we must retain something to meet a legal obligation.

7. Your rights

Subject to applicable law, you can:

• access the personal data we hold about you;
• correct inaccurate data;
• delete your data ("right to be forgotten");
• export your data in a portable form;
• object to or restrict certain processing;
• withdraw consent at any time, where processing is based on consent.

Many of these are available directly in the app (your Memory page, and deletion on request). To exercise any right, contact privacy@azrivo.com. You also have the right to lodge a complaint with a data-protection authority.

8. Cookies

Azrivo uses a single essential session cookie. It keeps you signed in after you log in and — if you are trying Azrivo without an account — it is what keeps that trial attached to your browser, so your conversation is still there when you return. It is required for the service to function and carries no advertising or cross-site-tracking purpose. We do not use advertising or third-party tracking cookies. A trial also keeps a few small items in your browser's own storage to make it work (that a trial is in progress, the message you typed before it started, and where to return you if you create an account); these stay in your browser and are described in the Cookie Policy.

We operate a consent banner so you can choose about optional cookie categories (analytics and marketing). Analytics is in use, and runs only if you turn it on; nothing at all is wired to marketing today. No optional cookie runs unless you opt in, and you can change or withdraw your choice at any time via the “Cookie settings” link in the footer. When we record your decision, we keep an audit record of it to demonstrate your consent. Full detail is in our dedicated Cookie Policy (linked in the footer).

9. Children

Azrivo is not directed to children. You must be at least 16 years old (or the minimum digital-consent age in your country) to use it. This applies to using Azrivo, not just to registering: the notice below the prompt box states the age requirement, on screen, before you can send a first message without an account, exactly as the registration form does. If we learn we have collected data from a child below that age without appropriate consent, we will delete it.

10. Changes to this policy

We may update this policy as Azrivo evolves. We will change the version and effective date above and, for material changes, give reasonable notice. A summary of changes is kept at the bottom of this document.

11. Contact

Questions or requests: privacy@azrivo.com.

Changelog

• 1.3 (effective 2026-07-21) — Trying Azrivo without an account: §2 adds what we process during a trial (prompts, responses, and a record that the notice was shown — no name, no email, no stored IP address); §3 adds the trial purposes and their legal bases, and states that content review applies to trial conversations too, while the "use my content to improve Azrivo" choice is not offered during one; §6 adds trial retention — deleted automatically about 14 days after it starts unless you create an account, and an account you began but never confirmed after about 30 days, with the confirmation link re-requestable until then; §8 describes the session cookie's second role and the browser storage a trial uses. Also corrected in §8: a line that still said the optional cookie categories were "not in use today", which stopped being true when analytics went live on 19 July 2026.
• 1.2 (effective 2026-07-19) — Website analytics, with your consent: §3 adds the measurement purpose on a consent basis; §4 adds the analytics provider (Google) as a recipient; §5 covers the US transfer. Full detail, including what we deliberately switched off, is in the Cookie Policy.
• 1.1 (effective 2026-07-19) — Public debate sharing: §2 adds public shares and their non-identifying visit counts; §3 adds the purpose of publishing a debate you share; §6 adds share retention and the un-share/cache caveat.
• 1.0 (effective 2026-07-07) — Initial published version.