Privacy

Updated September 20, 2026

This page describes the website's Growth audience measurement and browser storage. Measurement events are sent when audience measurement is enabled. This helps us understand which pages and referrals bring readers to useful product evidence and which interactions lead to retailer visits.

What audience measurement collects

• Event type and time, page or surface, product and comparison identifiers, creator or source identifiers where relevant, and interaction properties.
• Random visitor and session identifiers to connect related visits and events. They are browser identifiers, not your name, but they can distinguish visits and should not be treated as anonymous data.
• The current page URL and referring URL are sent to the collector. Query strings and fragments are removed from the stored URL fields. Campaign parameters (UTMs), ad click identifiers such as gclid, gbraid, and wbraid, and internal campaign, content, publication, and experiment identifiers may be retained separately for attribution.
• A bot or suspected-automation classification, used to keep automated traffic separate from reader activity.

Cookies and browser storage

The collector sets yeah_vid (visitor identity) and yeah_sid (session identity) as first-party cookies with random UUID values. Both use Secure, HttpOnly, and SameSite=Lax, apply to the whole site (Path=/), and have a Max-Age of 34,560,000 seconds (400 days). Their expiry is refreshed after a successful measurement submission. The session cookie is also persistent; it is not a cookie that expires when you close a tab.

The browser also stores a per-tab yeah_growth_session marker in session storage. It contains the value 1 and can be set even when measurement events are disabled. This marker does not itself contain a visitor identifier. Your browser controls the lifetime of this per-tab storage.

The home page sets yeah_tzto your browser’s time zone name (for example America/Los_Angeles) so the day headings and dates on stories match your calendar. It is readable by the page (not HttpOnly), uses SameSite=Lax and Path=/, lasts one year (Max-Age 31,536,000 seconds), and contains no identifier. Before it is set, the time zone may be estimated from your connection by our hosting provider; it is not stored.

Ask Yeah

When you ask Ask Yeah a question, the question, the details sent with it (such as the shoe you are asking about and your answers to its follow-up questions), and the answer are stored on our server so the answer can be shown to you. Each question is set to expire after a retention window (24 hours by default; the longest setting is 7 days). When an expired question is cleared, its text, details, and answer are removed; a record that a question was asked remains.

Asking sets a yeah_ask_owner cookie with a random value that links your questions to this browser. It uses Secure, HttpOnly, and SameSite=Strict, applies only to Ask Yeah requests (Path=/api/ask), and has a Max-Age of 604,800 seconds (7 days).

To limit how many questions one visitor can ask, our server turns your IP address (for IPv6, its first 64 bits) into a keyed hash and counts questions per hour against it. The address itself is not sent to the assistant service; the hash and its counts are stored there.

Retention and your choices

Stored analytics records do not currently have an automatic deletion schedule. The 400-day cookie expiry is a browser-storage limit, not a promise that server records are deleted after 400 days. Clearing cookies does not erase records already stored.

You can clear or block cookies and site storage in your browser. To ask about access, correction, or deletion of information, email hey@stillinlove.co. Please describe the request without sending sensitive information unnecessarily.

Other websites and contact

Linked retailers and video services apply their own privacy practices when you visit or use them. If you email us, your address and the information you send are used to handle your request. See Contact for corrections and takedown requests.