Cookie Policy

1) What Are Cookies?

Cookies are small text files placed on your device. Similar technologies include local storage, session storage, browser memory, pixels, and SDKs. We use them to operate the site, remember preferences, analyze usage, and support features like maps and payments.

2) How We Use Cookies

• Strictly Necessary — required for core functionality (security, session management, load balancing).
• Preferences — remember choices (e.g., language, view mode).
• Analytics — measure visits and actions, and collect browser diagnostics, unless you reject Analytics.
• Session replay — record masked public page activity unless you reject Session replay.
• Functionality — enable embedded services (e.g., Mapbox tiles/geocoding).

3) Third-Party Cookies/Technologies

• PostHog (EU project) — optional cookieless measurement and separately optional masked public session recordings.
• Vercel Web Analytics — optional visit measurement without analytics cookies.
• Vercel Speed Insights is disabled and does not collect new performance data.
• Supabase — essential account services and separately optional usage records with a browser sessionStorage identifier.
• Sentry — optional browser errors and performance traces, plus separate service operations on servers. No Sentry session replay.
• Upstash — essential request rate limits and abuse prevention. Rate-limit keys can contain IP addresses or account identifiers.
• Mapbox — maps, tiles, and geocoding.
• Stripe — payments (on checkout flows).
• Vercel / Cloudflare — performance and security (CDN/WAF).

Other feature providers may use cookies when their services are loaded.

4) Your Measurement Choices

Analytics and masked session recordings start automatically. You can explicitly reject tracking or change either purpose at any time. Closing the notice keeps the current settings. Only an explicit rejection turns a purpose off.

The Analytics choice covers PostHog, Vercel Web Analytics, Supabase usage records, and Sentry browser diagnostics. The separate Session replay choice covers PostHog recordings. You can allow either purpose without allowing the other. Refusal does not prevent access to the site. Essential service and security processing stays active. First-party browser fault reports remain active independently of tracking choices for service reliability. They send sanitized error messages, stack information, page paths, and technical context to RSNM. The server can add your account ID and browser user agent. These reports are separate from optional Sentry browser diagnostics and are not usage analysis.

PostHog usage measurement uses a daily server hash and no browser-stored visitor identifier. We do not send account IDs, names, emails, search text, form contents, or URL query strings to PostHog. Other optional tools use different data. Supabase usage measurement stores a session identifier in sessionStorage while Analytics is enabled. Some Supabase usage records can link to your account after sign-in.

PostHog replay records masked page layout, pointer movements, scrolling, and clicks unless you reject Session replay. It retains fixed public control labels and masks other page text and input values. Forms, dialogs, privacy controls, private pages, images, and maps are excluded. Replay uses random identifiers held only in page memory. Reloading a page can start a separate recording. We do not link these identifiers to your account or cookieless visitor statistics. The SDK can briefly test browser storage without retaining visitor identifiers.

While Analytics is enabled, visitor statistics include country, region, and city estimates from Vercel using your IP address. These estimates can be inaccurate or unavailable. The location request excludes cookies, account data, GPS coordinates, and postal codes.

Open Privacy choices below or in the footer to change either choice at any time. Closing settings cancels unsaved changes. A saved refusal remains in effect. Earlier refusals remain refused when the notice changes. Tracking stays on by default when no saved rejection exists.

Do Not Track and Global Privacy Control stop optional browser collection even if a saved choice allows it. Administrator sessions, unknown account roles, and private pages also block optional collection. Withdrawal stops future optional collection. It does not automatically erase earlier records or affect earlier lawful processing. Use the support address below to request deletion or exercise your rights.

You can also control cookies via your browser settings by blocking or deleting cookies. Note: blocking necessary cookies may affect site functionality.

5) Retention

We store your Analytics choice, Session replay choice, notice version, and choice time in browser local storage. These remain until you change or clear them. This choice record does not contain a visitor identifier. If storage is blocked, your choice applies only to the current page. A fresh page uses the automatic defaults.

Optional Supabase session identifiers remain in sessionStorage for the browser tab session. Refusing Analytics clears the optional session state owned by RSNM. PostHog replay identifiers stay in page memory. PostHog session recordings have a configured 30-day storage period. A daily analytics hash or short-lived browser identifier does not set the storage period for server records.

Other server records follow their database or provider storage settings. See Privacy Policy: Retention for the current criteria and provider limits. Clearing cookies or browser storage does not delete records already sent to a server.

6) More Information

For more details about how we process personal data, see our Privacy Policy. You can contact us at support@recordshopsnearme.com.