Trust
Security
Last updated 27 August 2026
A screen recorder sees everything on your screen, so it should have to earn trust structurally, not ask for it. Reverie's answer is to hold as little as possible: your recordings are made and kept on your own machine, the app sends us nothing about them, and the permissions it asks for are the narrowest that exist. This page lists the claims — and, where possible, how to verify them yourself.
Local-first, by architecture
Every recording is captured, edited and rendered on your machine, and the original always lands on your own disk first. No video is ever processed on our servers — on the free tier your videos never reach our servers at all, and on paid tiers a hosted video is stored and served exactly as your machine made it, never opened or analysed. There is no code path by which we could watch your recordings.
The narrowest Google scope that exists
If you connect Google Drive, Reverie requests exactly one file scope:
https://www.googleapis.com/auth/drive.file
It reaches only files Reverie itself creates — never your documents, photos, or anything made by another app. We will never request a wider Drive scope. This one is worth dwelling on: Reverie is closed-source, so you cannot read the code — but you don't have to take our word for the scope, because Google enforces it, not us. Verify it any time at myaccount.google.com/permissions — it will say Reverie can only see files it created. Sign-in adds only openid and email, which reveal your email address and nothing else.
No telemetry
The app contains no telemetry, no analytics, and no crash reporting. The only network traffic to us is sign-in, a cached subscription check that carries no recording data, and uploads you start yourself. You can confirm this from the outside with any network monitor — the app is quiet unless you ask it to do something.
The recorder does not depend on us
Your subscription state is cached on your machine and degrades gracefully: if our servers are unreachable, the app keeps its last known state and keeps working. A server outage — or Reverie disappearing entirely — can never lock you out of the recorder or interrupt a take.
Signed and notarised builds
Release builds are signed with an Apple Developer ID certificate and notarised by Apple, which means Apple has scanned the exact binary you run and macOS verifies its integrity at launch. Verify a build yourself:
spctl -a -vv /Applications/Reverie.app
Only ever download Reverie from reverie.video — a copy from anywhere else may not be the app we shipped.
What we hold, and where
The complete inventory is in the Privacy Policy: an account record (email, plan, storage used), and hosted videos on paid plans. Payment details never touch us at all — checkout runs entirely through Paddle, our merchant of record. The less we hold, the less there is to breach.
Reporting a vulnerability
If you find a security issue in the app, the website, or the hosted service, email [email protected] with "security" in the subject line. Include what you found and how to reproduce it. You will get a human reply within 48 hours, and a fix is the top priority until it ships.
We ask for coordinated disclosure: give us a reasonable window to fix the issue before publishing it, and don't access other people's data while demonstrating a bug. Reverie is an independent product without a paid bounty program — but reports are credited, if you want the credit, and always answered.