Legal
Cookie Policy
Last updated: April 21, 2026
1. Scope and Technologies Covered
This Cookie Policy explains how Postlyr uses cookies, local storage, and similar technologies on postlyr.io, the Postlyr web app, and related subdomains we operate. It should be read together with our Privacy Policy.
When we say “cookies” in this notice, we also mean comparable browser technologies such as local storage, session identifiers, and lightweight analytics scripts where they serve the same practical purpose of keeping the service working, remembering choices, or measuring product usage.
At a glance
- We use essential cookies and storage to keep Postlyr secure, signed in, localized, and able to remember your consent choices.
- We currently use one optional functional cookie in the web app to remember sidebar state.
- Optional analytics load only if you opt in, and Postlyr does not currently use advertising or retargeting cookies.
2. How Postlyr Uses Cookies
Postlyr uses cookies and similar technologies to do a small number of concrete things:
- keep the landing site and web app secure and functional;
- maintain authenticated sessions and detect when a signed-in user should be redirected into the app;
- remember consent choices, language selection, and other interface preferences;
- provide support chat through Crisp; and
- measure high-level usage through optional analytics if you consent.
Where practical, Postlyr shares consent and sign-in-detection cookies across .postlyr.io so the landing site and app behave consistently.
3. Consent Categories
We organise cookies and similar technologies into the following categories in our consent controls:
- Essential cookies — required for security, sign-in, consent storage, requested language selection, and support availability.
- Functional cookies — optional convenience cookies that remember interface preferences such as sidebar state.
- Analytics technologies — optional measurement tools that help us understand how Postlyr is used.
Postlyr does not currently use advertising, retargeting, or affiliate-tracking cookies.
4. Cookies and Similar Technologies We Use
Some provider-managed identifiers can change over time, especially for third-party services such as support chat. For that reason, we describe certain technologies by service and purpose rather than try to freeze every vendor-generated identifier on this page.
4.1 Essential Cookies
These are required for core functionality. They help Postlyr remember your consent state, keep sign-in and support flows working, and preserve settings you explicitly request, such as language selection.
| Name or provider | Where used | Purpose | Duration |
|---|---|---|---|
| postlyr_consent | Landing site and web app | Stores your cookie preferences so your choice is respected across the Postlyr experience. | 1 year |
| postlyr_auth | Shared across .postlyr.io | Lets the marketing site detect an authenticated session and redirect signed-in users into the app. | 30 days |
| NEXT_LOCALE | Landing site | Remembers the language you explicitly choose so the site can keep serving the requested locale. | 1 year |
| Crisp support session identifiers | Landing site and web app | Keeps support chat available and helps resume the correct support conversation when needed. | Session / provider-managed |
4.2 Functional Cookies
These are optional convenience cookies. Today, this category is used to remember interface state inside the Postlyr web app.
| Name or provider | Where used | Purpose | Duration |
|---|---|---|---|
| postlyr_sidebar | Web app | Remembers whether you collapsed or expanded the app sidebar. | 1 year |
4.3 Analytics Technologies
Postlyr uses privacy-conscious analytics tooling. Even where a provider does not rely on a classic browser cookie, we still group it under analytics so that it only loads if you opt in.
| Name or provider | Where used | Purpose | Duration |
|---|---|---|---|
| Vercel Analytics | Landing site and web app | Measures page usage and high-level traffic patterns so we can improve Postlyr. | Loaded only after analytics consent |
5. Browser Storage and App-Side State
In addition to cookies, Postlyr uses local storage and provider-managed browser storage where it is the most practical way to remember requested settings or maintain a secure authenticated session.
| Name or provider | Where used | Purpose | Duration |
|---|---|---|---|
| postlyr-theme | Landing site localStorage | Stores the theme you selected so the site can reopen in the same appearance. | Until changed or cleared |
| postlyr-auth-cooldown:verification:{email} | Web app localStorage | Applies a short client-side cooldown for verification email resend flows. | 60 seconds |
| postlyr-auth-cooldown:password-reset:{email} | Web app localStorage | Applies a short client-side cooldown for password reset resend flows. | 60 seconds |
| Supabase-managed auth session storage | Web app browser storage | Maintains authenticated sessions so signed-in users can stay logged in securely. | Varies by session and provider |
6. Third-Party Services
Postlyr relies on a limited number of service providers to deliver authentication, support, and analytics:
- Crisp powers customer support chat and may set provider-managed session identifiers so support conversations continue properly across visits.
- Supabase manages authentication for the web app and uses browser storage to keep users signed in.
- Vercel Analytics helps us measure high-level traffic and product usage only when analytics consent is enabled.
You can learn more about these providers here: Crisp Privacy, Supabase Privacy and Vercel Analytics Privacy.
7. Managing Your Choices
You can manage optional cookies at any time from the cookie banner, the floating cookie icon on the landing site, or the cookie controls available inside the web app. You can also manage cookies in your browser settings. Most browsers let you:
- View what cookies are stored and delete them individually.
- Block third-party cookies.
- Block cookies from specific sites.
- Block all cookies.
- Delete all cookies when you close your browser.
If you disable essential cookies or clear storage used for sign-in and support, parts of Postlyr may stop working correctly. Rejecting optional functional cookies will prevent Postlyr from remembering interface state such as the collapsed sidebar, and rejecting analytics will prevent analytics scripts from loading.
8. Changes to This Cookie Policy
We may update this policy as Postlyr evolves, for example if we add a new integration, change consent controls, or stop using a technology described here. When we do, we will update the date at the top of this page.
9. Contact Us
If you have questions about this Cookie Policy or about how Postlyr uses cookies and browser storage, contact us at: