iRevisit is a local-first memory app. It is designed to organize earlier photos and videos from your device around the current date. The app does not require an account in the reviewed build, and photo-library content is not sent to an iRevisit server by the app.
1. Overview
This policy applies to the iRevisit mobile app and to the iRevisit legal and contact website. It describes the current behavior identified in the app's iOS and Flutter source code. It does not describe Apple, Cloudflare, or other platform services beyond the ways iRevisit uses them.
The app is intended to help you revisit photos and videos associated with the same calendar date in earlier years. Features are controlled by your device permissions and by the actions you take in the app.
2. Information iRevisit accesses
Photo library data
If you allow photo-library access, iRevisit reads media available through Apple's Photos framework to find and display photos and videos. The app may use the media content and related device-library metadata, including a local asset identifier, media type, capture or creation date, modification information, and location information that is already attached to an item when available.
The app can create temporary thumbnails, preview images, and local indexes to make browsing responsive. If you select media for a delete action, the app asks the system photo library to delete the selected asset. This changes your device library and should be used carefully.
Camera data
If you choose the manual photo feature, iRevisit opens the device camera. A photo you capture through that feature is saved to your system photo library after the applicable permission is granted. The app keeps the resulting local photo-library identifier in its local state so it can associate the photo with your manual record.
Location data
If you choose to record your current location, iRevisit requests location access while the app is in use and retrieves a current coordinate. It can also read location data embedded in photos or videos that you allow it to access. Location coordinates and optional place labels may be used to organize or display memories and manual records locally.
When the app turns a coordinate into a place label or renders a map preview, it relies on iOS location and map services. Those platform services may process information under their own terms and privacy policies.
Local app state
iRevisit stores selections and app state on your device. This may include favorites, hidden-item choices, manual notes, manual mood selections, local record details, associated photo-library identifiers, recent browsing references, and settings related to the app experience.
Contact-form information
If you use this site's contact form, the form sends the name, email address, topic, and message that you enter to this site's contact endpoint. In its current implementation, the endpoint validates the request and returns a reference code. It does not persist the submission, send an email, or create a support ticket.
3. How information is used
iRevisit uses the information above to provide the features you request, such as finding on-this-day memories, presenting media previews, sorting media, creating a manual record, showing location-related information, preparing an item for system sharing, and performing a user-confirmed delete action.
The reviewed build uses local device storage and temporary files for app state, media previews, thumbnails, share cards, and indexes. It does not include account creation, advertising SDKs, or third-party usage analytics SDKs.
The iOS build makes a one-time connectivity request on first launch. This request is used as a network availability probe and is separate from the photo-library features. It is not a transfer of your photo library or manual record data.
5. Storage and retention
App preferences and local memory state are stored on your device using the app's local storage. Thumbnails, preview images, media-location indexes, and share materials may be placed in the device cache or temporary storage. iOS may remove cached or temporary material as part of normal system management, and the app can clear certain temporary share materials.
Information in your system photo library remains subject to your device's photo-library settings and backup configuration. Deleting the iRevisit app does not itself delete photos or videos held in the system library. Deleting an asset from the library through a user-confirmed app action can remove that asset from the library, subject to the behavior of Apple's Photos app and services.
The website contact endpoint does not retain form contents in the current implementation. Because it is not a monitored support channel yet, it should not be used for time-sensitive requests or as the only method for exercising a legal privacy right.
6. Your choices and controls
- You can decline, limit, or later change photo-library, camera, and location permissions in iOS Settings.
- You can remove or change local app choices, such as favorites, hidden items, and manual records, from within the app where those controls are available.
- You can clear temporary share materials through the app's privacy controls when that option is available.
- You can delete the app to remove its locally stored app state, subject to your device's operating-system behavior. Your system photo library is managed separately.
- You can avoid entering personal information into the website contact form. The current form does not have a persistence or reply workflow.
Depending on where you live, you may have rights to request access, correction, deletion, restriction, or information about personal data. A monitored contact channel must be configured before this website can process such requests. When a verified support address is published in the app listing or app settings, use that channel for a request that requires a response.
7. Children's privacy
iRevisit is not directed to children under 13. The app does not include an account or a child-directed experience in the reviewed build. A parent or guardian who believes a child has sent information through a future support workflow should use the published support channel to request assistance.
8. Updates and contact
We may update this policy when the app or website changes. The updated version will be posted here with a new last-updated date. Material changes should also be reflected in the app or its store listing where appropriate.
For general feedback, you may use the contact form. Read the notice on that page before submitting: the present endpoint is an acknowledgement-only implementation and does not create a retained support case.
This policy is an implementation-focused description of the reviewed build, not legal advice. Before a production release, have a qualified lawyer review the policy for the jurisdictions in which you offer iRevisit.