The same security on every plan
Every Norcube product is built with encryption and privacy as the default, not as a premium upgrade. The same protections apply to every user, from day one, at every scale.
What we will never do
These are engineering decisions built into the architecture, not policies that change with a new investor or quarterly target.
Never sell your data
Your data is yours. We don't monetize it, share it with anyone beyond the subprocessors that run the service, or use it for anything other than the service you signed up for.
Never profile you
No ad tracking, no profiling, no data brokers. In the dashboard we measure which features get used so we can improve the product. We never measure the content you store, and you can turn off the measurement too.
Never store credentials in plain text
Database passwords are encrypted with AES-256-GCM. API keys are hashed with HMAC-SHA256. This is the architecture, not a setting.
Security in practice
Credentials encrypted at rest
Sensitive credentials like database passwords are encrypted server-side using AES-256-GCM with AWS KMS for key management. They never exist in plain text in our storage.
API keys hashed, not encrypted
API keys are hashed with HMAC-SHA256 before storage, so we never hold the raw key. Each records its creation date and last use, and you can revoke it instantly.
Isolated backup execution
Every backup job runs on its own sandboxed server, created on demand. It decrypts credentials in memory, runs the backup and is destroyed. Jobs and customers share nothing.
Data stored in the EU
Your data is stored in AWS Frankfurt (eu-central-1). Status pages, CMS previews, SMS alerts and AI features use other providers, listed in the questions below.
Encrypted in transit
All API traffic goes through AWS Elastic Load Balancer with TLS encryption. Backup tasks connect to your database over TLS whenever your database offers it.
Encrypted at rest
Stored data is protected by AWS-managed server-side encryption. Client-side archive encryption for backups is on our roadmap as a high priority.
No request body logging
We don't log request bodies. Your credentials, translations, prompts and domain queries stay out of our service logs, which record routes, status codes and IDs.
CLI sessions you control
Every CLI sign-in is a session you can see and revoke under Account → CLI sessions. Refresh tokens rotate on every use, and a replayed token ends the whole session.
Least-privilege CI tokens
Automation uses organization CI tokens instead of personal sign-ins. Each carries only the scopes you grant, always expires and can be revoked at any time.
Monitor secrets encrypted per value
Monitor's secret headers, Slack and Discord URLs and webhook signing secrets are each encrypted with AES-256-GCM under their own data key from AWS KMS.
Access control
Members get per-product roles and resource-level policies, so you can give exactly what's needed. Two-factor authentication and SSO are on our roadmap, not built yet.
See the roadmapConnections to addresses you choose
Monitor's checks and alerts, DomainRadar's lookups and page fetches and Backup's alerts all pass one guard, which refuses private addresses after DNS resolution.
Audit logs
Backup, Monitor, Norcube Auth and LangSync keep audit entries for a year, then delete them. Backup and LangSync show theirs in the dashboard.
Monitor data retention
Raw check results for at least 30 days, hourly rollups for 90 days, daily rollups for 2 years, resolved incidents for a year. The questions below have the full list.
Rate limiting
Sign-in and public lookup endpoints are rate-limited to stop brute-force attempts and abuse. Monitor also limits costly actions per user and per organization.
Privacy & data protection
GDPR compliant
We process data lawfully, minimize what we collect, store it in the EU, and never sell it. Read the privacy policy.
Privacy policyCustomer DPA available
Our Data Processing Agreement is public and auto-applies to every customer. Signed copies available on request.
Read the DPATransparent subprocessors
Every third party that processes customer data is listed publicly, with what they see and where they are.
See the listAI Act transparency
We use AI as a deployer, via OpenAI's API. LangSync labels AI translations, and your content never trains AI models.
On the certifications roadmap
We don't hold SOC 2 or ISO 27001 yet. We're building the controls first, and we'll pursue audits when customers ask for them.
Trust CenterIf something goes wrong
Detection and containment
We monitor infrastructure for anomalies. If a security incident is detected, affected systems are isolated immediately to prevent further exposure.
Customer notification within 48 hours
If a breach affects your data, we notify your organization's owners within 48 hours of confirming it, so you can meet your own 72-hour GDPR deadline. The notification says what happened, what data was affected and what we are doing about it.
Transparent post-mortem
After resolution, affected users receive a post-mortem explaining the root cause, timeline, impact, and what we changed to prevent recurrence.
If Monitor itself fails
Monitor's checks run from one place. If our checker is down, checks and alerts stop and you won't get alerted. Published status pages keep showing the last known state and say live updates are delayed. Our own health is at status.norcube.com.
Our status pageReport a concern
Report a vulnerability or security concern to [email protected] with the subject "Security". We reply within 5 business days, and sooner for anything urgent. Scanners can find this at /.well-known/security.txt.
The details
The longer answers behind the cards above.
Where exactly is my data stored?
How do CI tokens limit what automation can do?
What happens if an encrypted Monitor secret is copied?
What does the connection guard stop?
How long do you keep logs and audit entries?
Can I read the audit logs?
What does Monitor keep, and for how long?
How do you use AI?
Questions about security?
We're happy to answer anything about how we protect your data. Reach out any time.
- GDPR compliant
- AES-256-GCM
- HMAC-SHA256
- AWS Frankfurt