CheekCache
Language: English

Effective 9 September 2026

CheekCache Privacy Policy

FFOX (“we”) develops the CheekCache application. This policy explains the data used by the app, why it is used, and the controls available to users.

1. Key information

2. Data stored locally

The app may store a URL, title, description, author, website name, preview image URL, favicon URL, creation and preview retrieval dates, and assigned tags and colors. It also stores language and theme preferences, advertising consent choices, and technical values required to limit advertising frequency.

Custom labels, private notes and reminder dates, times and recurrence are also stored locally. If you enable reminders, the app requests notification permission when required and schedules notifications on your device.

Data remains in the app’s private storage. Android or iOS may include app data in a device backup or transfer according to the user’s account, device, and system service settings.

3. Retrieving link previews

When a link is added, CheekCache may connect directly to the destination website to retrieve publicly available metadata, images, and its favicon. The website operator may receive standard connection data such as the IP address, request time, protocol information, and client headers. For supported platforms, the app may use a public platform endpoint such as YouTube oEmbed.

How a visited website uses connection data is governed by its own privacy policy. CheekCache does not send the website your tags or other contents of the local library.

4. Advertising and Google services

On Android, missing translations may be downloaded on demand through Google Play Feature Delivery. Google Play processes the list of installed languages and the app version and device information needed to deliver and update these packages. CheekCache does not send library links, tags, or notes for this purpose. Learn more in the Play Feature Delivery data disclosures.

The app displays Google AdMob advertising and uses Google User Messaging Platform to manage required privacy and consent choices.

Google Mobile Ads may process the IP address, approximate location inferred from it, app and ad interactions, diagnostic information, and device or account identifiers including the advertising ID, depending on region, device settings, and user choices.

Learn more in the Google Mobile Ads data disclosures for Android and iOS, the Google Privacy Policy, and the Google partner technologies notice.

5. Permissions and system access

6. Export, import, retention, and deletion

A JSON export contains the link library, metadata, and tags. The user chooses where and through which service the file is stored; the copy is then also governed by the selected storage provider’s terms. Import reads only the document selected by the user.

A link remains in the app until it is deleted. Deletion can be undone immediately after the action. All local data can be removed by clearing app storage or uninstalling the app. Exported files and system backups must be deleted separately from their storage location.

Sharing collections

In versions supporting attachments, selected images and documents are copied into private app storage. A collection may also include custom labels and attachment details: a random identifier generated for sharing, name, type, size and SHA-256 fingerprint used to verify the received file. The FFOX server does not receive the file contents. Files are sent separately through the application you choose, whose privacy policy and file processing then apply. Local pending-file import preparation is retained for up to 30 days. A full backup exported by the user may contain files and private notes.

After you confirm sharing, the app sends the collection title, selected link titles and URLs, and tag keys to the FFOX server. Notes and reminders are excluded. Anyone with the generated address can read the collection, so do not include confidential information. Creating and receiving collections require internet access; the local library remains available without an account.

A collection is available for 30 days from creation. Reading it does not extend its lifetime. Expired collections cannot be downloaded; an hourly task removes their contents. The identifier and dates remain for another 30 days to explain expired links. Encrypted backups have a separate seven-day retention window relative to the latest backup; older copies are removed during subsequent successful backups. Links already saved on devices and ordinary URLs included in sent messages remain available.

7. Data recipients and security

FFOX does not sell personal data. Our server receives selected collections when the user shares them. Network data may be processed by website operators contacted for previews and by Google as the advertising and consent provider. Connections to HTTPS websites are encrypted in transit.

8. User choices

Required advertising privacy options can be reopened in the app settings. The advertising ID can be reset or deleted in Android settings. On iOS, access to the advertising identifier and cross-app tracking are controlled by the user through App Tracking Transparency and system privacy settings. Users can choose not to save a link, delete individual entries, or remove all application data.

9. Children

CheekCache is not specifically designed for children. We do not knowingly collect children’s data through our own servers.

10. Changes and contact

We may update this policy when the app, external services, or legal requirements change. The current version and effective date will remain available on this page.

Developer and privacy contact: FFOX, privacy@ffox.xyz.