Privacy.

§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. The saved cart stays in your browser; the limited shopping events described in §05 are measured separately. Clearing your browser storage deletes the saved cart — we have no server copy of it to delete for you.

If you copy a plan link from your receipt, it holds the services and options you picked and nothing else — no name, no email, no prices, no Scope Desk figure. It sits after the # in the address, the part browsers don't send to our servers, and the page wipes it from the address bar as soon as it has read it.

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

The form details below are things you choose to send us. Analytics and visitor identification — including a name and employer worked out from a visit — are described in §05.

• Booking a Growth 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 contact form and our campaign pages. Your name, your email, and your message — or, on a campaign page, the one choice it asks you to make. Our team is alerted and writes back.
• 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.
• Referring a brand, or applying to partner. Your name and email, plus anything else the form asks — your company and website if you’re applying. If you’re referring a brand, you also give us details about someone else: the brand, the person to contact there, their email and store, and any note. You confirm they’ve agreed to hear from us. We use those details to contact that brand, and yours to keep you posted and pay you if they sign. We tell the brand who introduced them. We tell you only whether they booked, whether they signed, and when you’re paid — nothing they tell us.
• Emailing us. Whatever's in your email, which lands in a normal inbox.

One thing rides along with any of these without you typing it. If you arrived by clicking an ad or a tagged link, the tags on that link come with you: the campaign labels (utm_source and the like), the ad platform's click ID (gclid from Google, fbclid from Meta, and similar ones from TikTok and Microsoft) and the page you landed on. They're kept in this tab (gdCampaignV1, in §05) and sent with any form you submit or call you book during that visit, so we can tell which campaign brought you.

One more, if someone sent you here with their referral link (?ref= in the address): we keep that code (gdRefV1, and a gd_ref cookie our own server sets so Safari doesn’t clear it after a week; both in §05) for 90 days, or for this visit only if your browser sends Global Privacy Control, and send it with any form you submit or call you book, so we know who to thank. It goes to no ad platform.

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 Growth 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 contact form, our campaign pages, 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.
• PostHog — our product analytics, described in §05: which pages a visit went through and which steps of an enquiry it reached, tied to a random browser identifier. It never receives what you type into a form. 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. When you book a call or send any form other than the newsletter or the checklist, an alert with what you sent is emailed to us here too.
• Slack — where our team is alerted to the same bookings and forms, with what you sent, so we can answer it. It's also where Squid's matches arrive (§05). Their policy.

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.

Advertising and analytics companies also see that you visited: Google, Meta and OpenAI, 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 Google. Meta gets one thing: when a form you send or a call you confirm goes through, our server tells Meta it happened and includes your email address in hashed form — a one-way code (SHA-256) that Meta can only match against an email address it already has. Never your message, your plan or your Scope Desk answers. OpenAI gets more, and sooner: its script watches the forms on this site and sends the email address, phone number and first and last name you type into one to OpenAI in hashed form, as you fill it in and whether or not you send it (§05). Google's script can be set to pick up email addresses typed into a page and send them to Google in hashed form; we have that switched off, and our own code removes any such data from what is sent to Google as a second lock.

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.

Squid's script doesn't work alone. When it loads, it brings in three more parties, which also see your visit: LiveIntent (liadm.com), an identity-matching company that receives the address of the page you're on, tries to match your browser to identifiers it already holds, and sets its own cookie, lidid, on its own domain; a tracking pixel served from alocdn.com, which sets a cookie called uuid on its own domain; and ip-api (ip-api.com), which receives your IP address and returns an approximate location and network — city, postcode, internet provider, and whether the address belongs to a proxy or a data centre. Squid also runs a device-fingerprinting script, which reads characteristics of your browser and device so it can recognise them again without a cookie. None of this happens if your browser sends Global Privacy Control (§05).

§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.

PostHog helps us see where visits become enquiries and where people leave that journey. We send page paths, campaign labels and the same limited event properties described above. PostHog stores a random browser identifier in ph_gd_posthog in local storage and session information in ph_gd_posthog in session storage, alongside ph_gd_posthog_window_id, ph_gd_posthog_primary_window_exists and ph_gd_posthog_session_registered_properties, so it can connect steps across pages. We do not send names, emails, messages, Scope Desk answers, full query strings or advertising click IDs to it. We also collect JavaScript error types and locations in our own code to help fix broken pages and forms. We remove error messages, function names and variable values before sending an error report. Automatic click capture, session recordings and heatmaps are disabled. PostHog receives your IP address when your browser connects; we disable its use for location enrichment. PostHog's policy.

We also run advertising tools that 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.

The ChatGPT Ads Pixel loads OpenAI's measurement script on every page so we can measure our ChatGPT ads. It can store an ad-click reference and a browser reference in the cookies below. When a lead submission succeeds, the browser and our server tell OpenAI it happened using the same event reference, so it counts once. Our server includes the ad-click and browser references when available, never your email, message or other form fields. OpenAI's script itself goes further. Its automatic matching is switched on here: when you fill in a form on this site, it reads the email address, phone number and first and last name you type, turns each into a one-way code (SHA-256), and sends those to OpenAI so it can match your visit to a ChatGPT account. It does this when you move on from a field or press a button, even if you never send the form. It doesn't take your message, your plan or your Scope Desk answers, and it skips password and payment fields. Global Privacy Control, below, stops the script loading at all. OpenAI's policy.

Google never receives what you type into a form here. Meta gets one item from a form: when one you send or a call you confirm goes through, our server tells Meta it happened, with your email address in hashed form (see §04), your IP address and browser, and the two Meta cookies below, so Meta can credit the ad that brought you even if your browser blocked the pixel. Neither of them sees the contents of your plan, your Scope Desk answers, or your message to us.

Our Google Analytics also has Google Signals switched on. For visitors who are signed in to a Google account and allow ad personalisation, it lets Google connect this visit to that account. That gives us reports across devices and estimated age ranges and interests — in totals only, never who you are — and it makes remarketing possible: showing our ads on Google to people who have been here.

If you'd rather not be measured this way, note that Google, Meta and OpenAI set their cookies as this site's own, so blocking third-party cookies does not stop them. These do: Google's Analytics opt-out browser add-on; My Ad Center, to turn off personalised ads from Google; Meta's ad preferences, for Facebook and Instagram; a tracker-blocking extension, which stops all three; clearing this site's cookies (they come back on your next visit); or Global Privacy Control, below.

Our visitor-identification tool, Squid, has a different job: 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.

Global Privacy Control and Do Not Track. If your browser or an extension sends a Global Privacy Control signal, we treat it as an opt-out: PostHog, the Meta Pixel, ChatGPT Ads Pixel and Squid don't load at all, so neither do the companies Squid brings in, and our server sends Meta nothing about your forms or bookings either. Google Analytics still counts your visit but with Google Signals and ad personalisation switched off for it. We don't respond to the older Do Not Track signal, which never got an agreed meaning and which most browsers have dropped; Global Privacy Control is the one we honour.

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 tools above, and the companies Squid brings in, add their own cookies and browser identifiers on top of that, and those ones are identifiers. Rather than describe that in the abstract, here is the whole list.

Meta's script also writes lastExternalReferrer and lastExternalReferrerTime into that same browser storage — where you arrived from, and when — and, if you arrived from one of its ads, multiFbc, a copy of the same click ID as the _fbc cookie. 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, except lidid and uuid, which live on other companies' domains (see §06).

§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 Growth 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 contact form, our campaign pages, the checklist, your checklist score, the calculator, a request for other times, a referral, a partner application): 24 months, then deleted. If we pay you a referral bounty, the payment record and your tax form are kept as long as tax law requires. 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. We haven't set a period for it, so Squid keeps it under its own policy. Ask and we'll delete yours from both — see §07.
• PostHog: analytics are stored in our US-hosted PostHog project under its retention settings. We have not set a shorter custom retention period. Clearing your site data removes its browser identifier and session information; it does not delete events already sent. Contact us about deletion using the details below.
• Google Analytics: Google keeps the visit-level data for two months, which is its default setting, and after that it survives only in aggregate reports that don't identify anyone. Meta keeps what its pixel sends under Meta's own policy; we can't set a period for it.
• Cookies: as long as the table in §05 says, unless you clear them first. The ones set by LiveIntent and alocdn.com live on those companies' domains, so clearing this site's data doesn't remove them — clear all cookies, or block third-party cookies, and they go.
• Email in the inbox: 24 months, unless it's part of a client relationship, where normal business-record rules apply.

Vercel's analytics set no cookies and keep only totals, so there is no personal data in them to expire; 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 we’ll 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.