Privacy Policy
Last updated: 17 October 2026
This policy explains how Double Tap ("we", "us") handles your data. We designed Double Tap to process as little as possible by default and to keep your conversations off our servers, unless you explicitly choose otherwise.
1. The screenshot stays on your device — by default
By default, when you trigger Double Tap, the screenshot is captured by the iOS Shortcut and read using Apple's on-device text recognition (OCR). The image is never uploaded and never stored. Only the extracted text and your chosen "vibe" are sent onward to generate a reply.
If you turn on "Send raw screenshots to AI" in Account → Vision Replies, this changes: on-device text extraction is skipped, and the full screenshot image — exactly as it is, not just the extracted text — is uploaded to xAI to generate your reply. This feature is off by default, requires an explicit opt-in with its own consent screen before it can be turned on for the first time, and can be turned off again at any time in Account. Turning it off stops new screenshots from being sent, but a screenshot already sent before you turned it off cannot be retracted. See sections 3 and 4 below for what this means for third-party processing and retention.
A screenshot may include messages written by the other person in your conversation — and, if you have the vision-replies feature on, their photo and display name as they appear in the screenshot, too. You are responsible for ensuring you have the right to process that content.
2. What we process
- Conversation text — sent to generate a reply, and retained alongside that reply in your reply history so we can review and improve text-extraction accuracy.
- Generated replies — stored in your reply history, linked to your account, so you can review past replies in-app.
- Style profile — your preferred tones, language level, example messages, and expressions, stored to personalise the replies Double Tap generates for you.
- Account identifier — an anonymous user id, and (if you sign in) your email address or provider identifier.
- Usage metadata — a timestamp per request, to enforce free-tier quotas. Message content is not stored.
- Subscription status and device identifier — managed by RevenueCat to verify your subscription status across reinstalls and devices.
3. Third-party processors
- Supabase — hosting, authentication, and database (EU region).
- xAI (Grok API) — receives the conversation text to generate the suggested reply. If you have turned on "Send raw screenshots to AI" (Account → Vision Replies), xAI instead receives the full screenshot image, including anything visible in it — your match's messages, display name, and photo, for example. We use the API in a manner intended to exclude your content from model training; see xAI's API terms.
- RevenueCat — subscription management. Receives your account identifier and a device identifier (IDFV) to track and verify subscription status. See RevenueCat's privacy policy.
- Apple — App Store distribution, subscription payments, and (where offered) Sign in with Apple.
We do not sell your data and do not use your conversations to advertise to you.
4. Retention
Screenshots: never stored, unless you have turned on "Send raw screenshots to AI". When that feature is on, the screenshot image is stored for up to 30 days after it is sent, solely to support revising a reply, and is then automatically deleted. Deleting your account also deletes any screenshots stored for it immediately. Conversation text: retained alongside the generated reply in your reply history until you delete your account. Generated replies: stored in your reply history until you delete your account. Style profile: stored while your account is active. Account and usage metadata: kept while your account is active and deleted on account deletion (subject to legal retention obligations for billing records).
5. Your rights (GDPR & similar)
You may request access to, correction of, or deletion of your data, and you may delete your account in-app at any time. Contact fredericmamath@gmail.com. Data is processed in the EU.
6. Children
Double Tap is intended for users aged 17 and over. It is not directed at children.
7. Changes
We may update this policy; material changes will be reflected by the date above.