Privacy Policy

The controller for the processing of personal data on this website is:

When you create an account, we store your name, email address, language, currency, hashed password (if you sign up with email and password), and your verification status. If you sign in with GitHub or Google, we receive your name, email address, and a provider account identifier from the respective provider. We use this data to authenticate you, to associate your activity with your account, and to send you transactional emails such as verification or password reset messages.

Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).

We use strictly necessary cookies to keep you signed in and to protect your session. These cookies store a session token, your IP address, and your user agent for security purposes. We do not use advertising or third-party tracking cookies.

Legal basis: legitimate interest in operating a secure service (Art. 6 (1) (f) GDPR) and performance of a contract (Art. 6 (1) (b) GDPR).

Credit purchases are processed by Stripe Payments Europe, Ltd. (Stripe). When you make a payment, Stripe receives the data required to process the transaction (such as name, email address, billing address, and payment method details). We receive a Stripe customer ID, payment status, and the amount of the purchase, but we never see your full payment card details. Stripe acts as an independent controller for the payment data it processes.

The optional extension "ownAI Sync" is a subscription, and it runs through Stripe as well. Once you subscribe, we store the state of that subscription: status, currency, when the trial ends, the current billing period, and any cancellation date. Stripe holds the payment method and issues the invoices, we never see your card details.

You can also use ownAI without Stripe: contact us at support@ownai.com to request manual account activation and to top up your balance by invoice or advance bank transfer. In that case no data is transmitted to Stripe — we only process the contact and billing details required to issue an invoice and process the transfer.

Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).

More information: https://stripe.com/privacy

The cancellation form for subscriptions works without signing in, as the law requires. It asks for your name, your email address, optionally a customer number, whether you are cancelling ordinarily or for cause, optionally a reason, and the date you want the contract to end.

If the address belongs to an account, we store that declaration together with the time it reached us and the date the contract ends. We have to confirm both to you and to be able to show them later. The confirmation goes to the email address of the account. If the address belongs to no account, we store nothing and send no email.

Legal basis: performance of a contract (Art. 6 (1) (b) GDPR) and compliance with a legal obligation (Art. 6 (1) (c) GDPR).

If you use ownAI Credits, requests from the ownAI desktop app are routed through our LLM proxy (LiteLLM) to the AI provider you select. For each request, we store usage and cost data (such as model, token counts, and spend) to bill your credit balance and show you your usage. The content of your prompts and responses is forwarded to the selected AI provider, which processes it under its own privacy policy. If you bring your own API key or run a local model, your prompts and responses are not routed through our infrastructure.

Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).

Sync keeps one AI instance in step across every device you use it on, and it does that without us being able to read any of it. Everything is encrypted on your device before it leaves: what you talked about, what your AI remembers, the files it works with. The encryption uses a random key, and that key is itself locked with one derived from your sync passphrase — created on your device and never sent to us. What reaches our servers is ciphertext we store but cannot open. That is not a promise we could quietly walk back: we simply do not hold the key. There is nothing to hand over if someone asks us for it, and nothing to take if our servers are ever attacked. The other side of that belongs here too — if the passphrase is lost, we cannot get the data back either. There is no reset.

What is left unencrypted is only what we need in order to give the right data to the right device: how many instances, devices, records and files an account has, how large they are, and when each was last synced. File names and paths are not part of that — they sit inside the encrypted record, and every file is stored under a random name. Which part of your AI a record belongs to stays hidden as well: a chat message and a memory entry look the same to us.

One thing does stay readable, and we would rather spell it out than file it under "timestamps". Every record carries the time it last changed, unencrypted, because that is how two devices settle which version wins when both have edited the same thing. Collected over weeks, those times show when your devices were busy and how much changed at a time. They do not show what changed, or what kind of thing it was. It is a pattern of activity without content — but it is a pattern, and we can see it.

Every device that syncs is identified by the access key it was linked with, and carries the name shown in your device list — by default the app and the operating system it runs on, for example “ownAI App (Mac)”. Along with it we store when that device last synced and how far it has read the change stream. That is what lets a device that has been switched off for a while pick up in the right place, and what lets you see which devices are connected to your account and cut one off.

Deletions are kept for 90 days, so a device that has been switched off for a while still learns about them when it returns. If a subscription ends, syncing pauses and what sits on our servers is deleted after 30 days. None of that touches the copies on your own devices: they stay complete, and ownAI keeps working without a subscription.

Legal basis: performance of a contract (Art. 6 (1) (b) GDPR).

When you download the ownAI desktop application or when the application checks for updates, our servers process standard request data (such as your IP address, the requested file, and the time of the request) in log files. Release artefacts are hosted at Codeberg; following a download link may transmit your IP address to Codeberg.

Legal basis: legitimate interest in operating and securing the service (Art. 6 (1) (f) GDPR).

Our servers automatically record technical information about every request (such as IP address, timestamp, requested URL, HTTP status, and user agent). These logs are used to operate the service, to identify and resolve errors, and to detect abuse. They are stored for a limited period and then deleted or anonymized.

We use the following service providers to operate the platform:

• Hosting and operation of the platform infrastructure: Hetzner Online GmbH, Gunzenhausen, Germany
• Payment processing: Stripe Payments Europe, Ltd., Dublin, Ireland
• Hosting of release artifacts and source code: Codeberg e.V., Berlin, Germany
• Operators of large language models (LLMs): We offer you a choice between the following providers:
  • Scaleway SAS, Paris, France
  • Infomaniak Network AG, Geneva, Switzerland
  When using a local model, no data is forwarded to these providers.
• Delivery of transactional emails: Scaleway SAS, Paris, France

We keep account data for as long as your account exists. Credit transactions and invoices are retained for as long as required by applicable accounting and tax law. Server logs are deleted or anonymized after a short retention period.

Under the GDPR you have the right to access, rectify, erase, and restrict processing of your personal data, the right to data portability, and the right to object to processing. To exercise these rights, please contact us at info@ownai.com. You also have the right to lodge a complaint with a data protection supervisory authority.

We may update this Privacy Policy as the service evolves. The latest version is always available on this page.