Privacy Policy

Last updated 23 September 2026

The short version

• Recordings are made on your machine. When you are signed in, each finished take is uploaded to your Collection. We store it and never open it.
• Reverie reports nothing about how you use it. The only things that talk to our servers are signing in, checking your subscription, and the videos going to your Collection.
• The Chrome extension records only when you press record, saves the file to your own Downloads folder first, and carries no analytics. What each of its permissions is for is listed in full below.
• An account is an email address and a plan — plus the identifiers our payment provider gives us for your subscription, so we can tell which account a payment belongs to.
• Payments go through Paddle. We never see or store card details.
• Your Collection is yours to empty. Delete a video and it is gone from our storage, and its link with it.
• The mailing list is separate from all of that, opt-in with a tickbox you have to tick yourself, and you can leave it in one click at reverie.video/unsubscribe.

The three places Reverie runs

Reverie is one product in three places, and everything on this page is true of all three. Where something is true of only one, it says so.

• The Chrome extension — records from your browser's toolbar. This is the main way to use Reverie.
• The recorder on this website — the same recorder, at reverie.video/record, with nothing to install.
• The Mac app — a fuller studio, for later. It is not released yet; where this page describes file locations on a Mac, that is what it is describing.

In all three, the recording is made on your own machine by your own browser or your own computer. No video is ever processed on our servers, in any of them.

The Chrome extension — what it can reach, and when

An extension has to ask Chrome for permissions up front, and the list looks alarming if nobody explains it. Here is every permission Reverie asks for and the single reason it asks:

• Recording a tab, a window or your screen — used only after you press record and choose what to record. Chrome's own picker asks you; Reverie never selects for you, and never starts on its own.
• Showing controls on the page you are recording — the countdown, the stop button and the camera bubble are drawn onto that page. This is why Chrome warns that Reverie can "read and change data on all sites": it is the permission that lets those controls appear anywhere you might record. It is used only while a recording is running, on the tab being recorded, and removed when you stop. Reverie does not read page content, form fields, passwords or your browsing history, and sends none of it anywhere.
• The tab's title — read once, to give the recording a sensible name.
• Saving files — to write the finished recording into your Downloads folder, under Downloads/Reverie.
• Storage — your own settings, and your sign-in token if you sign in. Held in your browser.
• Google sign-in — only when you ask to connect Drive or to use a Reverie account. The Drive permission requested is drive.file and nothing else, which lets Reverie see only the files Reverie itself created. It cannot list, open or touch anything else in your Drive, ever.

The recording lands in your Downloads folder before anything else happens, and it goes nowhere else unless you choose a destination — your own Google Drive, or your Reverie storage on a paid plan. There is no analytics in the extension, no advertising, and nothing about you is sold or shared.

Recording on this website

reverie.video/record uses your browser's own screen, camera and microphone features, which your browser asks your permission for and you can withdraw at any time in the padlock menu. The picture and sound are assembled in the page, on your machine. Nothing is streamed to us while you record, and if you lost your connection mid-take the recording would carry on. When you stop, the take is kept in this browser and opens in the editor. If you are signed in, it is then uploaded to your Collection so it has a link; if you are not, it stays in this browser and never reaches us.

What Reverie sends us

Two kinds of thing, and nothing else:

• Sign-in and subscription checks. Reverie periodically confirms which plan your account is on. The check carries your account identity and nothing else — no recording titles, no file names, no usage data. It is cached on your machine, so Reverie works normally when you are offline or our servers are unreachable. If you never sign in, this never happens: recording needs no account.
• Your videos, to your Collection. On this website, a take you record while signed in is uploaded when it opens in the editor, along with its title and length. That file, as your machine made it, is all that is sent. See "Your Collection" below.

There is no telemetry, no crash reporting, no usage analytics and no event tracking in any of the three. We do not know when you record, what you record, or how often you open Reverie.

What stays on your computer

• Recordings — on this website, each take is kept in your browser's own storage for this site, so the editor can open it; clearing your browser data removes it. Anything you export is saved wherever your browser saves files. The extension saves to Downloads/Reverie, and the Mac app to ~/Movies/Reverie.
• Preferences — frame rate, resolution and similar settings. In the browser they are held by the extension or the page itself, and clearing your browser data clears them; in the Mac app they are in ~/Library/Application Support/app.reverie.desktop.
• Google credentials — the tokens Google issues you when you sign in or connect Drive, stored in that same folder. They leave your machine only in requests to Google's own API.
• Your subscription state — a cached copy, so the app never depends on our servers being reachable.

The mailing list

There is a sign-up form at reverie.video/signup for people who want to be told when Reverie opens. It is a list and nothing more: joining it does not create an account, is not a purchase, and gives you nothing to sign in to.

What it collects, and why each thing is there:

• Your email address — so we can write to you. Required, because a list with no address on it is not a list.
• Your first name, if you give one — so an email can say hello properly. Optional, and blank is fine.
• Where you heard about us, from the menu — the single most useful thing a one-person product can know, because it decides where the next month of work goes.
• How your visit started — the campaign tags on the link you first arrived on (utm_source and friends), the page you landed on, and the site you came from if you followed a link. This is kept in your browser for the length of the visit and sent only if you submit the form. It is deliberately the same question as the menu above, asked of the browser instead of you, because the two answers disagree often and the disagreement is the useful part.
• Whether you ticked the box, and the moment you ticked it.

The lawful basis is your consent, given by ticking a box that starts empty. Nothing is pre-ticked, marketing email is never a condition of anything, and if you submit the form without ticking it you are recorded as not having agreed and are not written to. The exact wording you agreed to is kept, with the date it took effect, in Reverie's own source history, so the question "what did I actually say yes to" has an answer that cannot be quietly edited.

Leaving. Every marketing email carries a link, and the page is always at reverie.video/unsubscribe whether you have an email to hand or not. It needs no account and no sign-in, takes one press, and is never a conversation. Leaving marks the record as unsubscribed rather than erasing it — that is what stops a later import or a mistake putting you back on. If you would rather the record itself were deleted, ask and it is deleted.

Where it is held. Not in a mailing tool. The list lives in Reverie's own database on Cloudflare and is read through fishpond.aryanfindsaway.com, which is the customer-records system the same developer builds and runs, on the same Cloudflare account. It is not a third party and your address is not shared with one. When an email is actually sent, it is handed to Resend for delivery — see the sub-processor list below.

What it is never used for. It is not sold, not rented, not passed on, not used to build a profile, and not joined up with anything about your recordings — which we could not do anyway, since we cannot see them. Account email (a receipt, a licence, a security notice) is a different thing and does not depend on this list, and leaving the list never stops it.

Your account

Reverie accounts use Google sign-in. When you sign in, we request the openid and email scopes, which tell us your email address and give us a stable identifier for your Google account — and nothing else. No profile data, no contacts, no access to anything in your Google account.

For each account we store:

• an internal account id and the stable identifier from Google;
• your email address, so we can reach you about your account;
• your plan, subscription state, and how much of your hosted-storage allowance is used;
• if a payment has failed, when your grace period ends.

That is the whole record. We keep no metadata about the recordings on your own machine, no history of what you have recorded, and no log of viewers tied to you or to anyone else.

Your recordings — what we can and cannot see

All rendering, transcoding, effects and thumbnails happen on your machine. Our servers have no code that opens, decodes, scans or processes video. A file you host with us is stored and served exactly as your machine made it — stored and served, never processed. We do not watch it, analyse it, or generate anything from it.

What happens to a video you record

If you are signed in, it goes to your Collection as soon as it opens in the editor — that is what puts a link in your hand without an extra step. Nobody can find it unless you give them that link, and you can make it private, add a password, or delete it at any time. If you are not signed in, it stays in your browser and never reaches us.

What we never do to a video in your Collection: process it. It is stored as your machine made it and served back byte for byte. No transcode, no thumbnail pass, no scanning, and no model reading your screen.

Google Drive access

Connecting Drive is optional; Reverie records and edits perfectly well without it. If you connect it, Reverie requests a single file scope:

https://www.googleapis.com/auth/drive.file

This scope grants access only to files Reverie itself creates. Reverie cannot list, read, modify or delete anything else in your Drive — not your documents, not your photos, not files created by other apps. It is the narrowest scope Google offers for writing files, and we will never request a wider one.

With it, Reverie does exactly three things:

• creates a folder named Reverie in your Drive;
• uploads the recording you asked it to upload;
• sets that file's sharing to "anyone with the link can view", so the share link works, and returns the link to you.

The uploaded file belongs to you and counts against your own Google storage. You can change its sharing or delete it from Drive at any time, and revoke Reverie's access entirely at myaccount.google.com/permissions. Reverie's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. We do not transfer, sell, or use that data for advertising, and no human at Reverie ever reads it — we have no mechanism by which we could.

Your Collection (hosted videos)

Every plan includes hosted storage — 2 GB during the free week, 50 GB on Quick — and it is where your videos live, each with its own reverie.video link. For each video we store the file itself, its size, length and picture size, the title you gave it, the settings you chose for its link, and a count of how many times it has been opened. That count is a single number: we do not record who opened it, from where, or when. You can delete any video from your Collection at any time.

Hosted videos are kept until one of these happens:

• You delete the video — it is removed from our storage and its link stops working.
• Your free week ends without a subscription — your links stay live for 7 more days, then the hosted files are deleted.
• Your subscription ends or a payment fails — your links stay live for a 30-day grace period, then the hosted files are deleted. Anything you exported to your computer is yours and is not touched.
• You delete your account — hosted files and the account record are deleted together.

A hosted link is viewable by anyone who has it, so treat it as you would any unlisted URL. Viewing a hosted video sets no cookies and runs no visitor analytics. The only thing a view changes is the counter described above — a number attached to the video, never to the viewer. Our infrastructure keeps standard, short-lived server logs (IP address, timestamp, requested path) for operations and abuse prevention.

Payments — Paddle

Subscriptions are sold through Paddle, our merchant of record. When you subscribe, the checkout is Paddle's: they process your payment, handle applicable taxes, and issue your invoice. We never see or store your card, bank or billing details — Paddle tells us only that a subscription exists, which plan it is on, and whether its payments are current. Paddle's handling of your data is described in Paddle's privacy policy.

Cookies

This site sets no cookies of its own and runs no analytics. The one exception is honest and specific: the Paddle checkout sets cookies when you open it — Paddle uses them to run the checkout and prevent payment fraud. They are Paddle's cookies, set by Paddle, and covered by Paddle's privacy policy linked above. If you never open the checkout, no cookies are set.

One thing is stored in your browser and is worth naming rather than hiding behind the word "cookie", because it is not one. When you arrive from a link with campaign tags on it, those tags, the page you landed on and the site you came from are written to this site's sessionStorage — which lives in the tab, dies when you close it, cannot be read by any other site, and never reaches us unless you fill in the sign-up form and press the button. It exists because people arrive on the homepage and sign up four clicks later, by which time the link they came in on is long gone. There is no identifier in it, nothing follows you between visits, and there is nothing here that needs a consent banner.

Sub-processors

Three companies process data on Reverie's behalf or at your direction, and this is the complete list:

• Cloudflare — hosts this website, stores and serves the videos in your Collection, and runs the service behind accounts and subscription checks. Cloudflare's privacy policy.
• Google — sign-in, and Drive uploads when you choose to connect Drive. The only Drive permission Reverie ever requests is drive.file: it can see the files it created and nothing else in your Drive. Google's privacy policy.
• Paddle — payments, tax and invoicing, as merchant of record. Paddle's privacy policy.
• Resend — delivers email. It is handed the address and the message at the moment one is sent, so that the message arrives; it is not the list, and the list is not kept there. Resend's privacy policy.

If this list ever changes, this page will be updated first.

Your rights

You can ask us, at any time, to show you the data we hold about you, correct it, export it, or delete it. Email [email protected] from your account's address and we will act on it — there is little to hold, so none of these requests are complicated. Deleting your account deletes your Collection and your account record. Anything you exported to your computer is unaffected, because it was never ours to begin with.

Withdrawing consent to marketing email needs no email to us at all. It is a press at reverie.video/unsubscribe, and it takes effect immediately. Withdrawing it does not affect anything that happened while it was given, and does not touch your account.

How long we keep things

• Account record — for as long as the account exists.
• Videos in your Collection — until you delete them, or 30 days after your subscription ends (7 days after a free week that was not followed by one).
• Payment records — held by Paddle under their own retention rules; we keep only subscription status.
• Server logs — standard operational logs, kept briefly for operations and abuse prevention, then discarded.
• Mailing-list record — for as long as you are on the list. Leaving marks it unsubscribed and keeps it, which is what stops you being added back by a later mistake; ask and it is deleted outright.

Children

Reverie is not directed at children under 13, and we do not knowingly collect information from them.

Changes

If this policy changes, the revised version will be posted here with a new date, and any change to what the app transmits will be called out in the release notes for the version that introduces it. You can verify the access Reverie holds on your Google account at any time at myaccount.google.com/permissions.

Who is responsible

Reverie is a trading name of Franz D'Sa, an individual developer, who is the data controller for the processing described above. The controller's address is Hauz Khas Village, New Delhi 110016, India.

Contact

Questions or concerns: [email protected]. More ways to reach us are on the contact page.