Privacy

Euxie Weave (“Weave”) stores what you put into it and what it makes for you: your projects and series, the concept and script of each, any source document you attach, the generated images, narration and music, and your Gemini API key (and an ElevenLabs key, if you add one) — encrypted, and readable only by the code that spends it on your behalf. Each account can see only its own rows and files; that is enforced by the database and the storage policies, not by the application code. The maintainer can read projects, scripts and usage figures for support and operations — never your key, whose ciphertext is withheld from that access too.

What goes to Google

Every generation runs on Google's Gemini API under YOUR key: the script call sends your concept and any attached source, each image call sends that scene's prompt and the style reference, each narration call sends the scene's words, and each music call sends the music description. In an animated explainer, redrawing a scene sends that scene's narration and your concept; a sprite call sends the name of the thing to draw; a picture call sends its description and labels, and placing its callouts sends the generated picture back with those labels. Google's API terms govern that processing, and its charges appear on your own bill. Nothing is sent until you click a generate button.

What goes to ElevenLabs, if you choose it

If you save an ElevenLabs API key and pick an ElevenLabs voice for an animated explainer, that project's narration is recorded by ElevenLabs under YOUR key: each narration call sends the scene's words (and its neighbours', so the delivery flows). The key is stored encrypted exactly like the Gemini key. ElevenLabs' terms govern that processing, and its charges fall on your own plan. Without an ElevenLabs key nothing is ever sent there.

The video

The finished video is encoded in your browser; this app's storage holds its ingredients, not the file. One copy does leave the browser — as telemetry, below.

The finished video is also kept in the browser that made it, on that device, so it is still there after a reload: the file, and a record of what it was rendered from. It is not uploaded, it is not encrypted, and it is shown only to the account that rendered it. It stays there after you sign out, until you delete it from the render page or from Settings, clear the browser's site data, or delete your Weave data on that device. On a shared computer, delete your videos before you leave it.

Usage telemetry

Separately from the data above, and to understand how Weave is used, it also records what you do here as telemetry. This is a second copy, keyed to your browser and, while you are signed in, linked to your account as well, and it includes the content — your concepts and scripts — plus the finished video. Specifically:

What we store

  • Your activity — which actions you take and when.
  • The content you process — the concept, settings and script of each project you create or edit — including how each scene of an explainer is drawn, the look you pick for it, and any words in a figure the app could not draw — your music descriptions, the voice you pick, the series you create, and the name and size of each generated image, clip and narration (never the media itself). Do not enter anything here you would not want stored, including passwords, secrets or personal documents.
  • Files you upload — the name, type and size of a source document you attach — never its contents are stored in our private file storage.
  • Files the app creates for you — the finished video and its subtitle file, when the video is under 4 MB are stored the same way, alongside the files you supplied.
  • Your network and device — your IP address, an approximate location derived from it, your browser and operating system, language, time zone, screen and window size, and similar technical details your browser exposes.
  • A device identifier — a random id kept in your browser’s storage so we can recognise return visits. It is also stored in a cookie so our servers can recognise the device. It is not tied to your name and clearing your browser storage resets it.
  • Page views via Vercel Web Analytics — the hosting platform records which pages are visited, referrers, and coarse device and country data. It sets no cookies and identifies a visitor only by a hash that changes daily, so it cannot follow you across days or sites.
  • Performance via Vercel Speed Insights — the hosting platform measures how quickly pages load and respond (Core Web Vitals), with the page, device type and country. It sets no cookies and does not identify you.
  • Your account — while you are signed in, telemetry recorded from this browser is also linked to your account (its id and email address), so we can see what one account did across devices. Deleting your account unlinks that telemetry but does not delete it: the records stay under the device identifier, without your account or email. To have them removed as well, ask separately (below).
  • Support access — to diagnose a problem, the operator can sign in to your account and see the app as you see it, without learning or changing your password. Each access is time-limited and logged, and does not sign you out anywhere else. Nothing done during it is recorded as your telemetry.
  • Feedback you send — your bug reports, feature requests and replies are stored linked to your account, so the maintainer can answer them on your Requests page, and each new report is also emailed to the maintainer. Deleting your account unlinks them but does not delete them.
  • Never your API key — the key is stored encrypted for the app's own use and is not part of any telemetry event.

How long we keep it

Stored data is retained indefinitely unless you ask us to remove it.

Requesting deletion

To have your data deleted, use the feedback button in the app (the message reaches James Argarin) and mention your device identifier if you have it. We will remove the associated records.

Your agreement and email choice

When you create an account, Weave records which version of the terms of use you agreed to and when, and whether you asked for product news and offers by email. That box starts unticked; you can change your answer under Account at any time. Deleting your account turns promotional email off; the record of what you agreed to is kept with your sign-in.

Bot check on sign-in

The sign-in, sign-up, password-reset and account forms run Cloudflare Turnstile, a check that the visitor is a person and not a script. It runs in a frame served by Cloudflare, which reads your network address and technical details of your browser to decide, and tells this site only whether the check passed. Cloudflare states that it uses those signals to detect and block bots, not to identify or profile anyone; its Turnstile privacy policy describes them.

Deleting your account

Account → Delete account removes every Weave row and every file belonging to you, immediately and irreversibly — download any video you want to keep first — and signs you out. The sign-in itself stays, because one account serves several apps by the same maintainer; delete it from each. Usage telemetry is unlinked from your account but not deleted — see above for how to have it removed. The delete control is switched on per app by the maintainer; if it is absent, ask through the feedback form.

Feedback

The feedback button in the header sends only what you type in it. It is stored with your account, emailed to the maintainer, and answered on your Requests page.

Back to Weave