TrickTic Studio Privacy Policy
Effective: October 30, 2026
Effective 2026-10-30. Published and operated by TrickTic (Daniel Shedrinsky). For privacy questions, contact contact@tricktic.com.
This policy covers the invitation-only hosted TrickTic Studio service at studio.tricktic.com and the TrickTic Studio Android app, which opens the same service. Studio turns pre-cut spoken clips into finished downloadable videos.
Information we process and why
- Your sign-in identity: the verified email address and display name supplied by your sign-in provider, matched against your invitation, let us identify your account and control access. We also store the latest accepted profile photo URL and your optional preset icon choice. If you use the photo, your browser loads it directly from the sign-in provider's image service without sending a referrer; that service receives your network address. Choosing a preset uses bundled artwork instead. Your avatar fields are included in your account export and cleared when you delete your account. We do not accept photo uploads or keep provider access tokens.
- Your content: projects, clips, voice recordings, still images, scripts, topics, hooks, transcripts, captions, Copilot discussion, library assets such as music, fonts and branding, their rights receipts, templates, renders and exports. We store and process it to provide the features you use. Uploaded files are kept as you provide them, including filenames and any embedded metadata.
- AI and usage records: for each AI request, the input it was given, the prompt version, the model and the usage it consumed, plus spending counters that enforce usage caps. Job progress and a project activity feed show you what happened.
- Sign-in sessions: a random session identifier, of which the server stores only a one-way hash, a coarse browser and platform label and the time it was last used. A session started in the Android app is also marked as the app and records your phone's name or model, such as "Pixel 7".
- The Android app's notifications: if you allow notifications in the app, we store the phone's push-notification token, linked to that phone's session, with the phone's name and the kinds of notification you have turned on. Notifications are off until you allow them.
- Technical information: network addresses, browser and device details, error details and timings, used to deliver the service, limit abuse and diagnose and fix problems. We keep it only as long as needed for those purposes and do not intentionally include your media, transcripts, scripts or discussion in logs or error reports.
- Feedback you send through Help & feedback: its category, your text and, if you choose, the app version, browser and a project identifier.
- Your invitation and pilot: the email address you were invited at, when you were invited and the free days offered, the start and end of your free pilot, any extension, and the support time the operator records for your account.
- Emails we send you: the invitation and a reminder before your pilot ends. For each message we keep the address, its dates and whether it was delivered. The messages contain only your own address, dates and public Studio links.
Cookies and browser storage
Studio uses essential cookies to sign you in and keep you signed in. It does not use advertising or cross-site tracking cookies.
Studio keeps a few things in your browser, for your account only: device settings, unsaved edits to projects and scripts for up to 14 days, the list of recent exports and the details of paused uploads. It does not keep download or upload links, credentials, file contents or AI answers there. Signing out or deleting your account clears it. Browser notifications are off until you allow them; when on, they show project titles.
In the Android app, the same sign-in cookie is kept in the app's own browser view, and the phone's push-notification token is kept in the phone's secure storage, for that phone only. The app is excluded from Android cloud backup and device-to-device transfer. Signing out of the app removes the token from the phone and from Studio. Uninstalling the app removes what it kept on the phone; it does not delete your Studio account. The app contains no analytics, advertising or crash-reporting component.
The Android app
- Sign-in uses the Google account sheet on your phone. The app sends Studio the resulting Google sign-in token once, to start an ordinary Studio session, and keeps no Google password or Google access token.
- You can film a clip with your phone's camera app or pick one from your phone's gallery. Only the files you pick or record are uploaded, through the same upload as on the web. The app does not ask for camera, microphone, storage, contacts or location permissions.
- Sharing a finished video uses Android's share sheet: the video goes only to the app you choose.
- A notification says that a render finished or needs attention, that new drafts from your stream are ready, that a stream needs attention, or that a test notification you asked for has arrived. Its text is fixed wording, such as "Your video is ready", with a link to the screen it opens. It contains no project title, name, transcript, video or account detail. You can turn each kind off in Settings → Notifications, or turn notifications off in Android's settings.
Service providers
We use service providers to run Studio. They process information only as needed to provide their service to us:
- Hosting, network and storage providers run Studio's servers and database, carry the connection to your browser and store uploaded media, finished videos and encrypted backups.
- Google provides sign-in.
- Google's push-notification service (Firebase Cloud Messaging) delivers notifications to the Android app. It receives the phone's push-notification token and the notification described above.
- Transcription of your audio and video may run on hardware we operate or with a speech-recognition provider.
- AI model providers power Copilot and other AI features. A request sends the project information needed for it, such as the script, transcript or captions, recent discussion and only the library descriptions you choose to share. It does not send your account credentials. We configure these providers not to use your content to train their models.
- Error-monitoring and operational services help us detect and fix problems, using the technical information described above.
- An email delivery provider sends invitation and reminder emails. It receives your email address and the message.
Providers may change as the service develops, and they may process information outside your country. A current list is available from the privacy contact above. We do not sell your information or use it for advertising. We do not promise that deleting your Studio data deletes copies already processed by a provider under its own retention rules.
Who can see your content
Your projects, scripts, library and renders are private to your account. Another account cannot see them, even if it uploads identical files, and does not gain your rights to an asset that way.
To run the pilot, the operator sees for each pilot account: your name and email from Google, your invitation, pilot start and end dates, when you last used Studio, counts of your projects, renders, failures (as error codes), waiting times and AI use, the feedback you send and the support time recorded. This overview does not include your videos, clips, transcripts, scripts, project names or Copilot conversations.
Studio is not end-to-end encrypted: the operator runs its servers and can technically access content stored there. Operator tools are restricted and their use is recorded. We access your content only to provide the service, to handle a support request you make, or when needed for security or legal reasons.
Retention
- Your content is kept until you delete it or your account.
- Upload sessions expire after 24 hours, and unfinished uploads are removed after 48 hours.
- The project activity feed keeps 30 days. Feedback is deleted after 90 days and is not included in backups. Operator audit records are kept for 90 days.
- Records of invitation and reminder emails are kept for 30 days. An invitation that is never used is deleted 30 days after it expires or is revoked. Your invitation, pilot dates and recorded support time are kept until your account is deleted.
- Expired sign-in sessions are removed a day after they expire.
- A phone's push-notification token is removed when you sign out of the app, remove the phone in Settings → Notifications, when that phone's sign-in session ends, when Google reports the token is no longer valid, or when you delete your account. Notifications not delivered within a day are cancelled, and their records are deleted after 7 days.
- Encrypted backups are made daily and kept for at most 7 days.
When your free pilot ends, Studio stops taking new uploads, edits, renders and AI requests for your account, and you can still sign in to watch, download and export your data or delete your account. Your content is not silently erased; the terms of service explain the notice we give before closing an account.
Exporting and deleting your data
Settings → Data & deletion lets you download your account's project, script, library, render and AI metadata as a JSON file. Original media and finished videos download separately from the app.
You can delete a single project, or your whole account in Settings → Data & deletion, on the web or in the Android app, by typing DELETE ACCOUNT. Deletion ends every session, cancels uploads and active renders and ends access to projects, scripts, discussion and private assets at once. Files are then removed from storage after at least 125 seconds, with retries; links already issued may work for up to 120 seconds. Copies you already downloaded stay with you.
Deletion does not rewrite existing backups. They expire within 7 days, and if a backup is restored before then, deletions are applied again first. A deleted-account identifier, minimal deletion records and minimal usage counters remain, so that a restore cannot bring back deleted data and usage caps cannot be reset. They contain no media, transcripts, scripts or discussion.
Security
Connections to Studio use HTTPS. Uploaded files are scanned for malware and inspected in isolation before use. Backups are encrypted, and the key that decrypts them is not held by the backup service. No service is perfectly secure; tell us promptly at the address above if you believe your account has been compromised.
Age
Studio is intended for people aged 18 or older and is not directed to children.
Your requests and changes
For questions about your information or a request for access, correction or deletion, email the privacy contact above. We may need to verify that the request concerns your account. Your rights may depend on the laws that apply to you. Do not send passwords, session cookies, sign-in codes or download links.
We will identify revisions with an updated date and tell affected users about material changes before they apply where practical.