Your trips
stay private.

What the app collects

Nothing. RelicPack does not send the developer your name, email address, trips, bookings, documents, costs, location, contacts, advertising identifier, diagnostics or usage analytics. There is no RelicPack account to create. The only server the developer runs for the app is the optional Premium Google place search described under Outside services, and it keeps no record of what you search. The app's privacy manifest declares no tracking and no collected data types.

What stays on your device

Your trips live in a single database in RelicPack's own storage, with attached PDFs and images kept beside it so they open offline. Its widgets and share extension can read that storage; nothing else can. Items in the Inbox are not synced to iCloud. They leave the device only if you export them or let an AI assistant on your Mac read them.

When you add a photo, screenshot or scanned PDF, its text is read on your device, and when RelicPack offers to translate an Inbox item, Apple's Translation framework does it on your device. On a shared trip, Recent Updates keeps a list of changes, who made each one and what it changed, for 60 days and on this device only.

RelicPack does not ask for access to your location, camera or contacts. Photos come through the system picker, so the app sees only the ones you choose, never the rest of your library. It asks for Calendar access only when you choose a calendar for a trip or import events from Calendar.

iCloud sync and partner sharing

Sync is off until you turn it on, start sharing a trip or accept an invitation. Sharing needs sync, so starting or joining a shared trip switches it on for your whole library. When it is on, your trips are kept in your private iCloud database through Apple's CloudKit.

Sharing a trip sends a private iCloud invitation, which shows the trip's name, by Messages, Mail or a link you copy. RelicPack never sees the link. A shared trip is stored in its owner's iCloud and counts against the owner's storage, and everyone in it sees its bookings, notes, checklists, documents and travel log. Apple holds this data under its own privacy policy. The developer cannot read it. Sync and sharing are still being tested on real devices and are not yet switched on in every build.

Outside services

Airport search works from a catalogue bundled with the app and makes no network request. Place suggestions, place search, saved directions, Maps links you save and the app's maps use Apple Maps, and an Apple Maps link that reaches the Inbox is looked up there. Suggestions are requested as you type in a place field, and none of it needs location permission. When a web link reaches the Inbox, however it arrives, RelicPack fetches that page once to read its title and description, following up to three redirects. For a saved video or post it also downloads the preview image and keeps it with the card. These fetches carry no cookies and are not repeated.

Google place search is optional. With Premium, your search text, the area you are searching and your device's language go to a RelicPack server, which checks your purchase with Apple and passes the search to Google. A Google Maps link saved to the Inbox is looked up the same way, with Premium or with your own key and the Settings option on. The server runs on Cloudflare and keeps no logs of its own. To enforce usage limits it stores only counters under keyed one-way hashes, and they expire within a day. If you use your own Google API key instead, searches go from your device straight to Google, and the key stays in your device's Keychain. Google handles searches under its own privacy policy.

Apart from Apple's services (iCloud, Maps, Siri and the App Store), your calendar account if you publish to it, the fetches and searches above, and any AI assistant you connect on a Mac, nothing reaches the network.

Apple Calendar

Nothing goes to Calendar until you choose a calendar for a trip in its settings, or one for new trips in Settings. It can be any calendar you can write to, or a RelicPack calendar in the account you choose. RelicPack then publishes that trip's bookings there: titles, places, times, links and the trip's name, with item notes only if you switch them on, and trip legs as all-day events only if you turn that on. Anyone who shares that calendar sees them, and your calendar account syncs them under its own policy. Travel log entries are never published.

If you change or delete a published event in Calendar, RelicPack leaves it alone until you choose whether to update the trip, put its version back or stop publishing that booking. To import, you browse events from the calendars you choose, on your device, and only the ones you pick are added.

Siri, Shortcuts, widgets and Spotlight

The Today, Next Up and Timeline widgets read your trips from RelicPack's storage on the device. Next Up can appear on the Lock Screen, and Timeline shows a booking reference for an item that has no place.

Siri and Shortcuts can open trips, tell you what's next or a day's plan, add items, log entries and checklists, and save to the Inbox. Trip names are made available to Siri so you can use them in requests. A shortcut you build can read an item's details, including its booking reference and notes; the actions that read out a day or a trip include those only if you turn on Include Private Details. Showing trips in Spotlight is off until you turn it on, and then adds trip and booking names, places and times to your device's search index, never notes, booking references or costs.

AI assistants on your Mac

On a Mac you can let an AI assistant app, such as Claude, read your trips and, if you choose Read and add, add trips, items, checklists and Inbox entries. It is off until you turn it on in Settings, under Siri, Shortcuts & AI, and assistants can never edit or delete anything. It works only on that Mac. macOS asks before each app can control RelicPack, and RelicPack asks for Touch ID, your Apple Watch or your password before it answers a new connection; approval ends after the time you choose, and whenever your Mac locks or sleeps.

By default an assistant can read notes, costs, contact details, who you're with, checklists and tags, but not booking references, and you choose which in Settings. What it reads, including the titles and links of Inbox items, leaves your Mac in that assistant's conversation and is handled under its provider's privacy policy. A list of what assistants have added stays on the Mac until you clear it.

Backups, exports and other apps

The Markdown mirror is off by default and writes only to the iCloud Drive folder or the folder you choose. It copies everything, including your travel log and attachments. Other exports go through the share sheet or a save dialog, and only where you send or save them: a trip as a spreadsheet, Markdown, a PDF or a calendar file, costs as a spreadsheet, documents as a folder, the Inbox, a one-time export of everything, and plain-text itineraries. A sent itinerary never includes your travel log, and leaves out booking references, costs, notes, phone numbers and links, who you're with and checklists unless you switch each one on.

If you turn them on in Settings, meals can go to the Restauranteer app through a vault folder you choose, and text to the Orbari app through the share sheet.

Purchases

RelicPack Premium is handled by Apple through the App Store, and the app checks your purchase on your device. The developer never receives your payment details, and receives nothing about your purchase unless you use Premium Google place search: each search then carries the App Store's signed proof of purchase, which the server confirms with Apple. If a purchase is refunded or Family Sharing changes, nothing you have saved is removed.

This website

This website counts visits with Simple Analytics, a privacy-first service that sets no cookies, keeps no personal data and does not fingerprint your browser. Its requests go through a.adamxweb.com, so your IP address is not sent to Simple Analytics, and browsers that ask not to be tracked are not counted at all. There is no advertising. If you submit feedback, it stores the information you enter: a bug report or idea, optional device and app details, and an optional reply email or display name. Bug reports and new ideas are private to the developer unless an idea is reviewed, stripped of personal details and published to the roadmap. Approved roadmap comments and their display names are public. Anonymous votes use a random browser cookie so the same browser cannot vote twice. If you ask for news, your email address is held by Resend, the service that delivers it, and only after you confirm it from a link; nothing is kept before then. It is used for RelicPack news alone, never shared or sold, and opens and clicks are not tracked. Every email carries an unsubscribe link, which removes the address.

Spam protection and hosting

Cloudflare Turnstile processes ordinary technical information needed to distinguish people from automated abuse. Raw IP addresses are not stored in the feedback database; a short-lived, keyed identifier is used only for submission limits. Cloudflare and the hosting provider may process request information under their own operational policies.

Feedback retention

Feedback is kept while it is useful for investigation, support and product planning, then removed when it is no longer needed. Do not include booking references, passport details, travel documents or other sensitive information in a report. You can request deletion of a submission by quoting its reference number in a support request.

Your control

From inside the app you can turn sync off, stop sharing a trip, remove a partner or leave a trip someone shared with you. You can stop publishing a trip to Calendar or leave out its notes and legs, turn off Spotlight, AI assistant access and the translation offer, choose what assistants may read, stop the Markdown mirror and the Restauranteer and Orbari handoffs, clear your export history and the list of assistant additions, delete items forever from Recently Deleted, and remove your Google API key.

Deleting RelicPack removes its local data from that device. Events it published stay in Calendar, so stop publishing first if you want them gone, and remove your Google API key in Settings if you added one. Anything synced stays in your iCloud, where you can manage it from iCloud settings, and anything mirrored stays in the folder you chose. The unsubscribe link in any news email removes your address.