SC 09 · TK 02

Privacy

Short version: we log what we need to see how the site is used and to stop abuse. We do not sell data, we do not use advertising trackers, and we do not collect card details.

What we log

• Usage events. Page views and actions such as choosing a resolution, using a prompt card, opening the pricing dialog or submitting your email.
• A random visitor id stored in your browser's local storage, so we can count unique visitors. It is not linked to your name.
• Path. Which page the event happened on.
• Referrer and campaign tags. The site you came from and any utm_ parameters in the link.
• Country as reported by our hosting network, and device kind (desktop, mobile or bot) from the browser's user-agent. We do not store the full user-agent.
• A hashed IP address. The IP is combined with a secret and hashed, and only the hash is kept. We use it to apply daily limits and to stop abuse. We cannot reverse it into your IP.
• Emails you leave for early access, together with the pack you picked, the time, and your visitor id.
• A test-group letter. Visitors are randomly placed in one of three groups (A, B or C) so we can compare how we explain the paywall. The letter is stored in your browser and added to events.

Cookies and local storage

We set two first-party cookies, sl_id (a random anonymous id) and sl_v (your test-group letter), plus matching entries in local storage. Local storage also keeps your saved prompt, your list of renders and your visitor id. None of these identify you personally, and none are shared with advertisers. You can clear them in your browser settings; doing so resets your free-render allowance on that device but not on the hashed IP.

When rendering is on

If rendering is open, the prompt and settings you submit are stored with the job (for example so you can see it in My renders) and are sent to the third-party video API that makes the clip. Do not put personal data in prompts. The anonymous id is hashed before it is stored with a job. If you choose "email me when done", the email is stored on the job.

Analytics

We use Cloudflare Web Analytics for aggregate traffic statistics. It does not use cookies and does not track you across sites.

Retention and your choices

Event logs are kept while they remain useful for understanding usage. To have your email removed, write to us from that address using the contact on the terms page once published, and we will delete it. You can use the site without leaving an email.

This notice may change as rendering and payments open. We will update the date and list new data we collect.