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
| Type | Used? | Needs your consent? | Where |
|---|---|---|---|
| Strictly necessary | Yes | No | Security cookies and bot check (Cloudflare); sign-in storage (app) |
| Functional | Yes | No (they only remember your own settings) | Browser storage on all three sites |
| Analytics | Yes: Google Analytics 4 | EEA, UK and Switzerland: yes. Elsewhere: no, but you can opt out. Today GA loads for everyone without asking | All three sites |
| Advertising measurement | Yes: Meta Pixel | No, but you can opt out, and we honor Global Privacy Control | dasreplay.com and the app |
| Retargeting | No | — | — |
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.
| Name | Type | Provider | Site | Purpose | Duration |
|---|---|---|---|---|---|
__cf_bm | Cookie | Cloudflare | All | Tells people from bots; protects against abuse | 30 minutes |
Turnstile bot check (e.g. cf_clearance) | Cookie / storage | Cloudflare | Most marketing-site pages (loaded with the email pop-up), the /access form, and signup on share pages | Checks that a signup comes from a person, not a bot | Up to the challenge validity period |
sb-<project>-auth-token | Local storage | DAS Replay (Supabase Auth) | App | Keeps you signed in: session token and refresh token | Until you sign out; the session refreshes automatically |
impersonation.session.v1 | Session storage | DAS Replay | App (staff only) | Read-only “view as user” session for support staff | Until the tab closes; the server ends it after 15 minutes |
2.2 Functional
These remember choices you make. They stay on your device and don’t track you.
| Name | Type | Provider | Site | Purpose | Duration |
|---|---|---|---|---|---|
replay.layout.v1:<user ID>, replay-named-layouts-v1:<user ID> | Local storage | DAS Replay | App | Your replay window layout and saved layouts | Until you clear site data (not cleared on sign-out) |
replay.popouts.v1:<user ID>, tm-layout-v1:<user ID>, forex-layout-v1:<user ID>, futures-layout-v3:<user ID>, and <layout key>.popouts:<user ID> | Local storage | DAS Replay | App | Window layouts and pop-out windows for the other desks | Until you clear site data (not cleared on sign-out) |
replay.startingCash:<user ID> | Local storage | DAS Replay | App | Your starting-cash setting | Until you sign out or clear site data |
replay.leverage, replay.forexLeverage | Local storage | DAS Replay | App | Leverage settings | Until you clear site data (not cleared on sign-out) |
replay.sessionDraft:<user ID> | Local storage | DAS Replay | App | Restores a replay setup you haven’t started yet | Until you clear site data (not cleared on sign-out) |
replay.resume-identity.v3:<asset class> | Session storage | DAS Replay | App | Reconnects you to a replay you were running | Until the tab closes |
drawings:<user ID>:<symbol> (and older replay.drawings.v1… keys) | Local storage | DAS Replay | App | Chart drawings, including any text you typed in them, kept on this device | Until you clear site data (not cleared on sign-out) |
chart.drawingRail:<user ID>, chart.drawingDefaults:<user ID>, indicator-favorites:<user ID>, interval-favorites:<user ID>, chart.settingsDefault:<user ID>, chart-templates:<user ID> | Local storage | DAS Replay | App | Chart tool preferences: last-used drawing tools, drawing defaults, favorite indicators and intervals, default chart settings, chart templates | Until you clear site data (not cleared on sign-out) |
theme, chart-timezone, quote-flash, fill-chime, trades.defaultView | Local storage | DAS Replay | App | Display, sound and chart preferences | Until you clear site data |
chart-trading-click-price-hint-seen | Local storage | DAS Replay | App | Remembers you’ve seen a tip | Until you clear site data |
dr_signed_in | Cookie (on dasreplay.com, set by the app) | DAS Replay | App and marketing site | Tells the marketing site you’re signed in to the app, so its header shows “Open app”. Holds only the app’s address: no token, no user ID | 30 days, renewed while you use the app; cleared when you sign out |
ad_sharing | Cookie (on .dasreplay.com) | DAS Replay | All | Remembers that you chose “Do not share” on Your privacy choices, so the Meta Pixel stays off. Holds only the word off | About 400 days, or until you choose “Share” again |
dr_email_modal | Local storage | DAS Replay | Marketing site | Remembers you’ve seen or submitted the email pop-up, so it doesn’t show again | Never expires (until you clear it) |
help-vote:<article> | Local storage | DAS Replay | Help center | Remembers your “Was this helpful?” vote | Never expires (until you clear it) |
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.
| Name | Type | Provider | Site | Purpose | Duration |
|---|---|---|---|---|---|
_ga | Cookie | Google Analytics 4 | All three, including public share pages | Tells visitors apart (random ID) | 2 years |
_ga_<container-id> | Cookie | Google Analytics 4 | All three | Keeps session state | 2 years |
_gl | URL parameter (not stored) | Google Analytics 4 | Links between dasreplay.com and app.dasreplay.com | Carries your analytics ID across our two domains, so a signup counts as one visit | Not stored |
Cloudflare Web Analytics beacon (beacon.min.js) | Script (no cookie) | Cloudflare | App | Page performance measurement | Doesn’t use cookies |
How Google Analytics works here:
- What we send.
- The web address of each page you view.
- 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, email or user ID 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 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.
| Name | Type | Provider | Site | Purpose | Duration |
|---|---|---|---|---|---|
_fbp | Cookie (on .dasreplay.com) | Meta Pixel | dasreplay.com and the app | Tells browsers apart for ad measurement (random ID) | 90 days |
_fbc | Cookie (on .dasreplay.com) | Meta Pixel / DAS Replay | dasreplay.com and the app | Holds the click code (fbclid) from the Meta ad you clicked, so a later sign-up can be matched to that ad. We set it ourselves when the Pixel is blocked | 90 days |
fbclid | URL parameter (not stored by us apart from _fbc) | Meta | Ad landing pages | The click code Meta adds to an ad link | Not stored |
- 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_sharingcookie 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.5 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.
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). 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 Pixel off and opts you out of ad measurement (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 ad measurement. Choose “Do not share” on Your privacy choices, or turn on Global Privacy Control in your browser. Opting out stops future reports; it doesn’t recall reports Meta already received.
- Block or delete cookies in your browser settings:
- 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: hello@email.dasreplay.com.
- 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