Skip to content

Omni Posto

Cookies and local storage

This page explains the cookies and local browser storage that are useful for operating the Omni Posto service.

Last updatedMay 19, 2026

1. Scope

Omni Posto uses cookies and local storage to keep sessions active, secure sign-in flows, remember preferences and make previously loaded media faster to display.

This V1 does not add a blocking banner for the functional media cache, because it supports a service explicitly requested by the signed-in user.

2. Strictly necessary cookies

Supabase authentication cookies and temporary OAuth cookies are used to sign users in, protect sessions and complete social platform connection flows.

Without these cookies, the service cannot identify the user or perform requested workspace actions.

3. Local browser storage

Omni Posto may use local storage for the selected theme, some form state and automatic Publish draft recovery.

This data stays in the browser and can be removed by the user through browser settings or cleanup actions exposed in the application.

4. IndexedDB media cache

Media thumbnails and previews may be copied into IndexedDB so the media library and Publish selectors reopen faster.

The media cache is size-limited, uses LRU cleanup and can be cleared manually from the media library. It is also cleared on sign-out.

  • Technical name: omniposto-media-cache.
  • Default limit: 150 MB or 400 entries.
  • Large video files continue to stream through HTTP Range requests and are not stored as offline Blobs in this cache.