What gets counted
Each reel keeps a view count, and a per-day total behind it. Both are plain numbers attached to the reel, not to you: watching adds one to a column, and nothing about the request is written down alongside it. Your IP address is used for a few seconds to stop one browser inflating a count, and nothing about watching stores it.
If you make an account
An account stores the name and email address you give it, and a hashed password — hashed, so nobody here can read it, including me. Signing in also writes a line to your account’s own history: the date, whether it worked, your IP address and the browser string your device sends. You can read that history yourself on your account page, which is the reason it exists — it is how you notice a sign-in that was not you. It is kept for 90 days and then deleted automatically.
The same line is written for a failed attempt, including one somebody else makes against your address. That is deliberate: an attempt to get into your account is exactly the thing the history is for. It also means a small number of IP addresses belonging to people who never had an account here are stored for those 90 days.
Deleting an account removes it, its sessions, its password and every reel drawn under it; the sign-in history is unlinked from it and ages out on the same 90-day clock. Ask and it goes sooner. A live Plus subscription is cancelled at Paddle in the same breath, and the payment records described below are kept with the account unlinked — amounts and transaction ids, nothing that identifies a card.
Your reels
A reel you draw is stored under your account — the pieces, the beats, the words — and is private to you: nothing you make is served from an address here, and it stays editable for as long as the account exists. A brand kit, a library of pieces and the earlier versions of a reel, on a plan that keeps them, are stored the same way under the same account. There is no delete for a single reel, by design; deleting the account removes all of them.
Paying for Plus
Plus is bought through Paddle, the merchant of record: the checkout is Paddle’s, the card goes to Paddle, and no card number, billing address or payment credential is ever stored — or even seen — by this site. What this site does store about a subscription is its status and dates (when the term started and ends, when access runs out, when the next renewal falls) and, for each completed payment, the amount and Paddle’s transaction id, so your account page can show your invoices and so the books balance. Invoices themselves are Paddle documents, fetched fresh when you ask for one.
Which plan you are on is a row on your account, and the only thing counted against it is how many reels you make in a calendar month. When a subscription ends, the row flips back to the free plan and the payment records above are kept — money history outlives the subscription, the way your sign-in history outlives a session.
Google Analytics
This site loads Google Analytics 4, which sets cookies in your browser and sends Google the page you are on, roughly where in the world you are, and six events: which reel you opened, whether it ran to the end, a share, a copied link, a filter chip you clicked, and — worth saying plainly — the text you type into the search box. It is used to see which comparisons people look for and which ones they finish. It is not linked to your account, and nothing here is ever sold or handed to an advertiser.
If you would rather it did not run, any content blocker stops it, as does Google’s own opt-out extension. Nothing on this site stops working without it. What Google does with what it receives is covered by their privacy policy.
What is not here
No advertising, no ad network, no cross-site tracking pixels, and no third-party JavaScript beyond the analytics named above and one exception with a job: opening the Plus checkout on your account page loads Paddle’s checkout script, which exists so that the card form is Paddle’s and never this site’s. It loads there and nowhere else. The fonts are served from this domain rather than fetched from Google, so reading a page makes no request to anyone else. Reels themselves run in a sandbox on a separate, cookieless origin and cannot reach the network at all.
Questions
Ask, or tell me something here is wrong, at [email protected].