Effective Date: September 16, 2026
FrameGlimpse is an on-device media utility that helps you find, view, organize, process, save, and clean up photos, videos, Live Photos, and related media.
This Privacy Policy explains what information FrameGlimpse (the “App”) may access, how that information is used, what remains on your device, what may be handled by Apple or another service you choose, and what may be sent to us when you choose to contact us.
FrameGlimpse is designed around the following principles:
After you grant permission, the App may access photos, videos, Live Photos, screenshots, screen recordings, albums, and related information within the scope allowed by iOS.
This access may be used to:
Most compatible features can operate on media available under iOS Limited Photos access. The Recall feature requires Full Photos access because a limited selection cannot represent the complete library needed for date-based historical discovery. If you grant Limited access, Recall is unavailable, while features compatible with the selected items may remain usable.
The App does not upload your media or media-analysis results to us.
To support media processing, Recall, cleanup, saving, sorting, display, and export features, the App may read metadata available through iOS, including:
This metadata is processed locally and is not uploaded to our servers. When iCloud Sync is enabled, a limited subset needed to associate and restore frame projects, including a PhotoKit cloud identifier and video duration, may be stored in your private CloudKit database as described in Section 4.2. Photo location and camera EXIF metadata are not included in App-data sync.
FrameGlimpse does not request your current location and does not use location services to track you. If an existing photo or video contains location metadata, the App may read and display that information locally. When preparing an optional Recall notification cover, the App may ask Apple’s system geocoding service to convert that media’s stored coordinates into a place name; this is handled by Apple under its own terms and is not sent to a developer-operated server. If you choose to preserve metadata while exporting, available location or camera metadata may be included in the exported result.
If an item is stored only in iCloud, the App does not automatically download your entire iCloud Photos library or batch-download all cloud-only media.
When you choose to view, analyze, export, save, play, or otherwise process a specific cloud-only item, the App may ask iOS to download that item. The App may warn you before an operation that could use cellular data, and you may cancel supported operations.
Within Recall, still photos, Live Photos, and display-size poster images for videos may use network access to load a selected or visible item through Apple’s Photos services. Loading a video poster does not download the original video file. If you explicitly choose to play a cloud-only video or find its highlights, Recall asks for confirmation before allowing that single original video download; you can cancel instead.
iCloud downloads are handled by iOS and Apple’s iCloud services. We do not receive the downloaded media, your Apple Account credentials, or information about the contents of your iCloud Photos library.
Recall notification background refresh does not download media from iCloud. If a suitable cover thumbnail is not already available locally, the notification remains text-only.
FrameGlimpse can use Apple’s CloudKit service to keep supported App data up to date across your devices signed in to the same iCloud account. This is separate from iCloud Photos: App-data sync does not upload or back up your photos or videos and does not replace iCloud Photos or a media backup.
When this feature is available, the iCloud Sync setting in the My tab controls transmission. Sync may initially be enabled by default for eligible users who have not previously chosen a setting. You can turn it off at any time. An available iCloud account and sufficient iCloud storage are required; your Apple Account credentials and password are handled by Apple, not provided to us.
The synchronized data is limited to:
These records are stored in the private CloudKit database associated with your iCloud account. They are not published to a public database or shared with other App users. We do not have routine access to your private database through the developer console. The App may store an app-scoped CloudKit account identifier locally to prevent transferring pending changes into a different iCloud account; it is not your email address or Apple Account password.
App-data sync does not upload photos, videos, Live Photos, thumbnails, generated media, original media filenames, local file paths, raw PhotoKit local identifiers, photo location or camera EXIF data, scan or cleanup analysis results, notification content, or diagnostic logs. Projects based on locally imported files are not synchronized by this feature. Notification preferences, notification permission, and notification schedules remain specific to each device.
Sync does not request Photos permission by itself. Associating synchronized records with media uses only the Photos access you have already granted. If access or a matching item is unavailable, some records may remain pending until the required access or item becomes available. Hiding an item in FrameGlimpse does not hide or delete that item in Apple’s Photos library.
CloudKit may use Apple Push Notification service (APNs) to wake the App silently for lightweight metadata synchronization. These silent notifications do not contain Recall reminder photos or reminder content. CloudKit synchronization does not itself run a media scan or download original media. Apple controls network delivery, background execution, storage availability, and synchronization timing; changes are not guaranteed to appear immediately.
Turning sync off, or losing access to the feature, stops subsequent App-data transmission but does not delete existing local or cloud data. The App may retain pending changes locally for a later sync. If sync is enabled again, local and cloud changes may be reconciled and cloud records may be restored to the device.
Synced records remain in iCloud until changed or deleted through supported operations or Apple’s iCloud data-management controls, subject to Apple’s storage and retention practices. Deleting a frame project can synchronize a deletion marker rather than immediately erasing every cloud record, so an older device does not recreate the project. Minimal identifiers and merge metadata may remain with that marker. Removing a Recall exclusion updates the exclusion state; it does not necessarily erase the corresponding synchronization record immediately.
Clearing local App data or deleting the App does not delete the private CloudKit database. To remove stored cloud data, use Apple’s iCloud storage-management controls for FrameGlimpse. On supported versions of iOS, open Settings, select your Apple Account, then iCloud and Storage or Manage Account Storage, select FrameGlimpse, and use the available data-deletion control. Names and availability of these controls may vary by system version. See Apple’s guidance for third-party app data in iCloud.
Before removing cloud data, turn off FrameGlimpse sync on your devices. Local copies can remain after cloud deletion; clear local App data on those devices as well if you want to remove those copies and avoid subsequently uploading them again. Clearing App data does not delete the original media in Photos. Contact us if you need help locating the applicable controls; we cannot directly inspect or erase your private iCloud database from the developer console.
Apple processes CloudKit storage and transmission under its own terms and privacy practices. We do not promise a particular encryption mode, backup duration, or immediate erasure from Apple’s infrastructure. See Apple’s Privacy Policy.
Recall searches your Photos library on device for photos and videos from the same calendar day or week in previous years. Recall requires Full Photos access and does not send the discovered media, dates, or results to us.
After Full Photos access is available and you first enter Recall, the App may request notification permission through the iOS system prompt. If permission is granted, FrameGlimpse can schedule two independently controlled types of local reminders:
These reminders are created locally on your device. FrameGlimpse does not send Recall notification content through APNs or developer-operated servers. App-data synchronization is separate and is described in Section 4.2; notification preferences and schedules are not synchronized.
The “Show Cover Photo in Reminder” option is enabled by default and can be turned off separately. When this option is enabled, the App may use a locally available thumbnail as a notification attachment shortly before delivery and may add a place name derived through Apple’s system geocoding service when the source media contains location metadata. iOS copies that attachment into system notification storage and may display it in a notification banner, Notification Center, or on the Lock Screen. The cover and place name are not uploaded to us.
A short iOS background refresh may revalidate the next reminder and attempt to replace a text-only reminder with a locally available cover. iOS decides whether and when background refresh runs, whether a notification is delivered on time, and how notification previews and attachments are displayed. Focus, Notification Summary, Lock Screen privacy settings, and other system settings may affect delivery and presentation.
You can independently disable weekly reminders, On This Day reminders, or cover photos in the Recall section of the My tab, or disable all notifications for FrameGlimpse in iOS Settings. Showing or hiding the Recall tab does not change these reminder preferences. When the App next reconciles its notification state, it removes or replaces its own pending and delivered Recall notifications after you change the reminder preferences, revoke Full Photos access, or clear local App data.
Deleting a source photo does not automatically remove a notification attachment already copied by iOS. The App limits when covers are created and revalidates them when possible, but a photo deleted shortly before delivery may still appear because final notification storage and delivery are controlled by iOS.
When you choose to save a generated photo, Live Photo, GIF, or other result, the App asks iOS to write the item you confirmed to your Photos library or another destination you select.
When you choose to organize media, the App may create a Photos album or add selected existing media to an album. It does not create albums or add media without your action.
The App saves or organizes only the items associated with the action you confirm. We do not receive a copy of the saved or organized media.
If you export or share an item through the iOS share sheet, Files app, Mail, or another app or service, the destination you choose may process and store that content under its own privacy policy and terms. You control the destination and can cancel before completing the action.
We do not receive exported media unless you deliberately include it in a message sent to us.
When you use cleanup or Recall features to delete media:
You are responsible for reviewing selected items before confirming deletion. FrameGlimpse does not control how long Apple retains items in Recently Deleted.
To provide its features, the App may store information in its local container or iOS preferences, including:
This local information is used to operate the App and is not automatically sent to us.
The App may also retain local sync state, safe business-data backup files, pending changes, and a write-ahead journal to protect edits during interrupted synchronization. The journal can contain local Photos identifiers; it remains on the device, is excluded from device backup, and is not uploaded by iCloud Sync. Other local App data may be included in system device backups according to your iOS settings. Device backup is separate from the App-data sync described in Section 4.2.
The App provides controls to clear local history, settings, and caches. Clearing local App data does not delete media already saved to Photos, Files, or another destination, does not change the Photos permission controlled by iOS, and does not cancel purchases managed by Apple.
Deleting the App generally removes information stored in the App’s local container, subject to iOS behavior. Copies stored by Photos, Files, Mail, iCloud, notification storage, or another selected service are controlled by those services.
Local diagnostic logging is disabled by default. You can enable or disable it in the Feedback and Suggestions section of the My tab.
When enabled, the App stores a limited diagnostic trail on your device to help investigate problems. Depending on the features you use, the log may include:
Diagnostic logs are designed not to include the contents of your photos, videos, Live Photos, or thumbnails; original media filenames; precise media locations; or raw PhotoKit identifiers.
The logs are stored in the App’s local container, excluded from device backup, and limited to approximately 50 MB through local rotation. Disabling diagnostic logging stops new diagnostic entries and prevents automatic diagnostic attachment creation, but existing local log files may remain until you clear local App data or delete the App.
FrameGlimpse does not automatically upload diagnostic logs. If diagnostic logging is enabled and you choose “Send Feedback” inside the App, the App informs you that a diagnostic file will be prepared. You may cancel, or continue to the system mail composer. Before sending, you can review the email, edit it, remove the diagnostic attachment, or cancel the message.
If you send a diagnostic attachment, we receive and use it only for support, troubleshooting, security, purchase assistance, and improving App stability or functionality. Your email provider and our email provider process the message and attachment under their own privacy policies.
FrameGlimpse provides an optional way to contact us by email. If you send feedback, we may receive:
Before sending, you can review, edit, or cancel the message using the system mail interface. You control the information and attachments included in the email.
We use information you send only to:
We do not use feedback information for advertising, cross-app or cross-website tracking, unrelated marketing, device fingerprinting, or sale to third parties.
FrameGlimpse may offer subscriptions or other in-app purchases through Apple’s StoreKit and the App Store. Apple processes payment information, purchase authorization, billing, subscription management, refunds, Family Sharing status, and purchase restoration under Apple’s terms and privacy policies.
We do not receive your payment-card details or Apple Account password. The App receives StoreKit transaction and entitlement information needed to present products, complete purchases, restore purchases, and determine access to paid features. This information is processed locally through Apple’s frameworks and may be cached locally for entitlement continuity.
If you enable diagnostic logging and voluntarily send us a diagnostic attachment, purchase-related troubleshooting information may be included as described in Section 8.
App download, installation, ratings, reviews, system-generated crash information, iCloud downloads, notification delivery, and related services may also be handled by Apple. Apple’s processing is governed by its own terms and privacy policies and is outside our direct control.
The current version of FrameGlimpse:
Information is sent to us only when you deliberately contact us, such as by sending a feedback email. Apple and any export, email, or sharing destination you select may separately process information under their own policies.
The App relies on Apple system services for functionality such as Photos access, iCloud media retrieval, private CloudKit App-data sync, silent push notifications, system geocoding, StoreKit purchases, local notifications, background tasks, Mail, Files, sharing, ratings, reviews, and App Store distribution.
If you export media or send information to another app, website, email provider, cloud-storage provider, or sharing destination, that third party’s privacy policy and terms apply to its processing.
Apple may collect system-generated crash, performance, purchase, or diagnostic information according to your Apple Account and iOS settings. This system-level processing is controlled by Apple and is separate from the App’s optional local diagnostic logging.
FrameGlimpse does not control third-party services and is not responsible for their independent privacy practices.
FrameGlimpse provides local media tools for general users. The App does not require an account and does not knowingly collect personal information from children.
A child should not send us an email, diagnostic attachment, media, or other personal information without the consent and assistance of a parent or legal guardian.
If you believe a child has sent us personal information without appropriate consent, contact us using the details below. If we learn that we received a child’s personal information without appropriate consent, we will take reasonable steps to delete it.
We reduce privacy risk by processing media on device, avoiding a developer media server, making diagnostic logging optional, limiting diagnostic-log size, requiring user confirmation for sensitive actions, and using Apple system interfaces for permissions, purchases, deletion, email, and sharing.
However, no device, storage system, transmission method, or service can be guaranteed completely secure. You should protect your device, Apple Account, iCloud account, email account, exported files, and system permission settings.
When you send an email, export content, or use an Apple or third-party service, that provider’s security and privacy practices also apply.
Media-processing state, preferences, caches, downloaded working copies, and enabled diagnostic logs remain on your device until the App removes them through normal cache management, you use an available clearing control, or you delete the App, subject to iOS behavior.
CloudKit records, deletion markers, pending local edits, and cloud-deletion controls are described in Section 4.2. Turning sync off, clearing local App data, or uninstalling the App does not by itself erase existing iCloud records. Cloud-data retention is separate from the feedback-email retention period below.
Diagnostic logs are locally rotated and limited to approximately 50 MB. A temporary diagnostic attachment prepared for feedback is removed from the App’s temporary storage after the mail composer finishes or the preparation is cancelled, where the App is able to do so. A copy included in a sent email is retained by the applicable email providers and by us as part of the support message.
If you send feedback, we may retain your email address, name or display name, message, and attachments only for as long as reasonably necessary to respond, investigate and resolve the issue, provide support, improve the App, prevent misuse, comply with legal obligations, or protect our legal rights.
Unless a longer period is required by law or reasonably necessary to protect our legal rights, we will delete feedback emails and their attachments no later than 90 days after the issue is resolved or the information is no longer actively needed.
You may ask us to delete feedback information you previously sent. To locate the relevant message, we may ask for the sending email address, approximate date, or subject.
Deleting FrameGlimpse or clearing its local data does not delete media already saved to Photos or Files, does not delete an email already sent, and does not control copies retained by iOS notification storage, Apple, or another destination you selected.
You can control your privacy in the following ways:
You can review or change Photos access in:
Settings > Privacy & Security > Photos > FrameGlimpse
You can review or change notification access in:
Settings > Notifications > FrameGlimpse
Some features may be unavailable or limited if you deny or revoke the permissions they require.
We may update this Privacy Policy to reflect product changes, legal requirements, App Store requirements, or changes to our privacy practices.
If we make material changes, we will update the effective date on this page. We encourage you to review this Privacy Policy periodically. The version in effect when you use the App applies to that use.
If you have questions about this Privacy Policy, FrameGlimpse’s privacy practices, or deletion of feedback information you previously sent, contact us:
FrameGlimpse uses Apple’s Standard End User License Agreement.