Cookie Policy
One cookie remembers the tale you started. Stripe and the account login set their own. We do not set advertising cookies.
Effective September 23, 2026 · Version 2
The tale you are starting
When you start a tale, we set one cookie named ht_sid. It holds the id of that start, so you can come back to the same cover.
It lasts 14 days. It is sent only to this site. It cannot be read by scripts on the page. It is not an advertising cookie, and we do not use it to follow you around the web.
If you never start a tale, we do not set it. You can also clear it in your browser. Clearing it starts a new tale the next time. It does not delete a tale you have already paid for.
Paying
When you pay, Stripe may set its own cookies so the payment can finish. Those cookies are Stripe's. Blocking them can stop the payment from completing. We do not use them for advertising. The card number stays with Stripe. We keep the card brand and the last four digits.
The account
When you sign in to the shelf, our login provider (Supabase) sets a session cookie so you stay signed in. It is used to know that the account is yours. Signing out ends that session.
What we do not set
We do not set advertising cookies. We do not set analytics cookies. We do not sell cookie data.
If we add a cookie that is not one of the three above, we will update this page first, and we will not use a new cookie for advertising without saying so here before it is set.
How to refuse
You can refuse ht_sid by not starting a tale, or by blocking cookies for this site in your browser. The site still loads. Starting a tale, paying, and signing in need the cookies described above. The privacy policy covers the photo and the other details, which are not stored in a cookie.
