Cookies & storage
Cookies and browser storage
Leyra does not use advertising pixels or third-party marketing trackers. Some cookies/storage are essential for sign-in and security; optional first-party analytics run only after you allow them.
If you enable Leyra browser push reminders, your browser stores a push subscription and Leyra stores the matching device reminder details for that opted-in device. This is separate from the offline app storage and can be disabled from your profile delivery settings or browser/device settings. Reminder scheduling stores user-selected morning/evening channels, timezone, quiet hours and generic delivery failure reasons, not private reading text.
Essential cookies and storage
Leyra uses essential cookies and related browser storage for account sign-in, anti-forgery protection, security, remembering short in-page transitions and keeping authenticated journeys working.
These are necessary for the service and are not used for advertising.
Optional first-party launch analytics
If you choose Allow analytics, Leyra stores a browser consent choice and uses a temporary first-party session identifier to understand whether public pages, free readings, pricing routes, feedback and checkout-intent journeys are working during launch.
These analytics do not include private reading text, tarot results, journal answers, profile-memory answers, confirmation tokens or raw query strings. They are used to fix usability problems and understand launch conversion, not to sell data or serve ads.
For share cards, optional first-party analytics may count public card views, native-share attempts, channel clicks, copy/download actions and click-throughs to the free reading, registration or pricing pages. Leyra stores public paths and event labels only, not the content of a private reading or profile memory.
Home Screen install and offline app storage
Leyra may use a small browser storage flag if you dismiss the install suggestion, so the same prompt does not keep reappearing. The installable web app layer links a manifest and Leyra icons for iPhone/Android Home Screen support.
Leyra may store public app files such as icons, styling and a safe offline page so the site opens smoothly. Private readings, account pages, billing pages, saved history, memory, tarot results and admin content are not stored for offline use.
How to change your choice
You can clear Leyra browser storage in your browser settings to show the analytics choice again. If you choose Essential only, client-side launch analytics remain off for that browser unless you clear storage and opt in later.
What Leyra does not use
- No advertising pixels.
- No third-party marketing retargeting tags.
- No sale of reading/profile data.
- No analytics on email-confirmation token pages.
Profile memory, browser storage and caching
Leyra profile-memory settings are stored server-side with your account, not in advertising pixels or third-party marketing cookies. The service worker remains conservative: private profile, memory, reading, tarot, account, billing and API responses should not be cached for offline use.
Profile and memory-consent pages may use ordinary first-party session and security cookies so signed-in controls work correctly. Leyra does not intentionally store private reading text, profile answers, tarot history or memory items in browser analytics diagnostics.
Daily check-ins and browser storage
Daily check-ins are stored server-side with the signed-in account, not in advertising cookies. The browser may use normal session and anti-forgery cookies so the signed-in form works, but the service worker should not cache private check-in pages, profile memory, personalised readings or private API responses.
Reading feedback and context audits
Reading feedback and reading-support records are stored server-side with the signed-in account. They are not advertising cookies and they are not intended to include raw long-history prompts. Optional first-party analytics may count button clicks, but private reading text, profile memory and reading-support details should not be stored in browser analytics diagnostics.
Private memory storage
Active themes are account data
Active themes and memory candidates are stored server-side with the account. The service worker should not cache profile memory, private readings, tarot history, account pages or API responses.
Private memory controls
Memory pages stay private
The What Leyra Remembers page is account-side private data. It is not a public SEO page and should not be cached by the service worker, analytics scripts or notification diagnostics.
Ask Leyra private storage
Ask Leyra stays private
Ask Leyra pages and admin audit pages are signed-in private routes. The service worker should not cache Ask Leyra questions, answers, profile memory, context packets or safety-review text.
WhatsApp and browser cache
WhatsApp messages are server-side private records
WhatsApp webhook and Admin WhatsApp routes are private account areas. The service worker should not cache WhatsApp messages, response previews, profile memory, safety-review text or webhook payloads. These records are handled server-side for audit and launch-gate testing.
WhatsApp safety queue storage
WhatsApp webhook rows, command audits, admin notes and safety-preview decisions are server-side private records. The service worker must not cache WhatsApp webhook/admin responses, Ask Leyra replies, readings, profile memory, account data, billing data or private API responses.
Waitlist forms
WhatsApp waitlist form storage
The WhatsApp waitlist form uses the same first-party feedback form handling as Leyra support notes. It does not add advertising pixels or third-party marketing trackers.
