This Cookie Policy explains how PrimusPost (“we,” “us,” or “our”) uses cookies and similar browser storage on our website and application.
1. What cookies are
Cookies are small text files placed on your device when you visit a website. They are widely used to make sites work reliably and to keep authenticated sessions secure.
2. How we use them
We keep this deliberately small. In practice that means:
- Cookies required for authentication, security, and session management are always set, because the service cannot sign you in without them.
- Product analytics is optional and off by default. Nothing is captured until you choose “Accept all” in our cookie notice, and choosing “Reject optional” keeps it off.
- We do not use advertising cookies, retargeting pixels, or cross-site behavioural tracking, and we do not sell or broker browsing data.
3. Strictly necessary cookies
These are essential to navigate the site and use secure features such as your private content studio and account settings. Under the EU ePrivacy Directive (Directive 2002/58/EC) and the GDPR, strictly necessary cookies do not require prior opt-in consent, because the service cannot function without them.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
__session | Clerk (authentication) | Holds the encrypted session token for a signed-in user. | Session / 7 days |
__client_uat | Clerk (authentication) | Records a client updated-at timestamp so sign-out propagates across open tabs. | 1 year |
__clerk_db_jwt | Clerk (authentication) | Carries session tokens through the development and production auth handshakes. | Session |
4. Optional analytics cookies
We use PostHog to understand which parts of the product are actually used — for example how many people finish a generation, or which screens produce errors. This is the only optional category we operate, and it is disabled until you accept it. If you reject it or have not answered the notice, PostHog is loaded in an opted-out state: it sends no events, sets no cookie, and stores no identifier.
| Cookie | Provider | Purpose | Duration |
|---|---|---|---|
ph_*_posthog | PostHog (product analytics) | Stores a pseudonymous device identifier so repeat visits can be counted once rather than many times. Set only after you accept optional analytics. | 1 year |
We deliberately restrict what PostHog may collect. Session replay is disabled, so no recording of your screen is ever made, and autocapture is disabled, so the text of what you click — which on this product would be your unpublished drafts — is never attached to an event. Analytics requests are proxied through our own domain rather than sent to a third-party host directly.
We also use Vercel Web Analytics for aggregate traffic and uptime measurement. It is cookieless: it sets no persistent identifier and does not track you across other websites.
5. Local storage & preferences
In addition to cookies, we use your browser's localStorage for functional preferences that stay on your device:
primuspost_cookie_consent— records your answer to the cookie notice so we can honour it and stop asking. Storing your choice is itself exempt from consent.theme— your dark or light interface preference.
6. Changing your choice
To change your analytics choice, clear this site's browsing data in your browser settings. The notice will appear again on your next visit and your new answer will be applied immediately.
Most browsers also let you block or delete cookies globally. Note that blocking strictly necessary cookies will prevent you from signing in to PrimusPost. To learn more about managing cookies generally, see allaboutcookies.org.
7. Updates & contact
We may update this Cookie Policy to reflect changes in the tools we use or in legal requirements. The date at the top of this page always reflects the most recent change. Questions go to privacy@primuspost.com.