Trust Center

Where we stand on compliance

The honest version: what we comply with today, what we're working toward, and what's on the someday list. No badges we haven't earned.

GDPR compliantEU AI Act transparencyPublic subprocessorsNo audit theater

Last updated: November 5, 2026

The honest summary: We comply with everything the law requires: GDPR, ePrivacy and the transparency rules of the EU AI Act. We haven't pursued voluntary certifications like SOC 2 Type II or ISO 27001 yet. We're a small team building the underlying controls first, and we'll pursue audits when customers ask for them. This page lays out exactly where we are.

#What we comply with today

GDPR (EU 2016/679)

Status: compliant.

As an EU-incorporated company processing EU residents' data, GDPR applies to us by law. We have:

  • A documented privacy policy covering all Article 13/14 disclosures
  • A public DPA that auto-applies to every customer
  • A list of subprocessors with transfer mechanisms for each, each governed by the provider's standard data processing agreement
  • A documented incident-response process: customers are notified within 48 hours of a confirmed breach, and the supervisory authority within 72 hours where required
  • Self-service data export in the product (Art. 15 right of access + Art. 20 right to data portability): signed-in users request a ZIP of their account data from Account → Data & privacy; the system emails a download link, typically within minutes, formally within the 30-day GDPR deadline
  • Self-service profile editing (Art. 16 right to rectification): name, avatar, and email editable in Account → Profile; password changes in Account → Security. Email and password changes both require the current password; email additionally requires a 6-digit code emailed to the new address before the swap
  • Self-service account deletion (Art. 17 right to erasure): Account → Delete account schedules the deletion with a 30-day cooling-off window. After 30 days the system permanently anonymizes every personal-data field on the account row (name, email, password, avatar) and removes all organization memberships. The account UUID itself is preserved so audit trails in other services keep resolving (rendered as "Former user"); pseudonymization that prevents re-identification satisfies Art. 17. Users can cancel from the same page any time before the 30 days elapse
  • Self-service organization deletion (also Art. 17, for org-scoped data): closing an organization you're the only member of removes it from your dashboard immediately and triggers a cross-product cleanup: open billing usage is finalized first, then Backup data, LangSync namespaces, DomainRadar watchers, Monitor's monitors, alert channels, status pages and their subscribers, and usage-limit overrides are deleted. Backup blobs in S3 are removed asynchronously by a sweep worker. The whole sequence typically finishes within a minute
  • Right to object to in-app product analytics is exposed as a toggle in Account → Profile (we process in-app analytics under legitimate interest, GDPR Art. 6(1)(f), and document the assessment internally)
  • Data subject requests outside the self-service flow (restriction, partial access, multi-member org deletion) go to [email protected]
  • Email verification (Art. 32 security measure): on signup we send a 6-digit code to the address you provided and ask you to enter it from inside the app to confirm control. The same mechanism re-confirms control when you change your email later. Codes are bcrypt-hashed at rest, expire after 15 minutes, and are limited to 5 attempts

ePrivacy / cookies

Status: compliant.

On norcube.com we set strictly-necessary cookies (your consent choice, CDN security) without consent, and one analytics cookie (PostHog, EU-hosted) only after you click Accept on the banner. You can reverse your decision at any time via the "Cookie preferences" link in the footer. No advertising cookies, no cross-site tracking, no fingerprinting. Full details on the cookies page.

Czech / EU consumer law

Status: compliant.

Our Terms of Service preserve all consumer-protection rights for EU customers and complies with Czech contract law.

EU AI Act (transparency rules have applied since August 2, 2026)

Status: compliant.

We use AI as a deployer (calling OpenAI), not as a provider of foundation models. Our obligations are limited to transparency:

  • LangSync labels AI-generated translations as AI output in the dashboard until a person edits them, and Norcube CMS shows AI Assist's proposed changes for review before they are saved
  • We disclose AI processing in our privacy policy
  • We don't deploy any "high-risk" AI systems under the Act's classification
  • Our DPA covers AI subprocessing

PCI DSS (Stripe handles cards)

Status: SAQ A scope (the lightest tier).

Stripe handles all card data; our servers never touch raw card numbers. We self-attest annually via Stripe's compliance dashboard.

#What we haven't pursued yet

SOC 2 Type II

Status: not pursued.

SOC 2 Type II is an auditor's attestation, developed in the US, that controls operated effectively over a period of time. It's widely asked for in enterprise procurement.

Why we haven't pursued it yet:

  • Our customers have not asked. SOC 2 is a deal-driven investment, not a prerequisite for selling
  • We are building the underlying controls (encryption, mTLS, audit logs, vendor management, change management, incident response) that an auditor would examine
  • The audit costs ($20–50k/year) plus the prep work (~6 months) don't have a clear ROI yet for our customer base

When that changes, we expect to start a SOC 2 Type II engagement within a quarter of the first customer asking. We can usually unblock a deal with a written gap analysis and a target audit date.

ISO/IEC 27001:2022

Status: not pursued.

ISO 27001 is the EU-favored counterpart of SOC 2. Same situation:

  • We are building an ISMS-shaped set of policies and controls in the background
  • We will engage an accredited certification body when a customer requires it

The same goes here: we can produce a gap analysis on request that demonstrates control coverage matching the 93 Annex A controls.

#What is on the roadmap

  • Multi-member organization deletion: sole-member org closures are self-service (see "what we comply with today" above); admin closures for orgs with other members still email us, until we add a UI for explicit co-member consent
  • Annual penetration test: once we reach a customer count that justifies the cost
  • SOC 2 Type II readiness assessment: lightweight gap analysis, to be ready when a customer asks

#How to verify our claims

We want our compliance claims to be checkable. You can:

We don't have a portal full of SOC 2 / ISO 27001 PDFs; when those exist, they will be linked here.

#Security questions, breach reports

  • Security inquiries and responsible disclosure: [email protected] with the subject "Security". We reply within 5 business days, and sooner for anything urgent. We don't run a bug bounty program yet, but we appreciate every report and credit researchers who want to be named
  • Privacy concerns / GDPR rights: [email protected]
  • Active incident affecting your account: [email protected] with subject "URGENT". We monitor this channel during business hours and respond outside them on a best-effort basis
// tick. tick. tick.
0 ticks since founding
Coming soon

Join the PromptHub waitlist

PromptHub is in active development. Leave your email and we'll invite you as soon as it opens, with a free tier and no credit card.

One email when access opens. No newsletter, no spam.