Cookie Policy
Sutherland Commerce Group LLC, trading as Smooth Voice Marketing Effective Date: on publication · Version 1.0
In short: this page lists every cookie and similar technology our site actually uses, who provides it, what it does and how long it lasts. It also tells you honestly where we are with consent, rather than describing a banner we have not built yet.
Where we are with consent, stated plainly
We have not yet deployed a cookie consent banner. Advertising and analytics technologies described in section 6 — principally the Meta pixel — currently load when a page loads, rather than waiting for you to agree.
Under the UK Privacy and Electronic Communications Regulations and equivalent EU rules, non-essential technologies of this kind should be set only after you consent. We are implementing a consent mechanism. Until it is live, section 8 explains how to block or remove these technologies yourself in your browser, and section 8.3 gives the direct opt-out routes for each provider.
We would rather say this than publish a policy describing a banner that is not there. This block will be removed once the mechanism is live and section 7 will be updated to describe how it works.
Index
- What this policy covers
- What cookies and similar technologies are
- First-party and third-party technologies
- The categories we use
- Legal basis and consent
- The technology table
- Our consent mechanism
- How to manage, change or withdraw
- Global Privacy Control
- Server-side logs, which are not cookies
- Changes, contact and complaints
1. What this policy covers
In short: cookies and anything that behaves like one, on our own sites.
1.1 This policy covers cookies and similar technologies — including local storage, session storage, pixels, tags and embedded player storage — used on the websites, funnels and landing pages we operate, currently served at smooth-voice-marketing.vercel.app and any successor or additional domain ("the Site").
1.2 It should be read with our Privacy Policy, which explains what we do with the information these technologies produce, and our Website Terms of Use.
1.3 What it does not cover. It does not cover third-party websites you reach from ours, or the separate landing pages we operate for our Clients, each of which carries its own notice. It does not cover a Client's own website.
2. What cookies and similar technologies are
2.1 Cookies are small text files a site asks your browser to store, and which your browser returns on later requests. They can hold an identifier, a preference or a state.
2.2 Similar technologies do the same job by other means:
- Local storage and session storage hold values in your browser rather than sending them with every request. We use these for advertising click identifiers and for interface state. Local storage persists until cleared; session storage is cleared when you close the tab.
- Pixels and tags are small pieces of code or invisible images that tell a third party a page was viewed or an action taken. The Meta pixel is one.
- Embedded player and widget storage is set by third-party components we embed, such as the video player and the booking widget.
2.3 Duration. A session technology lasts until you close your browser. A persistent one lasts for a stated period or until you delete it.
3. First-party and third-party technologies
3.1 First-party means set by us, on our own domain, and readable only by us. Our visitor identifier and the stored click identifiers are first-party.
3.2 Third-party means set or read by another company whose code runs on our page. On our Site those are Meta, Wistia and Cal.com. Those companies determine their own use of what they collect and have their own privacy policies. Note that the Meta pixel sets its cookies as first-party cookies on our domain, but the data goes to Meta, so we treat it as third-party technology for the purposes of this policy.
4. The categories we use
4.1 Strictly necessary — required to deliver the page and keep it secure, or to record your own privacy choice. No consent required.
4.2 Functional — remember a choice or make a feature work, such as the video player or the booking widget. Consent required.
4.3 Analytics — help us understand how the Site is used. Consent required.
4.4 Marketing and advertising measurement — tell us and Meta which advert produced an enquiry, and allow audiences to be built. Consent required.
5. Legal basis and consent
5.1 United Kingdom and European Union
Under PECR and the equivalent EU rules, we may store or access information on your device without consent only where it is strictly necessary to provide the service you asked for. Everything else needs your consent, and that consent must be freely given, specific, informed and unambiguous, given by a clear affirmative act.
Where consent is the basis for storing or reading the information, the further processing that follows is carried out under the UK/EU GDPR on the bases set out in section 4 of the Privacy Policy.
Our current position is set out in the block at the top of this policy and in section 7. We are not claiming compliance we have not yet achieved.
5.2 United States
We do not sell personal information and do not share it for cross-context behavioural advertising as those terms are defined under the CCPA. Advertising technology on the Site is used for first-party measurement of our own advertising. We honour Global Privacy Control — see section 9.
5.3 Australia
The Australian Privacy Act and the APPs apply to personal information collected through these technologies. See sections 3, 4 and 12 of the Privacy Policy.
6. The technology table
In short: this is the real list, checked against our own source code on 3 August 2026, not a generic one. Where something is present in our code but switched off, the table says so.
Third parties may set additional technologies, or change names and durations, outside our control. Where that happens we update this table as soon as we reasonably can. If you think something is operating that is not listed, tell us at privacy@smoothvoice.ai.
6.1 Strictly necessary
| Name | Provider | Purpose | Type | Party | Duration |
|---|---|---|---|---|---|
sv_consent | Smooth Voice | Records your cookie consent decision so we do not ask again and so other technologies honour it. Not currently set — it is written by the consent mechanism described in section 7, which is not yet deployed | Cookie | First party | 180 days from the decision |
| Vercel infrastructure cookies | Vercel Inc. | Page delivery, routing, load balancing, TLS session management and edge security. Not used for tracking | Cookie | First party | Session or short-lived |
6.2 Functional — consent required
| Name | Provider | Purpose | Type | Party | Duration |
|---|---|---|---|---|---|
sv_offer_exit_seen | Smooth Voice | Remembers that you have already been shown the exit prompt, so it is not shown twice in one visit | Session storage | First party | Until the tab closes |
sv_offer_gift_claimed_* | Smooth Voice | Remembers that you already claimed a guide, so you are not asked again | Local storage | First party | Until you clear it |
| Wistia player storage | Wistia, Inc. | Runs the video player, remembers your position in a video and your volume preference, and reports playback statistics. Loads on every page of the Site | Cookie and local storage | Third party | Session to approximately 1 year, per Wistia |
| Cal.com booking embed storage | Cal.com, Inc. | Runs the embedded booking calendar, maintains the booking session and your time zone. Loads only on the booking step of the assessment | Cookie and local storage | Third party | Session to approximately 30 days, per Cal.com |
6.3 Analytics — consent required
| Name | Provider | Purpose | Type | Party | Duration |
|---|---|---|---|---|---|
sv_offer_vid | Smooth Voice | A random first-party identifier for your browser, so that page views, scroll depth and form steps in one visit can be joined into a single journey and we can see where people stop | Cookie | First party | 365 days |
PostHog analytics identifiers (ph_*) | PostHog Inc. | Measure Site usage: which pages you view, how far through a video you watch, which steps of the assessment you reach, and clicks on links and buttons. They also tie the events of one visit together and link a session recording to it | Cookie and local storage | Third party | Up to approximately 12 months |
6.4 Marketing and advertising measurement — consent required
| Name | Provider | Purpose | Type | Party | Duration |
|---|---|---|---|---|---|
_fbp | Meta | Set by the Meta pixel. Identifies your browser to Meta so that a conversion can be matched to an advert and so audiences can be built. Currently loads on page load | Cookie, set first-party by Meta's script | Third party | 90 days |
_fbc | Meta | Set when you arrive from a Meta advert, holding that advert's click identifier so the enquiry can be credited to it | Cookie, set first-party by Meta's script | Third party | 90 days |
Meta pixel (fbevents.js) | Meta | The pixel itself. Reports page views and conversion events. Loads on every page where an advertising dataset is configured | Tag / script | Third party | Not stored; see the cookies above |
sv_fbclid (and _ts) | Smooth Voice | Stores the Meta advert click identifier from the link you arrived on, so an enquiry made later in the same browser can still be credited to that advert | Local storage | First party | 90 days |
sv_gclid, sv_gbraid, sv_wbraid (and _ts) | Smooth Voice | The same, for Google search advertising click identifiers, if we run search advertising | Local storage | First party | 90 days |
sv_utm_source, sv_utm_medium, sv_utm_campaign, sv_utm_content, sv_utm_term | Smooth Voice | Stores the campaign tags from the link you arrived on for the duration of your visit | Session storage | First party | Until the tab closes |
A note on the click identifiers. These are stored on your device by us and are not shared with Google or any advertising platform except as described in section 3.2 of the Privacy Policy. They are currently captured on arrival regardless of any consent choice. That is a deliberate design decision about first-party measurement, it is one of the things the consent mechanism in section 7 has to resolve, and we are naming it here rather than leaving it out.
6.5 What we do not use
We do not use Google Analytics, Google Tag Manager, Google Ads conversion tags or Google Consent Mode on the Site. We do not use Supabase or Stripe, and no cookies from either are set. Earlier versions of our documents listed some of these; they are not present. If we add any of them, this table and the Privacy Policy will be updated before it goes live.
7. Our consent mechanism
7.1 Current position. A consent banner is not yet deployed. The non-essential technologies in sections 6.2, 6.3 and 6.4 currently load when a page loads. The block at the top of this policy says the same thing.
7.2 What is already built. The underlying consent machinery exists in our code: a stored decision in the sv_consent cookie, and functions that switch analytics capture on or off according to it. What is missing is the interface that asks you and the gate that holds the advertising technologies back until you answer.
7.3 What it will do when it is live. A first visit will present a clear choice to accept or reject non-essential technologies, with both options equally prominent and nothing pre-selected. Non-essential technologies will not load until you choose. Your decision will be recorded for 180 days and you will be able to change it at any time from a control in the footer. This paragraph describes the intended behaviour and does not describe the Site as it stands today.
7.4 In the meantime. Section 8 explains how to block or remove these technologies yourself, and section 8.3 gives each provider's own opt-out.
8. How to manage, change or withdraw
8.1 Our own controls
Once the mechanism in section 7 is live, a "Cookie settings" control in the footer will let you review and change your decision at any time. Until then, use the browser and provider controls below.
8.2 Browser-level controls
Every major browser lets you block or delete cookies and clear local storage. Blocking everything may stop parts of the Site working, in particular the video player and the booking calendar.
- Chrome: Settings → Privacy and security → Third-party cookies; and Settings → Privacy and security → Delete browsing data
- Safari: Settings → Privacy → Block all cookies; and Safari → Settings → Privacy → Manage Website Data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Edge: Settings → Cookies and site permissions → Manage and delete cookies and site data
Private or incognito windows discard cookies and storage when closed, which is the quickest way to visit without leaving anything behind.
8.3 Provider opt-outs
- Meta: your advertising preferences are in Facebook or Instagram Settings → Accounts Centre → Ad preferences. Meta's own controls are at
facebook.com/adpreferences. Browser tracking-prevention features and content blockers also stop the pixel loading. - Wistia: blocking third-party scripts from
fast.wistia.comprevents the player and its storage. The video will not play. - Cal.com: blocking
app.cal.comprevents the booking widget. You can still contact us by email. - PostHog: blocking third party scripts stops PostHog loading. Because we route its requests through our own domain, a content blocker that works on domain alone may not catch it; blocking the
/ingestpath does. Once the consent mechanism in section 7 is deployed, rejecting analytics will opt you out.
9. Global Privacy Control
We honour the Global Privacy Control signal. If your browser sends GPC, we treat it as a valid request to opt out of any sale or sharing of personal information associated with that browser. We do not sell or share personal information, so there is nothing for the signal to stop, but we recognise and honour it.
10. Server-side logs, which are not cookies
Separately from anything stored on your device, our hosting provider and our own application keep server-side records of requests: your IP address, user agent, the page requested, the referring URL, and timing and error information. These are not cookies, you cannot switch them off in your browser, and they are kept for 30 days for security and operations. Rate limiting on our public endpoints also records an IP address to stop abuse. See sections 3.1 and 8 of the Privacy Policy.
We also store an attribution record against an email address when you submit the assessment, containing the Meta browser identifiers, your IP address and your user agent. That is described in full in section 3.2 of the Privacy Policy and is not a cookie.
11. Changes, contact and complaints
11.1 Changes. We update this policy whenever we add, change or remove a technology, and at least every 12 months. The Effective Date and Version at the top show the current version.
11.2 Contact.
- Privacy and data protection: privacy@smoothvoice.ai
- General: hello@smoothvoice.ai
- By post: Sutherland Commerce Group LLC, 1309 Coffeen Avenue, Sheridan, WY 82801, USA
11.3 Complaints. Complain to us first at privacy@smoothvoice.ai. You may also complain to a supervisory authority: in the UK the Information Commissioner's Office (ico.org.uk, 0303 123 1113); in the EU your local data protection authority; in Australia the OAIC (oaic.gov.au).
Read alongside our Privacy Policy and Website Terms of Use.