Security
Last updated 22 September 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.
Made on your machine, by architecture
Every recording is captured, edited and rendered on your machine. No video is ever processed on our servers: the videos in your Collection are stored and served exactly as your machine made them, 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 subscription check that carries no recording data, and your finished takes going to your Collection. You can confirm this from the outside with any network monitor — the app is quiet unless you ask it to do something.
A take does not depend on us
Nothing is streamed to us while you record, so once a take has started a lost connection or a server outage cannot interrupt it. The finished take waits in your browser until it can be uploaded.
Where to get Reverie, and how to know it is ours
There are exactly two places, and nowhere else is us:
- The Chrome extension — from the Chrome Web Store, linked from reverie.video. The store serves the exact package we uploaded and updates it the same way, so there is nothing to verify by hand. A "Reverie" extension from any other source is not one of ours.
- The recorder on this website — nothing to install, served over HTTPS from reverie.video.
The Mac app, when it is released, is a signed and notarised build: signed with an Apple Developer ID certificate and scanned by Apple, so macOS verifies the exact binary at launch. It will be downloadable only from reverie.video, and you can check any copy yourself:
spctl -a -vv /Applications/Reverie.app
What we hold, and where
The complete inventory is in the Privacy Policy: an account record (email, plan, storage used), and the videos in your Collection. 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.