Privacy Policy

Everything you make in the studio — your briefs, the titles derived from them, which projects you have pinned, the model, genre and aspect ratio you last used — is written to your browser's local storage on the device you made it on. It is not uploaded, not backed up, and not visible to us.

That has a consequence worth stating plainly rather than burying: work saved in one browser does not appear in another. Clearing site data for this domain deletes it, and nobody, including us, can restore it.

You can see exactly how much is held at any time under Settings → Data, and remove all of it with one button on that page.

The sign-up and sign-in screens ask for a display name and an email address. In this build both are stored in the same local storage as everything else and are used for one purpose: putting a name and an initial on the account plate at the top of the rail. Nothing is sent anywhere, no message is delivered to the address, and no password is stored.

You can change either at any time in Settings, and leaving them blank is a supported state rather than an error — the studio draws a signed-out plate and carries on.

Your theme (light, dark, or follow the system) and your interface language are kept in local storage under a separate key so that they can be applied before the page paints. They are read by a small script in the document head and by nothing else.

Breyvi sets no cookies for advertising, no cookies for analytics, and no third-party tags. The one exception is a functional cookie recording whether the studio rail is open or collapsed. This is covered in full by the Cookie Policy.

There is no analytics service in this build. No page views, no session recordings, no event stream, no fingerprinting. The figures the studio shows you — tokens remaining, projects saved, what you have made this month — are computed in your browser from what is already on your device, which is why they disappear when you clear it.

Generating a video cannot happen on your device, so when rendering is connected, the text of a brief and any reference files attached to it will be sent to the service that produces the video. That is the first point at which anything you write leaves your browser.

When it does, this policy will be amended before the feature ships, and the amendment will name what is sent, how long it is kept, and which providers process it. Until then no such transfer takes place, because there is nothing on the other end of it.

Requesting a page from Breyvi involves a web server, and web servers keep ordinary request logs — an IP address, a timestamp, the path requested, and the browser's user-agent string. These are operational records used to keep the site up and to investigate abuse. They are not joined to anything you make in the studio, because nothing you make in the studio reaches the server.

Data protection law gives you rights over personal data held about you: to see it, correct it, have it erased, and object to its processing. Where your data lives entirely in your own browser, these rights are ones you exercise directly and immediately rather than by asking us.

• To see everything held: Settings tells you how many briefs are stored, and your browser's developer tools show the stored value in full.
• To correct it: edit the project, or the name and address in Settings.
• To erase it: Settings → Data clears the studio's storage for this browser.

Breyvi is not directed at children and is not intended for use by anyone under 13, or under the age at which processing requires parental consent where they live, whichever is higher.

When this policy changes, the effective date at the top of the page changes with it. Changes that widen what is collected or where it is sent will be described in the studio before they take effect, not after.