Privacy
Free public beta · last updated 2026-07-30
This page describes what linel stores, why, and for how long. If something here is unclear, ask the service operator directly before relying on it.
What we collect
| Data | Why |
|---|---|
| Google account identity (a stable internal ID, not your email in most places) | Sign-in, tied to your account and credit balance |
| Prompts you submit, and the sequence of prompts in a chained/multi-clip generation | To generate motion, and reviewed to understand usage and improve quality |
| Selected model, generation settings (length, guidance) | To generate motion and compare model performance |
| Generated outputs (the motion data itself) | So you can view and replay your own results |
| Feedback: rating, fault tags, match-to-prompt score, written notes | To evaluate and improve models — this is central to what the beta is for |
| Usage records: which account, which generation, when, whether it succeeded | Capacity management, abuse prevention, debugging |
| Technical/session logs (IP address at request time, browser session identifiers) | Security, rate limiting, diagnosing problems |
| Session cookie | Keeps you signed in; not used for tracking outside linel |
Pseudonymous, not anonymous
Feedback and usage events are stored against a pseudonymous key — a one-way cryptographic hash of your account identity, not your account identity itself. This means a leaked copy of that data can't be trivially linked back to your account by anyone who doesn't already have the key used to generate the hash. It is not anonymous: we can still connect an event back to your account internally, and treat it accordingly.
How we use it
Prompts, generation settings and feedback may be reviewed to understand how linel is used and improve motion quality. Anonymised or aggregated findings — patterns across many users, not individual prompts or accounts — may be published as research results or shared with teams whose models we're evaluating. We do not publish individual prompts publicly by default, and would not place a private prompt into a public example without asking first.
Cookies
linel uses one cookie: an HttpOnly session cookie that keeps you signed in. It isn't readable by page scripts and isn't used for advertising or cross-site tracking.
Security
Secrets (API keys, session signing keys) are kept server-side and never sent to the browser. Sessions are cookie-based over HTTPS. See Terms for what happens if we suspect abuse of the service.
Retention
flagged for founder review — a specific retention period for generated outputs, prompts and feedback has not yet been finalised. Until it is, treat data as retained for as long as the beta is running and useful for the research purposes described above.
Deletion requests
You can request deletion of your account and associated data by contacting the service operator directly. flagged for founder review — the exact process and timeline for honouring this aren't yet formalised; requests will be handled manually until they are.
The disabled commercial layer
linel previously ran a paid-plan experiment via Stripe. That integration is currently
disabled (STRIPE_ENABLED=false) but its code and any historical billing
records (for accounts that paid before this beta framing) are preserved, not deleted —
Stripe's own privacy practices govern payment data it holds directly; we never see or
store full card details ourselves.
Questions about this privacy notice can be sent to the service operator directly.