Subprocessors

Every third party we work with, in the open

These are the companies that process customer data on Norcube's behalf. We name them, we say what they do, and we explain why the data transfer is lawful.

EU primary hostingDPF or SCCs for non-EUNo advertising vendorsUpdated when we change

Last updated: November 5, 2026

This page lists every subprocessor that processes personal data on behalf of Norcube and its customers, as required by Article 28 GDPR and our Data Processing Agreement (Annex 3). We announce changes here at least 30 days in advance. To receive change notices by email, write to [email protected].

#Summary

Subprocessor Purpose Data location Transfer mechanism
Amazon Web Services Hosting, databases, storage, encryption keys, logs EU (Frankfurt) Not needed for stored data; DPF and SCCs
Cloudflare Website, docs and web-app delivery; bot protection; website functions; public status pages Global edge network DPF and SCCs
Upstash Website waitlist and roadmap votes EU (Frankfurt) SCCs
Fly.io Norcube CMS live preview sandboxes EU (Frankfurt) SCCs
Stripe Payments United States and other countries DPF and SCCs
OpenAI AI features in LangSync, DomainRadar and Norcube CMS United States SCCs
Mailgun (Sinch) Transactional email, status page subscriber email EU Not needed in normal operation; DPF and SCCs
BulkGate (TOPefekt s.r.o.) SMS alerts and phone verification codes for Monitor Czech Republic Not needed for stored data; see the entry below
PostHog Website and product analytics EU (Frankfurt) Not needed for stored data; SCCs

#How to read the details

For each subprocessor we list:

  • Used for: the specific service we use them for
  • Data: the categories of personal data they receive
  • Location: where they process it, which matters for cross-border transfers
  • Transfer mechanism: the EU-US Data Privacy Framework (DPF), Standard Contractual Clauses (SCCs), or none needed when data stays in the EU
  • Agreement: the data processing agreement that governs them

#Our agreements with these providers

For every provider below, we rely on the provider's standard data processing agreement, which forms part of its service terms and which we accepted when we started using the service. We have not negotiated or separately signed individual agreements. Each agreement is published by the provider and linked in its entry.

#Hosting and infrastructure

Amazon Web Services (AWS)

  • Used for: The Norcube platform's backend: compute (Amazon ECS on Fargate, AWS Lambda), databases (Amazon RDS for PostgreSQL), file and backup storage (Amazon S3), encryption keys (AWS KMS), configuration and secrets (AWS Systems Manager Parameter Store), and service logs (Amazon CloudWatch)
  • Data: Everything you store in Norcube, plus service logs (request method and route, response codes, timestamps, IP addresses, and account and organization IDs)
  • Location: AWS Europe (Frankfurt) region, eu-central-1
  • Transfer mechanism: None needed for stored data, which stays in the EU. Amazon Web Services, Inc. (US parent) is certified under the DPF, and the AWS GDPR Data Processing Addendum includes SCCs
  • Agreement: AWS GDPR Data Processing Addendum, part of the AWS Service Terms
  • Vendor URL: aws.amazon.com

Cloudflare

  • Used for: Serving norcube.com, docs.norcube.com and the dashboard's web app (app.norcube.com) through Cloudflare's network (Cloudflare Pages), bot and abuse protection, and the small server functions behind the website's waitlist and roadmap votes. Cloudflare Workers and Workers KV also store and serve Monitor's public status pages, on norcubestatus.com and on customers' custom domains through Cloudflare for SaaS
  • Data: Visitors' IP addresses and request metadata (URL, browser user agent, headers), Cloudflare's security cookies (__cf_bm, _cfuvid), and waitlist email addresses and roadmap votes while the website functions handle them. For status pages: the content a customer publishes (page and component names, incident posts, availability, logos), custom hostnames, and page visitors' IP addresses and request metadata. Monitored URLs and internal monitor data are never sent to the status page store. An email address typed into a status page's subscribe form passes through on its way to Monitor in AWS Frankfurt, and isn't kept in the status page store
  • Location: Cloudflare's global network; a request is handled at a data center near the visitor, which may be outside the EU. Status page content is stored and served on this network, not in AWS Frankfurt. Cloudflare, Inc. is based in the United States
  • Transfer mechanism: Cloudflare, Inc. is certified under the DPF; its data processing addendum includes SCCs
  • Agreement: Cloudflare Data Processing Addendum, part of Cloudflare's terms of service
  • Vendor URL: cloudflare.com

Upstash

  • Used for: The database behind the norcube.com waitlist and the public roadmap votes
  • Data: Waitlist sign-ups (email address, product, sign-up time); roadmap votes (one record per voter's IP address, so each visitor can vote once per item); rate-limit counters keyed by IP address, deleted after one hour
  • Location: Upstash Redis in AWS eu-central-1 (Frankfurt), operated by Upstash, Inc. (United States)
  • Transfer mechanism: SCCs in Upstash's data processing agreement
  • Agreement: Upstash Data Processing Agreement, part of Upstash's terms of service
  • Vendor URL: upstash.com

Fly.io

  • Used for: Norcube CMS live preview: a short-lived sandbox per site that runs the site's own development server so editors can see their changes
  • Data: A copy of the connected repository's branch (site content and code) and the unsaved edits streamed from the editor while a preview is open. Sandboxes are suspended when idle and removed after about a week without use
  • Location: Fly.io machines in the Frankfurt region (fra), operated by Fly.io, Inc. (United States)
  • Transfer mechanism: SCCs in Fly.io's data processing addendum
  • Agreement: Fly.io terms of service and Fly.io's data processing addendum
  • Vendor URL: fly.io

#Payments

Stripe

  • Used for: Payment processing, payment-method storage and invoice payments. Card details never touch our servers; they go directly from your browser to Stripe through Stripe Elements
  • Data: Billing identity (name, email, billing address), payment-method identifiers (pm_xxx, never raw card numbers), invoice and payment records
  • Location: Stripe processes data in the United States and other countries where it operates
  • Transfer mechanism: Stripe, Inc. is certified under the DPF; the Stripe DPA includes SCCs
  • Agreement: Stripe Data Processing Agreement, part of the Stripe Services Agreement
  • Vendor URL: stripe.com

#AI processing

OpenAI

  • Used for: LangSync AI translation; DomainRadar brand-monitor checks and the AI name generator; Norcube CMS AI Assist, schema scaffolding and site analysis
  • Data: Only the text a feature sends to the model: for example the source strings and glossary terms being translated, the domain and page content being checked, the description you give the name generator, or the page content you ask AI Assist to work on
  • Location: OpenAI's API, operated by OpenAI from the United States
  • Transfer mechanism: SCCs in OpenAI's Data Processing Addendum
  • Agreement: OpenAI Data Processing Addendum, which applies to use of the OpenAI API under OpenAI's business terms
  • Model training and retention: Under OpenAI's API terms, data sent through the API is not used to train OpenAI's models. OpenAI may retain API inputs and outputs for up to 30 days to monitor for abuse, then deletes them
  • Vendor URL: openai.com

#Email

Mailgun (Sinch)

  • Used for: Transactional email only: sign-up verification and email-change codes, password resets, account-deletion notices, billing receipts and payment reminders, the product alerts you turn on, and confirmations and incident updates to people who subscribe to a Monitor status page, sent from mg.norcubestatus.com. We don't send marketing email through Mailgun
  • Data: Recipient email addresses and message content (which includes your name and the account event). For status pages: subscribers' email addresses and the page's name and posts
  • Status page subscribers: Unsubscribing deletes the address from Monitor. An address that isn't confirmed is deleted after 7 days, and all of a page's addresses are deleted when the page or its Organization is deleted. Mailgun keeps addresses that bounced or complained on its own suppression list, so they get no further email
  • Location: Mailgun's EU region (api.eu.mailgun.net), which stores email data in the European Union
  • Transfer mechanism: None needed for the EU region in normal operation. Sinch, Mailgun's parent, is certified under the DPF, and Mailgun's DPA includes SCCs for any access from outside the EU
  • Agreement: Mailgun Data Processing Agreement, part of Mailgun's terms of service
  • Vendor URL: mailgun.com

#SMS

BulkGate (TOPefekt s.r.o.)

  • Used for: Sending Monitor's SMS alerts, test messages and phone verification codes
  • Data: The recipient's mobile number and the message text (for an alert: the monitor's name, what went wrong and a link to the dashboard)
  • Location: Operated by TOPefekt s.r.o., Šumperk, Czech Republic, which states that all data is stored in the Czech Republic. A text reaches its recipient through mobile operators and SMS aggregators
  • Transfer mechanism: None needed for stored data. Monitor sends SMS only to numbers in Czechia, Slovakia, Germany, Austria, Poland and the United Kingdom, so a text to a UK number leaves the EU. BulkGate's privacy policy says transfers to countries on the European Commission's adequacy list rely on that status
  • Agreement: BulkGate Data Processing Terms, under Article 28 GDPR, accepted when the BulkGate account is created
  • Retention: BulkGate's terms allow it to archive the history of sent and received messages for two years
  • Vendor URL: bulkgate.com

#Analytics

PostHog (EU Cloud)

  • Used for: Web analytics on norcube.com and docs.norcube.com (only after you accept the cookie banner) and product analytics inside app.norcube.com (page views and feature-usage events such as "translation synced" or "backup created"). Autocapture and session recordings are turned off; we capture page views and the events we explicitly send
  • Data: A random visitor identifier (distinct_id), page URLs, basic device information (browser family, operating system) and the events we send. PostHog uses the IP address for coarse, city-level location. We don't capture form contents or keystrokes
  • Location: PostHog EU Cloud, hosted in Frankfurt
  • Legal basis: On norcube.com and docs.norcube.com, your consent (Art. 6(1)(a) GDPR and ePrivacy Art. 5(3)) given through the cookie banner. Inside app.norcube.com, our legitimate interest in improving the product (Art. 6(1)(f)); PostHog runs in memory-only mode there, so it sets no cookies and writes nothing to local storage. You can object at any time by clearing the "Allow in-app analytics" option in your account settings (Art. 21)
  • Transfer mechanism: None needed for data stored in the EU instance. PostHog Inc. (US parent) provides SCCs in its DPA for any access from outside the EU
  • Agreement: PostHog Data Processing Agreement, part of PostHog's terms
  • Retention: For as long as our PostHog account exists; we can delete any visitor's data on request
  • Vendor URL: posthog.com

#Is this the full list?

Yes. The nine providers above are all the subprocessors that process personal data on our behalf. A new subprocessor is listed here before it receives any personal data, as described below.

#Integrations you connect (not our subprocessors)

Some Norcube features let you connect your own third-party accounts, for example the GitHub repositories you connect to Norcube CMS, the S3-compatible storage you connect to Backup (such as Cloudflare R2, Backblaze B2, Wasabi or MinIO), or the Slack, Discord and webhook destinations you set up for alerts. Data then flows to that provider under your agreement with them, on your instructions. We are not their customer for that data, so they are not our subprocessors. Their data-protection terms come from them directly.

#Internal tools that never receive customer data

For completeness, these tools support our internal operations and never receive the content you store in Norcube:

  • GitHub (US, DPF and SCCs): source code hosting and CI/CD
  • Slack (US, DPF and SCCs): internal team communication
  • Accounting software: Czech tax and accounting compliance

They don't process customer data on our behalf, so they aren't subprocessors under GDPR Article 28. We list them because customers sometimes ask.

#Recent changes

November 5, 2026: added BulkGate, which was already delivering Monitor's SMS alerts when we listed it here, and extended the Cloudflare entry to cover public status pages. Added status page subscribers' email addresses to the Mailgun and Cloudflare entries, as Monitor now sends email to people who subscribe to a status page.

#Changes to subprocessors

When we intend to add or replace a subprocessor, we:

  1. announce the change on this page at least 30 days before it takes effect, with its date;
  2. email the customers who have asked to receive change notices at [email protected]; and
  3. where an urgent replacement is necessary to keep the services secure or available, announce it as soon as possible.

Removing a subprocessor takes effect when we update this page.

#Right to object

Under section 4.3 of our DPA, you may object to a new subprocessor on reasonable data protection grounds within the notice period. We will look for a solution with you in good faith; if none is found, you may terminate the affected services without penalty. To object, email [email protected].

// 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.