Privacy Policy

Re:vive — Last updated: September 20, 2026

1. Data That Stays on Your Device

Re:vive stores all of your data locally on your device. The following data is created and stored only on your device and is never uploaded to or stored on our servers:

• Imported chat histories — conversations you bring in from WhatsApp, KakaoTalk, LINE, or (on iPhone) a screen recording of iMessage/SMS are parsed and stored locally.
• AI-generated conversations — Your chat history within Re:vive is stored locally.
• Conversation memory and embeddings — Vector databases used for memory recall are created and stored locally. Embedding generation always happens on-device. For some languages, Apple's on-device language model used for this is downloaded from Apple the first time it is needed — only the model comes down, and none of your conversation goes up. On Android, the optional language packs (small embedding models for Korean, Japanese, or English) are delivered through Google Play the same way: only the model comes down.
• Style profiles and relationship data — Analysis of conversation patterns remains on your device.
• User preferences and settings — Your name, preferences, and app settings are stored locally using standard iOS or Android app storage.

2. Bringing In Your Conversations

Re:vive can bring in a conversation in two ways. Either way, what you hand over is read on your device and is never uploaded to us.

• Exported chat files — a .txt or .zip export from WhatsApp, KakaoTalk, or LINE. You can pick the file inside Re:vive, or send it to Re:vive from another app's share sheet.
• Screen recordings (iPhone only) — Apple does not let apps export iMessage or SMS history, so for those you record your Messages screen and hand Re:vive the video. Re:vive reads the text off the video frames on your device using Apple's built-in text recognition. The video itself is never uploaded anywhere. Re:vive keeps only the text it read — its copy of the video is deleted as soon as reading finishes, and a copy left behind by an interrupted import is cleared the next time you open the app.
• Your photo library — when you pick a recording or a photo, iOS or Android shows its own picker and hands Re:vive only the one item you chose. Re:vive cannot browse or see the rest of your library.
• On Android, Re:vive reads only the export file you pick or share to it. It does not read your SMS/MMS messages, contacts, call logs, or other apps' data, and it asks for no such permissions.
• Text read from a recording is treated exactly like any other imported chat — stored on your device, and, if you have turned Cloud AI on, small relevant excerpts may be sent to generate a reply (see Section 3).

3. Cloud AI (Optional, Consent-Based)

Re:vive can generate replies using Google Gemini through our secure relay server ("Cloud AI"). This mode is off until you explicitly agree to it in the app, and you can turn it off at any time in Settings → AI Engine. When Cloud AI is enabled:

• What is sent: the message you type, recent messages from your current Re:vive chat, photos you explicitly choose to share in a chat (resized on-device before sending), and small excerpts of your imported conversation that are relevant to the reply (selected on-device), together with persona style instructions, and a random per-install identifier used only to enforce usage limits and prevent abuse (it is not linked to your name or any account). This is the minimum needed to generate a reply.
• What is never sent: your full imported chat archive, your contacts, your photo library (only individual photos you pick to share are sent), or anything from conversations you are not actively chatting in.
• How it is used: solely to generate the reply. Content is processed transiently and is not stored on our server. Our server logs contain only technical metadata (status codes, message counts) — never your message content.
• No AI training: requests are processed via Google's paid API tier, which per Google's API terms does not use your data to train AI models.
• Security: all data is transmitted over encrypted connections (TLS).
• If you decline or turn Cloud AI off, replies are generated entirely on-device using Apple Intelligence (supported iPhones) or Gemini Nano (supported Android devices), and nothing is sent to any AI service.

4. Device Backup (iCloud / Google)

If you have iCloud enabled on your device, Re:vive may back up your conversation data to your personal iCloud account. This is handled entirely by Apple's iCloud infrastructure.

• iCloud backups are encrypted and managed by Apple.
• We do not have access to your iCloud data.
• You can disable iCloud backup for Re:vive in your device's Settings.

For more information on how Apple handles iCloud data, please refer to Apple's Privacy Policy.

Android. If Google's automatic backup is enabled on your device, your imported conversations (message text and timestamps) and app settings may be included in your device backup to your Google account. Photos you attach in chats and the on-device memory index are excluded. Backups are encrypted and managed by Google; we do not have access to them. You can turn off backup for Re:vive in Android Settings → Google → Backup. See Google's Privacy Policy.

5. Third-Party Advertising

Re:vive displays ads to free-tier users through Google AdMob. In connection with serving ads, the following may apply:

• Google AdMob may collect device identifiers, IP address, and general usage data for ad personalization and analytics.
• Ad data collection is governed by Google's Privacy Policy.
• You can limit ad tracking through your device's Settings → Privacy & Security → Tracking (iOS), or Settings → Privacy → Ads (Android), where you can also delete or reset your advertising ID. The Android app uses the advertising ID only for AdMob.
• Consent in the EEA, UK, and Switzerland (Android). Before any ad is requested, the app shows a consent form provided by Google's User Messaging Platform. You can consent, refuse, or manage options per purpose, and change your choice at any time in Settings → "Ad privacy options". If you do not consent, ads may still be shown but are not personalized.
• Premium subscribers do not see ads, and no ad-related data collection occurs for premium users.

6. Subscriptions & Purchases

Premium subscriptions and purchases are processed by Apple (iOS) or Google Play (Android) and managed with RevenueCat, a subscription management service. We never see or handle your payment details — those stay with Apple or Google.

• RevenueCat receives your purchase and subscription status (for example, which plan is active and when it renews) along with a randomly generated app user ID and basic device information.
• This ID is not linked to your name, email, or any contact information, and we do not use it to identify you personally.
• This is used only to unlock Premium features, restore your purchases on a new device, and keep your subscription status accurate.
• Apple or Google Play may send subscription events (renewals, cancellations, refunds) to RevenueCat on our behalf so your access stays correct even when the app is closed.

7. Data We Do NOT Collect

To be clear, we do not collect, store, or retain:

• Your imported conversations, whatever app they came from
• The screen recordings you import — the video never leaves your device, and Re:vive's copy is deleted after it is read
• Messages you send or receive within Re:vive (when Cloud AI is enabled, message content is processed transiently to generate a reply and is never stored — see Section 3)
• Names, phone numbers, or contact information
• Your SMS/MMS messages, contacts, or call logs (Android)
• Photos, media, or attachments
• Your location data
• Your payment details (card numbers, billing information) — these are handled entirely by Apple or Google Play
• Any personal information beyond what is described above

8. On-Device AI Processing

When Cloud AI is off (the default until you consent), Re:vive uses Apple Intelligence (on-device Foundation Models) on supported iPhones, or Google's Gemini Nano on supported Android devices, to generate AI responses. This means:

• All AI processing happens on your device — nothing is sent to external servers.
• No conversation data leaves your device for AI processing.
• Apple's and Google's on-device models run without an internet connection.

On devices that support Apple Intelligence, on-device processing is also used as an automatic fallback whenever Cloud AI is unavailable (for example, offline).

Android. Gemini Nano is available only on devices Google supports, and the "On-device AI" option appears in Settings → AI Engine only on those devices. When Cloud AI is off, replies are generated on-device there. Turning the option on additionally lets the app fall back to on-device generation when Cloud AI cannot be reached. Gemini Nano handles text only; photos are never processed on-device.

9. Children's Privacy

Re:vive is not intended for children under the age of 13. We do not knowingly collect any personal information from children.

10. Your Rights (EEA, UK, and Elsewhere)

Re:vive is available worldwide. Wherever you live, most of your data never leaves your device, so there is little for us to hand over — but the rights below still apply to what we do handle.

• Who is responsible — FatTail Labs is the data controller for Re:vive. You can reach us at fattaillabs.ceo@gmail.com.
• Why we may process data — Cloud AI runs on your consent, which you give before first use and can withdraw any time in Settings → AI Engine. Ads and subscription handling rest on our legitimate interest in operating a free tier and on performing the contract you entered when you subscribed.
• Your rights — you may ask us for access to, correction of, deletion of, or a copy of any personal data we hold about you, object to or restrict how we use it, and withdraw consent at any time. Write to the address above and we will answer within one month.
• Deleting your data yourself — because everything is local, deleting the app removes your imported chats, memories, and settings from your device. If iCloud backup is on, remove Re:vive's data in your device's Settings → iCloud as well; on Android, delete the app's backup under Settings → Google → Backup.
• Where data goes — when Cloud AI is on, the small excerpts described in Section 3 travel to our relay server hosted on Google Cloud in Seoul, South Korea, and from there to Google's Gemini API. These transfers outside the EEA and the UK rely on the European Commission's Standard Contractual Clauses that Google Cloud applies to its customers. Content is processed transiently and is not stored.
• How long we keep things — we keep no conversation content at all. Server logs hold only technical metadata (status codes, message counts) and are kept no longer than our hosting provider's default log retention, currently 30 days. Purchase records held by RevenueCat last as long as your subscription plus the period Apple, Google, and tax law require.
• Complaints — if you are in the EEA or the UK you may complain to your local data protection authority. We would rather hear from you first so we can put things right.

11. Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be reflected on this page with an updated revision date. Material changes — such as the introduction of Cloud AI — are also disclosed in the app and require your consent before taking effect for your account. Continued use of Re:vive after changes constitutes acceptance of the updated policy.

12. Contact Us

If you have any questions about this Privacy Policy, please contact us at:

fattaillabs.ceo@gmail.com