PIXENOA

PIXENOA

Privacy Policy

How PIXENOA handles optional analytics and the limited information needed to operate the public wallpaper catalogue.

Last updated: 29 September 2026

Public access and administration

The public PIXENOA catalogue does not require a visitor account. Supabase is used to authenticate authorized administrators on private Admin routes; those authentication sessions are separate from public Analytics consent.

Optional Google Analytics 4

PIXENOA uses Google Analytics 4 only after you explicitly accept Analytics. Its purpose is to understand traffic, site usage and engagement so the experience can be improved.

Analytics is optional. Rejecting it does not prevent you from browsing wallpapers or downloading available originals. You can change your choice at any time through Cookie Settings in the footer.

Information Analytics may process

After consent, Google Analytics may process technical, device and usage information associated with visits and interactions. Google handles that information under its applicable Analytics terms and privacy framework.

  • Page location, page path and page title
  • Public wallpaper number and public category for selected product events
  • General device, browser and engagement information collected by Google Analytics

Information excluded from custom Analytics events

PIXENOA does not intentionally send the following as custom Analytics parameters:

  • Supabase user or Admin identifiers
  • Internal wallpaper or category UUIDs
  • Private R2 keys, private storage URLs or original filenames
  • Passwords, form contents or arbitrary search text
  • Names, email addresses or other deliberately supplied personal information

Consent preference

Your Analytics choice is saved locally in your browser under a versioned PIXENOA preference for approximately six months. When it expires, PIXENOA asks again. The preference is not stored in Supabase and is not tied to an account.

If you change from Accept to Reject, PIXENOA stops sending future custom Analytics events, disables the active GA runtime for the page, clears accessible GA cookies where technically possible and reloads when necessary.