Legal · Sub-processors

Sub-processors

Every company that receives data because of Pliuz, in two groups: the ones that handle your Customer Data, and the one that does not but gets listed anyway. Any addition triggers a 30-day notice to existing customers (via email and updates to this page).

Process Customer Data — governed by our DPA

These are the sub-processors our Data Processing Addendum governs under GDPR Art 28.

Supabase

Purpose: Hosted Postgres database, authentication, Realtime, edge functions, cron jobs
Region: Frankfurt, Germany (eu-central-1)
Data accessed: All Customer Data (audit events, approvals, tools, policies, users)

Cloudflare

Purpose: DNS, CDN, DDoS protection for marketing site and app endpoints
Region: Global edge (no Customer Data stored)
Data accessed: IP addresses, request metadata for caching and security

Slack

Purpose: Approval notifications, interactive buttons, DM routing (only if Customer enables Slack integration)
Region: US (Slack default infrastructure)
Data accessed: Approval request summary, approver Slack user IDs, channel IDs

Vercel

Purpose: Hosting for marketing site (pliuz.com) and Next.js app (app.pliuz.com)
Region: EU (Frankfurt) for app routes; global edge for static marketing
Data accessed: Request metadata only. Customer Data is fetched at request time from Supabase (EU), never stored on Vercel.

Resend

Purpose: Transactional and waitlist email delivery (double opt-in confirmation, launch and early-access notices)
Region: EU (Ireland, eu-west-1)
Data accessed: Recipient email address and the content of the email sent (no audit payloads, no Customer Data)

Do not process Customer Data — listed for transparency

This one never touches approval payloads, approver identities or audit events, and it does not run inside the authenticated product. Pliuz is the controller of its own marketing-site visitor data, so under Art 28 it is not a sub-processor at all — we list it because leaving it out would look like hiding it. If a security review requires no US processor anywhere in your supply chain: Slack is optional per tenant, and this one is a property of our own website that can be switched off entirely.

Google (Google Analytics 4)

Purpose: Website analytics on the marketing site only. App routes (app.pliuz.com) are never tracked. Runs without cookies until you accept in the cookie banner; if you accept, it sets analytics cookies so returning visits can be told apart. Never used for advertising or profiling.
Region: United States (Google LLC). Which Google entity is the contracting party for this account is not yet verified: the Ads Data Processing Terms name “Google LLC, Google Ireland Limited or any other Affiliate” and do not designate one for the EEA, so we do not claim one here. The EU-to-US transfer relies on the EU-US Data Privacy Framework, under which Google LLC is certified, with the Commission’s Standard Contractual Clauses as fallback.
Data accessed: Marketing-site visitors only: page views, referrer, device and browser type, and your IP address — which Google states it uses to derive an approximate location and then discards without logging it for EU, UK and Swiss visitors. That is Google’s representation, not something we can verify ourselves. With your consent, a client identifier stored in a cookie. No Customer Data — audit events, approvals and payloads never leave the EU and are never sent to Google.

Recent changes

2026-09-05 — Google added. Google Analytics has been running on this marketing site since 2026-06-21 and was not listed here until today. Listing it is the correction. From today it also requires your consent: it sets no analytics cookies unless you accept them in the banner.
2026-09-05 — Plausible removed. Plausible Analytics was listed here. We have now confirmed that no account ever existed, so nothing was ever collected or stored there and there is no data to delete. The script did load on every marketing page between 2026-05-24 and today, so their servers received the requests — carrying visitors’ IP addresses — and discarded them as belonging to no registered site. For those months this page named Plausible as an active processor: that described an intention, not a fact. The script and the listing are gone as of today.

Last updated: 2026-09-05. Subscribe to changes by emailing founder@pliuz.com with subject "Subscribe sub-processor updates" — we will email any addition 30 days before it goes live.

← Read our security model