Relive is a local-first personal memory timeline. This policy explains what information the current Relive app handles, where it is stored, and when it may be sent to a third party. Please replace the placeholders in this document before publishing it.
1. Information you provide
You may create Moments containing titles, text, creation and update times, favorite status, tags, custom-timeline assignments, and optional location information. The current location flow supports a location label or other readable place details entered for a Moment. Relive does not currently implement an active GPS acquisition, reverse-geocoding, background-location, or separate location-history feature.
2. Media and Moment data
When you choose to add them, Relive stores photos, videos, and audio as attachments to Moments. The current implementation stores the media files in Relive-managed device storage and stores references to those files in the local database. Android-initiated shares are copied into temporary Relive-owned files while you decide whether to keep the Moment; cancelled or invalid shares are cleaned up by the share flow.
3. Device permissions
Depending on the feature and platform, Relive may request access to the camera to capture photos or videos, the microphone to record audio, and the photo or document library to import selected media. Android may request notification permission for optional Rediscover reminders. The current app does not request location permission because GPS capture is not active. You can deny permissions, although the related feature may not work.
4. Local storage and deletion
Relive’s archive database, preferences, and Relive-managed media are designed to be stored on the device. There is no Relive account, Relive-hosted backend, or general-purpose cloud synchronization implemented in the repository. You can delete individual Moments and their attached data in the app, or delete the app and its local data using your device’s normal controls. Device and operating-system backups may follow separate rules that Relive does not control.
5. Backups and restore
The current Android implementation can optionally package the local archive, including Moment data and Relive-managed media, and upload it to the Google Drive App Data area after you connect a Google account and authorize the requested Drive scope. Relive can discover and restore that backup. Scheduled automatic backup is a Relive Pro feature; manual backup and restore are available independently of that entitlement in the current product specification. No separate user-facing export feature is verified in the repository reviewed for this policy. The iOS backup implementation is not active in the repository reviewed for this policy. Google processes information under its own terms and privacy policy.
6. Purchases and RevenueCat
Relive uses RevenueCat’s SDK to present, purchase, restore, and check access to Relive Pro. Relive Pro is represented by the relive_pro entitlement and currently has monthly, yearly, and lifetime purchase options. RevenueCat and the relevant Apple App Store or Google Play billing platform may process purchase, subscription, transaction, and related app/device information needed to provide these services. Relive does not receive your payment card details through the app. Review RevenueCat’s privacy policy and your store’s privacy information for their practices.
7. Third-party services
The repository reviewed for this policy contains integrations for RevenueCat purchase services and, on Android, Google Identity Services and Google Drive App Data backup. It does not contain an analytics, advertising, crash-reporting, AI, or recommendation-backend integration. This statement describes the current repository and should be updated if the app’s integrations change.
8. Retention
Relive retains local archive data until you delete it, delete the app’s data, or replace it through a restore operation. A Google Drive backup may remain in your Google account until you delete it or it is replaced or removed by the backup flow. RevenueCat and app stores retain transaction and subscription records according to their own policies and legal obligations. The repository does not define a separate server-side retention schedule for Relive.
9. Security
Relive uses platform storage, operating-system permission controls, device authentication features, and HTTPS-based third-party SDK or service connections where applicable. No method of storage or transmission can be promised to be completely secure. Protect your device, Google account, and any exported or backed-up files.
10. Children’s privacy
Relive is not directed to children under 13, and we do not knowingly collect personal information from children through a Relive account. If you believe a child has provided information to a service used by Relive, contact us at the address below.
11. Changes to this policy
We may update this policy when Relive’s features, integrations, or legal requirements change. We will post the revised policy at this URL and update the effective date. Your continued use of Relive after an update means the revised policy applies to future use.
12. Contact
Questions about this policy can be sent to vs9109807@gmail.com.