Legal
Data Processing Agreement
Effective date: 12 November 2026
Review by counsel before signing. This is the standard text we offer. It has not yet been reviewed by our lawyers and is not a signed agreement until both parties execute it. Have it reviewed by your own counsel before you sign; to request a countersigned copy or propose changes, write to support@nanoflags.io.
This Data Processing Agreement ("DPA") forms part of the Terms of Service between the customer organization ("Customer") and Alibtekarat Althkiya Company for Trading & Marketing, a limited liability company registered in Building 2607, Zainab Bint Omar Street, Al Fakhiriyah District, Secondary No. 6957, Riyadh 12737, Kingdom of Saudi Arabia (commercial registration no. 7016629938, VAT no. 314143963600003) ("NanoFlags", "we") when it is executed by both parties. Where the DPA and the Terms conflict on the processing of personal data, the DPA prevails.
1. Roles and scope
Customer is the controller, and NanoFlags the processor, of the personal data that Customer and its users put into NanoFlags in the course of using the service ("Customer Personal Data"): workspace content, diagnostics sent by Customer's SDKs, code references and the audit log of Customer's organization.
NanoFlags is a controller of the account, billing and website data described in the privacy notice; this DPA does not cover that data.
2. Details of the processing
- Subject matter and purpose: providing the NanoFlags service: storing, reviewing, testing and publishing feature-flag configuration, delivering signed configuration to Customer's SDKs, showing which revisions Customer's services report, and the related diagnostics, support and security.
- Duration: for the term of the Customer's subscription and until deletion under "Return and deletion" below.
- Categories of data subjects: Customer's authorized users of the dashboard; and Customer's own end users, only to the extent Customer places their identifiers or attributes in flag rules, segments, scenarios or telemetry.
- Categories of personal data: names and e-mail addresses of members and invitees; actions in the audit log; identifiers or attributes Customer writes into rules and segments; sampled evaluation events (flag key, value, reason, revision and, by default, only the names and types of context attributes, never their values unless Customer configures otherwise); code references (file path, line number and up to 240 characters of the line) if Customer uploads them or installs the GitHub App.
- Special categories: none are required by the service. Customer should not place special-category data in flag rules, values or telemetry.
- Frequency: continuous, while the service is used.
3. Our obligations
- Process Customer Personal Data only on Customer's documented instructions, which are the Terms, this DPA and Customer's use and configuration of the service, unless the law requires otherwise (in which case we will inform Customer unless the law prohibits it). We will tell Customer if, in our opinion, an instruction infringes data protection law.
- Ensure that people authorized to process Customer Personal Data are bound by confidentiality.
- Implement the technical and organizational measures in "Security measures" below, and keep them appropriate to the risk.
- Taking into account the nature of the processing, assist Customer with requests from data subjects and with security, breach-notification, impact-assessment and prior-consultation obligations, to the extent Customer cannot fulfil them through the dashboard or the export.
- Make available the information reasonably necessary to demonstrate compliance with this DPA, and allow for and contribute to audits, as described in "Information and audits".
4. Sub-processors
Customer authorizes NanoFlags to engage the sub-processors listed on the sub-processors page, currently: Supabase, Cloudflare, Resend, Sentry, Paddle, GitHub (only if the GitHub App is installed).
- We impose data protection obligations on each sub-processor that are no less protective than this DPA, and remain responsible for their performance.
- We will update the list, with a dated changelog entry, at least 30 days before a new sub-processor starts processing Customer Personal Data, except where a change is urgently needed for security or continuity of the service, in which case we update it as soon as possible.
- Customer may object on reasonable data-protection grounds by writing to support@nanoflags.io within that period. We will work in good faith to find a solution; if none is found, Customer may terminate the affected service with a pro-rata refund of prepaid fees for the remaining term.
5. Security measures
- Encryption in transit: all traffic to the website, dashboard and edge uses HTTPS.
- Access control: organization roles (viewer, editor, admin, owner) enforced by row-level security in the database; optional two-step verification, which an owner can require for owners and admins.
- Credentials: SDK and API keys are shown once and stored as SHA-256 hashes; webhook signing secrets are stored in columns the dashboard cannot read back.
- Integrity of configuration: every published revision is immutable and signed with Ed25519; the SDKs verify signatures by default on the official edge.
- Change control: reviewed changes with independent approvals bound to the exact draft, scenario checks that gate publishing, and an audit log that members cannot edit.
- Data minimization: flags are evaluated locally in Customer's applications; telemetry is sampled and, by default, sends no context attribute values.
- Staff access: operator access to customer records requires two-step verification, is limited by role-based permissions, and every action and every customer record opened is written to a staff audit log.
- Resilience: the edge keeps serving the last signed configuration when the database is unreachable; hourly logical backups of customer configuration are kept outside the database provider for 30 days and restores are tested.
- Monitoring: error monitoring without personal data in reports (see the privacy notice), and automated checks of configuration propagation with alerting.
6. Personal data breaches
We will notify Customer without undue delay after becoming aware of a personal data breach affecting Customer Personal Data, with the information reasonably available to us at that time (nature of the breach, categories and approximate numbers concerned, likely consequences, measures taken or proposed), and will update Customer as more information becomes available. Notification is not an acknowledgement of fault.
7. Return and deletion
- During the term, Customer can export its configuration (Settings → Data & export, or the admin export API) and delete projects from the dashboard; a project deletion removes its flags, segments, revisions, keys and history immediately.
- Sampled evaluation events are deleted automatically after the retention of Customer's plan (Explore 3 days, Team 14 days, Scale 30 days).
- On termination, or on request, we delete Customer's organization and its Customer Personal Data, unless the law requires us to keep it. Deleted data can remain in backups until they expire (configuration backups after 30 days; the database provider's backups in its normal cycle).
8. International transfers
Customer Personal Data is stored in the regions described in the privacy notice (database and authentication in Mumbai, India (AWS ap-south-1, via Supabase); application and configuration delivery on Cloudflare's global network; transactional e-mail via Resend (Tokyo, Japan)). Where data protection law requires a transfer mechanism for a transfer to a sub-processor, we rely on the sub-processor's standard contractual clauses or an equivalent safeguard, and will enter into the standard contractual clauses with Customer where required.
9. Information and audits
On written request, and no more than once a year unless a supervisory authority requires it or a breach has occurred, we will answer Customer's reasonable security questionnaires and provide the documentation needed to demonstrate compliance. On-site audits, where the law entitles Customer to them, are carried out by an independent auditor bound by confidentiality, on reasonable notice, during business hours and at Customer's cost.
10. Liability, term and law
Each party's liability under this DPA is subject to the limitations in the Terms. This DPA lasts as long as we process Customer Personal Data. It is governed by the law and courts named in the Terms (the laws of the Kingdom of Saudi Arabia; the competent courts in Riyadh), except where data protection law requires otherwise.
11. Contact
Questions about this DPA, requests to execute it, and notices under it: support@nanoflags.io.