Privacy policy

1. Operator and contact

IKARU is operated by Unlimitive Media. For privacy questions, account requests, or data-rights requests, contact contact@unlimitive.com. This policy covers the IKARU app and the public website pages; external services have their own notices.

2. Information you provide

Depending on the features you use, we process an account email address, an authentication credential handled by Supabase Auth, an optional display name, public handle and avatar, settings, and messages you send to support. We also process the trip content you create or sync, such as trips, destinations, itineraries, packing lists, tasks, private notes or journal entries, language-learning progress, reminders, feedback, public profiles, ratings, follows, and sharing choices.

3. Local-first planning and device storage

Guest and local-first features can keep planning state on your device, including trips, packing data, itineraries, language-learning state, and references to local photo-library assets. The photo-to-route flow reads photo dates and location metadata on the device to suggest editable trip evidence. Running that scan does not by itself upload your photo library or its metadata to IKARU. Local data can be removed by deleting it in the app where supported, clearing app storage, or uninstalling the app; device or platform backups may be governed by your device provider.

4. Accounts, sync, and cloud data

When you sign in, IKARU uses Supabase Auth, database services, Edge Functions, and Storage to authenticate you and provide account-backed sync and collaboration. Data is sent to the cloud when the relevant account or feature requires it, including profile data, trips, collaboration records, planner conversations, selected media, and related app state. Access is restricted by the app and backend policies, but no online service can be guaranteed to be completely secure.

5. Public profiles, trip sharing, and family links

You choose whether to publish a profile, itinerary, rating, or other social information. A family-share link is a bearer link: a person who obtains it may open the bounded, read-only trip view without an IKARU account or app installation. The view can include the trip name, destination and dates, bounded route notes, selected photos or Journey media, and optional shared location; it does not expose the packing list, private notes, documents, or the whole local photo library. Recipients can copy, screenshot, or forward what they can see. The service enforces a minimum link expiry of 30 days, and a trip end date can extend that minimum to at least seven days after the end date; you can revoke a link sooner.

6. Location sharing

The native app requests location permission before using device location. If you explicitly enable trip or social location sharing, the app may collect location in the foreground and, subject to your operating-system permission and settings, while the app is running in the background. The feature requires a signed-in account and premium access; visibility can be off, friends-only, or public-approximate. The service receives exact and coarse forms with capture and expiry times: accepted friends may receive exact location where the access rules allow it, while public views and family links receive coarse location. The client requests roughly ten-minute freshness and the backend bounds live-location expiry to no more than fifteen minutes for live reads. A family view may show a stale status for a last-known coarse value updated within the preceding 24 hours. Turning sharing off deletes the active live-location row, but expiry and deletion do not describe provider backups or every downstream retention period.

7. Health data, photos, media, and camera features

If you choose to connect Apple Health on iOS or Health Connect on Android, IKARU requests read-only access to your step count. It uses step-count data to calculate travel-step totals for your saved travel days and trips and to show statistics in travel stats, trip recaps, and profile or comparison surfaces. Raw HealthKit and Health Connect samples stay on your device and are never uploaded by IKARU. For signed-in users, IKARU may store one aggregate step total per device and trip, together with the trip scope, platform, and device identifier needed to replace and combine totals across devices, in Supabase. That aggregate may appear in a public profile or a comparison visible to friends only according to your profile and sharing settings. IKARU does not read, write, change, or collect other Apple Health or Health Connect categories through this feature. You can decline or revoke access in your device settings.

The app can read selected photo-library metadata on-device for trip suggestions. An image is uploaded only when you choose a cloud feature such as a public avatar, family photo sharing, or Journey media. The associated cloud record may contain a caption, capture time, trip or stop reference, country, and optional coordinates, together with a visibility choice. Image access uses short-lived signed URLs; the current app requests five-minute URLs. The translator camera uses on-device text recognition and on-device translation, and a generated travel-stats card is saved to your device only when you request it.

8. AI assistance, search, maps, and audio

When you use the Trip Assistant, the app sends your prompt or message and the bounded trip context, history, or state needed for the request to a Supabase Edge Function. Signed-in assistant conversations and generated planning results can be stored in your account-backed planner records; guest requests send the guest history and state with the request rather than creating a signed-in conversation. Text generation and automatic audio transcription use Google Gemini through the backend. Planning requests can also use Google Search, Google Maps grounding, and Mapbox geocoding. Recorded audio is sent as a request for transcription; the current app code does not store raw audio in its own planner tables. Do not send information to the assistant that you would not want processed by these services. Provider retention, training use, and processing locations are controlled by the providers and are not promised by this policy.

9. App diagnostics and website measurement

Release builds of the app enable Firebase Analytics for product events, Firebase Crashlytics for crashes and error reports, and Firebase Performance for performance traces. These services may receive app, device, version, event, crash, and performance metadata; the app event adapter is designed not to put message or trip content into event parameters. On ikaru.app, the site initializes Google Consent Mode with storage denied by default, loads the Clickio consent platform, and uses GA4 measurement only within that consent-controlled setup. The website also stores small local preferences such as locale and consent state and does not request browser geolocation.

10. Purchases, premium access, and eSIM connectivity

If you purchase premium access in the app, the Apple App Store or Google Play handles the transaction and RevenueCat supplies the purchase and entitlement layer used by the app. The app can associate a RevenueCat customer with an account identifier and, when available, an email address or display name; the app also receives entitlement status and a management link. Supabase stores an entitlement mirror used for access checks. Payment-card details are handled by the store or payment providers rather than entered into IKARU. Prices, renewal terms, cancellation, and refunds are shown or managed through the applicable store and its policies.

If you buy an eSIM or data top-up through IKARU, we process the selected package and currency, order and payment/provisioning status, optional trip or traveler reference, support or refund information, and the eSIM profile and usage details needed to deliver and manage connectivity. This can include an ICCID, installation instructions, activation and status data, data/voice/SMS allowances, and remaining usage. Stripe processes eSIM payments; card details are handled by Stripe and are not entered into IKARU. The Airalo connectivity provider receives information needed to provision the eSIM and, where applicable, deliver installation instructions or process usage, top-up, or refund requests. IKARU may retain support messages and diagnostics linked to the order to handle support. The website hosted checkout may use a technical anonymous account and a delivery or access email; this is not an IKARU customer login. Provider, payment, and email services have their own notices and retention rules.

11. Retention and deletion

Local data remains in the app’s device storage until you remove it or the device removes it. The in-app Delete account action calls a server function intended to remove the authentication user, account-backed records, public profile and avatar, live-location records, family-share data and objects, planner records, entitlement mirror, and other linked rows covered by the current deletion function. You can also disable location sharing, revoke share links, remove uploaded media, and sign out. Share-link expiry, five-minute media URLs, and live-location expiry limit access; they are not a promise that every database row, log, provider copy, backup, purchase record, or legal record disappears immediately. The current code does not establish one universal retention schedule for every provider, so we do not publish a fixed period that the implementation cannot verify.

Account deletion also targets linked aggregate health-step data and, where covered by the current account schema, eSIM orders, profiles, plans, refunds, and support records. The website’s anonymous eSIM checkout identity and Stripe, Airalo, email, and other provider records are separate and may remain under their own policies.

12. Your choices and privacy requests

You can use guest mode, manage account and sharing settings, disable location sharing, revoke links, remove content where the feature provides it, and request account deletion from Settings. You may email contact@unlimitive.com to request access, correction, deletion, restriction, objection, portability, or other rights available under the law that applies to you. We may ask for information needed to verify the request and protect the account. Website consent choices can be revisited through the Clickio consent controls.

13. Children

IKARU is not designed as a service directed to children. We do not knowingly ask children to create accounts or submit personal information. If you believe a child has provided personal information, contact contact@unlimitive.com so we can review the situation under the law that applies.

14. International processing, security, and updates

IKARU depends on services that may process information in countries different from where you live. The current repositories do not establish a complete, permanent list of provider regions, subprocessors, backup periods, or transfer mechanisms, so this policy does not invent those details. We use access controls and the protections provided by the relevant platforms, and we update this page when the product or its processing changes. The date above identifies the current version of this page.