Cookie Policy

1. Introduction

This Cookie Policy explains how Persoon.ai Inc. ("ShipReady Metrics", "we", or "us") uses cookies and similar technologies on the ShipReady Metrics websites and application ("Service"). It supplements our Privacy Policy, which describes our broader data practices.

A cookie is a small text file stored in your browser. We keep our use deliberately small: a handful of essential cookies that make sign-in and the product work, one cookie that remembers your analytics choice, one short-lived marker used only when a staff link asks for it, and — on our public marketing pages only — analytics tools that run under the conditions described below.

2. Essential Cookies

These cookies are required for the Service to function — they keep you signed in and remember basic workspace selections. They do not track you across other websites and are not used for advertising.

Cookie	Purpose	Duration
Supabase authentication cookies (names beginning with "sb-")	Set by our authentication layer (Supabase) to keep you securely signed in; they hold your session and are removed on sign-out.	Session-managed by the authentication layer
srm_active_org	Remembers which organization you are working in when your account belongs to more than one (the organization switcher). HttpOnly, same-site.	Up to 1 year
srm_active_unit	Remembers your selected business unit within an organization. HttpOnly, same-site.	Up to 1 year
sr_consent	Stores your analytics consent choice (granted or denied) so we do not ask again and can honor a decline. This is the consent cookie itself.	180 days
sr_traffic	Set only when you open a link that includes ?traffic_type=internal. A first-party marker that labels the browser as internal traffic so our own analytics can exclude it. Not set for ordinary visitors, not an advertising cookie, and not shared.	8 hours

During sign-in and connector setup, short-lived technical cookies may also be set and then discarded — for example, a code-verifier cookie used by the secure OAuth sign-in flow, and an anti-forgery state cookie used while installing the GitHub App integration. These exist only to protect the flow they belong to.

3. Analytics on Public Marketing Pages Only

Analytics tools may run on our PUBLIC MARKETING PAGES ONLY. They are never loaded on authenticated in-app surfaces — your dashboards, reports, and other signed-in product pages never receive these tags, so confidential tenant data is never session-recorded or sent to an analytics provider. Pages whose address contains a secret link token never load them either.

Provider	What it does	Cookies / data
Google Analytics 4 and the Google Ads tag	Aggregate website analytics for the marketing site (page views, referrers, approximate location, device and browser metadata). The same gtag loader also carries the Google Ads tag.	On non-homepage marketing pages the gtag library may load before you choose, with Consent Mode v2 storage denied (ad_storage, analytics_storage, ad_user_data, and ad_personalization). That sends cookieless pings and does not set analytics or advertising cookies. After Accept, Google may set analytics cookies (names beginning with "_ga") and advertising cookies. The homepage does not load the gtag library until Accept.
Microsoft Clarity	Session analytics for the marketing site: heatmaps and interaction recordings (clicks, scrolls) to improve the public pages.	Still consent-gated. The Clarity tag loads only after Accept, and only then may set Microsoft analytics cookies. Marketing-site visitor interaction data only.
Vercel Web Analytics	Cookieless page-view counts for non-homepage public marketing pages in production.	No cookie. It does not wait for the consent banner. It does not load on the homepage, on preview deployments, on secret-link pages, or for internal traffic (a signed-in @persooninc.com session, or a browser that opened ?traffic_type=internal).

Production only: Google, Clarity, and Vercel Web Analytics are disabled in preview and development builds.
Non-homepage marketing pages, when consent is required (our production configuration): the Google tag loads with storage denied until you choose Accept, so no analytics or advertising cookie is set beforehand. A decline leaves those cookieless pings in place and does not load Clarity. Accept updates consent to granted.
The homepage is an exception until the owner lifts the homepage freeze: Google and Clarity tags there still load only after Accept, and Vercel Web Analytics does not load on the homepage.
These providers are disclosed in our Subprocessors document and Privacy Policy.

4. Your Consent Choices

When analytics consent is required, a banner on the marketing pages offers a clear Accept or Decline choice. Declining stores your choice. On non-homepage marketing pages, Google tags stay in cookieless mode and Clarity does not load. On the homepage, declining means those tags do not load. Your access to the site and the Service is never affected either way.

Your choice is stored in the sr_consent cookie for 180 days; after it expires you will be asked again.
To change your mind before then, delete the sr_consent cookie in your browser settings and revisit the site — the banner will reappear. An in-page control for revisiting this choice without editing browser settings is a planned enhancement; until it ships, deleting the sr_consent cookie is the supported way to change your consent.
You can also block or delete cookies entirely through your browser. Blocking the essential cookies in Section 2 will prevent sign-in from working.

5. What We Do Not Use

For clarity, the following are NOT used anywhere on the Service:

No sale or sharing of cookie data for advertising purposes.
No analytics or session recording on authenticated in-app pages (dashboards, reports, and other signed-in product surfaces).
No analytics or advertising cookies before you accept. The Google tag's pre-accept pings on non-homepage pages are cookieless.

6. Local Storage

Separately from cookies, your browser's local storage is used to remember your display theme preference (light or dark mode). This value stays in your browser as part of how the page renders and is not used to identify or track you.

7. Changes to This Policy

If we add, remove, or change cookies or analytics providers, we will update this Policy and the Subprocessors document. Material changes to what is collected on the marketing site will be reflected in the consent banner behavior where consent is required.

8. Contact

Questions about cookies or this Policy: info@persooninc.com. Postal contact: Persoon.ai Inc., 525 Randall Ave Ste 100 PMB 228, Cheyenne, WY 82001. This document is an AI-generated draft pending legal and owner review and is not legally binding.