Privacy Policy

The short version

Your work is yours, and it is stored securely. We never sell personal data and we never share it for advertising. The only outside parties who touch it are the service providers named further down — the database, the hosting, the payment processor, the mail sender and the model providers — and only so that the product can run at all. There is no advertising cookie, no cross-site tracker and no third-party profiling anywhere in it.

We do not train any model on your content, and we do not use one customer's runs to improve anything another customer sees.

Every account's data sits in its own partition, and the separation is enforced by the database itself rather than only by the application asking nicely. Provider keys and other secrets stay on the server and never reach a browser.

Card details never reach our servers at all. Stripe collects them on its own pages.

Deleting is real. A run you delete goes to the Trash for 30 days so you can change your mind, and after that it is destroyed for good — the transcript, the run's history and the files you uploaded with it.

What we cannot promise on someone else's behalf: running a discussion means sending text to a model provider, and what that provider does with it is governed by its own terms, not by ours. That is the one part of this we do not control, and the section on model traffic below says exactly what leaves and what we keep. The rest of this page is the detail behind the five points above.

Who is responsible

[operator's full name and postal address] is the controller of the personal data described here. Reach us at hello@delibora.com.

We have not appointed a data protection officer, because the law does not require one for processing of this kind and scale. Every question about your data goes to the address above.

What we collect

Account data: your email address, your password in hashed form (or the fact that you sign in with Google instead), when you signed up and when you last signed in.

What you create: conversations, participant briefs, uploaded evidence files, transcripts, generated reports, and the settings behind them.

Billing data: your plan, your subscription status and the period it runs to. Card details are entered on Stripe's own pages and never reach us.

Operational data: request and worker logs, run events, error reports, and per-run model usage and cost. These carry account identifiers so a failure can be traced to the run it belongs to.

Site measurement: aggregate page and traffic measurement on the public site through Vercel Analytics. It sets no advertising cookie and builds no profile of you.

Public site request data: when you visit the home page, we record your IP address and the country Vercel infers from it, when available, in Vercel runtime logs. When you submit the waitlist form, we store those details with your submission in Neon. This is separate from the aggregate site measurement above.

Model traffic — read this one

Running a discussion means sending text to a model provider. What goes out is the prompt a run needs: the participants' briefs, the relevant part of the transcript and any evidence excerpts the run admits.

We record those exchanges so a run can be audited and a failure explained. Before anything is stored, a sanitizer removes HTTP headers, credentials and secret-shaped values, signed links, images and binary data, and the models' hidden reasoning. Ordinary prompt and response text is kept, and that includes private participant briefs and moderator instructions, because those are what the model was actually told.

This record stays inside your own account partition. It is not shown in ordinary exports, it is not used to train anything, and only Enterprise accounts can export it at all.

What we use it for

To run the service you asked for, to keep your account separate from everyone else's, to bill you, to send the few emails the service has to send, to find and fix failures, and to meet legal obligations.

We do not sell personal data, we do not share it for advertising, and we make no automated decision about you that has a legal effect.

Who else processes it

Supabase (Supabase Pte. Ltd., Singapore) — the database, sign-in and file storage behind the whole application. Your account, your runs and your uploads live here.

Railway (Railway Corporation, United States) — runs the background workers that carry out each run. Prompts, transcripts and evidence pass through them on the way to the database and to the model providers.

OpenRouter (OpenRouter, Inc., United States) — routes each model call on to the provider that serves the model chosen for that seat. Prompt and response text passes through it, and on to that provider in the country it operates in.

Stripe (Stripe Payments Europe, Limited, Ireland) — payments, subscriptions and the billing portal. Stripe is the only party that sees your card.

Resend (Plus Five Five, Inc., United States) — transactional and invitation email.

Vercel (Vercel Inc., United States) — hosting for the application and this site, plus the aggregate traffic measurement named above.

Neon (Databricks, Inc., United States) — the waitlist and interest forms on this public site, and nothing else. If you have an account, your account data is not here.

Google (Google Ireland Limited, Ireland) — only if you choose to sign in with Google, and then only to confirm who you are.

Ireland's data protection law is recognised as adequate by Switzerland and by the European Union. For the providers in the United States and in Singapore, the transfer rests on the European Commission's standard contractual clauses in the provider's data processing terms — read with the Swiss addendum where Swiss law applies — and, for a provider certified under it, on the Data Privacy Framework as well. When a provider is added or replaced, this list changes with it.

Where it is stored

The service runs on infrastructure operated by the parties above, which means data can be processed outside the country you live in, and in particular in the United States.

This page does not name data centres, because those can change without the protection changing. What does not change is the mechanism: a transfer to a country whose law is not recognised as adequate rests on the standard contractual clauses described in the section above, read with the Swiss addendum where Swiss law applies.

How long we keep it

A run you delete goes to the Trash and stays there for 30 days, then it is destroyed for good, including the uploaded files behind it. Until then you can restore it yourself.

An archived run is kept as long as your account is, because archiving is a shelf and not a deletion.

Account and billing records are kept while your account exists, and afterwards only as long as tax and accounting law requires.

Request and worker logs are deleted automatically after 30 days, and are not used for anything but operating and debugging the service.

When you delete your account, it is deleted at once and cannot be restored: your runs, workers, teams, uploaded files, settings, support tickets and API keys, your sign-in, and the logs that belong to your account. A running plan ends at that moment, without a refund for the rest of the period.

Two things are kept after that, and nothing else. Stripe keeps your invoices and payment records for the ten years Swiss accounting law requires (Art. 958f of the Code of Obligations). We keep a short record that an account was deleted and when, without your email address, so that we can show the deletion happened and finish it if it was interrupted.

Copies in the database's automatic backups are overwritten within 14 days. Emails we sent you remain in the sending logs of our mail provider for its own retention period.

Your rights

You can ask for a copy of your personal data, ask us to correct it, ask us to delete it, object to a particular use, or ask for a portable export. Write to us and we will answer within the period the law sets.

You can also complain to a data protection authority. In Switzerland that is the Federal Data Protection and Information Commissioner (FDPIC), at edoeb.admin.ch. If you live in the European Union, the European Economic Area or the United Kingdom, you can go to the authority of the country you live in instead.

You can delete your account yourself, at any time, under Account in the application. You will be asked to have signed in within the last few minutes and to type your email address, and we send a short confirmation once it is done. If you cannot sign in any more, write to us and we will delete it for you. What deleting removes and the little we have to keep is described in the section above.

Cookies

The application sets the cookies it needs to keep you signed in. There is no advertising cookie, no cross-site tracker and no third-party profiling on either the application or this site.