Draft prepared November 16, 2026 · Effective date pending
1. Scope and operator
This document is intended to cover personal information handled by the Tricko app and its product website. Screenshots establish product features, but do not establish the underlying collection, storage, or sharing practices.
To confirm before publication: Identify the operator responsible for personal information, its address, privacy contact, and the policy effective date.
2. The product website
The supplied website code has no analytics, advertising scripts, forms, cookies, or browser-storage code. Product images, styling, and scripts are embedded in the HTML. The menu and availability dialog run in your browser without sending interaction events to a server. Following an external store link takes you to a separate service.
To confirm before publication: Disclose the actual hosting/CDN/security providers, request logs, purposes, retention, cookies if any, and processing locations after hosting is selected.
3. App data and video content
Tricko’s interface includes media imports, video links or codes, collections, a guest account identifier, daily usage limits, and plan information. It also advertises Plus features including no opening ads. These facts alone do not establish what information is transmitted or retained.
To confirm before publication: Inventory actual video/audio files, source URLs/codes, library metadata, favorites/offline records, account identifiers, usage counters, purchase records, device details, and diagnostics. For each applicable category disclose source, purpose, recipients, and local versus server processing. Confirm whether video content is uploaded.
4. Permissions
You can review device permissions in your device settings. Disabling access may prevent a related feature from working.
To confirm before publication: Confirm actual Photos, selected-media, Files, camera, microphone, notifications, or other permissions. List only permissions actually requested and explain the feature and timing for each.
5. Advertising, analytics, and providers
The interface mentions opening ads and a Plus option without them. This draft does not assert that the free plan is ad-free, that there is no tracking, or that no SDK receives data.
To confirm before publication: Identify actual advertising, analytics, crash-reporting, payment, account, storage, and content providers. Disclose shared data, purposes, tracking or targeted-advertising behavior, provider roles and notices, consent choices, and any sale/sharing opt-outs that apply.
6. Uses and processing grounds
The final policy should connect each collected data category to a specific purpose. When you send a support email, the email services involved process the message you choose to send. Avoid sending unnecessary personal or sensitive recordings.
To confirm before publication: Verify the actual purposes for imports, retrieval, editing, account access, limit enforcement, billing, security, support, and analytics. Identify legal grounds where required and describe consent withdrawal for optional processing.
7. Retention and deletion
Deleting a local file, uninstalling the app, and deleting an account can have different effects. This draft makes no claim that any one action erases all server or backup copies.
To confirm before publication: Specify storage locations, retention periods or criteria, backup handling, exceptions, and a working deletion request process. Explain how guest users delete account data and whether uninstalling preserves an identifier or server records.
8. Choices and requests
Depending on your location and the processing involved, rights may include access, correction, deletion, portability, restriction, objection, consent withdrawal, and a complaint to a competent authority. Device permissions can be managed through your device settings.
To confirm before publication: Provide an actively monitored privacy contact and the actual request, verification, and appeals process. Disclose any regional choices relevant to the app.
9. Audience and international processing
The website design and screenshots do not establish an age threshold or processing country.
To confirm before publication: Confirm the intended audience, minimum age, any parental-consent requirements, and handling of children’s information. Identify actual processing countries and applicable cross-border safeguards.
10. Security and updates
The published policy should identify its effective date and explain how material changes are communicated. For conditions of use, read the Terms of Service.
To confirm before publication: Describe security safeguards actually implemented without promising absolute security. Add the real privacy email and correspondence address. Verify that the final policy matches the shipping app, SDK behavior, and store privacy disclosures.