Effective date: April 11, 2026
This policy explains what cookies OpenPost uses and why. We keep our use of cookies minimal and focused on what is needed to run the service.
Cookies are small text files stored on your device by your web browser. They help websites remember information between page loads and visits. Some cookies are essential for a service to work; others are optional and used for analytics or preferences.
| Cookie | Purpose | Type | Duration |
|---|---|---|---|
| sb-*-auth-token | Keeps you signed in. Set by Supabase Auth. | Essential | Session / 1 year |
| openpost-org | Remembers your active workspace so you return to the right one. | Functional | 1 year |
| twitter_pkce_verifier | Temporary cookie used during Twitter/X OAuth flow for PKCE security. | Essential | 10 minutes |
| twitter_oauth_state | Prevents cross-site request forgery during Twitter/X OAuth. | Essential | 10 minutes |
| sidebar-expanded | Remembers whether you prefer the sidebar collapsed or expanded. | Functional | Persistent (localStorage) |
Essential cookies are required for OpenPost to work — if you disable them, you will not be able to sign in. Functional cookies (workspace and sidebar preferences) can be cleared from your browser settings without affecting core functionality.
Most browsers allow you to manage cookies through their settings. You can typically find these under “Privacy” or “Security” in your browser preferences. Keep in mind that blocking all cookies will prevent you from using OpenPost.
If we add new cookies or change how we use existing ones, we will update this page. For material changes (such as introducing analytics tracking), we will notify users in advance.
If you have questions about our use of cookies, contact privacy@openpost.so.