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

What leaves your phone

When you choose moments for a film, the app sends the server:

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.

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

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

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

Your controls

Contact

Questions about privacy or your data: craig@broadgun.com (Broadgun Software).

Home · Terms · Account help