Photos and scrapbooks

With your permission, Relive reads the photos you grant access to and information such as when and where they were taken and which camera took them. It uses this information to organize trips, identify places, and choose cover photos. To choose covers, pick photos for the widget, and give a reminder before you share, Relive checks on your device whether a picture shows faces. It only tells whether faces are there. It does not recognize who they are or keep any face data. Photo analysis and scrapbook organization happen on your device, including captions written for trips by on-device Apple Intelligence on supported iPhones. Your scrapbook, edits, and cached data are stored on your device.

What you enter in Relive, such as where you grew up and your birth year when you first open the app, names you give places, corrections, the answers you give to its questions, and anything you write, is stored on your device. If you turn on Sync to iCloud in Relive’s Settings (it is off by default), it is synced to your own iCloud (your private CloudKit database), so it is also on your other devices and on a new iPhone signed in with the same Apple Account. Only your Apple Account can access it. The developer can’t see it and it is not sent to the developer; Relive has no server of its own. If sync is off, or you’re not signed in to iCloud, it stays on this device only. If iCloud Backup is on for your iPhone, it is included in your device backup. Copies of photos you added and the widget’s thumbnails are not. If this device signs in to iCloud with a different Apple Account, Relive stops syncing and asks you first, and saves what is on the device into that account only if you agree.

Only what you write and answer is synced, not your photos: photos are never uploaded, and the scrapbook itself isn’t uploaded either, because each device organizes it from its own photos. If you haven’t given Relive photo access and add a photo through the system photo picker, Relive keeps a copy of it on this device, and that copy is not synced.

The On This Day and This Year widgets use a small local cache of thumbnails (about 400 pixels on the longest edge, plus one of about 800 pixels when a large On This Day widget is added) and display details. Relive keeps it in shared storage for the app and widgets on this device, excludes it from backups and sync, and replaces it as widget content updates. By default, widgets only use photos in which no face was detected. You can turn on Photos with People in a widget’s settings; when you turn it off, Relive deletes the thumbnails it made for it. Lock Screen widgets show only text, which people near you may see.

If you turn on reminders or add the widget, Relive checks for new photos in the background when the system allows, to tell whether a trip has ended and to update the widget. The check happens on your device and no data is sent. Reminders are local notifications created on your device and do not pass through any server. They include the destination city, the trip number, and the photo count, and can appear on the Lock Screen. Names you gave and text you wrote never appear in reminders.

If a photo’s original is only in iCloud Photos, Relive can request it through Apple’s Photos framework. When you save a share image, Relive adds it to your photo library. You can also send the image through the system share sheet. The service you choose handles the image from there.

Export and import

In Settings → Export and Backup you can export your scrapbook as a PDF or long images, and export everything you wrote as a data file. The data file holds all of it, including what you marked as not to bring up again and the names you gave places. It has no photos. You keep and send these files yourself. Relive never sends them to anyone.

Place lookups and purchases

When online, Relive sends latitude and longitude rounded to the nearest 0.1° to Apple Maps to look up city or region names. Relive uses exact photo coordinates to organize photos on your device.

When online, the scan animation and the map download map tiles from Apple Maps for the places you have been, including the area around your home. Only map data is downloaded. No photos are sent.

Apple’s App Store handles purchases and restores for the full version. Relive uses the purchase status from StoreKit to unlock features. The developer never sees your payment information. The full version supports Family Sharing. Only the purchase is shared. Each person’s scrapbook is made from the photos on their own phone, and family members can’t see each other’s.

TestFlight beta feedback

If you install Relive through TestFlight and opt in to beta reports, a Feishu group bot delivers the reports to the developer’s feedback group, where they are stored on Feishu’s servers and only the developer can see them, to help improve how Relive organizes photos. Reports may include a random tester ID, device model, iOS and app versions, photo counts and other statistics, the phone and camera models found in your photos and how many photos each took, your phone’s region setting, your system language (without region), trip dates and distances, summaries of how Relive organized your photos and what you corrected, and any feedback you choose to write. Days whose photos look like ones someone sent you, and the weeks you lived somewhere away from home, are reported only as dates, numbers of days, and distances, never where they were; answers to question cards are reported only as the kind of card, its date, and what you chose. Days out near home are reported only as their year, number of days, number of photos, and distance from home rounded to 10 km, never where they were.

Reports may also include: the state of your phone, including battery level and whether it’s charging, Low Power Mode, thermal state, network type, text size, Dark Mode, Bold Text, Reduce Motion and whether VoiceOver is on, and whether an iPhone Duo is unfolded; how many photos, videos, Live Photos, screenshots, and RAW photos your library holds; which widgets (On This Day, On This Day on the Lock Screen, This Year) you added and their sizes, and whether a widget is set to show photos with people in them; which pages you opened, how long you stayed on each, and how long each step of the first launch took; how often features were used, such as lines written, covers changed, exports and imports, and times the paywall appeared, and how much the reveal, the map, chapter suggestions, and question cards showed and how much you answered, how many days out near home you counted as trips or took off, how often you changed second photos and chapter covers, how many memories Turned Up showed on an iPhone Duo, what you tapped, whether its switch is on, how many memories it can choose from, and whether this device has shown two panes, and where the invitation to notifications appeared, what you tapped, and what you answered in the system’s permission prompt; which choice you picked when asked which city you live in, and whether it was the first place found in your photos (never the city); which phones (models and photo counts) took photos in the same period, which is why you were asked which phones are yours; how often you opened Relive from a widget and chose not to bring something up again on the page it opens, how many of On This Day’s next 14 days were filled from each tier, and how many photos it left out because a face was detected; how often each kind of strip on everyday pages was opened; how long each step in the app took and how much memory it used; whether you’re signed in to iCloud, how many records were synced, the types of sync errors, how often each sync status appeared in Settings, and what you chose when asked about a changed iCloud account; the number of records of each kind and a check value for each (a string that reveals nothing of their content, used to tell whether two devices hold the same data); Apple MetricKit’s daily summaries of crashes, hangs, and launches, with call stacks limited to module names and offsets, and totals of CPU time, data downloaded, data written and memory used; the system’s error codes when a photo can’t be loaded (codes only, no photos or file names); how many problems Relive’s own checks found and how it last quit; which items of the beta checklist you ticked, and how many of the trips and events you listed in the memories form were found in your scrapbook and how many days away with photos without camera data fall in the months you wrote (numbers only); and your ratings of pages with the rank and score the algorithm went by, and the kind and approximate month you choose under “A Missing Chapter or Life Moment” or “Something That Shouldn’t Be There.”

When you send feedback by taking a screenshot or shaking your phone in Relive, it also includes the time and the name of the page, your system language (without region), display settings, the last 20 pages you opened, the types of recent errors, and the warnings and errors Relive logged in the last 5 minutes. Before they’re sent, place names, text you wrote, coordinates, and other numbers that could indicate a location are removed from the log lines. You can review everything that will be sent on the feedback page before sending it.

Automatically generated reports omit photos, coordinates, place names, and labels you’ve given places. Feedback you enter is sent as written. In Relive, go to Settings → Beta to review reports under Sent Feedback or turn off Automatically Send Beta Reports to stop future reporting. The developer deletes received reports after the current beta test ends. To request earlier deletion, email the developer with your tester ID.

If you submit feedback through TestFlight, Apple passes your submission to the developer, including any screenshots you attach.

Third parties

Relive shares the data described above only with Apple (place-name lookups, map downloads, iCloud Photos originals, iCloud sync of what you write, and App Store purchases) and Feishu (TestFlight beta reports only, and only after you opt in). They handle this data under their own privacy policies and provide the same or equal protection for it as this policy. Relive has no ads, uses no third-party analytics or tracking, and never sells data.

Manage access and contact the developer

You can change or revoke Relive’s photo access in your iPhone’s privacy settings. After you revoke access, Relive no longer reads your photos. What it cached while organizing (place names, camera models) stays on the device until you delete Relive. Deleting Relive removes the app’s data from your device, but not what is in your iCloud: it comes back when you reinstall Relive and turn on Sync to iCloud. To delete it, use Settings → Erase Everything I Wrote in Relive, which also clears it from iCloud (with sync off, iCloud is cleared once you turn sync back on). Deleting Relive’s data in your iPhone’s Settings → Apple Account → iCloud removes only the copy in iCloud: any device that still has Relive syncs its own copy back. You can delete any saved share images in the Photos app.

For privacy questions or to request deletion of a beta report or email feedback, contact noah@noahqin.dev. The developer uses your email address and the details you provide to respond to your request.

Changes to this policy

If a change to Relive affects how it handles data, this page will be updated first, along with the date at the top.