ObelismTrust
How we look after your data.
Obelism is made in Amsterdam. This page says what the products do today, not what we plan. If your security review asks something it doesn’t answer, write to hello@obelism.studio.
Where it runs
- Cloudflare
- Every product runs on Cloudflare Workers. Files are stored in Cloudflare R2, caches in Workers KV, background work in Cloudflare Queues.
- One database in Frankfurt
- Accounts, content, tests and events are in one PostgreSQL database at PlanetScale, on AWS in Frankfurt (eu-central-1), reached through Cloudflare Hyperdrive.
- Served from the nearest location
- Cloudflare answers visitors from the data centre nearest to them, so cached copies of published content and files, and the session cache, live on Cloudflare’s network rather than in one region.
- Encrypted in transit
- Every product, API and file link is served over HTTPS; plain HTTP is redirected to it.
Who processes data for us
- Cloudflare
- Hosting, file storage, caches, queues, the emails we send (Cloudflare Email Service) and the AI models behind prompts, alt text and search (Workers AI).
- PlanetScale
- The PostgreSQL database.
- Polar
- Payments. Polar is the merchant of record: it takes the card details, charges VAT and sends the invoices. We never see a card number.
- No other AI providers
- The AI features run on open models on Cloudflare Workers AI. Nothing you write is sent to another AI company. Content can instead send its prompts to an endpoint you run yourself.
Signing in
- One account for every product
- Signing in happens on www.obelism.studio only; the products share that session.
- Passkeys and two-factor
- Every account can add passkeys and an authenticator app. With two-factor on, a password alone signs nobody in, and a password reset asks for the code too.
- Nothing stored that signs in
- Passwords are stored as salted, slow hashes, and sessions and API tokens only as a hash of their secret: a copy of the database holds nothing that signs in directly. Two-factor keys are encrypted.
- Sessions you can end
- A session expires after 30 days without use. Your account lists where you are signed in, and ending a session ends it in every product at once. Repeated wrong passwords or codes are refused for a while.
Who can do what
- Roles
- Every member is an admin, developer, editor or reader. Admins manage members and billing; an Organization always keeps at least one admin.
- Per space and per product
- A member can be limited to some spaces, with a role in each, and to some products: a client’s editor sees their own site, and only Content.
- An audit log in Content
- Content records who changed what in a space, when, and whether it was a person, an agent or an API token. Admins and developers can read it; entries are kept for a year.
API access
- Tokens that expire
- API tokens expire after 30 days, 90 days or a year (the default), or never if you choose so. Only a hash is stored, and admins are emailed 14 and 3 days before one expires.
- No token at all
- Vercel deployments and GitHub Actions can reach Content and Improve with their own short-lived OIDC token instead, checked against rules you set per space.
- Agents
- Agents connect over OAuth, act as the person who connected them with that person’s role, and can be disconnected from the account page at any time.
Your files
- Protected by default
- An original file uploaded to Media is only served to members, or through a link signed for minutes. What your site shows comes from public, resized image URLs, unless you mark a file private. Files uploaded before this protection started keep their earlier public links.
- Shares with a password
- A share link to a file or a folder needs a password and works only within the time window you set.
What Numbers keeps
- No IP addresses
- Numbers doesn’t store IP addresses. It keeps the country and region, the device type, screen size, browser and operating system, and a random visitor id.
- No query strings
- Page paths and referrers are stored without their query strings, so whatever a link carries after the ? is never kept.
- Without cookies if you want
- The visitor id can live in a cookie, only for the browser session, or nowhere at all.
Leaving
- Your content as SQL
- Content exports an environment’s model, entries, paths and redirects as plain SQL files that load into any PostgreSQL database. Files can be downloaded from Media.
- Deleting an Organization
- It stops serving at once. Thirty days later its content, its files and its analytics events are removed for good.
Not yet.
- Single sign-on (SAML or OIDC) and requiring two-factor for an Organization’s members.
- An audit log for Improve and for the Organization itself (members, roles, billing).
- Removing Improve’s tests and flags with a deleted Organization: today they stay, no longer served.
- Security certifications such as SOC 2 or ISO 27001, and a contractual uptime SLA.
Questions, or a security issue?
Write to hello@obelism.studio for a data processing agreement, a security questionnaire, or to report a vulnerability.