Privacy Policy
What we collect, why, your rights under applicable law, and how to exercise them.
Last updated: April 24, 2026
Zappz Pte. Ltd. ("zappz," "we," "us") is committed to protecting your privacy. This policy covers what personal information we collect through app.zappz.co and related services ("the Service"), why we collect it, the legal basis for processing, and the rights you have under applicable privacy laws — including the EU/UK General Data Protection Regulation (GDPR), Canada's Personal Information Protection and Electronic Documents Act (PIPEDA), Singapore's Personal Data Protection Act (PDPA), and the California Consumer Privacy Act as amended by the CPRA (CCPA/CPRA).
This is revision v1-2026-04-24. Material changes get at least 30 days' notice by email before they take effect.
1. Information we collect
- Account information — your name, email address, and a salted-hash of your password. We never see your plaintext password.
- Conversation content — messages you send to your zappz copilot and the workflow drafts it produces. Used to build your app and, in aggregated form, to improve the product.
- Contact and data-request submissions — name, email, optional business name, the message or request body, and the jurisdiction you're invoking.
- Technical logs — IP address, user agent, request metadata, consent events. Kept for security, debugging, rate- limiting, and compliance recordkeeping.
- Payment information — handled by Stripe. We receive a customer identifier and the last four digits of the card; full card numbers are never stored on our servers.
- Protected Health Information (PHI) — only when a customer's project explicitly opts in on the
handles_phiflag and a signed Business Associate Agreement is in place. See §10.
2. How we use it (purposes and lawful basis)
Under GDPR Art 6, each processing activity has a specific lawful basis. Under PIPEDA and PDPA we use the equivalent principle of identified purposes and consent.
- Deliver the Service (run your account, host your app, handle logins) — contractual necessity.
- Security and fraud prevention (rate-limiting, IP logging, authentication) — legitimate interest.
- Billing and tax compliance — legal obligation.
- Transactional emails (verification, password reset, receipts) — contractual necessity.
- Product improvement (aggregated analytics on conversations, not tied back to individuals) — legitimate interest. You can object under GDPR Art 21.
- Non-essential cookies (none today; reserved for future analytics) — consent, which you can grant or revoke any time via Cookie Settings.
3. Subprocessors — who else touches your data
We do not sell your personal information. We share limited data with service providers under Data Processing Agreements and, where applicable, EU Standard Contractual Clauses:
- Anthropic, PBC — LLM inference for the zappz copilot and the public chatbot. Location: United States. Their privacy policy.
- OpenAI, LLC — Vector embeddings for RAG retrieval on the public knowledge base. Location: United States. Their privacy policy.
- Amazon Web Services (AWS) — Application hosting, database storage, and transactional email (SES). Location: Canada and United States. Their privacy policy.
- Stripe, Inc. — Subscription billing and payment processing. Location: United States. Their privacy policy.
- Cloudflare, Inc. — Edge network, DDoS protection, and DNS. Location: Global edge network. Their privacy policy.
See /dpa for our Data Processing Addendum and an always-current subprocessor list.
4. International transfers
Our production infrastructure is hosted in Canada and the United States. If you access the Service from the EU/EEA, UK, Singapore, or elsewhere, your information will be transferred to and processed in those regions. For transfers from the EU/EEA/UK to the US we rely on the European Commission's Standard Contractual Clauses (SCCs), and for UK transfers we use the UK Addendum to the SCCs.
5. Your rights
Regardless of where you live, you can exercise these rights via our data request form or by emailing [email protected]. We respond within 30 days.
Under GDPR (EU/EEA/UK)
- Access (Art 15), rectification (Art 16), erasure (Art 17)
- Restriction (Art 18), portability (Art 20), objection (Art 21)
- Withdraw consent at any time (Art 7(3))
- Lodge a complaint with your supervisory authority — e.g. the EDPB member list or the UK's ICO.
Under PIPEDA (Canada)
- Know whether we hold your personal information, request access to it, and challenge the accuracy of it.
- Withdraw consent (subject to legal or contractual constraints).
- Complain to the Office of the Privacy Commissioner of Canada.
Under PDPA (Singapore)
- Access to personal data about you and information about how it's been used within the past year.
- Correction of data you believe is inaccurate.
- Withdrawal of consent for any identified purpose.
- Complain to the Personal Data Protection Commission of Singapore.
Under CCPA / CPRA (California)
- Know, access, correct, delete, opt out of "sharing."
- Non-discrimination for exercising your rights.
- We do not "sell" personal information as defined under the CCPA and we do not use it for cross-context behavioural advertising.
6. Data retention
- Active accounts — retained for as long as your account exists.
- Abandoned conversations (no build submitted, no activity) — purged automatically after 90 days.
- Billing records — retained for 7 years to comply with Canadian and US tax law.
- Audit and security logs — retained for 1 year, longer only where required by law.
- After account deletion — we remove personal identifiers from audit records but retain the anonymised records required for legal, tax, or security accountability.
7. Security
We use TLS in transit, AES-256 encryption for secrets at rest, role-based access control inside the company, and least-privilege practices on our infrastructure. If we discover a breach that affects you, we'll notify you and the relevant regulators within 72 hours of becoming aware of it — the maximum window permitted under GDPR Art 33.
8. Cookies and tracking
We use only strictly-necessary cookies today (auth, security, preferences). We do not use analytics, advertising, or cross-site tracking cookies. See our Cookie Policy for the complete list and Cookie Settings to manage your choices.
9. Automated decision-making
zappz uses AI models to help generate your app's configuration based on your conversation with our copilot. This is not automated decision-making within the meaning of GDPR Art 22 because the output is always reviewable and editable by you before any build happens. Every spec the copilot writes is shown for your explicit approval.
10. Protected Health Information (HIPAA)
The standard zappz service is not a HIPAA Business Associate. Customers who need to handle Protected Health Information can opt into a HIPAA-ready configuration on the Premium plan, which includes:
- A signed Business Associate Agreement (BAA) with zappz.
- Routing of conversation and build data to subprocessors with matching BAAs in place (Anthropic Claude for Enterprise, OpenAI Enterprise, AWS HIPAA-eligible services).
- Tightened access logging and retention appropriate to 45 CFR §164.
To discuss a BAA, email [email protected]. Do not upload PHI into a standard (non-BAA) account — we are not authorised to receive it.
11. Children
zappz is for businesses and is not directed at anyone under 16 in the EU/EEA/UK or under 13 elsewhere. We do not knowingly collect personal information from children.
12. Contact
For any privacy question or to contact our Privacy Officer, email [email protected] or write to:
Privacy Officer
Zappz Pte. Ltd.
20 Sin Ming Lane
Singapore, 573968
Singapore
See also: Terms & Conditions, Cookie Policy, Cookie Settings, Data Processing Addendum, Submit a data request.