Privacy policy

Who is responsible

The controller of your data is Alexandre Joly, entrepreneur individuel (sole trader) trading as Kwern, SIREN 912 000 403. The address is on the legal notice. For anything on this page, write to hello@kwern.app. There is no data protection officer.

What you give us

Your account: the email address you sign in with. You need one to have an account; nothing else is required to sign up.

If you sign in with Google or GitHub, Kwern also receives the name, profile picture and account ID of that account and keeps them with your email address. It keeps the sign-in tokens too, encrypted, and uses them only to know it is you.

Your billing details, when you buy a plan or a top-up: the name, address and payment details you enter at checkout. Stripe holds the payment details; Kwern never sees a card number.

What you create

Your products: the URL you start from, the foundation doc and growth plan written from it, the instructions you give an agent, the chats, the files and images you add or generate, and what you approved, edited or rejected. This is the working memory of the product and it is scoped to it.

What we read for you

What Kwern reads on your behalf: the public pages of your site, the public App Store and Google Play listings, and, for every service you connect, the data that connection allows. It is kept as a dated snapshot per connector, refreshed on a fixed cadence, and deleted with the connection.

Keys and tokens

Credentials: the API key of your model provider and the tokens of the accounts you connect, stored encrypted and used only to run what you asked for. Kwern never sends them anywhere except to the provider they belong to.

What we record as it runs

Technical logs: the hosts record the requests made to the site and the API, with their IP address and time, to keep the service running and secure. The API also reports its own errors to PostHog; see Cookies for what that holds.

Why, and on what basis

• Running your account, your products and your agents, and emailing you the sign-in codes and account messages: to perform the contract you accepted in the terms.
• Taking payment and keeping invoices: to perform the contract, and because French accounting law requires the invoices to be kept.
• Keeping the service secure and diagnosing server errors: Kwern's legitimate interest in a service that works and is not abused.
• Measuring the audience and diagnosing errors in your browser: your consent, given in the cookie card and withdrawn there at any time.

Kwern does not train anything on your data and does not sell it. It shows no ads.

Who receives it

Each of these receives only what its part needs:

• Stripe: payments, invoices and your billing details.
• Railway: hosts the API.
• Neon: hosts the database.
• Cloudflare: serves the site and the app's pages, and stores your files and images.
• Resend: sends the emails.
• PostHog (PostHog Cloud EU): audience measurement and error diagnosis.
• Google Analytics (Google): audience measurement.
• The data vendors Kwern reads through on its own accounts: DataForSEO (search data), RapidAPI (X and Reddit reads), TypeSafe (reading AI answers) and Google PageSpeed. They receive the queries a run makes, such as a keyword, a URL or a handle, never your account. To rank the requests a new Chat offers, TypeSafe also reads your product's Foundation doc, Growth plan and setup (its surfaces, connectors and loops), never an account or a credential.
• Your model provider. Every run sends the instructions, the foundation doc and the data the run needs to the provider whose key you entered, on your account and under that provider's own terms.
• An AI app you connect to Kwern yourself through Kwern's MCP server, signed in as you: what it asks for, such as your product's docs and snapshots.
• GitHub: when you report a Chat answer or a proposal, it holds your report, your email address and the messages or run it is about, as an issue on Kwern's private repository.
• The services you connect, when you approve a write: X, LinkedIn, Apple Ads, Google Ads, App Store Connect, Google Play and your repository receive the post, the bid, the change or the pull request you approved, and nothing else.

Outside the European Union

Kwern's API and database run in the United States, and several of the recipients above are based there. These transfers rely on the EU–US Data Privacy Framework where the recipient is certified under it, and otherwise on the standard contractual clauses of the European Commission. PostHog stores Kwern's data in the European Union.

How long it is kept

• Your account, your products and what Kwern read for them: as long as the account exists. Removing a connection deletes its snapshots. Deleting a product deletes its foundation doc, its growth plan, its memory, its agents and their proposals. Deleting your account deletes all of it.
• Invoices and the billing records behind them: 10 years, as French accounting law requires, even after the account is deleted.
• Technical logs: up to 30 days.
• PostHog data: at most 25 months.
• Google Analytics data: at most 14 months.
• Your cookie choice: 180 days, after which you are asked again.

Cookies

Kwern sets a few cookies you cannot turn off: they keep you signed in and remember how you left the app's sidebar, and do nothing else.

Everything else is for one purpose, audience measurement and error diagnosis, through PostHog Cloud EU and Google Analytics, and waits for your choice. Until you accept, nothing is sent to either from your browser. If you accept, PostHog records the pages you visit, what you click and the errors your browser meets, tied to your account once you are signed in, and Google Analytics records the pages you visit, never tied to your account. Google Analytics sets its cookies _ga and _ga_<id> for 180 days, with Google signals and ad personalisation off. If you deny, nothing is sent, and Google Analytics stops from the next page you open. There is no session recording and no advertising tracker.

Your choice is kept in PostHog's consent cookie for 180 days. You can change it at any time from Cookies in the site's footer, or from Settings › General in the app.

The API reports its own errors to PostHog too. For a visitor who denied, it sends nothing. For one who accepted, the report names the account. For anyone else it names no one. A report holds the error, the page and the product it happened on, never what you wrote.

How we protect it

• Encrypted credentials. The tokens of the accounts you connect and the API key of your model provider are encrypted with AES-256-GCM before they are written to the database. The encryption key is kept on the API's host, apart from the database. The tokens of a Google or GitHub sign-in are encrypted too, with XChaCha20-Poly1305.
• Encrypted in transit. The site, the app and the API are served over HTTPS only; a plain HTTP request is redirected to HTTPS. The API reaches the database over TLS, which Neon requires for every connection, and reaches Google's APIs over HTTPS.
• Encrypted at rest. Neon encrypts the database with AES-256. Cloudflare encrypts the files and images it stores with AES-256.
• Scoped to you. A request that reads or changes your data must come from your signed-in account, and Kwern reads and writes only the products and connections that account owns.

Google user data

Google sign-in. When you sign in with Google, Kwern asks only for your basic profile: your name, email address, profile picture and Google account ID. It uses them to create your account and sign you in, and for nothing else. Removing Google from your sign-in methods in Settings › General deletes its tokens; deleting your account deletes the rest.

Connecting Google. When you connect Google, Kwern asks for read access to Search Console and Google Analytics, and for access to Google Ads. It reads your search queries, pages and positions, your traffic and conversions, and your campaigns, keywords, bids and spend. On Google Ads it changes only what you approve.

This data is used only for what you see in Kwern: the snapshots and charts of your product and the proposals its agents write. It is never used for advertising, never sold, and never used to train or improve any model. Nobody at Kwern reads it unless you ask us to, or unless security or the law requires it. It is protected as described in How we protect it.

Kwern shares, transfers or discloses Google user data only with:

• Your model provider, the one whose key you entered: only when a run for your product needs the data, at your request, on your account and under that provider's own terms.
• Railway, which runs the API that reads Google for you.
• Neon, which hosts the database that holds the tokens, the snapshots and the daily figures.
• Cloudflare, which runs the app's pages: the figures a page shows pass through it while the page is built. Kwern stores no Google user data on Cloudflare.
• Google, which receives the Google Ads changes you approve.
• TypeSafe, only as text a run already wrote: to rank the requests a new Chat offers, it reads your product's Foundation doc and Growth plan, and either can quote a figure Kwern read from Search Console, Google Analytics or Google Ads. It also reads which services are connected and when they last synced. It does not receive your Google account, your tokens or your snapshots.
• An AI app you connect to Kwern yourself, through Kwern's MCP server and signed in as you: it can read your product's snapshots when you ask it to.
• GitHub, when you report a Chat answer or a proposal: Kwern files your report as an issue on its own private repository, with your email address and the messages or run it is about, which can hold data read from Google. It is read there to fix the problem you reported.
• The services you approve a write for: a post, a change or a pull request you approve can draw on what Kwern read from Google, and goes to the service you approved it for.

Nobody else receives it.

Removing the Google connection in Settings › Accounts deletes its tokens, its snapshots and its daily figures. Disconnecting Google from one product deletes that product's snapshots and daily figures. What a run already wrote from it, such as a proposal or a chat, stays with the product until you delete the product. You can revoke Kwern's access at any time from your Google account permissions.

Kwern's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.

Your rights

You have the right to access your data, to have it corrected or erased, to restrict or object to its use, to receive it in a portable form, to withdraw your consent at any time, and to leave instructions for what happens to it after your death. Write to hello@kwern.app and ask.

You can also complain to the CNIL, the French data protection authority: cnil.fr, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France.

Changes

This policy can change; the date at the top says when it last did.