Privacy Policy

Effective Date: 2026-10-01
Application: Eagle Pocket (iOS)

Our Commitment to Your Privacy

The Eagle Pocket iOS Application processes your library data on your device. Its library synchronization does not route content through a developer-operated backend, and we do not sell your library data or use it for advertising. This policy describes this Application's data flow, not unrelated applications or services.

The Application works with Eagle library folders located on your device or in your connected storage. Integration with Google Drive is entirely optional and used only if you choose to connect your Google account.

This policy describes the Google Drive read-only release. Earlier versions could request Drive write access for import or editing features; see the historical-version note in Section 2. Libraries opened through iOS Files may still support editing and photo import, subject to the storage provider's capabilities.

1. Libraries Opened Through iOS Files

By default, the Application works with Eagle library folders that you open through the iOS Files app.

Data Accessed

• Files and metadata contained in the Eagle library folder that you explicitly select through the Files app.

Data Usage

• Files and metadata are used to browse, display, search, and synchronize your Eagle library. Library settings and browsing/search state may be stored locally to support these features.
• When you initiate an edit, import, or item deletion in a supported Files library, the Application may write changes to the selected source library. Availability depends on the storage provider and its permissions. The direct Google Drive read-only integration is described separately in Section 2.

Data Sharing

• The Application does not send library content to a developer-operated backend.
• Storage providers handle requests and transfers needed to open, synchronize, or write the files you select through iOS Files, under their own services and privacy practices.
• If you explicitly use the iOS share or export feature, the selected file is provided to the destination you choose. Copies outside the Application are controlled by you and that destination.

Data Storage & Protection

• The Application processes library files and metadata on your device and stores its local cache and imported database records in its app container.
• The Application relies on standard iOS protections for its local container. Device and account security also depend on your settings and the storage provider; no absolute security guarantee is made.
• App data may be included in device or cloud backups according to your iOS and backup-provider settings. The Application does not exclude all of its local data from operating-system backups.

Data Retention & Deletion

• Local cache, imported metadata, library settings, and browsing/search state are retained to support Application functionality.
• Clear Cache attempts to remove active downloaded files and designated image caches; cleanup failures can leave local files. It does not delete all database records, authorization information, or every possible cache.
• Delete Library removes the library's Application database record and associated imported records and attempts to remove its active local file cache. It does not delete the original source library. File-cleanup failures can leave local copies.
• Deleting the app, rather than merely offloading it, removes its local app container. Previously exported files and copies held in device, cloud, or storage-provider backups may remain and must be managed separately.

Note: The practices described in this section apply only when you use the Application with files accessed through the iOS Files app. If you choose to connect Google Drive, the data handling practices are described separately in Section 2. Optional Google Drive Integration.

2. Optional Google Drive Integration

If you choose to connect your Google account, the read-only release uses Google Sign-In for authentication and requests the following additional Drive permission:

• https://www.googleapis.com/auth/drive.readonly — to read metadata and contents of files and folders accessible to your Google account. This is a broad Drive read permission, not a permission limited by Google to one selected folder.

The read-only release does not request Drive write permission and does not upload, edit, move, or delete files in Google Drive. Google's sign-in SDK also requests basic email and profile permissions for authentication; the Drive permission above is not the only OAuth permission involved in sign-in.

Historical versions: Earlier releases could request https://www.googleapis.com/auth/drive for Google Drive import, editing, or deletion features. Those versions could write to the selected library. The read-only statements in this policy do not describe those older installed versions. The read-only release rejects detected older Drive write grants, attempts to remove that authorization, and may ask you to reconnect. If removal cannot complete, you can revoke Eagle Pocket in your Google Account settings before reconnecting.

Data Accessed

• Drive folder metadata, including names, IDs, and parent relationships, used to browse available folders and select or validate an Eagle library. Folder browsing can read metadata outside the library you later select.
• Root and item metadata and thumbnails from the selected library, used for browsing, search, and one-way synchronization to this device. Original image or other item files are downloaded when needed for viewing or an action you initiate.
• Basic Google sign-in/profile information processed by Google's SDK, which can include your email, name, and profile picture. The Application itself uses your email and account identifier on your device to show the connected account and validate the active synchronization session; it does not use this information for advertising.
• Google's sign-in SDK manages received profile/session information and authorization credentials locally to support sign-in, session restoration, and authenticated requests. You can sign out without deleting downloaded library content.

Data Sharing

• Your device communicates directly with Google over HTTPS for authentication and Drive requests. Library data is not routed through an Eagle Pocket synchronization server.
• The Application does not automatically transfer Drive library content to advertising, analytics, or AI services, and we do not sell Google user data.
• If you explicitly use the iOS share or export feature, the selected downloaded file is provided to the destination you choose. Copies you export, or voluntarily provide when contacting support, are outside the Application's local cache and cannot be removed by its cache controls.

Data Storage & Protection

• The Application stores downloaded metadata, thumbnails, originals, file-ID mappings, and imported database records in its local app container to provide library features.
• During migration or synchronization, the Application can retain previous metadata and replaced or removed cached files in a separate local recovery area to reduce the risk of losing local work. These copies are not uploaded to an Eagle Pocket server.
• The Application relies on standard iOS protections for its local container rather than making an absolute security or app-specific encryption guarantee.
• Local files, database records, and recovery copies may be included in device or cloud backups according to your operating-system and backup-provider settings. This does not change the read-only behavior of the direct Google Drive integration.

Data Retention & Deletion

• Active downloaded files, imported metadata, settings, and browsing/search state are retained locally for Application functionality. Signing out or a failed sign-in does not delete these copies.
• Clear Cache attempts to remove active downloaded files and designated image caches; cleanup failures can leave local files. It does not clear the imported database, sign-in authorization, or the separate local recovery area. A successful sync may be needed to rebuild downloaded metadata and file mappings before originals can be downloaded again.
• Delete Library removes the library's Application database record and associated imported records and attempts to remove its active file cache. It does not revoke Google authorization or remove source files from Drive; cleanup errors can leave local files.
• Recovery copies are not cleared by Clear Cache or Delete Library. They currently have no automatic expiration or in-app purge control and may remain in the app container until you delete the app. Do not treat either control as complete deletion of all Google-derived local data.
• Deleting the app removes its local app container, but does not delete files you exported, data still in Google Drive, or copies in operating-system or provider backups. Backup copies may persist or be restored according to those services and your settings.
• The Application does not retain your Drive library on a developer-operated backend. Google's sign-in SDK manages local session credentials; app removal is not a substitute for revoking Google's authorization.
• Sign Out ends the app's connected session; it does not revoke the grant in your Google Account. You may revoke Eagle Pocket's authorization via your Google Account settings to stop subsequent authorized Drive access. Revocation does not remove content already downloaded, recovery copies, exported files, or backup copies.

3. Analytics and Crash Reports

Eagle Pocket does not include a separate third-party analytics or crash-reporting integration for library content. Depending on your iOS diagnostic settings, Apple may collect or provide diagnostic reports under its own platform policies. Review the data you choose to include when contacting support. Never send passwords or authorization credentials. Include private library files only if you intentionally want to share them.

4. Third-Party Services

Services involved in the features you choose can include:

• Google Sign-In and Google Drive APIs — optional authentication and direct read-only Drive access.
• iOS Files and your selected storage provider — access and, where supported, writing to selected Files libraries.
• iOS sharing, diagnostics, and backup services — used according to your explicit actions or operating-system settings and the relevant provider's policies.

Our use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

5. Children's Privacy

Connecting a Google account is optional and is subject to Google's account eligibility requirements. We do not knowingly seek personal information from children under 13. If you are a parent or guardian and believe a child has provided personal information to us, please contact us using the address below.

6. Changes to This Privacy Policy

We may update our Privacy Policy from time to time. Updates will be posted on this page, and changes become effective immediately upon posting. You are encouraged to review this Privacy Policy periodically.

7. Contact Us

If you have any questions or concerns about this Privacy Policy, please contact us at:

Email: [email protected]