Legal
Sub-processors
Effective date: 12 November 2026
These are the providers NanoFlags uses to run the service and that may process personal data on behalf of our customers. The Data Processing Agreement refers to this list, and the privacy notice describes the data itself.
We update this page, with a dated entry in the changelog below, before a new provider starts processing customer personal data. Questions or objections: support@nanoflags.io.
1. Current sub-processors
| Provider | Purpose | Personal data | Location |
|---|---|---|---|
| SupabaseSupabase, Inc. | Database and authentication: stores accounts, organizations, workspace content, published revisions, the audit log, diagnostics and website analytics aggregates. | Account data (e-mail, name, password hash, two-step factor), organization and workspace data, audit log, sampled evaluation events, service reports. | Mumbai, India (AWS ap-south-1) |
| CloudflareCloudflare, Inc. | Hosting of the website and dashboard, the edge network that serves signed configuration to SDKs (Workers, KV, Durable Objects), hourly configuration backups (Workers KV or R2, private), and the cookieless website analytics endpoint. | Request metadata needed to serve traffic (IP address, user agent), published configuration, SDK keys as hashes, configuration backups, website analytics events before aggregation. | Global network |
| ResendResend, Inc. | Delivery of transactional e-mail: verification and sign-in links, invitations, approval requests, publication and billing notices. | Recipient e-mail address and name, e-mail content. | Tokyo, Japan |
| SentryFunctional Software, Inc. | Error monitoring of the website, dashboard and edge services (errors only, no tracing or session replay). | Error messages, stack traces, page paths, browser type and an opaque user id. Configured not to collect cookies, request bodies, query strings, IP addresses, names or e-mail addresses; keys and tokens are removed. | Frankfurt, Germany (EU region) |
| PaddlePaddle.com Market Ltd and its affiliates | Online reseller and merchant of record for subscriptions: checkout, payment, tax, invoices and fraud prevention. Paddle handles payment details as an independent controller. | Name, e-mail, billing address, payment and tax details of the buyer; plan and subscription status shared with NanoFlags. | As described in Paddle's privacy notice |
| GitHubGitHub, Inc.Only if you install the GitHub App | Only when an organization installs the NanoFlags GitHub App: repository events, reading linked repositories to find flag references, and posting pull request comments and check runs. | GitHub account or organization name, installation and repository names, file paths, line numbers and the source line of each flag reference (up to 240 characters), commits. | United States |
2. What is not on this list
- No advertising or tracking providers. The website's analytics are built in-house, cookieless and aggregated (see the privacy notice); they run on Cloudflare and Supabase, listed above.
- Evaluation contexts. Flags are evaluated inside your applications by the SDKs, so the attributes you evaluate with are not sent to any provider to make a decision.
- Professional advisers and authorities receive data only where needed or required by law, as described in the privacy notice; they are not sub-processors of the service.
3. Changelog
List published on its own page. No new provider: the same six providers named in the privacy notice of 10 November 2026 (Supabase, Cloudflare, Resend, Sentry, Paddle, GitHub). Cloudflare's role now also covers the cookieless website analytics endpoint.