Avey Platform Privacy Policy

Effective 16 November 2026

About this Privacy Policy

This Privacy Policy explains how Avey USA Corp., a Delaware corporation at 425 Page Mill Rd, Suite 200, 2nd Floor, Palo Alto, CA 94306, USA (“Avey”, “we”, “us”), handles data on the Avey Platform: the Avey APIs, the developer portal and the documentation (the “Platform”).

You sign in to the Platform with your Avey Account. The Avey Account Privacy Policy covers sign-in, your profile and billing details. This policy adds what happens on the Platform. If the two conflict on anything about the Platform, this policy prevails.

Your use of the Platform is also governed by the Avey Platform Terms of Service.

Questions and requests: privacy@avey.ai.

Our two roles

We handle two kinds of data, in two different roles.

DataWhat it includesOur role
Customer contentWhat customers send through the APIs (clinical inputs, prompts, files) and what the APIs returnProcessor. The customer is the controller and decides what to send and why. We process it only on the customer’s instructions.
Account, billing and usage dataYour Platform account, API keys, credit and payments, usage records, request history, logsController. We decide how this data is used, as this policy describes.

If you are a patient, or anyone else whose data a customer sent to us, that customer is responsible for your data. Please contact them first. We will help them answer your request.

Health information

Customers must not send protected health information through the Platform unless they have signed a Business Associate Agreement with us.

A Data Processing Agreement is available on request at privacy@avey.ai. If you need a Business Associate Agreement, contact us at the same address. Where either is signed, it sets out our duties for that customer’s content.

What we collect

Account, billing and usage data (we are the controller):

  • From your Avey Account: your name and email address.
  • Your Platform account: your projects, and the version of the Terms of Service and Privacy Policy you accepted and when.
  • API key details: key name, creation date and a partial identifier. We store keys in a form we cannot read back.
  • Credit and payments: your balance, top-ups, spending, and any credit we give you. Stripe handles card payments, and we never store full card numbers.
  • Usage records: for each request, the time, model, status, latency, size and cost, linked to your API key and project. This is also the request history you see in the portal.
  • Logs and traces from our API gateway and services. They carry user ids and may include request query strings and IP addresses.

Customer content (we are the processor):

Customers send content to Olive, Avey’s large language model. It can include prompts, clinical notes and other free text, and, where offered, files.

Olive returns generated text.

Customers choose what content to send. We do not ask for it outside the API calls they make.

How we use data

Customer content is used only to produce the output the customer asked for, and to run, secure and fix the service.

We do not use customer content to train or improve our models.

Account, billing and usage data is used to:

  • run your Platform account and API keys, and check each request is authorised;
  • meter usage, charge credit, apply your spending cap and block requests when credit reaches zero;
  • show your request history and send service emails, for example when your credit runs low, when you top up, and when an API key is about to expire;
  • keep the Platform secure and prevent fraud and abuse;
  • give you support;
  • improve performance and reliability, using aggregated data that does not identify you;
  • meet our legal, tax and accounting duties.

We do not sell personal data, and we do not use it for advertising.

Where data protection law applies, we rely on these legal bases for account, billing and usage data:

Legal basisWhat we use it for
ContractRunning your account, processing your requests, billing
Legitimate interestsSecurity, fraud prevention, and service improvement with aggregated data
Legal obligationTax, accounting and lawful requests from authorities
ConsentProduct analytics on the portal, if you agree to analytics cookies (see Cookies and analytics). You can withdraw consent at any time.

For customer content, the customer is the controller and must have its own legal basis, including any condition the law sets for health data and any consent from patients.

Where a Business Associate Agreement is signed, we use and disclose protected health information only as that agreement and HIPAA allow.

Where data is stored

The Platform runs on Amazon Web Services (AWS) in Frankfurt, Germany (EU). Olive, the model that answers API requests, runs on dedicated servers hosted by Ooredoo in Qatar, so the content you send is processed there to produce the reply.

API requests enter through our API gateway, which runs Kong Gateway software on our own servers on AWS in Frankfurt.

The Platform has its own managed database on AWS in Frankfurt. It is encrypted at rest, replicated across two data centres in the region, and backed up, with backups kept for 14 days.

Files are encrypted at rest and private, never public. All traffic to and from the Platform is encrypted in transit.

Who receives data

We share data only with providers that help us run the Platform, and only for the purposes below.

ProviderPurposeWhat it receivesWhere
Amazon Web ServicesHosting, API gateway servers, database, file storageAll Platform data, including customer contentFrankfurt, Germany (EU)
Kong Inc. (Kong Konnect)Usage metering and billingUsage events linked to your account, API key and project, with no request content; your name and email address for billingEU
StripePaymentsPayment detailsMay process outside the EU
OpenObserveLogs and tracesLogs and traces from our API gateway and services, with user ids; may include request query strings and IP addresses. Product analytics, if you agree (see Cookies and analytics)EU (cloud service)
Other Avey group companiesStaff who run and support the PlatformPlatform data they need for that workMainly Qatar
ResendEmail deliveryYour email address and the emails we send youMay process outside the EU
OoredooDedicated servers that run OliveCustomer content, while a reply is produced; it is not stored thereQatar
GoogleFeedback formWhat you write in the feedback formMay process outside the EU

Logs and traces are not meant to hold customer content, though an error report can occasionally contain part of a request.

We may also disclose data when the law, a court or a lawful request from an authority requires it; to enforce our Terms of Service; to detect and stop fraud or security problems; or to protect the rights and safety of Avey, our customers or the public.

If Avey is part of a merger, acquisition or sale of assets, data may transfer as part of it. We will tell you before your data becomes subject to a different privacy policy.

International transfers

Avey USA Corp. is based in the United States. Platform data is stored in the European Union (Frankfurt, Germany). Olive runs in Qatar, so customer content is processed there to produce replies. Our staff work for Avey group companies, mainly in Qatar, and access data from outside the EU. We are putting the EU Standard Contractual Clauses in place for this access. Some providers, such as Stripe and Resend, may process data in other countries.

For transfers to Stripe and Resend, we use the EU-US Data Privacy Framework or the EU Standard Contractual Clauses. For a copy, email privacy@avey.ai.

How long we keep data

DataHow long we keep it
Customer content in requests and repliesNot kept after the reply is returned, except as listed below
Analytics events, if you agreed to analytics cookiesUp to 90 days
Olive files and saved responses, if offeredKept until you delete them. There is no automatic expiry.
Logs and tracesup to 90 days
Raw usage eventsKept as your request history and billing record (see When you delete your account)
API keys, projects and Platform account recordWhile your account is open, then deleted (see When you delete your account)
Credit, wallet and usage recordsSee When you delete your account
Database backups14 days
Records the law requires us to keep, such as tax recordsFor the period the law requires

When you delete your account

You delete your account through your Avey Account. The Avey Account Privacy Policy explains the 30 day grace period.

When the grace period ends, the Platform deletes your API keys, projects and Platform account record.

Your billing customer records with Kong and Stripe are deleted too. Usage and credit records are kept as billing records, under an internal id, without your name or email address.

What happens to unused credit is set out in the Terms of Service, Credit and payment.

Security

  • All traffic is encrypted in transit. The database and files are encrypted at rest.
  • API keys are stored in a form we cannot read back.
  • Every request must carry a valid API key.
  • Access to Platform data is limited to the people and services that need it.
  • If a personal data breach affects you, we will tell you, and the authorities where required, within the time the law sets.

Your rights

Depending on where you live, you may have the right to:

  • know what data we hold about you, and get a copy;
  • correct it;
  • have it deleted, subject to records we must keep;
  • object to, or restrict, some processing;
  • receive it in a portable format;
  • withdraw consent where we rely on it;
  • complain to a data protection authority.

To use these rights, email privacy@avey.ai. We may need to confirm your identity first. We reply within the time the law sets.

For customer content, send your request to the customer that sent your data. As their processor, we will help them respond.

We do not make decisions about you based only on automated processing that have legal or similarly significant effects. Customers decide how they use outputs.

Children

The Platform is for people aged 18 and over. We do not knowingly collect personal data from children through the portal.

Customer content may include data about children, for example paediatric patients. We process it only as the customer’s processor, and the customer is responsible for having a legal basis and any consent needed.

Cookies and analytics

The portal uses the cookies needed for sign-in and sessions, and no advertising cookies. Sign-in cookies are described in the Avey Account Privacy Policy.

Product analytics run on the portal only if you agree to analytics cookies in Manage cookies, in your profile menu. Your choice applies across your Avey products and is saved with your account. If you agree, we measure how the portal is used, for example which pages are opened, how long visits last and which features are used, so we can improve it. We use OpenObserve, hosted in the EU, which sets an analytics cookie in your browser. These events carry your account id, never your name or email address. We record which page you opened, not its full web address, and which of our campaign links brought you there, if any. Analytics events are kept for up to 90 days. If you do not agree, no analytics run. Analytics cover the portal only, never what you send through the APIs.

Changes to this Privacy Policy

The date under the title is the effective date of this version.

If we make a material change, we publish a new version with a new effective date and tell you by email or in the portal at least 45 days before it takes effect, or sooner if the law requires.

Small corrections, such as typos, do not create a new version.

Contact

If we cannot resolve your concern, you can complain to the data protection authority where you live or work.

Looking for the Terms of Service? Go to Avey Platform Terms of Service

Need help?