Privacy Policy

camrip — a service of 50wei · Last updated 12 September 2026

This policy explains what personal data camrip collects, why, and your rights over it. We collect the minimum needed to run the service and we do not sell your data.

What we collect

Account — your email address, and either a password (managed entirely by Firebase Authentication; we never see or store it) or basic profile info if you sign in with Google.
Your media — the video and audio used to make a reel. What we receive depends on where you use camrip:
- In the app, your full-resolution video never leaves your phone — the reel is rendered on the device. camrip uploads only a small low-resolution copy (540p) of each take, which is what the service uses to work out the edit: where the beat is, and which angle to show at each moment.
- On the website, the files you upload are the originals, because the reel is made on our servers.
Either way, what you sent us is kept for a short while so that you can change the cut — swap an angle, move a cut point, change the style or the format — without uploading anything again. About 24 hours, or about 72 hours if you have ever bought credits. After that it is deleted automatically, and re-cutting that reel is no longer possible. The finished reel is kept for a download window of about 72 hours and then deleted automatically.
Payments — handled by Stripe. We never receive or store your card details; we only keep a Stripe customer reference and your credit balance.
Technical — limited logs (e.g. IP address, error reports) kept for security, abuse-prevention and debugging.
Diagnostics you send us — the app keeps a short technical log on your phone (the last few hundred lines: what the renderer did, which step failed). Nothing is sent automatically. If you use Share diagnostics in the account menu, you choose where the file goes and you can read it first. Before it is written, the app removes what could identify you or your footage: file names are replaced by numbers (“<file 1>”), email addresses are removed, and the parameters of upload links — which act as credentials — are stripped. It contains no video, no audio and no transcript.

How we use it

To provide the service: authenticate you, process and deliver your reel, and manage credits.
To keep the service secure and prevent abuse.
To respond to your support requests.

Who processes your data (sub-processors)

Google Cloud / Firebase — hosting, database, storage and authentication (EU region).
Stripe — payment processing.
Firebase Crashlytics (Google) — crash diagnostics from the mobile apps, release builds only, not linked to your account.
Google Ads (Google Ireland Ltd) — measures which advertisement brought a visitor, and only after that visitor agrees. Not used at all while advertising is switched off.

Retention

What you upload — the app's 540p analysis copies, or the originals on the website: about 24 hours, or about 72 hours for an account that has bought credits, so that the cut can be changed without uploading again. Deletion is enforced by the storage provider's own lifecycle rule, not only by our code. Finished reels: ~72 hours. Crash diagnostics (Firebase Crashlytics, release builds only): retained by Google per their policy and never linked to your account. Account data: kept until you delete your account, after which it is erased — including anything you had uploaded.

Your rights (GDPR)

You can access, correct, export or erase your personal data. You can delete your account and all associated data at any time from within the app ("Delete my account & data"). You may also contact us at [email protected], and you have the right to lodge a complaint with your local data-protection authority.

Cookies & local storage

We store a sign-in token in your browser's local storage to keep you logged in, along with a few preferences (which mode you chose, whether the timeline is open) and a random install id used only to group your own visits together. None of these identify you, and clearing your browser's site data removes them.

Advertising cookies — only if you say yes. When we run advertising, we ask before anything is set. Until you answer, and if you answer no, Google's advertising cookies are disabled and nothing about you goes to Google. If you answer yes, Google Ads sets cookies that tell us which advertisement brought you here — and, when you buy, that the purchase came from it. What travels is the amount and the goal, never your email, your name or your videos. You can change your mind by clearing this site's data.

Our own counters do not use cookies and do not need your consent: they count screens (someone opened the page, pressed make, got a reel) against a random install id, are sent to our own servers only, and go to no third party.

Security

All traffic is encrypted in transit (HTTPS). We do not store card data or passwords. Access to systems is least-privilege.

Changes

We may update this policy; material changes will be reflected by the "Last updated" date above.

Contact

[email protected]