Draft: this text has not been reviewed yet and is not yet in force.

Security

How we protect wemovedata and the data you process with it.

Hosting

• Servers in data centres in the European Union, operated by Kwitaro from the Netherlands.
• Your apps run on their own domain (wemovedata.digital), apart from the portal, so customer code cannot reach portal sessions.

Isolation

• Every app runs in its own sandbox (gVisor), with limits on memory, CPU, time and network; apps cannot reach private networks.
• Tenants are separated in the database by row-level security.

Accounts and access

• Two-step sign-in (TOTP), required for sensitive actions.
• Personal access tokens and app keys with scopes, stored hashed.
• Session cookies limited to the portal's own host; protection against cross-site requests.

Data

• All traffic over TLS.
• Secret settings and data store credentials encrypted with a key kept apart from the database.
• Daily backups [encrypted, stored in the EU, restores tested: true once the off-site backups of the go-live plan are running].
• Logs are kept 7 or 30 days, depending on the plan.

Reporting a vulnerability

Found a weakness? Mail security@wemovedata.eu with the details and how to reproduce it. Please give us reasonable time to fix it before making it public, and do not access or change other customers' data. We answer within [3] working days. See also security.txt.