Security & compliance

Security is not a feature. It is the architecture

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.

Encrypted credentials EU data processing GDPR compliant No security tiers
Guarantees

What we will never do

These are engineering decisions built into the architecture — not policies that change with a new investor or quarterly target.

principle 01

Never sell your data

Your data is yours. We do not monetize it, share it with third parties, or use it for anything other than running the service you signed up for.

principle 02

Never track you

We collect what we need to run the service. Nothing more. No analytics on your content, no profiling, no behavioral data.

principle 03

Never store plain text creds

Database passwords are encrypted with AES-256-GCM. API keys are hashed with HMAC-SHA256. This is the architecture, not a setting.

How it works

Security in practice

01

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.

02

API keys hashed, not encrypted

API keys are hashed with HMAC-SHA256 before storage. We never store the raw key — only the hash. Each key tracks creation date, last usage, and can be revoked instantly.

03

Isolated backup execution

Every backup job runs in a dedicated sandboxed task, provisioned on demand. It decrypts credentials in memory, runs the backup, and is destroyed. No shared resources between jobs or customers.

04

EU data processing

All infrastructure runs in AWS Frankfurt (eu-central-1). Your data is processed and stored within the European Union.

05

Encrypted in transit

All API traffic goes through AWS Elastic Load Balancer with TLS encryption. Database connections from backup tasks use encrypted channels.

06

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.

07

No request body logging

We do not log request bodies. Your credentials, translations, prompts, and domain queries never appear in application logs.

08

Rate limiting

API endpoints are rate-limited to prevent abuse and protect service availability for all users.

Compliance

Privacy & data protection

01

GDPR compliance

We process data lawfully, minimize what we collect, and store everything in the EU. We do not sell, share, or monetize your data.

02

Data export

Each product provides API access to your data. Backups download as standard gzip archives. Translations export as i18n JSON. Domain data is available via API.

03

Data deletion

You can delete your data from the dashboard or via API. Account deletion removes your data from our systems.

04

No certifications yet

We do not hold SOC 2, ISO 27001, or similar certifications at this time. As we grow, we plan to pursue formal compliance certifications.

Incident response

If something goes wrong

01

Detection and containment

We monitor infrastructure for anomalies. If a security incident is detected, affected systems are isolated immediately to prevent further exposure.

02

User notification within 72 hours

If your data is affected by a breach, we notify you within 72 hours of confirmation — as required by GDPR. The notification includes what happened, what data was affected, and what we are doing about it.

03

Transparent post-mortem

After resolution, affected users receive a post-mortem explaining the root cause, timeline, impact, and what we changed to prevent recurrence.

04

Report a concern

Security concerns can be reported to team@norcube.com. We take every report seriously and respond promptly.

Ready when you are

Questions about security?

We are happy to answer anything about how we protect your data. Reach out anytime.

GDPR compliant EU data processing
AES-256-GCM Credential encryption
HMAC-SHA256 API key hashing
AWS Frankfurt eu-central-1
// tick. tick. tick.
0 ticks since founding