SpeclySpeclySpecly holds the data model: tables, columns, descriptions and the rules around them. Here is how we store it, protect it and give access to it.
Specly stores the description of your data, such as names, types, relations and documentation. The rows in your tables are never read in.
All data is stored and operated in the EEA and Switzerland, with primary storage in Norway. Backups and logs are kept in Sweden with a European cloud provider. Integrations you turn on yourselves go to your own services and regions.
The database and its backups are encrypted at rest with AES-256. All traffic from the browser to Specly and on to the database uses TLS 1.2 or newer.
Sign in with SSO through your identity provider, so MFA and password rules follow your policy. Four roles in each project control what each person can do: Admin, Developer, Contributor and Viewer. When someone leaves, an admin removes the user in Specly and their access stops within minutes.
Specly asks only for the permissions it needs. The secret can be rotated and revoked at any time, credentials are stored encrypted, and every import and export is recorded in the audit log.
When you import, the key is used only while the import runs and is not stored. Specly never writes to the data platform.
Changes and events in the organisation are recorded in an audit log that admins can read in Specly and download.
Specly uses no third-party analytics, tracking or AI services. AI agents only get access when a user connects them with their own sign-in.
You can export your models to your own Git repo at any time. When the agreement ends, the content is deleted. Backups and logs expire automatically within 30 days.
We keep the platform and its dependencies up to date and check them regularly for known vulnerabilities. Specly is built for ordinary personal data, not sensitive data.
We are happy to help fill in your security questionnaire, and share our data processing agreement on request.
Tell us how you work today, and we'll show you how Specly could fit in.