Cookies and Browser Storage
Service operator: spinevfxbuddy
Version date: September 20, 2026
This Notice supplements the Privacy Policy and describes the main purposes and controls for cookies and browser storage used for authentication, editor functions and preferences. Specific names, periods and attributes depend on deployment and the information received by the browser.
1. Necessary cookies and session verification
Session authentication, OAuth redirect validation and two-factor authentication use necessary cookies. Some are cleared after the operation, while sessions expire on sign-out, expiry or revocation. Actual cookie attributes determine their duration. Age and consent enrollment uses a short-lived, HTTP-only policy-enrollment cookie holding a random reference for up to 30 minutes; age-group and consent records remain on the server. Blocking necessary cookies may affect the corresponding service.
2. Local storage and project recovery
The website stores theme and interface preferences; the editor may locally store editing state, settings and projects for recovery. Users should save important content before clearing browser data. Local storage does not imply exclusively local computation: some exports and previews send animation, layers, keyframes and resource metadata to the server, as described in the Privacy Policy. Clearing local data does not automatically delete cloud copies.
3. Analytics and independent third-party storage
When Vercel Analytics is enabled, aggregate public-page visits are processed under the Privacy Policy. Cookies and storage on independent Google sign-in and Creem checkout pages follow those providers’ policies. The service does not use advertising-profile cookies. New purposes legally requiring consent will be described with the relevant choices.
4. User controls and functional effects
Users may inspect, restrict and delete cookies or local storage through browser settings. Blocking necessary cookies may affect authentication, verification and payment redirects. Signing out or revoking sessions does not automatically remove local projects; local and cloud deletion must be handled separately.
Notices, inquiries and rights requests
Account, billing, personal-information and infringement matters should be submitted through the contact page. Users should provide the relevant account email, order reference or facts. The Operator may verify identity and relevant records to the extent necessary to handle the request. Passwords, verification codes and full payment credentials must not be submitted.
Contact the Operator