FetchAhead: Offline Cache Privacy Policy

# FetchAhead: Offline Cache Privacy Policy Last updated: September 17, 2026 FetchAhead is published by Quazmoz / Quinn Favo. It is an Android app for preparing web pages, files, feeds, and other supported content while connectivity is available so the saved material can remain useful when the network becomes 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 the current release candidate does not use a developer-operated backend to store your saved library. Data can leave the app when a feature inherently requires an external service: for example, when your device requests content from a source website or CDN, when Google Play processes or restores the optional Pro purchase, when Android opens a user-selected document/content provider, or when you deliberately open an external support destination. The current release candidate does not include a FetchAhead advertising SDK, developer-operated analytics backend, session-replay service, or automatic diagnostic-upload service. ## Information stored on your device Depending on the features you use, FetchAhead may store locally: - Captured page text, supported images/assets, PDFs, files, feeds, 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, and other app preferences. - Local diagnostic events and normalized error/state information used for troubleshooting. - Bounded Google Play Pro entitlement state needed to keep previously validated Pro access usable offline where supported. 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, 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 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. FetchAhead intentionally does not bypass DRM, paywalls, authentication controls, or third-party access restrictions. Its direct-video feature is limited to explicitly supplied supported progressive files and does not discover streaming media from web pages or parse HLS/DASH streaming playlists. ## 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 current app configuration excludes captured content/assets/imports, the library database containing source metadata, authentication/session material, capture/refresh job state, and cached purchase-token/entitlement state from Android cloud backup and device-to-device transfer where the platform honors those rules. Only explicitly approved non-sensitive preferences may be eligible for Android backup. ## 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 gates scale and automation features; losing or changing entitlement does not make already-downloaded user content inaccessible merely because it was previously prepared while Pro was active. ## Diagnostics and support FetchAhead does not automatically upload diagnostics in the current release candidate. 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, 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 The current FetchAhead release candidate does not include a developer-operated product analytics backend, advertising SDK, session-replay SDK, or custom crash-reporting upload service. Google Play can separately provide publisher-facing platform services such as acquisition statistics and Play Vitals under Google's own platform terms. Those platform services are distinct from a FetchAhead-operated analytics backend. If a future release adds analytics, advertising, crash reporting, remote configuration, or another SDK that changes data handling, this policy and the Google Play Data Safety disclosure must be reviewed before that build is released. ## 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. FetchAhead includes controls to remove individual saved content and to clear the local library. Clearing app storage or uninstalling the app removes app-private local data subject to Android platform behavior. A failed refresh does not destroy the previous good saved revision merely because the new request failed. Data already processed by an external source website, Google Play, a document provider, or another 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. Current 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/offline-reading utility and is not specifically directed to children. The app does not provide a FetchAhead account system in the current release candidate. ## Changes This policy will be updated when FetchAhead materially changes its SDKs, permissions, network destinations, billing behavior, storage/backup rules, diagnostics, analytics, advertising, or other data handling. ## Contact For privacy questions, contact Quazmoz@vivaldi.net.