Privacy Policy

Last updated: July 20, 2026

Reelvana is built so your content stays yours. Your video never leaves your phone. But Reelvana is not a no-network app, and this policy says so plainly: it explains what stays on the device, the cloud features and exactly what each one sends, the analytics and crash reporting the app ships with, and how to delete what we hold.

1. Your video stays on your device

Recording, the teleprompter (it scrolls your script at a speed you set, and you hold to pause it; it does not listen to you), on-device captions (Whisper transcription), silence and filler removal, background blur and replace, editing, transitions, watermarks, and export all run locally on your phone. Reelvana never uploads your video file, and these core steps work offline. Your scripts also stay on the device unless you use the AI writing tools described below.

Your recordings, projects, and exports live in the app's own storage and in whatever you save to Photos or your Gallery. They leave your device only through a share you start yourself, or, if you switch it on, as audio for cloud captions (section 3).

2. The two IDs Reelvana creates

There is no account: no name, no email, no password, no sign-up. Instead the app creates two random identifiers, and we would rather describe both than pretend there is one:

• An anonymous user ID, created by Firebase Anonymous Authentication. It identifies your purchase to RevenueCat, carries your cloud-feature usage allowance, and tags your invite links.
• A device ID, generated separately on the device. It keys crash reports and your push-notification registration.

Neither is linked to your name, email, or phone number, and neither lets us work out who you are. They are how an anonymous app tells one install apart from another. You can view and copy your user ID from the Account screen, reached from the top of the app's Settings, useful if you ever need support to look up a purchase.

3. The cloud features, and what each one sends

Most of Reelvana runs with the network off. Three features do reach the internet, and this section lists everything each one sends.

• Cloud captions, the on-device caption model is the default and keeps everything local. If you switch to the cloud caption model instead, Reelvana extracts the audio track from your clip and sends that, and only that, to our transcription endpoint. Our server passes the audio on to OpenAI or ElevenLabs to transcribe it, and their policies govern the audio from that point. Your video file is never sent, not to us, not to them. Our server does not save the audio to disk.
• AI script writing, when you generate, improve, translate, or extract a script, the text you typed is sent to our server, which passes it to OpenAI. If you use the "extract from a link" action, the URL you paste is sent too, and our server fetches that page. Your video and audio are not sent.
• Vana, the voice assistant (Pro only), sends two different things at two different moments, and we would rather spell out both.
  • First, your recorded command. When you tap the microphone and speak, Reelvana records to a temporary file. It stops on its own once you stop talking, so a normal command is a few seconds, but the recording can run up to 12 seconds before it is cut off, and whatever the microphone picked up in that window is what gets sent. On the default Recognition setting of "Cloud first" it sends that recording to our transcription endpoint, the same one cloud captions use, and from there it goes to OpenAI or ElevenLabs, exactly as above, whose policies govern the audio from that point. This is real microphone audio, not a summary or a fingerprint of it.
  • Second, and only sometimes, the words you said. Once your command has been transcribed, Reelvana tries to turn it into an action on the device. When the transcript came back with at least two words but the on-device rules could not work out what you meant, it asks for help: it sends your whole transcribed sentence to a second service of ours, a Cloudflare Worker separate from the transcription endpoint above, which passes it to OpenAI. To be exact about this, the full transcript leaves your phone. Our Worker trims it to the first 500 characters after it arrives, so the trimming protects our costs, not your privacy. Sent alongside it are a two-letter language code, a true or false for whether you have an edit open, and a short line of numbers describing that edit: how long the timeline is, where the playhead sits, and how many images, titles, music tracks and video overlays it holds. No audio, no video, no filenames and no script text are sent on this step.
  Before the first upload, Vana asks. The prompt is headed "Where should Vana listen?" and offers two answers, "Send it to the cloud" or "Keep it on device". Nothing is sent until you answer. This consent choice is available in Reelvana 1.2.0 on iPhone and Android. If your copy of the app has not updated yet, it does not ask, and you can set Recognition to "On device" yourself instead. If you dismiss it without choosing, nothing is recorded and nothing is sent, and you are asked again next time. Answering "Keep it on device" stops both legs, not only the audio: for that command and every later one, no recording, no transcript and none of the editor-state numbers leave the phone. That choice costs you something and we would rather say so, because Vana then works from a fixed offline vocabulary and understands fewer ways of phrasing a request. You can also decide in advance. Vana needs Pro, and once you have Pro it is switched on for you. Its Recognition setting has three positions: "Cloud first", the default, which tries the cloud and falls back to the on-device model when the network is gone; "Cloud only"; and "On device". You will find it under Settings, then Vana. Picking either cloud option there is itself the permission, so the prompt does not appear afterwards. Your answer is deliberately kept out of your phone's cloud backup, so restoring onto a new device does not quietly carry a permission across. After each command Vana tells you which path it used, "heard in the cloud" or "heard on device".

One limit worth stating plainly. Your answer to the prompt governs both legs, but the Recognition setting governs only the audio one. If you answer "Send it to the cloud" and later switch Recognition to "On device", your voice recording stops leaving the phone, but a sentence the offline rules cannot read is still sent on as text, with the editor-state numbers beside it. There is currently no control in the app that turns that second leg off on its own, and no way to withdraw an answer once it is given. If you want neither leg to leave the phone, answer "Keep it on device" when you are asked.

These calls only happen when you use the relevant feature. We keep a per-request count of how much you use them, so we can enforce the free limits. That record holds the provider name, the model name, the number of seconds of audio, the kind of request, and your anonymous user ID, and nothing else. The text of your scripts, the words you say to Vana, and the audio itself are not stored in it. Our transcription server holds your audio in memory only for as long as the request takes, and never writes it to disk.

One thing we cannot promise. When a transcription or AI provider returns an error, we record that error so we can fix it, and the record includes the provider's own error message alongside your anonymous user ID. We have not been able to rule out that such an error message could quote part of what was sent to it. We would rather tell you that than claim a guarantee we have not verified.

Two smaller connections, for completeness. Our transcription endpoint counts requests that arrive without an anonymous user ID against the sending IP address, so an unidentified caller cannot run up the bill. That counter lives in memory, covers a one-hour window, is never written to disk, and is never passed to anyone else. Separately, the first time you make captions on the device, the app downloads a speech model from Hugging Face, a public file host. That download tells them your IP address, the same as visiting any website, and carries none of your content.

With cloud captions switched off, which is the default, and Vana's Recognition set to "On device", no audio leaves your phone at all.

4. Analytics, crash reports, and notifications

Like most apps, Reelvana ships a few standard Google and third-party services. These are active from first launch:

• Firebase Analytics, anonymous product events, so we can see which features get used and where people get stuck. The events are things like: a recording started, the teleprompter was used, a project was opened, an export started or finished, the paywall was shown, a plan was selected, a purchase completed.
• Firebase Crashlytics, crash stacks plus device and OS details when the app falls over, keyed to your device ID.
• Firebase Cloud Messaging, a push token so we can send app updates and occasional announcements. Turn notifications off in your device settings and nothing is delivered.
• Firebase Authentication, the anonymous user ID described above.
• RevenueCat, records your Pro purchase and subscription state against your anonymous user ID.

The app also checks in with our own server when it launches, to register for push and to ask whether a required update is available. That check sends your device ID, push token, platform, app build, and device locale. It sends no media, audio, transcript, or script text.

There is currently no in-app switch to turn analytics or crash reporting off. We would rather tell you that than imply a control that does not exist. If you do not want the app reporting anything, the only option today is not to install it. We are looking at adding an opt-out.

None of this ever carries your content. Your video, your microphone audio, your transcripts, and your script text are never sent to us for analytics or crash reporting. The only content that leaves the device is what the features in section 3 send, and only when you use them. We do not sell your data.

5. Purchases

Pro subscriptions and the lifetime purchase are billed by Apple or Google under their own terms. We never see your card or payment details. RevenueCat manages your subscription status and receives the purchase and your anonymous user ID, so the app knows whether Pro is active.

6. Inviting friends

If you use the invite feature, Reelvana creates a short random invite code tied to your anonymous user ID. You can optionally add a first name so a friend's screen can say "Sara invited you" instead of "You've been invited", it is optional, it is shown to people you invite, and you can leave it blank or clear it. When someone redeems a code, we store a record linking the inviter's and invitee's anonymous IDs along with whether the free days have been granted, so rewards get delivered and invite limits stay honest. No IP address, device ID, or advertising ID is stored on these records.

7. Sharing

Every share goes through your phone's own share sheet. Reelvana hands the finished file to the app you chose (for example TikTok, Instagram, YouTube, or your messages) and the receiving app's privacy policy takes over from there. There is no direct in-app upload to any social network.

8. Permissions

Reelvana asks for the camera and microphone to record, for on-device speech recognition to power captions, and for photo library access to import and save clips. You can change these any time in your device settings; the app degrades gracefully when a permission is declined.

9. Advertising ID, and how the two platforms differ

Reelvana shows no ads inside the app, on either platform, and no Reelvana code reads an advertising identifier. But we do run ads for Reelvana elsewhere, and the two platforms handle the measurement differently. Rather than give you one tidy sentence that is only half true:

• Android, the app carries the advertising ID permissions, which come from Google's measurement library. This lets Google Ads tell that an install came from one of our ads. You can reset or opt out of the advertising ID in your Android settings.
• iOS, the app ships no advertising frameworks and no access to the IDFA. You will never see a tracking prompt from Reelvana, because there is nothing behind it. Install measurement on iOS uses Apple's own system-level mechanism, which does not identify you to us.

On neither platform do we track you across other companies' apps or websites, and we do not share your data with data brokers.

10. How long we keep things

We will not quote you a tidy number we do not actually enforce.

• On your device, your recordings, projects, exports, scripts, and settings stay until you delete them or uninstall the app. We cannot reach them.
• On our servers, your device registration, push token, invite records, and cloud-feature usage counts are kept until you ask us to delete them, as described in section 11. There is no fixed automatic expiry schedule for these records today, and we would rather say that than invent one.
• Cloud-feature content, audio sent for cloud captions is transcribed and not saved to disk by our server. What OpenAI or ElevenLabs retain is governed by their policies. Script text is not stored in our usage records.
• Analytics and crash data, held by Firebase under Google's retention settings for that product.
• Server logs, our hosting provider keeps short-lived request logs (IP address and timestamp) as ordinary infrastructure logging. They are not searchable by your ID.

11. Deleting your data

You can delete your data from inside the app: open Settings, then Account, then Delete my data. There is a step-by-step guide, with the full list of what is deleted and what is kept, on Delete your data. The in-app deletion control is available in Reelvana 1.2.0 on iPhone and Android. If your copy of the app has not updated yet, the button will not be there. Either way you can email us at reelvanaapp@gmail.com and ask, and we will run it for you.

What we delete outright:

• Your device registration and push notification token.
• Your invite code and the optional name attached to it.
• Your cloud-feature usage records, AI script usage rows, cloud-caption usage counts, any error records tied to you, and any custom allowance set on your account.
• On the device itself: your saved settings, and your link to the anonymous user ID, the app starts fresh with a new one.

What we keep, and why: a record of an invite between two people is a record about someone else as well as you. If we deleted it because you asked, a friend who had earned free Pro days could silently lose them, or an inviter could quietly get an extra slot back. So those records survive with your ID replaced by an unlinkable placeholder. What remains is a bare fact, some account invited some account, that no longer points at you.

What deletion cannot reach:

• Purchase records held by Apple and Google. These are their records, not ours, and they are retained for tax, refund, and chargeback obligations. They cannot be deleted on request.
• Your Pro entitlement at RevenueCat. We deliberately leave this alone, deleting it would revoke Pro you actually paid for. If you want it removed too, email us and say so.
• Anonymous totals. Aggregate usage and cost counters were never keyed to your ID, so there is no row identifying you to delete.
• Short-lived infrastructure logs at our hosting provider, which age out on their own.

Deleting your data does not cancel a paid subscription. Those are two different things. To cancel or manage a subscription, use your App Store or Google Play account settings, that is the only place it can be done.

You can email the same address to ask what we hold about an ID. Our address, written out in plain text, is reelvanaapp@gmail.com (the same address linked in section 13).

12. Children

Reelvana is a general-audience tool, not directed at children under 13, and we do not knowingly collect personal information from them. We hold no name, email, or personal profile for anyone. The analytics and crash reporting described above are anonymous and are not used to build an advertising profile.

13. Contact

Questions about privacy, a deletion request, or anything you want explained? Email [email protected].

14. Changes

If this policy changes, we will update the date above and post the revision here before it takes effect.