Privacy Policy
Effective September 20, 2026
This Policy explains the information Clips handles, why it is used, and the choices available to you.
Information we handle
- Account and device: account identifiers, sign-in status, device/session identifiers, app version, security and integrity signals, and push tokens.
- Your choices: selected streaming services, watchlist and library entries, notification preferences, Trailer Match Pass/Keep activity, scans, points, reward activity, and support requests.
- Games and mailboxes: game answers, submissions, scores and point awards; private fan messages and replies; the selected recipient; internal sender and reply-author references; and profile-claim verification records.
- Shared clips: submitted URLs and derived page, caption, thumbnail, title-match, and diagnostic metadata needed to identify the movie or show.
- iMessage channel: Photon/Spectrum processes the raw sender address and message contents needed for delivery. The Clips messaging worker derives opaque sender, conversation, and message identifiers, structured actions and feedback, hashes, delivery state, scan and action results, reminder and Clips Picks settings, a bounded recent catalog-title-ID history used to avoid repeats, an optional account-link pointer, and an encrypted delivery-route envelope.
- Ticket rewards: if you choose to claim a ticket reward, the ticket image, extracted ticket details, privacy-redaction evidence, and claim status needed to verify eligibility and prevent duplicate or fraudulent claims.
- Reward delivery: when redeeming a reward that requires manual delivery, you may provide an email address or phone number. Clips uses it only to arrange that delivery, not marketing. Contact details are available only to authorized fulfillment staff and are cleared when the reward is marked delivered or the account is deleted. Team alerts contain a claim reference, not the contact details.
- Subscriptions: product, entitlement, renewal, and transaction-status information supplied by Apple, Google, and RevenueCat. We do not receive your full payment-card number.
- Usage and diagnostics: product events, performance, crashes, approximate network information, and request logs. Product analytics may be processed with PostHog; crash diagnostics may be processed with Sentry.
How we use information
We use information to operate accounts and scans, personalize discovery, provide recommendation notifications when you opt in, filter titles by your services, save choices, enforce limits, calculate rewards, validate subscriptions, send requested notifications, respond to supported iMessage commands, provide recommendations and lists, apply feedback, monitor aggregate messaging cost, delivery health, and bounded problem categories, prevent abuse, diagnose failures, support users, and meet legal obligations.
Ask Clips AI recommendations
Ask Clips is optional. After you agree in the assistant, we send your request, preferences you explicitly save for the assistant, limited prior conversation context and relevant movie/TV metadata to DeepSeek to interpret your request and explain recommendations. DeepSeek is based in China; processing may occur outside your country. We do not attach your account name, email, phone number or raw activity history to those model requests. Do not include sensitive or private information in messages.
Clips uses library and preference signals locally to rank catalog candidates. AI output is checked against catalog and availability data, but suggestions can still be wrong or incomplete. We do not automatically convert conversations into permanent preferences or use a scan alone as evidence you liked a title.
Conversation content is encrypted in Clips storage and normally expires after 30 days; minimal usage and cost records are retained for up to 90 days to enforce limits and prevent abuse. Explicitly saved assistant preferences remain until you edit or remove them or delete your account. In Settings → AI conversations & privacy you can remove preferences, delete conversation history or withdraw consent. Deletion removes content from Clips; it does not reset usage allowances or guarantee deletion of provider security records. Contact us for a provider-specific privacy request. Raw assistant messages and results are excluded from product analytics and session replay.
Private fan mailboxes
The public mailbox shows the named person's profile, total message count and claimed or unclaimed status. Message contents stay private, including after a mailbox is claimed. The named person or their authorized representative can read the inbox only after Clips independently verifies their claim. The recipient is shown “Anonymous,” not your name or account details. This means anonymous to the recipient, not unlinked from Clips: we retain an internal account or anonymous-session reference. Anything you write may identify you, so do not include sensitive or identifying details. An unclaimed mailbox does not imply participation or delivery, and a claimed mailbox does not guarantee a reply.
A verified mailbox owner or authorized representative may send a private reply that only the original sender can retrieve. Clips encrypts messages and replies in storage; this is not end-to-end encryption. Authorized Clips staff may review content for safety or support. We retain the recipient, internal sender and reply-author references, timestamps and removal state to deliver the feature, enforce access, support deletion and prevent abuse. Message and reply text is excluded from product analytics and session replay. Clips does not publish private submissions or replies in a public feed or reuse them in social-media content without separate permission.
Messages and replies remain stored until removed. Use the message receipt in the app or the same browser session to remove both your message and its reply. The website stores an anonymous-session token and message receipts in your browser; clearing browser data, losing that session, or deleting the app can make removal and reply access unavailable. Signing in can associate messages from your app's anonymous session with that account. Deleting an account removes its linked submissions and authored replies, removes its claim records, and revokes its mailbox access. Revoking a claim alone prevents further inbox access and replies but does not remove replies already delivered. Content-free removal records may remain for abuse prevention. Contact support for help with a privacy request. Removal cannot undo content already read or copied, and limited backup and legal-retention obligations may apply.
To claim a profile, Clips stores your signed-in account reference, the person's profile, your stated owner or representative role, submitted social-profile and proof-post URLs, a verification code, claim status, timestamps and the reviewer's verification note. Authorized staff use this information to verify control and authority, approve or revoke access, and resolve disputes. Claim records remain until account deletion or an approved deletion request, subject to limited backup and legal obligations. The current X verification flow does not collect your X password or OAuth access token and does not post automatically. If you choose to publish a verification post or announcement, its profile association, mailbox link and verification code are public on X under X's own privacy practices; deleting your Clips account does not delete those posts. Announcement drafts do not include private messages or replies.
Mailbox safety controls use automated text checks, rate limits, private reports and operator review. Reports record the message reference, reason and time; block records prevent further messages and replies for that sender/mailbox pair without revealing the sender to the recipient. Reported content may be reviewed by authorized Clips staff. Block and content-free safety records remain until account deletion or an approved privacy request, subject to limited legal obligations. Contact support to appeal a block or report decision.
Video and data providers
When Clips loads external metadata, images, embeds, trailers, or clips, the relevant provider may receive ordinary request information such as IP address, browser or device headers, and the requested asset. Providers can include Clip.Cafe, KinoCheck, YouTube/Google, TMDB, and streaming-availability services. Their privacy policies govern their independent processing.
Clips via iMessage
The current messaging channel is direct iMessage only. It does not offer SMS, RCS, WhatsApp, Telegram, group-chat features, or image, video, audio, or file attachments as Clips scan inputs. Photon/Spectrum may still process native message and attachment information as needed to deliver iMessage under its own terms.
- Onboarding and consent: a new messaging identity may receive one onboarding or help reply and a Clips contact card after sending any direct message. That first message is not consent. Clips does not start a scan, recommendation, or product action until you receive the prompt and reply YES or START. After consent, Clips may send the one-time welcome Pick described here; it does not enable a recurring schedule. Send the original request again after opting in.
- Commands and requested messages: Clips converts supported text into bounded structured actions for status, recommendations, saved titles, your list, availability, similar titles, streaming services, reminders, scheduled Picks, account linking, wrong-result feedback, watched or not-for-me feedback, and ratings. For BUG or REPORT, the worker classifies the text in memory and sends Clips only a bounded problem category; the report text is not stored by the Clips API. REMIND may enable a title-specific message. Only PICKS DAILY or PICKS WEEKLY enables scheduled Picks; PICKS OFF cancels a still-pending welcome Pick and disables the schedule without changing the separate messaging-consent status.
- Raw delivery and pseudonymous identifiers: Photon/Spectrum and the Clips messaging worker process the raw sender address, direct-message route, and message content as needed for delivery. Before a request reaches the Clips API, the worker replaces sender, conversation, and provider-message identifiers with stable opaque identifiers. The structured request may contain the public URL or bounded recommendation text you submitted, but the API does not receive the raw phone number, email address, or native iMessage conversation identifier.
- Encrypted delivery route: the worker protects the provider route with authenticated encryption and a worker-held key. The Clips API stores and returns only the linkable ciphertext envelope and cannot decrypt it.
- Optional account link: if offered, a single-use HTTPS claim and short code create a revocable pointer to an authenticated app account; they do not merge the identities or scan quotas. Eligible actions and Picks may read or update the linked app library and preferences and use selected streaming services when available. A linked active Free account may keep separately requested scheduled Picks; an eligible Premium subscription may include ongoing interactive messaging and deeper checks. Information written to the linked account becomes app-account data and remains until separately edited or deleted through Clips. Claim tokens and confirmation codes are not sent to product analytics.
- Welcome and scheduled Picks: after current consent, Clips sends one welcome Pick selected from local policy-safe aggregate catalog signals without starting a paid provider. It does not enroll you in recurring delivery. Only PICKS DAILY or PICKS WEEKLY enables a schedule. Scheduled selection may use linked watchlist, taste, and selected-service signals when they are actually available. Recent catalog title IDs are retained in bounded history to avoid repeating the same Pick.
- Trial and eligibility: messaging begins as a limited, capped acquisition trial; the current trial period and allowance are disclosed in messages. Unlinked scheduled Picks stop when that trial ends. Clips may include one notice within about 48 hours of the end date explaining how to open Clips, create or sign in to an account, and text LINK. A linked active Free account may keep separately requested scheduled Picks. Ongoing interactive messaging and deeper checks may be included while an eligible Premium subscription remains active. Clips does not separately bill a phone number or messaging identity.
- Frequency and controls: daily or weekly is the maximum requested cadence. If no later message is received, Clips may progressively send less often; inactivity does not itself pause the preference. A valid inbound message resets that backoff. PICKS OFF cancels a still-pending welcome Pick and stops scheduled Picks without opting you into or out of other Clips messages. STOP or DELETE suppresses all pending Picks, and START does not restore a schedule or resend the one-time welcome solely because messaging restarted.
- Operational telemetry and retention: when an unlinked messaging profile remains pending or stopped and inactive for at least about 90 days, Clips deletes or anonymizes its delivery receipts, route ciphertext, account-link claims, conversation cursor, reminder and Picks settings, recent-title history, and synthetic-member conveniences. Clips retains only the non-content consent, anti-trial-reset, welcome-issued, and abuse-prevention tombstone described below. Linked, opted-in, current-trial, recently active, and provider-retirement-pending profiles are excluded from that automated cleanup; their operational records may remain while needed for the requested feature or until another retention or deletion rule applies. Downloaded scan frames are removed when the scan ends. An owner-only dashboard reports aggregate fixed and variable cost, volume, outcomes, Picks enrollment and backoff counts, allowance use, queue and worker health, and cost per success without phone numbers, raw or opaque sender or conversation identifiers, URLs or URL hashes, titles, captions, or message bodies. Non-PII daily cost and usage aggregates may remain after detailed events are deleted.
- STOP and START: STOP withdraws consent, revokes the route, disables messaging reminders and scheduled Picks, and suppresses queued or in-progress results where technically possible. START opts in again for new requests only; it does not replay an earlier request, restore reminders or Picks, or mint another welcome Pick solely because messaging restarted.
- DELETE or ERASE: these commands withdraw consent, suppress future results, request cancellation, remove the encrypted route and account-link pointer, and delete messaging-owned messages, URLs, jobs, delivery records, synthetic lists and service preferences, reminders, Picks settings and recent-title history, feedback signals, and detailed messaging cost records. Active provider work can make deletion temporarily pending. A linked app account and information already written into its app library and preferences remain until separately edited or deleted in Clips.
- Limited records after deletion or expiry: operational identity cleanup is separate from compliance and abuse-prevention records. A minimal pseudonymous sender tombstone may retain only consent or opt-out state, the original trial anchor, a content-free marker that the one-time welcome Pick was issued, and a content-free provider-use counter as needed to prevent deletion from minting a fresh trial or welcome benefit or bypassing abuse controls. Counted allowance rows may remain for their bounded quota-retention period. These records contain no submitted URL or URL hash, title, message or conversation content, or result. Short-lived hashed rate-limit, request-count, and estimated-spend controls containing no phone number or email address are normally removed within 49 hours after the last event. Cleanup may take longer during an outage.
Messaging consent disclosure version: clips-imessage-v5-2026-09-01.
Ads and analytics
Clips does not insert personalized ads for Premium members or use their Clips activity for advertising profiling. Provider-hosted media, including YouTube videos, may still contain ads, and the provider may independently process ordinary request information for advertising under its own terms and privacy policy. Clips does not sell personal information. Essential product measurement, security, fraud prevention, crash reporting, and purchase analytics still occur for all tiers.
Optional contacts matching
Friend matching is not currently available. If launched, Clips will ask before accessing contacts or matching identifiers. The intended design is to normalize and hash eligible contact identifiers for opt-in matching, avoid retaining a raw address book, reveal only mutual participation, and provide a way to disable matching and delete associated data.
Sharing, retention, and security
We share information with processors and providers only as needed to operate Clips, comply with law, protect users, or complete a transaction. We retain information while needed for the purposes above, then delete or de-identify it subject to security, fraud, backup, accounting, and legal requirements. We use reasonable safeguards, but no system is completely secure.
The approximately 90-day automated operational-profile cleanup applies only to inactive unlinked pending or stopped messaging profiles, as described above. Other messaging operations follow the more specific STOP, START, DELETE, active-feature, trial or current-period allowance, short-lived security-control, and non-PII aggregate rules above. Expiry of an unlinked trial identity does not override the limited opt-out, quota, anti-abuse, or legal records described above. Photon/Spectrum's applicable terms and practices also govern its provider-side delivery processing.
For ticket rewards, the original upload is queued for deletion after its short signed upload and verification window expires. If object deletion fails, we keep the private storage key and scrubbed claim row only so automated cleanup can retry; the original is not available for further product use. A privacy-redacted review image and associated claim record are normally retained for up to 365 days to administer the reward, resolve disputes, and prevent fraud, but may be kept longer when deletion is still being retried or law requires it.
Your choices
You can change services and notifications in Settings, manage app permissions on your device, manage the subscription in your app store, and delete your account from Account settings. You can also follow the instructions on our account-deletion page. Depending on location, you may request access, correction, export, deletion, or an appeal by contacting contact@cloutopstechnologies.com. We may verify the request before acting.
Children and changes
Clips is not directed to children under 13. We may update this Policy as the product or law changes; the effective date above identifies the latest version.