Privacy.
The short version: we collect very little, we sell nothing, and your plan cart lives in your own browser until you book a call. Two ad tools — Google and Meta — set cookies so we can tell which of our own ads work. A third, Squid, tries to work out who you are and where you work. None of them see what you type. The whole trade is in §05.
Last updated September 2026
§01 · Your plan cart
Your plan cart
The services you add to your plan are stored in your own browser (localStorage), along with any figure the Scope Desk worked out for you. That's so it's all still there when you come back. Nothing is sent anywhere while you shop, and clearing your browser storage deletes it for good — we have no copy to delete for you.
The one exception, stated plainly: when you book a call or request times, what's in your plan is sent along with your booking — so whoever takes the call already knows what you were looking at instead of asking you to list it again. No payment details are collected on this site at any point.
§02 · What we collect, and when
What we collect, and when
Every item below is something you typed into a form on purpose. The one thing we can learn without you typing anything — your name and where you work, worked out from your visit — is in §05.
- Booking an audit. Your name, your email, and either your store address or a line about what you're launching — plus the time slot you picked and the contents of your plan cart. We use it to hold the slot, send the calendar invite, and go through your store before we meet.
- The Scope Desk. Your description of the job, your current platform, and your rough catalogue size. No email is required to see a number. If you ask for a copy of the ticket afterwards, that's the point at which we get your email address.
- The newsletter, the checklist, and the calculator. Your email, plus whatever else that particular form asks for — your checklist score and weakest area, or the projection you had on screen. We use it to send you the thing you asked for.
- Emailing us. Whatever's in your email, which lands in a normal inbox.
We don't ask for special-category data and we don't buy mailing lists. We never sell or rent any of it.
§03 · If you give us access to your accounts
If you give us access to your accounts
Read-only access to an ad account or Klaviyo is optional, and it's arranged on the call — never through this site. If you grant it: we read, we never write, we use it only for your audit, and you can revoke it the same afternoon. Nothing we see there appears in a case study without your written yes.
§04 · Who else touches it
Who else touches it
These are the only companies that handle anything you send us. Each is a processor working on our instructions — none of them get to use your data for their own ends.
- Vercel — hosts the site and serves every page, so it necessarily handles the usual request data (IP address, browser, page requested) to deliver the site and keep it standing. Also runs our analytics, described in §05. Their policy.
- Railway — hosts our own scheduling and estimating system, which is where your booking and your Scope Desk description are sent. The system is ours; Railway is the infrastructure underneath it. Their policy.
- Supabase — the database underneath that same system: what you submit through any form here — the booking form, the Scope Desk, the newsletter, the checklist, the calculator — is stored there, on our instructions and nowhere else. Their policy.
- Anthropic (Claude) — the language model inside the Scope Desk, and nowhere else on this site. The description you type is read by Claude so the desk can ask a sensible follow-up question and pick the right tasks. Anthropic does not train on it: business API traffic is excluded from training by default. Their policy.
- Resend — delivers the thing a form promised you: the checklist, the email copy of your Scope Desk ticket, and the like. It handles the sending; it isn't a mailing list and you are not subscribed to anything by asking for one of these. Their policy.
- Listmonk — our mailing list, which we run ourselves on the Railway servers above rather than handing to a marketing platform. Only two forms put you on it: the newsletter and the checklist, both of which say so at the point you submit them. Everything else here — the calculator, your checklist score, a request for other times — is a one-off and never reaches it. Joining takes a confirmation click in an email, and leaving takes one click in any email after that.
- Web3Forms — a fallback that relays a form into our inbox if the system above is unavailable, and on our preview builds. It passes messages along; it doesn't keep a marketing database of you. Their policy.
- Cloudflare — the spam check on our forms, called Turnstile. It runs only at the moment you submit something, and only on the form you submitted — not while you read the site. To decide whether you’re a person it looks at signals from your browser and at your IP address. It does not receive what you typed.
- Google Workspace — where our email lives, so anything you send us or we send you sits there.
These providers run on servers in the United States, which means data you send us is transferred there. If we ever add another one, this list gets updated before it goes live — not after.
Two more companies see that you visited, but never what you send: Google and Meta, the analytics and advertising tools described in §05. They're not processors working on our instructions like the list above — they use what they collect for their own advertising businesses. That's what they're for, and it's the trade we're making to find out which of our ads actually work. Nothing you type into a form here reaches either of them.
One more sees your visit and tries to put a name to it: Squid (ScriptEngine, Inc.), the visitor-identification tool described in §05. It works on our instructions, and the names it finds come from business-contact data held by five other companies: People Data Labs, ZoomInfo, 5x5, BigDBM and Experian. Nothing you type into a form here reaches Squid or any of them. Squid's policy.
§05 · Analytics, cookies, and what we measure
Analytics, cookies, and what we measure
We use Vercel Web Analytics and Speed Insights to see how many people visit which pages, which buttons actually get used, and how fast the site loads for them. Both are cookieless and aggregate: we can see that a plan was started on the shop page, not that you started it. The event data is deliberately narrow — a service name, a page path, a count — and the list of properties allowed through is fixed in our own code.
We also run two tools that do use cookies, because we buy ads for our own business and they are how we tell which ones bring people who actually book a call. Google Analytics 4 measures pages and events, sets cookies in your browser, and sends that data to Google. The Meta Pixel tells us which Facebook and Instagram ads led to a booking, and lets us show ads to people who visited but didn't book; it sets a cookie Meta can match to your account if you have one.
Neither of them ever receives what you type into a form here. They see pages and events, not the contents of your plan, your Scope Desk answers, or your message to us. If you would rather not be measured this way, blocking third-party cookies or running a tracker-blocking extension stops both.
The third tool, Squid, does something the other two don't: it tries to work out who you are. Its script runs on every page and tells Squid which pages you view, how far you scroll, where you click, how your pointer moves (that's how it tells people from bots), your IP address and your browser. Squid checks your visit against the business-contact data named in §04. If those sources agree on who you are, we get your name, work email, job title, LinkedIn profile and employer, next to the pages you looked at. If they don't, we get nothing and you stay anonymous.
Why we run it: it tells us which businesses are looking at us even when nobody fills in a form, so we can get in touch with the ones we think we can help. What it finds goes to Squid and to our team's Slack. It never goes onto our mailing list, and nothing you type into a form here reaches Squid.
If you'd rather not be identified, Squid's do-not-identify list takes your email address and stops it on every site that runs Squid, not just this one. To have what we already hold deleted, see §07.
The things this site stores on your device by itself are your plan cart, the Scope Desk figure, and a handful of notes about what you have already seen — all local, and none of it an identifier anyone can follow you around the web with. The three tools above add their own cookies on top of that, and those ones are identifiers. Rather than describe that in the abstract, here is the whole list.
| Name | Set by | What it does | Lasts |
|---|---|---|---|
_ga | Google Analytics | Tells one browser apart from another, so two visits from you are not counted as two people. | 13 months |
_ga_NB7XSEH1JW | Google Analytics | Holds the state of your current visit for this specific property. | 13 months |
_fbp | Meta | Lets Meta connect a visit here to an ad of ours you saw there. | 90 days |
squid_sid | Squid | Ties the pages of your current visit together. | Until the browser closes |
squid_vid | Squid | Carries the ID Squid keeps for your browser, so it can link this visit to earlier ones. | Until the browser closes |
| Name | What it holds | Lasts |
|---|---|---|
gdPlanV2, gdPlanV1 | The services in your plan, and which option you picked for each. | Until you clear it |
gdBuildV1 | The one-off build figure the Scope Desk worked out for you. | Until you clear it |
gdAudit20 | Your answers to the 20-point checklist, so a refresh does not lose them. | Until you clear it |
gdSoundV1 | Whether you switched the interface sounds on. | Until you clear it |
gdMode | Which route through the shop you chose, so the page opens where you left it. | Until you clear it |
gdBuyBarHidden, gdMarqueePaused, gdStamped | Notes that you dismissed the bar at the bottom, paused the moving banner, or have already seen an animation play once. | This tab only |
Meta's script also writes lastExternalReferrer and lastExternalReferrerTime into that same browser storage — where you arrived from, and when. Squid's writes squid:version there and squid_tab_id into this tab's storage, and keeps its longer-lived ID for your browser inside a small frame loaded from its own site. We do not read any of them; they are Meta's and Squid's, in your browser. Clearing your site data removes everything in both tables.
§06 · How long we keep it
How long we keep it
- Your plan cart: in your browser only, until you clear it. We never had a copy.
- Booking and audit records: 24 months after the call, then deleted. If you become a client, your records live as long as we work together, plus 24 months.
- Scope Desk descriptions: 12 months, so we can check our own estimates against what was actually asked for.
- Form captures (the checklist, your checklist score, the calculator, a request for other times): 24 months, then deleted. These used to be an email in our inbox and nothing else; they are now a row in the database above, which is what lets us answer you and see whether the thing you asked for was any use.
- Newsletter: until you unsubscribe, which is one click in every email.
- Visitors Squid identifies: the match sits in Squid and in our team's Slack. Ask and we'll delete yours from both — see §07.
- Email in the inbox: 24 months, unless it's part of a client relationship, where normal business-record rules apply.
Aggregate analytics have no personal data left in them to expire, so they're kept for as long as they're useful.
§07 · Questions, copies, deletions, complaints
Questions, copies, deletions, complaints
The company behind this site is Golden Digital LLC, 307 W Freedley St, Norristown, PA 19401. It decides what gets collected here and why, which in the law's language makes it the controller of your data.
Email hello@goldendigital.co and a human will answer. Ask for a copy of what we hold, ask us to correct it, or ask us to delete it — same address, and we'll confirm when it's done. No account, no ticket system, no form standing in the way.
Depending on where you live, you may also have the right to complain to a data protection authority. We'd rather you told us first and gave us the chance to put it right.

