How I handle your data.
The short version: your data sits encrypted in the EU, isolated from everyone else's, used for exactly the purposes we have agreed in writing, and not one more. Here is the full model, without legal fog.
Nothing is collected without a written, agreed purpose.
Every module has its purposes described in a purpose catalogue, which is part of the agreement. That is not just a principle on paper. It is enforced technically: a module can only be activated and collect data once the corresponding purpose has been approved in the system. Modules you have not bought sit locked in the dashboard, and no data is collected for them.
Data stays in the EU
One Postgres database hosted in Frankfurt (Supabase), with login, data and backups in the same EU system.
Encrypted end to end
TLS in transit, encryption at rest, and backups are encrypted as well.
Isolated per client
Row Level Security: it is the database itself, not the app code, that enforces that each client can only see their own rows.
Pseudonymised analytics
End-customer references in analytics data are pseudonyms, never a name or an email.
The security lives in the architecture.
Client isolation is enforced by the database itself through Row Level Security: a logged-in user can technically only reach rows belonging to their own business. Even a bug in the frontend cannot leak data across clients. Secret keys never live in the browser: the public key can do nothing without a valid login, and the keys that can do more exist only in the server environment as secrets. Connection credentials for your systems (webshop, accounting) are stored AES-256-GCM encrypted, never in plain text. And the analytics foundation is data-minimised: it holds sales, stock and product data plus pseudonymised customer references. Direct personal data exists only for the users who actually need to log in.
A data processing agreement is included, and you own all the data.
As the client you are the data controller, and algoritma is the data processor. We sign a data processing agreement under Article 28 of the GDPR with the mandatory elements: instructions, confidentiality, security, sub-processors, assistance, breaches, deletion and audits. The purpose catalogue is an appendix, documenting exactly which data is processed and why. The Danish Data Protection Agency is the supervisory authority. On termination your data is deleted or handed over, at your choice. Code, models and data are yours, afterwards too.
And the honest line at the end: algoritma does not advertise certifications I do not hold. In return, I will gladly answer any technical or legal question about the model above, including the hard ones.