Privacy Policy

Effective date: August 23, 2026 · Version 1.11

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 you would give us; the provisional record we create carries nothing that identifies you apart from the one-way network code described below. We keep that record 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 keep, with the trial's own provisional record, a one-way code derived from the network address the trial was started from — calculated once, when the trial starts. We do not store the address itself. The code is not the address, and it cannot be matched back to one without a secret key that never leaves our servers; we do not use it to identify you, and we do not use it to work out the address it came from — it is only ever compared with the codes on other trials. It lets us treat trials started from the same network within a short window (about a day; we may adjust it) as one free trial, so a trial's allowance cannot be renewed by clearing cookies or opening a private window. People who share a network — an office, a campus, a shared mobile connection — can therefore end up sharing one trial; where that happens we say so on screen, and you can create a free account instead. Only trial records carry this code, and we keep it only for as long as that window: a nightly job clears it once the trial is older than the window, it is removed straight away if the trial becomes your account, and it goes with the trial record itself in any case (§6). Separately, we use the address your request comes from to limit how many trials can be started from one place at once: that check holds the address in the server's memory for about fifteen minutes and then forgets it, and the address is not part of what we store about your trial. Like any website, our web server also 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. If instead you sign in to an account you already had, we move the trial's conversations onto that account so your work is not lost, and the provisional record is deleted on the schedule in §6.
• 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.
• Web-search results kept with a conversation — when a specialist searches the web while answering you (§4), we store, alongside that conversation, the list of web addresses the search returned. This includes results the specialist did not end up quoting or linking to. We keep it so we can show you which claims were actually checked against a source and which were not — a link that no search returned is marked unverified rather than presented as confirmed. It is a list of addresses only: we do not store the contents of those pages.
• 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.

• Email preferences and email history — your choices about which optional emails we may send you (each choice recorded with the date and the wording you were shown, so we can demonstrate what you agreed to), a record of the emails we have sent you, whether you are partway through one of our automated series (for example a short "getting started" series after you sign up) and which message is next, and — if an address permanently fails or is reported as spam — a one-way scrambled form of that address so we stop sending to it. You can see and change all of this at any time under Email in your settings. An automated series is scheduled purely by how long ago you signed up — we do not analyse your conversations or your activity to decide what to send you, and there is no automated decision-making with legal or similarly significant effects. We do not use tracking pixels in our emails: we do not know whether you opened a message or which links you clicked.

• Subscription and billing records — if you buy a paid plan, we store which plan you are on, the status and renewal date of your subscription, and the identifiers our payment provider uses for you and for that subscription. We read your payment history from them when you open the billing page, but we do not keep our own copy of it. We never receive or store your card number.

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 and to tell which of our adverts brought a visit. Page addresses are trimmed before they are sent; the only thing kept from the address is the click identifier Google adds to a link when you arrive from one of our adverts. Your conversations, prompts, files, name, and email address are not sent to it, and 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.
• Content-moderation provider — before an image is generated from a prompt, the prompt text is sent to a content-moderation service that screens it against a content policy; a prompt that fails screening is declined and no image is generated. Your account name and email address are not sent.
• Payment / merchant-of-record provider — if you buy a paid plan, our merchant of record sells the subscription to you and handles payment, invoicing, and any sales tax or VAT. They receive the billing details you give them at checkout (including your name, billing address, any VAT number, and your payment-method details) together with a pseudonymous identifier for your Azrivo account, and they return the subscription's status and your payment history to us. Your card details are entered on their checkout page and are never seen or stored by Azrivo. This is the same company as the content-moderation provider above, acting in a second, separate role.
• 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.
• Web-search results kept with a conversation (§2) — the list of web addresses a search returned is stored inside the conversation it belongs to, so it lives and dies with that conversation: deleting the conversation or closing your account deletes it too, and for a trial without an account it is reaped on the trial schedule below. We keep no separate copy of it anywhere else.
• 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 end up with an account — whether you finish creating one, or sign in to one you already had, in which case your trial conversations are moved onto that account. Then it becomes your account data, and the account rules above apply instead. The one-way network code described in §2 sits on that provisional record, and we keep it only for the window it is there to serve — about a day: the same nightly job clears it from trials older than that window, and clears it from every trial if we switch the network check off. It is removed sooner than that if the record becomes your account, because an account never carries one, and it is deleted with the provisional record in any case.
• 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.
• Email choices and email history — your recorded choices are kept while your account is active and deleted when you close it; because each choice is a dated record rather than a setting we overwrite, changing your mind adds a new entry rather than erasing the old one. The log of emails we sent you is kept for up to 24 months, then deleted. Your place in an automated series is kept while your account is active and deleted when you close it.
• Suppressed addresses — if an address permanently fails or reports us as spam, we keep a one-way scrambled form of it (not the address itself) indefinitely, including after an account is closed. This is the only email record that outlives an account, and it exists solely so that we can keep honouring the objection: we can check whether a given address is on the list, but the list cannot be read back to identify anyone.
• Operational and cost logs — retained for a limited period for security, debugging, and accounting, then deleted or aggregated.
• Subscription records — kept for as long as you hold a paid plan and then for as long as tax and accounting law requires us to keep records of the sale. Your payment history is held by the merchant of record, not by us, and is subject to their retention rules.

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; no marketing cookie or tracker is in use 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).

Two different “marketing” choices — they are not connected. The marketing category in the cookie banner is about cookies and trackers on this website, and nothing uses it. Whether we may email you product updates is a separate choice, made when you sign up or under Email in your settings, and covered in §2 and §3 above. Turning cookies off does not unsubscribe you from email, and unsubscribing from email does not change your cookie choices.

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.11 (effective 2026-08-23) — One free trial per network, not per browser. §2 adds that we keep a one-way code derived from the network address a trial was started from, with that trial's own record: we do not store the address itself, the code is not the address and cannot be matched back to one without a secret key that never leaves our servers, we do not use it to identify you, and it lets us treat trials started from the same network within about a day as one free trial — so the allowance cannot be renewed by clearing cookies or opening a private window, and people sharing an office or mobile network can share one trial. §3's abuse-prevention purpose names the mechanism (same legal basis); §6 adds that we keep the code only for that window (a nightly job clears it once the trial is older than the window), that it is removed sooner if the trial becomes your account, and that it is deleted with the trial record in any case. The fifteen-minute in-memory limit on how many trials can be started from one place is unchanged — only its wording — and nothing here is shared with anyone outside Azrivo.
• 1.10 (effective 2026-08-04) — Paid plans went on sale, so billing data now flows for the first time. §4 adds a payment / merchant-of-record provider recipient category (the same company as the content-moderation provider, in a second and separate role); §2 describes the subscription and billing records we hold — and states that we never receive or store your card number, which is entered on the provider's own checkout page; §6 states how long subscription records are kept and that your payment history is held by the merchant of record rather than by us.
• 1.9 (effective 2026-08-02) — Knowing which advert brought you: §3's measurement purpose now covers campaign attribution as well as visits and page views, and §4 says that the one part of a web address kept when it is trimmed is the click identifier Google adds when you arrive from one of our adverts. Same consent basis, same provider, no new recipient, and nothing extra kept by us. Advertising features stay switched off and no advertising cookie is set — the detail, and how to turn Analytics off, is in the Cookie Policy.
• 1.8 (effective 2026-08-01) — Web-search results kept with a conversation: §2 adds that when a specialist searches the web while answering you, we store alongside that conversation the list of web addresses the search returned — including results the specialist never quoted — so we can show you which claims were actually checked against a source and which were not; §6 adds that this list lives and dies with the conversation it belongs to. Addresses only; we do not store the contents of those pages.
• 1.7 (effective 2026-07-28) — Trial work now survives signing IN, not only signing up: §2 states that if you sign in to an account you already had, we move the trial's conversations onto it so your work is not lost; §6's trial exception widens from finish creating an account to end up with an account, either way. (Changelog entry added 2026-08-01 — 1.7 shipped without one.)
• 1.6 (effective 2026-07-26) — Automated welcome series: §2 adds that we keep your place in an automated email series, and states plainly that such a series is scheduled only by how long ago you signed up — we don't analyse your conversations or activity to decide what to send; §6 adds how long that's kept.
• 1.5 (effective 2026-07-26) — Email preferences: §2 adds what we keep about your email choices and the emails we've sent you; §3 sets out the legal basis for each kind of email, including that optional product updates are sent only with your consent; §6 adds how long we keep those records — and that a scrambled form of an address that permanently fails or reports us as spam is kept indefinitely so we stop sending to it; §8 clarifies that the marketing cookie category and your email choices are two separate things. We do not use tracking pixels in email.
• 1.4 (effective 2026-07-24) — Prompt screening for image generation: §4 adds a Content-moderation provider as a recipient — before an image is generated from your prompt, the prompt text is screened against a content policy, and your name and email are not sent to it.
• 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.