Privacy Policy
Zapp
Last updated: April 28th, 2026
Summary
- What Zapp does: Zapp is an IRL party game app. You and your friends play together in the same room using one device as a host. Games include "Convince the AI" (a word-guessing bluffing game) and "Imposter" (a social-deduction game).
- Data stored: Zapp stores account data and gameplay session data on Zapp servers (Supabase) so the app can save your game history and compute game functionality.
- AI features: In various gamemodes, player clues are sent to an AI model (hosted on Microsoft Azure AI Foundry) to generate a guess and response. No personally identifiable information is required in clues.
- Account: Apple Sign In and Google Sign In (OAuth). We do not store your password. Authentication is handled by Supabase Auth using the credentials from Apple or Google.
- Anonymous play: You can try the app without an account. We assign a temporary device identifier to track a small number of free anonymous AI interactions. This identifier is securely stored locally on your device.
- Purchases: In-app purchases are processed through Apple or Google and managed via RevenueCat. We store your entitlement status (whether you have an active subscription or session pass) in our database to gate premium features.
- Analytics: We use PostHog analytics to understand app performance and improve features. We do not use analytics for advertising.
- No tracking: We do not "track" you across other companies' apps and websites for targeted advertising (as defined by Apple). We do not sell your data.
- Deletion: You can request deletion of your account and associated data from within the app or by emailing us.
- Contact: retrospective.technology@gmail.com
1. Data Controller
Zapp is the data controller for personal data processed through the App.
Contact: retrospective.technology@gmail.com
2. Data We Collect
2.1 Account and Identifiers
When you create an account or sign in, we collect:
- Email address: Provided by Apple or Google via OAuth. Used for account creation, authentication, and account recovery.
- Display name: A name you choose during onboarding, stored to personalize the experience.
- User identifier: A unique account identifier (Supabase UID) used to associate your game history and settings with your account.
- Authentication credentials: Handled entirely by Apple or Google via their OAuth flows and by Supabase Auth. We do not store passwords.
2.2 Anonymous Device Identifier
Before you create an account, Zapp allows limited anonymous play. To manage the free anonymous AI interaction limit, we generate a random device identifier and store it in your device's secure storage (iOS Keychain / Android Keystore). This identifier is:
- Randomly generated — it is not derived from your identity or device hardware ID.
- Sent to our server when you make an AI request, so we can count anonymous calls against your device's allowance.
- Stored on Supabase alongside a usage counter (number of calls used). No other personal data is linked to this identifier unless you later create an account.
2.3 Gameplay Session Data
When you play a game, we record and store a session record. This may include:
- Game mode: Which game you played (e.g., "convince" or "imposter").
- Player count: The number of players in the session.
- Session timing: Start and end timestamps.
- Round count: Number of rounds played.
Player clues submitted during games are sent to our AI backend for processing but are not stored permanently in association with your account. See Section 2.4 for AI data handling.
2.4 AI Interaction Data
Various gamemodes send player-submitted clues to a AI models hosted on Microsoft Azure AI Foundry to generate a guess, reasoning, and a mascot response. Specifically:
- Clues submitted: Short text clues entered by players during a round are transmitted to our Supabase Edge Function, which forwards them to Azure AI Foundry.
- Game context: The game mode, player count, and round number are included in the request to shape the AI response.
- AI output: The guess, reasoning, and mascot line returned by the AI are displayed in the app. AI responses are not permanently stored on our servers.
Players control what they type as clues. Clues are short (designed to be 3 words or fewer in the game flow) and are not required to contain personal information. Avoid entering sensitive personal information in clue fields.
2.5 Purchase and Entitlement Data
Zapp offers in-app purchases managed through RevenueCat:
- Monthly subscription ("premium"): Unlocks unlimited gameplay.
- 24-hour session pass: A one-time purchase unlocking gameplay for 24 hours.
Payment processing is handled entirely by Apple (App Store) or Google (Play Store). We do not receive or store your payment card details. RevenueCat notifies our server of purchase events via webhook, and we store your entitlement status (whether you have an active subscription or session pass, and its expiry) in Supabase to gate premium features.
RevenueCat may collect and process analytics data related to purchases and subscription lifecycle events. See RevenueCat's privacy policy for details.
2.6 Analytics, Usage Data, and Diagnostics
We collect analytics and diagnostics data to operate and improve Zapp. This may include:
- Usage events: Product interaction events (for example, onboarding completed, first game completed, paywall shown, purchase successful) to understand what's working and what needs improvement.
- Identifiers: An analytics identifier or internal user ID used for analytics and debugging. Not used for targeted advertising.
- Diagnostics: Crash logs and performance data to fix bugs and improve stability.
3. Purposes and Legal Bases
| Purpose | Legal Basis (GDPR) |
|---|---|
| Create and manage your account | Contract necessity (Art. 6(1)(b)) – to provide account-based functionality |
| Provide core gameplay functionality | Contract necessity (Art. 6(1)(b)) – to run game modes, compute AI results, and show history |
| Process AI requests | Contract necessity (Art. 6(1)(b)) – clues must be sent to AI to run the game |
| Store and sync your saved game sessions | Contract necessity (Art. 6(1)(b)) |
| Manage anonymous device usage limits | Legitimate interests (Art. 6(1)(f)) – to prevent unlimited anonymous AI calls without account creation |
| Process and verify in-app purchases | Contract necessity (Art. 6(1)(b)) – to fulfil purchases and unlock entitlements |
| Improve app performance and reliability | Legitimate interests (Art. 6(1)(f)) – analytics and diagnostics to improve Zapp |
| Security monitoring and abuse prevention | Legitimate interests (Art. 6(1)(f)) – protecting users and service integrity |
| Customer support and communications | Legitimate interests (Art. 6(1)(f)) or Contract necessity (Art. 6(1)(b)) |
| Comply with legal obligations | Legal obligation (Art. 6(1)(c)) |
4. Recipients and Processors
We use the following third-party service providers (processors) to operate Zapp:
- Supabase: Authentication (Supabase Auth), database (Postgres), and server-side logic (Supabase Edge Functions). All app data — accounts, game sessions, entitlements, and anonymous usage records — is stored on Supabase infrastructure.
- Microsoft Azure AI Foundry: Hosts the AI model used in "Convince the AI." Player clues and game context are sent to Azure for processing. Microsoft may process this data in accordance with their enterprise data processing terms.
- RevenueCat: Manages in-app purchase lifecycle events (subscriptions, consumable purchases, renewals, cancellations) and relays entitlement data to our backend. RevenueCat does not receive payment card information — that stays with Apple or Google.
- Apple / Google: Handle OAuth sign-in (Apple Sign In, Google Sign In) and payment processing for in-app purchases. We receive a user identifier and email from their OAuth flows; we do not receive passwords.
- PostHog: Product analytics to help us understand usage and improve features. We do not use PostHog for advertising.
We do not sell personal data to third parties. We do not share personal data with third parties for cross-context behavioral advertising.
5. International Data Transfers
Your data may be transferred to and processed in countries outside your country of residence, including the United States, where our service providers (Supabase, Microsoft Azure, RevenueCat, and PostHog) operate data centers.
For users in the European Economic Area (EEA), United Kingdom, or Switzerland: we rely on recognized transfer mechanisms used by our service providers (such as Standard Contractual Clauses) to facilitate lawful data transfers to countries without an adequacy decision.
You can request more information about international transfer safeguards by contacting us.
6. Data Retention
- Account data: Retained until you delete your account, subject to limited retention needed for security, fraud prevention, and legal compliance.
- Gameplay session data: Retained until you delete your account or request deletion. Aggregate statistics may be retained in de-identified form.
- AI clue data: Clues submitted to Azure AI Foundry are processed in real time and are not stored permanently on our servers after the AI response is returned. Microsoft Azure may retain data in accordance with their data processing terms.
- Anonymous device usage records: Retained for a limited period sufficient to enforce the anonymous play limit. If you create an account, the anonymous record is not linked to your account.
- Entitlement data: Retained while your account is active. Subscription status is updated in real time by RevenueCat webhooks.
- Analytics and diagnostics: Retained for as long as necessary to understand app performance and improve Zapp. Where feasible, we can delete or anonymize analytics data associated with your account upon request.
- Account deletion receipts: A limited audit record may be retained for a short period to confirm deletion was processed and prevent abuse.
7. Your Rights
Under GDPR and applicable US privacy laws, you may have the following rights regarding your personal data:
- Access: Request a copy of your personal data.
- Rectification: Request correction of inaccurate data.
- Erasure: Request deletion of your data ("right to be forgotten").
- Restriction: Request restriction of processing in certain circumstances.
- Portability: Request your data in a portable format.
- Objection: Object to processing based on legitimate interests.
- Withdraw consent: Withdraw consent at any time where processing is based on consent.
How to Exercise Your Rights
- Email: Contact us at retrospective.technology@gmail.com with your request. We may ask you to verify your identity before processing.
- In-app deletion: You can delete your account directly in the App via Settings → Delete Account. This removes your server-side account data and saved sessions, subject to limited retention described in this policy.
We aim to respond to data subject requests within 30 days, or as required by applicable law.
8. Account Deletion
You can delete your account at any time from within the App:
Settings → Delete Account
Account deletion triggers removal of your server-side account data, game session history, and entitlement records stored in Supabase. Some limited records may be retained for a short period for security, fraud prevention, backup integrity, and legal compliance as described in this policy.
If you can't access the app, you can also request deletion by emailing us from the email associated with your account.
9. Supervisory Authority (EU Users)
If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland and believe your data protection rights have been violated, you have the right to lodge a complaint with your local supervisory authority (data protection authority).
A list of EU/EEA data protection authorities is available at edpb.europa.eu. We encourage you to contact us first so we can try to resolve any concerns directly.
10. Security Measures
We implement appropriate technical and organizational measures to protect your personal data, including:
- Encryption of data in transit (TLS/HTTPS) for all API communication.
- Encryption at rest applied by our service providers (Supabase, Microsoft Azure) as part of their standard infrastructure.
- Authentication via Apple Sign In and Google Sign In (OAuth) — no passwords stored by Zapp.
- Supabase Row-Level Security (RLS) rules to restrict data access per user.
- Server-side purchase verification via RevenueCat webhooks — purchases are never trusted from the client alone.
- Regular review of access controls and security practices.
11. Children and Minors
Zapp is not intended for use by children under the age of 13 (or the applicable minimum age in your jurisdiction, such as 16 in parts of the EU). We do not knowingly collect personal data from children below these ages.
If you believe a child under the applicable age has created an account or provided us with personal data, please contact us at retrospective.technology@gmail.com. We will take steps to delete the data as soon as reasonably practicable.
12. California Notice
We do not sell or share personal information for cross-context behavioral advertising as defined under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA).
13. Automated Decision-Making
AI responses in Zapp (guesses and mascot reactions) are part of the game experience and do not produce legal effects or similarly significant effects concerning you. We do not use automated decision-making for account management, moderation, or any consequential decisions about users.
14. EU Representative
If required under Article 27 of the GDPR, we will designate a representative in the European Union and update this policy accordingly.
15. Purchases and Subscriptions
Zapp offers the following in-app purchases:
- Zapp Premium (monthly subscription): Unlimited gameplay at $4.99/month. Managed via RevenueCat and billed through the App Store or Google Play. You can manage or cancel your subscription at any time through your device's subscription settings.
- Session Pass (one-time purchase): 24-hour unlimited play at $1.99. Processed as a consumable purchase through the App Store or Google Play.
All billing disputes and refund requests for App Store purchases are handled by Apple; for Google Play purchases, by Google. Contact us at retrospective.technology@gmail.com if you experience issues with entitlement delivery.
16. Changes to This Policy
We may update this Privacy Policy from time to time. We will notify you of material changes by updating the "Last updated" date at the top of this page. Continued use of the App after changes constitutes acceptance of the revised policy.
17. Contact
For questions, requests, or concerns about this Privacy Policy or your personal data, contact us at: