Back to home

Cookie Policy

Last updated: [DATE]

This page is a template prepared for OmniPost. It has not yet been reviewed by a lawyer, and the bracketed placeholders below (legal entity name, address, jurisdiction, contact emails, dates) are not filled in. It must be reviewed by qualified legal counsel and completed with OmniPost's actual details before being relied on in production.

OmniPost uses a small, deliberately minimal set of cookies. This page explains what they are, why we use them, and how to control them.

Cookies we use

  • Session cookie (authentication) — a strictly necessary, first-party cookie that keeps you signed in to the OmniPost dashboard. It stores a signed session identifier, not your password or API keys. Without it, you would need to sign in again on every page.
  • Theme preference cookie — a first-party cookie (set via next-themes) that remembers whether you prefer light or dark mode so the dashboard renders consistently on your next visit.

No third-party ad-tracking cookies

OmniPost is a developer tool, not an ad-supported product. We do not use third-party advertising cookies, cross-site tracking pixels, or ad-retargeting scripts on the dashboard or marketing site. We do not sell or share cookie data with advertising networks.

What about analytics?

If OmniPost adopts a privacy-respecting analytics tool in the future, this page will be updated to name it and describe what it collects [Analytics Provider Placeholder — not currently in use].

How to control cookies

The session cookie is required for the dashboard to function — if you block or delete it, you will be signed out. You can clear cookies at any time through your browser's settings. Blocking the theme preference cookie has no functional impact beyond resetting to the default theme on your next visit.

For questions about this Cookie Policy, see our Privacy Policy or contact [DPO/Privacy Contact Email].