PRIVACY POLICY

1. INFORMATION RELIVE PROCESSES

1.1 Journal Content You Create

Depending on how you use Relive, your local library may contain:

• Trip names, trip status, dates, time zones, and cover photos
• Moment timestamps
• Moment photos
• Notes you write
• Locations you choose to save, including location names, addresses, latitude, and longitude

This content is used to provide the travel-journal features you request, including timelines, photo views, calendar summaries, and the Atlas.

1.2 Information Collected Automatically

Relive uses Firebase services in the main app for limited product analytics and diagnostics.

1.3 Permissions and Device Features

Relive requests permissions only when relevant to a feature you choose to use:

• Camera – Capture a trip cover or moment photo after you choose Camera.
• Photo Library – Select existing photos through Apple's system picker.
• Location When In Use – Attach your current location to a moment when you request Current Location. Relive does not continuously track your location.
• Notifications – Schedule local upcoming-trip reminders only after you enable Notifications in Settings.
• iCloud / CloudKit – Synchronize the Relive library for verified Premium users who are signed into iCloud.

Relive does not request microphone, Contacts, Calendar, Health, Bluetooth, biometric, Always Location, background-location, or App Tracking Transparency permission.

2. HOW INFORMATION IS USED

Relive processes information only as needed to operate and improve the app, including:

• Creating, editing, displaying, organizing, and deleting your travel journal
• Generating local timelines, photo collections, calendar activity, trip summaries, and destination groupings
• Providing map and geocoding functionality when requested
• Providing Premium features and verifying StoreKit entitlements
• Synchronizing eligible Premium libraries through private iCloud/CloudKit
• Creating user-requested ZIP exports
• Scheduling local trip reminders when notifications are enabled
• Measuring product usage through privacy-scoped analytics
• Diagnosing crashes and technical problems
• Checking optional app-update metadata

Relive does not use your journal content to build advertising profiles.

3. LOCAL STORAGE, ICLOUD SYNC, AND EXPORT

3.1 Local Storage

SwiftData on your device is Relive's source of truth. Cover photos and moment photos are stored as app-managed data. Relive also stores lightweight preferences such as onboarding completion, theme selection, notification preference, cached Premium status, and sync-state metadata.

3.2 Premium iCloud Sync

For verified Premium users, Relive can open the library with Apple's private CloudKit-backed synchronization. The synchronized data can include trips, moments, notes, saved location information, dates, relationships, and image assets required to reproduce your library on another compatible device signed into the same iCloud account.

Apple controls CloudKit transport, scheduling, authentication, and the private iCloud database. Relive does not maintain a separate Firebase, Firestore, or custom server copy of your travel-journal content.

3.3 Export

Premium users can create a ZIP export containing metadata and images from the currently available Relive library. The export is created at your request and is placed under your control for sharing or storage. Once you export or share a file outside Relive, the destination you choose controls that copy.

4. THIRD-PARTY AND PLATFORM SERVICES

4.1 Firebase

The Relive main app uses Google's Firebase SDK family for:

• Firebase Analytics – Privacy-scoped product analytics
• Firebase Crashlytics – Crash and diagnostic reporting
• Firebase Remote Config – Optional configuration such as app-update discovery

Relive does not use Firebase Authentication, Firestore, Firebase Storage, Firebase Cloud Messaging, or an advertising SDK for the features described in this policy.

4.2 Apple Services

Relive also relies on Apple platform services, which are governed by Apple's own terms and privacy practices, including:

• iCloud and CloudKit for optional Premium synchronization
• StoreKit and the App Store for purchases, subscriptions, entitlement verification, and restore
• MapKit, Core Location, and Apple geocoding for location features
• Photos and Camera system interfaces for media selection and capture
• UserNotifications for local trip reminders
• WidgetKit and App Groups for the Relive widget and shared theme/widget state

Relive does not receive or store your payment-card information. Purchases are processed by Apple.

5. DATA RETENTION AND DELETION

• Your local Relive journal remains on your device until you edit or delete it, delete all app data, or remove the app/device data through system-level actions.
• If Premium iCloud Sync is active, local deletions are synchronized through Apple's CloudKit mirroring when the system processes those changes.
• Delete All Data removes the records currently known to that device and related local app data. Because CloudKit synchronization is asynchronous, Relive cannot promise an instantaneous, atomic wipe from every disconnected device at the exact moment you tap delete.
• Firebase analytics and diagnostic information is retained and processed according to the applicable Firebase service configuration and Google's policies.

Relive has no custom account database from which we can manually retrieve or delete your private iCloud journal on your behalf.

6. YOUR CONTROLS

• View and edit: You can view and edit your trips, moments, notes, photos, and saved locations in the app.
• Delete: You can delete individual content or use Delete All Data in Settings.
• Export: Eligible Premium users can export their Relive library in the supported ZIP format.
• Permissions: You can change camera, photo, location, and notification permissions in iOS Settings.
• Notifications: Relive notifications can be disabled from the app's Settings or iOS Settings.
• Premium subscription: Yearly subscriptions can be managed through Apple's subscription-management interface.

7. SECURITY

Relive is designed to minimize centralized storage of journal content by keeping the core library local and using Apple's private iCloud database for optional Premium synchronization. We use platform and service security mechanisms provided by iOS, iCloud/CloudKit, StoreKit, and Firebase. However, no electronic storage or transmission system can be guaranteed to be completely secure.

8. INTERNATIONAL PROCESSING

Firebase and Apple services may process technical, analytics, purchase, or synchronization data using infrastructure located in different jurisdictions. Their handling of that data is governed by their respective terms, privacy policies, and applicable law.

9. CHANGES TO THIS PRIVACY POLICY

We may update this Privacy Policy as Relive changes. The effective date at the top of this page will be updated when the policy changes. Where appropriate, material changes may also be communicated through the app or its App Store listing.

10. CONTACT