ObelismPrivacy policy

Privacy policy

Last updated 15 Nov 2026

Obelism builds Content, Improve, Numbers and Media, and runs the sites and dashboards at obelism.studio. This policy explains what personal data we collect, why, how long we keep it, and what you can ask us to do with it.

Two kinds of data, and two roles

  • Your account. When you sign up, use a dashboard, or write to us, we decide what is collected and why: we are the controller of that data.

  • Your visitors' data. When our products run on your site, you decide what they collect and we process it for you: you are the controller, we are the processor. We do that only on your instructions, under a data processing agreement, which we're glad to sign (ask us). Each product's docs set out exactly what it collects about a visitor: Content, Improve, Numbers and Media.

The rest of this page is about the first kind.

What we collect about you

  • Your account: your name and email address, a salted hash of your password (never the password itself), and the organizations you belong to with your role in each.

  • Signing in: passkeys and two-factor keys (encrypted), a hash of your recovery code, and for each signed-in session the browser's user agent and the city and country it was opened from, so you can see where you are signed in. No IP address is stored.

  • Billing: your plan and usage. Card details, VAT and invoices are Polar's, our merchant of record; they never reach our servers.

  • What you send us: waitlist applications, support email, and anything you type into a contact form.

  • Audit logs: who changed what in an organization, and how, kept for a year. They are how an admin answers "who paused that test?".

Cookies on our sites

  • The session cookie, when you are signed in. It is what keeps you signed in across our products, and it is essential.

  • Our products' visitor cookies, on obelism.studio itself: an opaque, randomly generated visitor id, first-party, used for the homepage's A/B test and the site's analytics. It contains no personal data and isn't used for advertising. Improve's Privacy & GDPR page describes it in full, including how to opt a site out.

We don't use third-party advertising or tracking cookies.

When we process data for you

Our products record, for your site's visitors, an opaque visitor id, which test or flag variant they saw, coarse device and browser categories, the country and region your host's edge reported, and the events you send. No IP address is stored. What each product keeps, and for how long, is in its docs (linked above); the DPA covers our obligations when we process it.

AI features

Some features use Cloudflare's Workers AI: Content's prompt editing and entry search, the dashboards' ⌘K prompt, the docs' question box, and Media's alt text and product suggestions. They send the content you are working on, and nothing else. No other model provider is called, and we don't use your content to train models.

Who we share it with

We use three sub-processors:

  • Cloudflare — hosting, file storage, caches, queues, rate limiting, outgoing email and AI.

  • PlanetScale — the PostgreSQL database.

  • Polar — payments as merchant of record: checkout, card details, VAT, invoices.

Some integrations are yours to connect, with your own account, so they aren't our sub-processors: Shopify, Vercel, and the OIDC issuers such as GitHub Actions and Vercel whose tokens we verify.

We don't sell personal data, and we don't share it for advertising.

Where it is processed

Requests are answered from the Cloudflare location nearest the visitor. The database is in Frankfurt, Germany (AWS eu-central-1), and the Workers that query it run there. Files are stored in Cloudflare R2 in Western Europe, which is not an EU-only jurisdiction, so we can't promise that files never leave the EEA. Where data does leave, our providers' transfer safeguards (standard contractual clauses) apply.

How long we keep it

  • Your account and organization: while they exist.

  • Sessions: 30 days after the last use.

  • Audit logs: one year. A deleted organization's are removed 30 days after it is deleted, while its products stop serving it at once.

  • Content's deleted entries: 30 days in the trash, then gone.

  • API tokens: until they expire or you revoke them.

  • Analytics and exposures: no automatic retention limit today. See Improve's page for what that means for a site you run with it.

  • Support email: while we need it to answer you.

Security

Passwords are salted PBKDF2-SHA-256 hashes, API tokens and session secrets are stored as hashes, and everything is served over HTTPS with HSTS. Sign-in, sign-up and the API are rate limited, access is scoped per organization, space, environment and role, and changes are recorded in an audit log. More, and what we don't have yet, is on our trust page: there is no security certification (SOC 2, ISO 27001) and no uptime SLA.

Your rights

You can ask us to show you your data, correct it, delete it, restrict what we do with it, or send it to you in a portable form, and you can object to processing based on our legitimate interest. Write to hello@obelism.studio and we answer within a month.

  • If we process your data for a customer (you are their site's visitor), ask that customer first: they decide, and we help them answer.

  • You can complain to a supervisory authority. Ours is the Dutch Data Protection Authority, the Autoriteit Persoonsgegevens.

  • Deleting your account is by request: we remove it once you are not the only admin of an organization that still exists. Your memberships, invites, sessions in every product, passkeys, two-factor key and connected apps go with it, and your name and email are replaced in our audit logs.

Changes

We update this page when what we do changes, and the date at the top says when. If a change is material, we email account holders about it.