PlaybookFlow Cookie Policy

Effective date: 2026-07-21
Last updated: 2026-07-26

This Cookie Policy explains how PlaybookFlow uses cookies and similar browser storage technologies on the website and application.

1. Scope

PlaybookFlow uses essential session mechanisms and browser storage required for core functionality. With your analytics consent, PlaybookFlow also uses first-party anonymous analytics and partner-attribution storage. Limited telemetry about signed-in use is sent directly to the server and does not add analytics cookies or browser identifiers. We do not use third-party advertising, remarketing, or behavioral profiling cookies on the PlaybookFlow domain.

2. What We Use

PlaybookFlow may use the following technologies.

A public campaign parameter such as `pbf_ref` may be carried between same-origin PlaybookFlow addresses and through the short-lived Steam sign-in return URL. This parameter identifies the campaign, not the visitor, and is not stored in local storage, session storage, or an anonymous attribution cookie. If sign-in is completed in the same journey, the validated campaign can be linked directly to the account. Persistent anonymous attribution between separate visits uses the optional cookie described below.

a. Essential authentication or session cookies

After Steam authentication, the backend may set essential session or authentication cookies to:

• keep you signed in;
• maintain a secure authenticated session;
• protect access to your account and workspace;
• support core application security.

These cookies are necessary for the operation of the Service.

b. Browser local storage for interface preferences

PlaybookFlow may use browser local storage to remember interface preferences, such as light mode or dark mode.

This allows the interface to preserve your preferred appearance between visits.

c. Legal acknowledgement storage

PlaybookFlow may use browser storage to remember the local state of legal acknowledgement prompts and avoid unnecessary repeated prompts before the server-side acknowledgement status is synchronized.

The authoritative legal acknowledgement status is stored server-side on your PlaybookFlow account.

d. Analytics consent preference

PlaybookFlow stores your analytics choice in local storage and a first-party preference cookie so the backend can respect it when a partner link is opened. This preference does not identify a partner or campaign.

e. Optional partner attribution cookie

After analytics consent, a first-party HttpOnly cookie may store a random, non-personal attribution token for up to 30 days. The token is used to preserve first-touch attribution between a valid partner-link visit and later registration, team activation, trial, or paid subscription. It does not contain an IP address, user ID, partner name, or other personal data.

f. Signed-in product telemetry does not use additional cookies

When you are signed in, PlaybookFlow may send a limited product event directly to the backend after a successful meaningful action. Authentication already identifies the signed-in account. This telemetry does not create an analytics cookie, anonymous session ID, advertising identifier, or additional browser-storage entry. The optional analytics choice controls anonymous journeys and optional attribution storage, not this limited server-side telemetry.

3. Why We Use These Technologies

We use cookies and similar browser storage technologies to:

• authenticate users after Steam sign-in;
• maintain secure sessions;
• remember interface preferences;
• support core app functionality and usability;
• support legal acknowledgement flows;
• protect the Service from unauthorized access or abuse.
• measure anonymous journeys and persistent partner attribution when optional analytics consent is granted;
• measure limited, aggregated signed-in product usage without adding analytics cookies.

4. Third-Party Checkout and Customer Portal

PlaybookFlow uses Polar for hosted checkout, subscription management, customer portal access, invoices, receipts, and related billing functionality.

When you are redirected to Polar-hosted checkout or customer portal pages, Polar may use its own cookies, session storage, local storage, or similar technologies on Polar-controlled domains to:

• complete checkout;
• manage payment sessions;
• support fraud prevention and security;
• provide invoices and receipts;
• allow subscription cancellation or payment method updates;
• operate the customer portal.

Those technologies are controlled by Polar and are subject to Polar's own terms, privacy, and cookie documentation.

5. What We Do Not Use

At this time, PlaybookFlow does not use cookies or similar technologies on the PlaybookFlow domain for:

• advertising;
• remarketing;
• behavioral profiling;
• third-party marketing tracking;
• cross-site partner tracking;
• tracking of every page view or navigation.

6. Managing Cookies and Browser Storage

You can control cookies and browser storage through your browser settings.

Please note that disabling essential cookies or clearing browser storage may affect the functionality of the Service, including:

• your ability to remain signed in;
• saved interface preferences;
• legal acknowledgement prompt behavior;
• secure access to private workspaces.

7. Third-Party Services

PlaybookFlow uses Steam for authentication. Steam authentication may involve redirects and technical session handling necessary to complete sign-in securely.

PlaybookFlow may also rely on hosting, infrastructure, payment, billing, email, storage, and security providers whose services are necessary for operating the Service.

8. Changes to This Cookie Policy

We may update this Cookie Policy from time to time to reflect legal, technical, billing, operational, or product changes.

The updated version will be published with a new effective date.

9. Contact

If you have questions about our use of cookies or browser storage technologies, contact:

contact@playbookflow.com