Docs
BlogHomeStart building

Data Storage & Security

Where your data lives, how it is protected, and what you own.

This page describes how Totalum works today. It matches our Privacy Policy, Data Processing Addendum and Sub-processor list; where they differ, the legal documents govern.

#Where your data lives

  • Your apps run on Cloudflare's global network. Every project is a Next.js app on Cloudflare Workers, served from the location nearest each visitor, with TLS, DDoS protection and caching included.
  • Each project has its own databases. A SQL database for development and another for production, never shared with any other project. By default a database is placed near the app's users, with read copies in other regions so pages load fast everywhere.
  • EU-only data, when you need it. Once a project is created with EU data residency, all of its database and all of its files stay inside the European Union: they are never stored or processed outside the EU (details below). Set it per project or as your account default (how). It is fixed when the project is created.
  • Files, backups and logs are kept in Totalum's object storage for the project — in the EU-only storage for an EU project.
  • The AI agent works in an isolated build environment that exists only for your project and sleeps when the agent is not working. Your app's data stays in the project's own databases.
  • AI processing of prompts, code and the apps' own AI features is done by AI model providers. They do not use your data to train their models under our commercial terms.

#What EU data residency covers

For a project created with EU data residency, all of the project's database and files stay inside the European Union and are never stored or processed outside it (Cloudflare's EU jurisdiction). That includes:

  • the project's databases (development and production), their restore points, read copies, restores, backups and exports;
  • the files your app stores, their 30-day deleted-file copies and their nightly second copy;
  • the agent's code versions, source archives and the project's download bundle;
  • the app's request and console log archive, the agent's run records and the mobile build files.

Separate from the project's database and files: AI requests, e-mail delivery, payments, running mobile builds, the agent's build environment, other integrations you use, the project's control data (chat history, run state, keys and settings, real-time messages, vector-search index) and short-lived request logs and traffic metrics. Your app's code is served from Cloudflare's global network.

Transfers outside the EEA are covered by Standard Contractual Clauses or the EU-US Data Privacy Framework (Privacy Policy, DPA). The full list of providers and locations is on the Sub-processor page.

#Isolation

  • One database per project and environment. Your app's data is never in a shared table.
  • Development and production are separate. The agent and the preview use the development database; the published site uses the live one. The agent never writes production data unless your prompt explicitly asks for it, and a publish that would delete live data asks for your confirmation first.
  • Every project is its own app. Its code runs in its own Worker with its own keys; one project cannot read another's data.
  • Scoped keys. Account keys (tlm_sk_) can be restricted to some projects; project keys (tlm_pk_) work on one project only, with only the scopes you give them. All keys are revocable at once.

#Encryption and access

  • In transit: HTTPS/TLS on every connection — browsers, the API, and between services.
  • At rest: databases, files and backups are encrypted at rest by our storage providers; secrets and third-party tokens are stored encrypted and are never returned by the API.
  • Sign-in protection: generated apps hash passwords, lock out repeated failed sign-ins and check sign-ups with Totalum's own privacy-friendly captcha (no third-party script, no cookie).
  • Team roles: the account owner decides who can work on each project; money, keys and production settings are the owner's.
  • Logging: access and agent activity are logged for security, abuse prevention and support. Secrets are redacted from logs.

#Backups and restore

  • Nightly backups of every production database on paid plans, kept 7 daily, 4 weekly and up to 12 monthly copies depending on the plan.
  • Point-in-time restore to any minute of the last 30 days, and restore points taken before every agent run and every restore — so an AI change can always be undone.
  • Manual backups whenever you want, downloadable as standard SQLite SQL.
  • Every code change is a version you can compare and restore.

Details and the API: Database Backups & Restore.

#Data ownership

  • Your code: a standard Next.js project — download it or sync it to GitHub at any time (paid plans; reading it is free on every plan) and run it anywhere.
  • Your data: standard SQL, exportable as a SQLite dump at any time.
  • Your files: downloadable, or copied to your own storage.
  • What still depends on Totalum: the built-in features (AI, e-mail, file storage, payments…) work through the open totalum-sdk package and Totalum's service; keep using them, or replace them to leave (Move to another host).
  • White-label: anyone with a paid plan may white-label and resell the Service.
  • After termination: export remains available for 30 days, as set out in the Terms of Service.
  • Deletion: deleting a project removes its sites, code, databases and files; its last backup is deleted 30 days later.

#Privacy commitments

  • We do not sell your data, and we do not use your prompts, code or project data to train AI models.
  • We do not track the visitors of your apps. Totalum adds no analytics script or tracking cookie to the sites you publish; visit counts are measured on the server without cookies. Free-plan sites show a small "Made with Totalum" badge, which tracks nothing.
  • Our own marketing site uses advertising tags subject to your cookie choices (Cookie Policy) — that concerns visitors of totalum.app, not the data in your projects.

#Certifications and availability

Published apps run on Cloudflare, whose infrastructure is certified ISO 27001 and SOC 2 Type II; those certifications are Cloudflare's. There is no uptime guarantee unless one is agreed in a signed Order Form (Terms). For provider certificates or a security questionnaire, contact contacto@totalum.app.

#Your responsibilities

The apps you build are yours: you decide what data they collect, show the privacy notice and cookie consent your users need, and keep your own third-party keys safe. The Acceptable Use Policy and the DPA set out who is responsible for what.

#Questions?

Questions about storage, security or compliance, or a vulnerability to report: contacto@totalum.app.

← Previous
Limits