Privacy Policy

Last updated: 21 October 2026

This policy explains what personal data VibeSlate ("VibeSlate", "we", "us") processes when you use our website, application and related services (the "Service"), why we process it, and the choices you have. It forms part of our Terms of Service.

1. Data we process

Account and identity data. If you register with email, we store that email address as your login identity, a hash of the six-digit verification code with its expiry, resend time and attempt count, and the time you registered. If you register with Google, we request only the openid email scope and store the account identifier Google returns for you together with that email. We never receive or store a password. We also store a normalised form of your email (with any + alias part removed) used solely to decide whether a signup bonus is due, an internal flag marking staff accounts, the two-letter country your first request came from, reported by our network provider, and the browser identification string (user agent) of that first request.

Form of address. Many of the languages the assistant writes in change their word forms for a man or a woman. Once, after you register with an email address, a language model receives that address alone and answers he, she or unknown, judging only by a clearly gendered first name in it and never by the domain. We store that one word on your account and use it only so the assistant's replies take fitting grammatical forms. It never changes what the Service does for you or what it costs, is not shown to anyone else and is not used for advertising; unknown keeps the neutral wording anonymous accounts get. To correct or clear it, email [email protected].

We keep selected campaign tags and click identifiers from your landing address, the referring site's origin, browser language, device category, visit time and available country. Your initial attribution is preserved when you register; later visits and account merges retain their original visit references. We record editor readiness, accepted tasks, preview results, registration, exports, failures and top-up choices, including the selected USD amount and payment method. These records help us evaluate campaigns internally. Advertising conversion delivery to external platforms is currently disabled. Top-up attempts are marked as mock activity and are not purchases or revenue. We do not use these records to show you ads.

Anonymous session data. You can use the Service without registering. We then create an account record with no email and place a signed session cookie in your browser. Your free credit balance is not attached to that record but to a keyed hash of your network address (the IPv4 address, or the IPv6 /64 network), so everyone using the same network shares one free balance and one set of top-ups. We store that hash, not the address itself. We also derive, from a local database and without contacting a third party, whether your address looks residential or looks like a proxy, VPN or data centre, and record that result and the free amount granted for abuse control. The same kind of hash is stored on registered accounts to limit how many bonuses one network can claim.

Project content. The files you upload (video, audio, images and other media), the prompts, scenarios and instructions you write, derived material generated from them (transcripts, descriptions, waveforms, previews, proxies, figures, generated voices and sounds, browser recordings, exported videos), and the project structure itself, including project names, timeline state and your chat history with the editor. Project content may contain personal data if you choose to include it; you decide what you upload. Separately from the project itself we keep a small record per stored media item — its content hash, kind, origin, byte size and, where applicable, the original file name and file type — so we can account for storage.

Credit and cost records. An append-only ledger of every credit grant, charge, refund and top-up attempt, with the resulting balance, an event type, a reference to the operation and audit details such as the amount and payment method you attempted. Separately, one immutable record per priced piece of computing work, holding its time, category, your account identifier, the project, the internal cost in US dollars and, where the provider returns one, the identifier of that provider request. These are accounting records and are not editable after the fact.

Diagnostic traces. For each turn you send, we store a technical trace in that project: the timing and status of every internal step, token counts and costs, error messages, and the full text of the requests sent to the model, which includes your prompt, the project state we sent with it and the tool calls it made. Media inside such a request is replaced by a marker rather than copied. Traces exist to debug and explain a turn, and they are shown in the editor: every account sees a reduced summary, and staff accounts can open the complete trace.

Support requests. If you ask the editor to escalate to a human, we store your account identifier, the project, the turn and a written summary of your problem, and email it to our support address so a person can answer you. This requires a registered email address.

Usage and technical data. Server request logs containing the time, method, requested address, IP address and port, browser and device information, feature and error events, and capacity and reliability measurements. The editor in your browser also sends us short diagnostic events, such as that a message was sent, how many files it carried and how long the reply took, and, when the editor encounters a fault, the error message with its technical stack trace, the page address, your browser type and the app version, so we can find and fix the problem. These logs are linked to your account and project identifiers, are never used to profile you, and are rotated automatically within a fixed storage limit.

Session recordings and heatmaps. During our launch period we use Hotjar (Hotjar Ltd, Malta, part of Contentsquare) to see how the editor is actually used and to find usability faults and bugs. Its script is loaded only after you start interacting with a page. From then on it records your pointer movements, clicks, taps and scrolling, the pages you view, the visible structure of the page, your viewport size, browser and device type, an approximate location derived from your IP address, and a random visitor identifier kept in a cookie. Text you type into fields is masked by Hotjar before it leaves your browser; the timeline canvas and the media you upload are not captured. Chat messages and the editor's replies are page text and may therefore appear in a recording, so do not put into the chat anything you would not want a member of our team to read back. We do not pass Hotjar your email address or account identifier. You can stop this recording at any time by enabling your browser's Do Not Track setting or through Hotjar's opt-out page.

Payment data. Credit purchases are sold and processed by PLACEHOLDER, our reseller and merchant of record, which collects your payment details, billing address and applicable tax on its own checkout under its own privacy notice. We give PLACEHOLDER your account email to prefill that checkout, the amount and an internal reference, and receive only the result: its status, order reference, amount, tax and currency. We never receive or store card numbers.

2. Why we process it and on what basis

We do not sell personal data, we do not use your project content for advertising, and we do not use it to train our own models.

3. Automated processing and subprocessors

Producing the results you ask for requires sending relevant parts of your project content and prompts to third-party processors. We send only what a given operation needs and instruct these providers to process the data on our behalf. Some of them may retain content briefly for abuse monitoring under their own terms.

Browser recording opens public web pages you describe in a scenario and captures the resulting frames. Anything visible on the recorded page, including data you cause it to display, becomes part of the recording.

The Service does not make decisions producing legal or similarly significant effects about you by automated means. The residential-or-proxy classification described above affects only the size of a free credit grant, never your access to the Service or your ability to register.

4. Cookies and local storage

We use the following storage. We do not install an advertising pixel or cross-site tracking cookie:

• vibeslate_session — the signed session cookie identifying your account. It is HttpOnly, Secure and SameSite=Lax, is not readable by scripts, and lasts up to 120 days.

• Browser local storage — the identifier of the project you had open, so a reload returns to it.

• Limited first-party browser storage — used to reduce repeated use of free offers.

• Browser session storage — your current timeline view, acquisition visit reference and selected campaign tags, plus a bounded queue of measurement events awaiting delivery to our server.

• Cache storage — files you share into the installed app from your phone, held only until the editor picks them up. The service worker caches no application content.

• _hj… cookies — set on our domain by the Hotjar script described in section 1 to tell one visit and one visitor from the next. They appear only after you begin interacting with a page; the session cookie lasts 30 minutes and the visitor cookie up to 365 days.

Clearing this storage signs an anonymous session out permanently and its projects can no longer be reached, because there is nothing else identifying you.

5. Sharing

We share personal data with the processors described above, with professional advisers, and with authorities or other parties where required by law or where necessary to establish, exercise or defend legal claims, to enforce our Terms, or to protect the rights and safety of our users and third parties. In a merger, acquisition or sale of assets, data may transfer to the acquirer subject to this policy.

Our own staff can access account, credit, cost and support records through an internal backoffice, and can access project data and diagnostic traces where that is needed to operate the Service or to answer a support request. Such access is limited to the people who need it.

If you publish an exported video, the video becomes accessible to anyone who has its public link until it is removed. The link contains no account information, but the video itself contains whatever you put in it.

6. International transfers

Our providers may process data outside your country, including in the United States. Where such a transfer leaves the European Economic Area or the United Kingdom, it is covered by an adequacy decision or by standard contractual clauses together with additional safeguards where required.

7. Retention

Project content, its derived material, your chat history and the project's diagnostic traces are kept while the project exists. Archiving a project hides it from your list but does not delete it. Deleting a project or an account removes its content, subject to short-lived backups and caches that expire in the ordinary course; media that other projects of yours still reference stays as long as those projects do. Anonymous accounts with no projects and no cost history are removed once their session can no longer be valid; anonymous accounts that still own projects are kept until you ask us to delete them.

Email verification challenges expire within minutes and are deleted once used. Failed browser capture artefacts are kept for seven days for debugging. Hotjar recordings and heatmap data are deleted by Hotjar within 365 days. Traces of uploads whose message was never sent are discarded within an hour. Credit ledger entries, cost records and export mappings are immutable accounting and integrity records and are kept as long as legally required, typically for accounting and tax periods, even after the related project is gone.

8. Security

We use technical and organisational measures appropriate to the risk, including transport encryption, HttpOnly session cookies, request origin checks, access control, keyed hashing of network addresses and isolation between projects. Signed media links are time-limited and bound to the file they grant. No service can be completely secure, and we cannot guarantee absolute security. Keep your email account protected, and do not upload material you cannot afford to have exposed.

9. Your rights

Subject to applicable law, you may request access to your personal data, its correction, deletion or portability, restriction of or objection to processing, and withdrawal of consent where processing relies on consent. Withdrawal does not affect processing already carried out.

You can remove an attachment before sending it, and archive a project from the editor. Deleting a project or an account is handled on request at the address below; we may need to verify your identity. We cannot delete individual credit ledger entries or cost records, because they are append-only accounting records; a correction is recorded as a further entry. You also have the right to lodge a complaint with your local data protection authority.

10. Children

The Service is not directed to children under 16, and we do not knowingly collect their personal data. If you believe a child has provided us with personal data, contact us and we will delete it.

11. Changes

We may update this policy. Material changes take effect when the updated policy is posted with a new "last updated" date. Continued use of the Service after that date means you accept the updated policy.

12. Contact

Privacy questions and data requests: email [email protected]. A person replies within three business days. You can also ask in the editor chat.