Cookie Policy

1. Scope

This policy applies to Hitbook websites and browser-based applications. Cookies are small records stored by a browser. We also identify local storage and similar browser technologies where they serve the same purpose.

2. Strictly necessary storage

These records support authentication, security, language, session continuity and consent. They do not require optional analytics consent.

• access-token: authenticated session, HttpOnly and SameSite=Lax where issued as a cookie.
• pb_client_token and key: secure client portal and shared-gallery access.
• google-auth: short-lived OAuth state during a Google sign-in flow.
• cookie_consent, cookie_consent_version and hitbook_session_id: the decision, policy version and pseudonymous consent record identifier stored locally in the browser.

3. Optional analytics and marketing

Google Analytics, Google Tag Manager, Google Ads and Meta Pixel are not loaded until the visitor expressly accepts optional cookies. Rejecting keeps these scripts unloaded. If accepted, they may process page views, campaign attribution, device/browser data and identifiers according to their own policies.

4. Consent and changing your choice

The banner offers Accept and Decline with equal access to this policy. The decision and version are saved locally and recorded on our server with time, language, page and technical audit data. A new material version asks again. You can withdraw consent by clearing the Hitbook consent entries or browser site data and revisiting the site.

5. Hitbook Desktop and Photographer Plus

The Photographer Plus desktop application creates a temporary local preview cache under the application data directory. That local preview cache is not a browser cookie, is not a browser tracking technology, is not shared with advertising providers, and is removed under cache-expiry and logout rules. Media processing and cloud retention are described in the Privacy Policy and Photographer Plus Storage Policy.

6. Providers, retention and controls

Stripe may use necessary anti-fraud storage during web checkout. Sentry may receive error and performance events without setting a persistent marketing cookie. Google and Meta are optional as described above. Browser settings can delete or block storage, although blocking necessary records may prevent login or secure portal access.

7. Typical retention periods

Exact durations may vary by browser settings, provider configuration and login state. Typical periods are:

• access-token / authenticated session: session or short-lived renewal period appropriate to security settings.
• pb_client_token / portal key: until the portal session expires, the link is revoked, or the browser data is cleared.
• google-auth OAuth state: minutes during the sign-in flow only.
• cookie_consent and cookie_consent_version: until withdrawn, cleared, or a new material policy version is published.
• hitbook_session_id: local pseudonymous identifier for consent audit continuity until cleared.
• Optional Google Analytics / Ads / Tag Manager identifiers: according to Google settings after Accept, commonly up to 24 months unless shortened.
• Optional Meta Pixel identifiers: according to Meta settings after Accept, commonly up to 90 days for browser cookies unless shortened.
• Stripe checkout anti-fraud storage: as needed for the payment attempt and Stripe security rules.
• Sentry diagnostics: event retention under Sentry configuration without a persistent marketing cookie.

8. Managing preferences, Do Not Track and Global Privacy Control

To change an earlier Accept decision, clear the Hitbook cookie_consent and cookie_consent_version entries or the site data for hitbook.io in your browser, then reload the page and choose Decline or Accept again. You may also block optional cookies in browser settings. We currently treat a clear Decline and withdrawal as the controlling choice for optional analytics and advertising scripts on Hitbook marketing pages. Browser Do Not Track signals are not uniformly standardized; where Global Privacy Control or a similar legally recognized opt-out signal is detected and required to be honored, we will not load optional advertising cookies for that visit beyond what is needed to record the opt-out state.