FetchAhead: Offline Cache Privacy Policy

FetchAhead: Offline Cache Privacy Policy

Last updated: September 25, 2026

FetchAhead is published by Quazmoz / Quinn Favo. It is an Android app for preparing supported web pages, files, feeds, and other content while connectivity is available so that saved material can remain useful when the network is unreliable or unavailable.

Summary

FetchAhead is local-first. Your saved library is stored on your device by default. FetchAhead does not require a FetchAhead account and does not operate a developer-hosted backend that stores your saved library.

When you capture or refresh content, your device contacts the relevant source website, CDN, feed, API, or other supported service directly. FetchAhead also uses Google Play Billing for optional lifetime Pro and, in configured builds, Google User Messaging Platform (UMP) plus Google Mobile Ads for an optional user-requested rewarded Prep Pass.

FetchAhead does not use a developer-operated product analytics backend, session replay, or automatic diagnostic upload.

Information stored on your device

Depending on the features you use, FetchAhead may store locally:

• Captured page text, supported images/assets, PDFs, files, feeds, video files, and other saved content representations.
• Sanitized source and canonical URLs plus source metadata required to identify or refresh saved content.
• Offline Pack names, Pack membership, item titles, capture timestamps, freshness state, and refresh history.
• Full-text-search indexes and local search state needed to search your saved library.
• Capture, preparation, refresh, and bounded background-work state.
• Reader, theme, storage, battery, network, consent-related, and other app preferences.
• Bounded Google Play Pro entitlement state needed to keep previously validated Pro access usable offline where supported.
• Local Prep Pass balance plus opaque reward-event identifiers/timestamps used for exactly-once reward handling and bounded allowance rules.
• Sanitized local diagnostic events and normalized error/state information used for troubleshooting.

FetchAhead treats URLs, titles, Pack names, browsing/capture timestamps, imported files, page/document content, search context, authentication material, and similar source metadata as sensitive local information.

Requests to websites and third-party services

When you capture or refresh content, FetchAhead connects from your device directly to the source website, feed, CDN, API, or other supported service needed to retrieve that content.

Those third parties can receive ordinary request information such as your IP address, request headers, and the requested resource. A supported source-specific flow may also require source-specific cookies, authentication, or session data. Third-party sites and services process information under their own privacy practices.

FetchAhead does not operate a general-purpose relay that receives your saved library on behalf of those source sites and does not intentionally bypass DRM, paywalls, authentication controls, or third-party access restrictions.

Optional rewarded ads, consent, and Prep Passes

Configured FetchAhead builds include Google's User Messaging Platform (UMP) and Google Mobile Ads SDK for the optional rewarded Prep Pass feature.

UMP may contact Google when the app process starts in order to refresh consent information and determine whether ads may be requested. A rewarded ad is not requested unless you explicitly choose the disclosed "Watch ad · Get 1 Prep Pass" action and UMP reports that ads may be requested. Google Mobile Ads initialization and rewarded-ad loading are deferred until that explicit action.

FetchAhead deliberately removes the Android Advertising ID permission (com.google.android.gms.permission.AD_ID) and disables Google Mobile Ads SDK crash reporting in the app configuration. Those choices reduce identifier and diagnostic surface but do not mean Google processes no data. Google may still process device, network, consent, diagnostic, security, advertising, and ad-delivery information under Google's applicable terms and policies.

FetchAhead does not intentionally place your saved pages, Pack names, search queries, purchase tokens, or captured content into a rewarded-ad request.

Prep Passes are local, temporary feature credits and are separate from a purchased Pro entitlement. Clearing app data or uninstalling the app removes local Prep Pass state.

Android sharing, files, and storage providers

FetchAhead can receive supported text, URLs, images, PDFs, files, and video files through Android sharing and content-URI flows. The app uses Android-scoped document/content APIs rather than requesting broad all-files storage access.

When you deliberately choose an external document or storage provider, that provider can process the content you select according to its own privacy practices.

Android backup behavior

FetchAhead uses explicit Android backup rules because an offline library can contain sensitive browsing and reading context.

The app configuration excludes captured content/assets/imports, the library database containing source metadata, authentication/session material, capture/refresh job state, cached purchase-token/entitlement state, and Prep Pass balance/reward history from Android cloud backup and device-to-device transfer where the platform honors those rules.

Only specifically approved non-sensitive preferences may be eligible for Android backup. FetchAhead export/import is the intended portable-library mechanism.

Google Play Billing and Pro

FetchAhead offers optional one-time Pro access through Google Play Billing. Google Play processes payment credentials and purchase transactions under Google's applicable terms and privacy practices. FetchAhead does not receive your full payment-card or bank-account details from Google Play.

FetchAhead may cache bounded entitlement state locally so previously validated Pro access can remain available during temporary connectivity loss. Purchase tokens or order identifiers are not intended to be included in user-facing diagnostics or Android backup.

Pro is separate from Prep Passes. A rewarded Prep Pass does not mutate permanent Pro ownership.

Diagnostics and support

FetchAhead does not automatically upload diagnostics.

A user-initiated Copy diagnostics action can create a bounded local diagnostic summary containing operational facts such as app/build information, Android/device class, storage buckets, Pack/item/job counts, normalized error codes, worker state, renderer/adapter identifiers, and entitlement-status category where useful for troubleshooting.

The diagnostic output is designed to exclude saved URLs and query strings, page/document content, titles, Pack names, filenames, search text, cookies, authentication tokens, purchase tokens/order identifiers, ad response payloads, creative identifiers, and other content secrets.

If you deliberately paste diagnostics or other information into an email, support form, or another service, that submission is controlled by the destination you chose and its applicable privacy terms.

Analytics, advertising, and crash reporting

FetchAhead does not use a developer-operated product analytics backend, session-replay service, or automatic custom diagnostic-upload service.

Configured builds do include Google UMP and Google Mobile Ads for the optional rewarded Prep Pass path as described above. Google Play can also provide publisher-facing platform services such as acquisition statistics and Play Vitals under Google's own platform terms.

If a future release adds or materially changes analytics, advertising, crash reporting, remote configuration, backend verification, source adapters, or another SDK that changes data handling, this policy and the Google Play Data Safety disclosure must be reviewed before that build is released.

Export and import

Exports can contain private browsing or reading material even when the original sources were public.

Export is user-initiated through Android's Storage Access Framework. FetchAhead is designed not to export source cookies, authorization headers, signed tokens, purchase tokens, advertising identifiers, or diagnostic secrets. Imported archives are treated as untrusted content and are subject to path, size, recursion, and archive-safety checks.

FetchAhead does not provide a developer-operated public hosting service for exported Packs.

Retention and deletion

FetchAhead retains local saved content until you delete it, clear the local library/app storage, or uninstall the app, subject to normal Android behavior and the app's reference rules.

Deleting a Pack does not silently delete an item that is still referenced by another Pack. Removing the final reference allows the associated saved data to be removed according to the app's deletion rules.

Clearing app storage or uninstalling the app removes app-private local data, including local Prep Pass state, subject to Android platform behavior. A valid Google Play Pro purchase can be restored through Google Play.

A failed refresh does not destroy the previous good saved revision merely because the new request failed.

Data already processed by a source website, Google, a document provider, or another external service must be managed according to that service's own retention and deletion controls.

Security

FetchAhead is designed to treat downloaded web/file content as untrusted. Safeguards include app-private storage, TLS for normal network requests, cleartext traffic disabled in the app manifest, bounded fetch/file handling, sanitized URL persistence, restricted offline rendering, and diagnostic redaction.

No method of electronic storage or transmission is completely secure, so absolute security cannot be guaranteed.

Children's privacy

FetchAhead is a general-purpose productivity and offline-reading utility and is not specifically directed to children. The app does not provide a FetchAhead account system.

Changes

This policy will be updated when FetchAhead materially changes its SDKs, permissions, network destinations, billing behavior, advertising/consent behavior, storage/backup rules, diagnostics, analytics, or other data handling.

Contact

For privacy questions, contact Quazmoz@vivaldi.net.