Cookie Policy

This policy explains how Pressay uses cookies and similar technologies when you visit our website. Please read it together with our Privacy Policy.

1. What Are Cookies?

Cookies are small pieces of text data stored in your browser by a website. They can keep features such as sign-in sessions working. Similar technologies include localStorage (browser storage) and in-memory identifiers, which this policy also covers.

2. How We Use Cookies

The Pressay website uses the necessary storage and optional analytics described below. We use no advertising or personalization cookies and do not set third-party cookies.

Necessary Storage and Preferences

First-party session cookies maintain your sign-in state. Browser storage remembers language, appearance, and analytics preferences. Analytics choices belong to this browser, last 365 days, and do not sync with your account. Turning optional analytics off does not sign you out or affect downloads.

Optional Website Analytics

We use PostHog (US) to record page visits, download clicks, login events, an anonymous identifier, and the source of the first visit eligible for collection. Sources include UTM campaign tags, a landing page without query parameters, and the referring site. After sign-in, anonymous visits are linked to your Pressay account ID. We exclude form contents, email addresses, verification codes, and login tickets, and do not enable session replay.

We do not track you: analytics data is not linked with other companies’ data for advertising or advertising measurement, and is not shared with data brokers.

Analytics identity and first-visit attribution are stored in first-party localStorage. The PostHog SDK uses memory only, sets no cookies, and does not read authentication cookies. PostHog encounters your network IP when receiving requests. Cloud records follow the project’s retention settings.

Without a valid choice, we use Delve’s region endpoint to identify the country and region of your request’s exit IP. Delve encounters that IP but receives no account, attribution, or current page. The EEA, UK, and Switzerland fall under gdpr and require permission before collection. California falls under ccpa; other identified regions fall under other. Analytics is on by default in ccpa and other. If detection fails, we use your browser’s time zone instead: time zones in the EEA, UK, Switzerland, or their territories require a choice before collection, and analytics is on by default elsewhere. VPN users are classified by the actual exit IP. Your valid acceptance or rejection takes priority over regional defaults.

3. Managing Cookies

Use the Cookie settings button in this section at any time to turn optional analytics on or off. You can return here through the Cookie Policy link in the footer of any page. Rejecting stops future collection and clears local analytics identity and attribution; it does not delete data already sent.

Your browser settings can also block or delete cookies and local storage. Blocking necessary cookies may affect sign-in. Clearing storage loses the original anonymous link and applies regional defaults again. Contact support@deepflywheel.com to request deletion of historical analytics records by an administrator. Deleting your account in the app does not automatically delete PostHog records.

4. Updates to This Policy

We may update this policy as website features and data practices change. Updates will be published on this page with a revised date at the top.