Privacy — early-access Trippy Clip
Updated 9 November 2026. This describes the current Trippy Clip apps for Android and iPhone/iPad and the trippyclip.com service. It is an early-access notice for the software as it works today. If you connect an app to a server run by someone else, that operator is responsible for its deployment, providers and retention.
In short
- Your photos and videos stay on your phone. The original files are never uploaded, and the finished film is made on your phone.
- To plan the edit, the app sends small preview images, saved details such as capture time and location, and, once you approve a film, a small audio-only copy of any speech in your videos.
- Your finished film stays private to the app until you choose to save or share it.
- We don't sell your data or show ads.
What leaves your phone
When you choose moments for a film, the app sends the server:
- Source details: filename, file type, size, duration, capture time, a content fingerprint (used to spot the same file again) and, if saved with the item, its location.
- Preview images: small, metadata-free JPEG frames taken from each photo or video, usually 640 pixels wide and never more than 720. They can show people and faces.
- Your creative choices: length, frame, sound, style, title and anything you type as story or revision notes. Don't include private information you don't want processed.
- Speech audio, only after you approve a film: a small, low-quality, audio-only copy of the speech in your videos (never the video itself). See Speech analysis.
Uploads are resumable and tied to your project. Nothing is uploaded just because it appears in the app's photo grid.
Photos access and location
The app asks the system for access to your photo library so it can show a date-filtered grid of your photos and videos. You can allow access to selected items only; the app then shows just those.
Location comes only from what is already saved with your photos and videos. The app never asks for your live location and never guesses a location.
- Android: reading saved locations needs the "Access your media's location" permission.
- iPhone and iPad: the app reads the location saved in the file, or else the location the Photos app has saved for that item.
Saved coordinates are sent with the source details and given to the AI planner. To name the place (for example "Oia, Santorini") the server may send the coordinates only, never images or anything else about you, to the OpenStreetMap Nominatim geocoding service. Titles that show a position use coordinates rounded to about a kilometre.
Speech analysis
Every new film uses speech analysis to time titles, cuts and music around what people say. It starts only after you review the price and tap Generate, never while you are just choosing moments, and never on films you have already made.
The phone makes a small audio-only copy (mono, low quality) of each video with speech and uploads it. The server sends that audio for transcription to the configured speech provider, currently OpenAI. Temporary transcription chunks are deleted after each attempt. The resulting private transcript is stored with the film and given to the AI planner. Provider-side retention follows the operator's agreement with the provider.
How the film is planned and made
- AI planning: the server sends the preview images, source details, place names, transcripts and your choices to the configured AI model provider, which writes an edit plan. The server checks the plan before using it.
- Motion titles: the server draws the titles from the plan's text, style, music tempo and rounded coordinates. It never sees your footage, previews or audio. Titles are sent to your phone as a graphics pack.
- Music: if your film uses library music, the phone downloads a licensed music excerpt.
- Rendering: your phone combines the plan, your originals, the titles and the music into the finished film, entirely on the device.
So a video you keep selected isn't sent or transcribed again, the server keeps a private cache of the previews and transcripts made from each original, linked to your account (or, without an account, to that app installation). The cache is never shared with other accounts. Entries are deleted after 48 hours without use, unless the operator sets a different period, and are deleted with your account.
On your phone
- Finished films are kept in the app's private storage. They go to your photo library or another app only when you tap Save or Share.
- Device credentials: each installation has its own key, stored in Android Keystore or the iOS Keychain (on this device only, not synced or backed up). The server keeps only a hash of it. You can revoke it by signing out.
- iPhone and iPad: the app keeps a private, non-backed-up working copy of each selected original so it can render reliably. It is removed when it's no longer part of your current clip, for example when you start a new clip. iOS pauses rendering when the app is in the background, and it resumes when you return.
- Android: rendering can continue in the background with a visible notification, but may pause under Android's battery restrictions until you reopen the app.
- Notifications are local only: the app tells you when a film is ready. No push-notification service is used.
Accounts
You sign in with Google (Android and web) or Apple (iPhone and iPad). The provider verifies who you are; we don't use passwords. We store a provider-specific identifier, the name and verified email address the provider shares, and the time you joined. Provider ID tokens are verified and then discarded. We never automatically merge accounts by email. App sessions are revocable, and their server-side credentials are hashed; browsers keep sessions in HttpOnly cookies. We also store your credit balance, grants, usage and cost records, and which projects are yours. We use your email only to run your account and to reply if you contact us. Marketing consent is never required.
Credits and purchases
Films are paid for with prepaid credits in US dollars that don't expire. Each film shows its exact price before you generate it. We store your balance, credit grants, quotes, charges and refunds, input sizes and durations, and estimated processing costs.
Credit given by an administrator (for example a welcome credit) is not a purchase. On Android, credit packs may be bought through Google Play: Google handles payment, and we never receive your card details. Purchase tokens are verified on the server, indexed by hash and stored encrypted for recovery, and order identifiers are kept for delivery, refunds and fraud prevention. On iPhone and iPad, credit packs are bought through the App Store: Apple handles payment, and we never receive your card details. The server verifies each signed App Store transaction, credits it once, and keeps its transaction identifier for delivery, refunds and fraud prevention.
Authorized administrators can view usage and estimated costs. Cost figures are estimates, not invoice totals.
Test builds (TestFlight)
If you test the iPhone or iPad app through Apple's TestFlight, Apple may share crash reports, device and usage information, and any feedback or screenshots you choose to send with the developer. Apple's own privacy policy governs this.
Retention and deletion
- Server-side project data stays until it is removed. This includes source details, preview images, speech audio and transcripts, edit plans, title packs and job records. This version has no automatic expiry apart from the cache described above.
- Removing a moment from your selection removes that source from your project on the server. It doesn't change films you have already made.
- Deleting your account removes its linked projects and their server-side data, its identities and its sessions. Usage and cost records are de-identified, so they no longer link to you or your projects.
- Records needed for financial or legal reasons may be kept under the operator's retention policy, for example to prevent a Google Play or App Store purchase being replayed. The link to your deleted account and any decryptable purchase token are removed. Deleting an account removes unused credits; it is not a refund request.
- Your original photos and videos, films saved to your photo library, and copies you shared are on your devices, not our servers. Deleting an account doesn't touch them.
- Provider and operator backups follow their own retention policies. Security and audit logs are kept by the operator.
Your controls
- Allow photo access for selected items only, or remove a moment at any time before generating.
- Nothing is transcribed or planned until you approve a film's price.
- Saving and sharing a film are always your choice.
- Use Account → Sign out to end this installation's session and revoke its device credentials.
- To delete your account, use the app or your account on the web. See Account help.
Contact
Questions about privacy or your data: craig@broadgun.com (Broadgun Software).
Home · Terms · Account help