Privacy and cookies
Updated 22 October 2026
Seller and support
Seller name, country and support email have not yet been provided. Do not send money outside the checkout or share payment credentials.
Information processed
Checkout uses your purchase email, selected product, order and invoice identifiers, payment status, purchase time, selected prompts, opening slots, and a hashed browser receipt. Optional accounts also store a verified email, display name, account language, hashed session identifiers and expiry dates. Login codes are hashed and expire after ten minutes; failed attempts are limited. Hashed request identifiers and counters limit abuse. Payment events prevent duplicate processing and handle refunds or disputes. We do not receive full card numbers or store account passwords.
Why we use it
We use order information to initiate checkout, verify paid access, prevent unauthorised access, reconcile payment events and investigate purchase problems. Infrastructure and payment providers may process technical connection information according to their own policies.
Cookies and local preferences
The secure HTTP-only receipt cookie lasts up to one year. An optional secure HTTP-only account session lasts up to 30 days; a login challenge cookie lasts ten minutes. These cookies are used for requested purchases and sign-in, not advertising. The saved-animation list uses localStorage on your device. Clearing browser storage can remove guest access, but does not cancel subscriptions. When available, verified email sign-in can restore account purchases. Signing out on all devices invalidates account sessions and guest receipt identifiers associated with that account. Browsing does not create a newsletter subscription.
Optional campaign attribution
If you allow campaign attribution, we store sanitised UTM source, medium, campaign, content and term labels, first and latest landing paths, timestamps and a hashed random browser identifier for up to 30 days. A secure HTTP-only campaign cookie links later checkout starts to those labels. No advertising pixel is installed. Attribution preferences are stored locally on your device; you can change them using Attribution preferences. Declining clears the campaign cookie and visitor record. Campaign labels linked to an existing order remain with the order record for purchase analysis; this is separate from an anonymous campaign visit. Never include personal or payment information in UTM labels.
Site traffic statistics
Public pages send a page-view event with the clean page path, time, referring website hostname and a broad device category. Traffic records are retained for up to 90 days and removed as new views arrive. We do not store raw IP addresses, full referring URLs, page query strings or email addresses in these records. Without attribution consent there is no visitor cookie or cross-page browser identifier; anonymous counts are not unique people. Do Not Track and Global Privacy Control signals are respected. Requests blocked by your browser may not be counted.
Optional visit attribution
With your permission, visit records also include sanitised UTM labels and a hashed random browser identifier. Its secure HTTP-only cookie lasts up to 30 days; attributed visit records remain for up to 90 days. Declining Attribution preferences clears that cookie and removes its identifier and UTM labels from stored visit records associated with that browser. Separate purchase attribution follows the order-retention rules above. Access to traffic reports is restricted to authorised administrators who confirm their email.
Providers
Lava.top processes payments. Cloudflare supplies hosting, order storage and video storage. Resend delivers requested login codes when email sign-in is enabled; it receives the destination email and message. If you choose “Open Claude”, your browser opens Anthropic’s service; you choose whether to paste the prompt there. Normal playback comes from our storage, not from the source gallery.
Retention and requests
Order information is retained while needed to provide purchased access, resolve payment issues and satisfy applicable record-keeping duties. Operational retention periods and the data-controller identity will be finalised with the seller details before live sales. Contact the published support address for an access, correction or deletion request; legal retention duties may limit deletion.
Payment-provider information: Lava.top terms ↗