Security

Where the data lives

The database and files are on our own server at UpCloud in Stockholm, Sweden. The server is reachable only through Cloudflare's network; its services are not exposed to the internet directly. Each device also keeps a local copy of the data its user may see, so the app works offline.

Encryption

• All traffic is encrypted with TLS.
• Share links are stored as hashes, so a copy of the database alone opens nothing.
• Tokens for connected services (Slack, other calendars) and share links are stored encrypted (AES-256-GCM).

Access

• Every change is a named command that the server checks against the person's role (owner, admin, editor, viewer or guest) before it is written.
• A device only receives the workspaces and projects its user may see.
• Sign-in uses email links or Google, so there are no thisflow passwords to leak. Settings → Account lists your signed-in devices and can sign out all the others.
• Personal API tokens act with your own access, are shown once, and can be revoked at once.

Backups and recovery

The database is backed up every night and the backups are kept for 14 days. Today the backups are on the same server; a copy in a second location in the EU is planned. How to restore is documented step by step.

How we build

Changes are made through pull requests with automated tests. We review the code for security problems and fix what we find.

Not yet

thisflow has no certification such as ISO 27001 or SOC 2, and no single sign-on (SAML) yet. If your organisation needs either, tell us at help@thisflow.com. The subprocessors page lists who else handles data for us.