Cookie Notice

This notice explains the cookies and similar browser storage used on:

• dasreplay.com: the marketing site;
• dasreplay.com/support: the help center;
• app.dasreplay.com: the app, including public share pages.

It is part of our Privacy Policy. The operator is Shark Belly Industries LLC.

Summary

1. What cookies and browser storage are

• Cookies are small text files a website saves in your browser.
• Local storage and session storage are similar browser features that keep data on your device.
  • Local storage lasts until it’s cleared (by you, or by us for some keys when you sign out; see Section 4).
  • Session storage is cleared when you close the tab.
• “Cookies” in this notice. We use the word “cookies” for all of them. Most of what DAS Replay stores is in local storage.
• Not sent automatically. Browser storage isn’t sent to our servers on its own. But some of the same settings (for example layouts, chart drawings and chart templates) are also saved to your account, so they follow you to other devices.

2. Cookies we use

2.1 Strictly necessary

These keep the Service secure and let you sign in. The Service doesn’t work without them.

2.2 Functional

These remember choices you make. They stay on your device and don’t track you.

Email pop-up: the pop-up runs during the beta and sets the dr_email_modal key. We plan to retire it when paid plans begin after 11:59 p.m. ET on October 5, 2026; the key is no longer set once it is gone.

Shared computers: several of these keys include your user ID, and drawings can include text you typed. They stay in the browser after you sign out. On a shared computer, clear site data after signing out.

2.3 Analytics

These tell us how people use our sites, in aggregate.

How Google Analytics works here:

• What we send.
  • The web address of each page you view.
  • When you’re signed in to the app, your user ID: a random code, not your name or email. It lets Google count one person across your devices.
  • Interactions: sign-up, sign-in, starting a replay, seeing or submitting the email pop-up, clicking a call-to-action button, and help-center votes.
  • Google’s automatic measurements (for example scrolls and outbound clicks).
• What’s in page addresses. Some addresses carry codes, such as sign-in and password-reset links, share links, unsubscribe links and help-center search terms. We redact those codes and search terms before the address is sent to Google Analytics.
• What we don’t send. We never send your name or email as analytics data.
• What Google derives. Google works out your approximate location from your IP address, and may process data in the US.
• No advertising. We don’t use Google Analytics for advertising, and Google signals are switched off.
• Google’s policies. See How Google uses information from sites that use its services.

2.4 Sign-up attribution

These two first-party cookies remember how you found us, so a later sign-up can be credited to the right link, campaign or site. That is how referrals and creator links are counted (see the Terms of Service, Section 4.16).

• What happens to them. When you create an account, we read both and save the first and the latest touch with your account (see the Privacy Policy, Section 2.2).
• Not sent to anyone else. They are ours alone. No ad network or analytics provider reads them.

2.5 Advertising measurement (Meta)

We advertise on Facebook and Instagram. These cookies let Meta tell us which ad clicks led to a sign-up, a trial or a payment. Our Privacy Policy, Section 6 explains what is sent and why.

• When the Pixel doesn’t load. It doesn’t load if your browser sends Global Privacy Control, or if you chose “Do not share” on Your privacy choices (the ad_sharing cookie in Section 2.2).
• Meta’s own cookies. If you’re signed in to Facebook or Instagram in the same browser, Meta can also read its own cookies on its own domains when the Pixel loads, under Meta’s cookie policy.
• No retargeting. We don’t build retargeting audiences from these cookies.

2.5b Advertising measurement (Reddit)

We also advertise on Reddit. These cookies let Reddit tell us which ad clicks led to a sign-up, a trial or a payment, the same way as Meta above. Our Privacy Policy, Section 6 explains what is sent and why.

• When the Pixel doesn’t load. The same rule as Meta’s: not under Global Privacy Control, and not after “Do not share” (the ad_sharing cookie in Section 2.2).
• No form reading. Reddit’s “advanced matching”, which reads email addresses typed into a page, is switched off.
• No retargeting. We don’t build retargeting audiences from these cookies.

2.5c Advertising measurement (X)

We also advertise on X. These cookies let X tell us which ad clicks led to a sign-up, a trial or a payment, the same way as Meta above. Our Privacy Policy, Section 6 explains what is sent and why.

• When the Pixel doesn’t load. The same rule as Meta’s: not under Global Privacy Control, and not after “Do not share” (the ad_sharing cookie in Section 2.2).
• X’s own cookies. If you’re signed in to X in the same browser, X can also read its own cookies on its own domains when the X Pixel loads, under X’s cookie policy.
• No retargeting. We don’t build retargeting audiences from these cookies.

2.6 Other third-party requests and cookies

• Google Fonts. The marketing site, the help center and the app (including public share pages) load fonts from Google (fonts.googleapis.com, fonts.gstatic.com). Google receives your IP address and browser details, but no cookie is set.
• Stripe. Checkout and the billing portal run on Stripe’s own pages. Stripe sets its own cookies there, under Stripe’s cookie policy.
• Email tracking pixel. Our emails contain a tracking pixel that records opens. See Privacy Policy §5.

2.7 Visitor ledger

This first-party cookie lets us see how people use our sites before they sign up: how many visits it takes, and which pages they read on the way. It is ours alone; no ad network or analytics provider reads it.

• What a visit records. One row per visit: the page you landed on, the referring site (its name only, such as www.google.com), the UTM source, medium, campaign and content, your country, whether you’re on a phone or a computer, how long you actively used the page while it was on screen, and how many pages you viewed.
• What it doesn’t record. No IP address, no browser details (user agent) and no full web addresses.
• When you sign up or sign in. We link the visits from that browser to your account, so we can see which visits led to it. We don’t if that browser has switched the ledger off (below).
• How long we keep it. Visits that are never linked to an account are deleted after 13 months, or after 90 days if they recorded no active time on the page. Linked visits are kept with your account and deleted with it.
• Your answers on /try. On the /try page, each answer is also saved on our server against your vid, so a browser that lost its local copy can pick up where it left off: the answers, the screen you reached and whether you’re on a phone or a computer, plus the email once you give it (we never send the email back to the browser). With the ledger switched off nothing is saved this way, but an email you give on /try, even under “Do not share”, is still saved with the answers you’d given by then, so we can send the link back to your deal. Kept like visits: 13 months unless linked to an account. See the Privacy Policy, Section 2.2.
• How to switch it off. Global Privacy Control, or “Do not share” on Your privacy choices (the ad_sharing cookie in Section 2.2), switches the ledger off in that browser: we stop setting the vid cookie, record no visits from it, and don’t link it to your account when you sign up or sign in. Visits recorded before you opted out are kept only as long as the rules above allow.

3. Consent

• Today. There is no cookie banner. Google Analytics loads for every visitor, in every country, as soon as the page opens.
• Planned: EEA, UK and Switzerland. We are building a geo-gated consent banner. It is not live yet. When it ships:
  • visitors from these countries will see a banner, and Google Analytics will not run until they click “Accept”;
  • Google Consent Mode will default to “denied”;
  • “Reject” will be as easy as “Accept”;
  • a “Cookie settings” link in the footer will reopen the choice at any time;
  • the choice will be stored for 12 months in a first-party cookie on .dasreplay.com, so one choice covers all three sites (strictly necessary; no consent needed);
  • strictly necessary and functional storage will still not need consent.
• Everyone else. No banner. Google Analytics runs, and you can opt out at any time (Section 4).
• Advertising measurement (Meta, Reddit and X). No banner: our ads run in the United States only, and US law asks for notice and an opt-out, which Your privacy choices provides.
• Global Privacy Control. We honor it: a GPC signal keeps the Meta, Reddit and X Pixels off, opts you out of ad measurement and switches off the visitor ledger (see the Privacy Policy, Section 14).
• Do Not Track. We don’t act on it.

4. How to control cookies

• Opt out of Google Analytics. Install Google’s opt-out browser add-on. It works on every site that uses GA.
• Opt out of Meta, Reddit and X ad measurement and the visitor ledger. Choose “Do not share” on Your privacy choices, or turn on Global Privacy Control in your browser. Opting out stops future reports, visit records and links between that browser and your account; it doesn’t recall reports Meta, Reddit or X already received.
• Block or delete cookies in your browser settings:
  • Chrome
  • Safari
  • Firefox
  • Edge
  • Clearing “site data” also clears local storage.
• What happens if you block them:
  • If you block strictly necessary storage, you can’t sign in.
  • If you clear functional storage, your on-device preferences reset. Settings saved to your account stay.
• Sign out. Signing out of the app ends your session and clears your replay layout, saved layouts and starting-cash setting from the browser. Other app settings and chart drawings stay until you clear site data (see Section 2.2).
• Private browsing. It clears everything when you close the window.

5. Changes and contact

• Changes. When we add or change cookies, we’ll update this notice and the “Last updated” date.
• Contact. Questions: [email protected].
• Postal address. Shark Belly Industries LLC, 1209 Mountain Road Pl NE, Ste H, Albuquerque, NM 87110, USA.

Related: Terms of Service · Privacy Policy · Your privacy choices · Risk & Simulated Performance Disclosure