One key is stored before you choose. Every ad cookie waits for Allow.

Article 1 / Commencement

Effective dateThis notice takes effect on 28 September 2026 and replaces any earlier cookie statement on salesforce.us.org. It applies to every page of the site, the cost estimator and the support chat. The site is operated by Salesforce, trading at salesforce.us.org under the studio name Salesframe, 415 MISSION STREET, 3RD FLOOR, SAN FRANCISCO, CA 94105, United States.

A cookie is a small text file a site asks your browser to keep. Local storage does the same job without being sent back to the server on every request. We treat both the same way here: if it persists in your browser, it is listed.

Article 2 / Categories

Strictly necessaryTwo things only. The key site_consent_v2, which remembers whether you pressed Allow or Decline, and the chat token, which exists only if you open the support chat and send a message. Neither tracks you across sites. Neither can be switched off without breaking the thing it serves, and no consent is required for them.

AnalyticsCookies that count visits and pages, so we can see whether people read the process page before they write, or leave the estimator after the first slider. Set only when analytics_storage is granted. The figures we look at are aggregate. We do not look up individuals.

AdvertisingCookies written by Google Ads, Microsoft Advertising and Meta Ads to record that a paid click led to a visit and, sometimes, an inquiry. Set only when ad_storage is granted. They are the reason the banner exists at all.

There is no fourth category. We do not use social share widgets, embedded video, heatmap recorders or session replay tools, so none of their cookies appear here.

Article 3 / Schedule of cookies and keys

The scheduleEvery name below is set on salesforce.us.org or by a platform named in Article 4. Durations are the maximum; clearing your browser removes them sooner.

Schedule A is set out as a real <table>, not a paragraph: one row per cookie or storage key, with who sets it, what it is for and how long it lasts, so nothing is buried in running text.

Only the first two entries exist before you choose. The rest appear after Allow and disappear from new writes after Decline.

Article 4 / Advertising platforms

Paid trafficThis site receives paid clicks today from Google Ads, Microsoft Advertising and, where a campaign runs there, Meta Ads. Someone searches "crm setup for small sales team", sees our ad, clicks it. The platform adds a click identifier to the link before you land.

The identifiersGoogle adds gclid. Microsoft adds msclkid. Meta adds fbclid. Each is a random string that means something only to the platform that issued it. With consent, the platform's tag reads it and stores it in the cookies from Schedule A, so a later inquiry can be counted against the ad that produced it. Without consent, the parameter still sits in the address bar, but nothing is written to your browser and no conversion is stored against you.

We pay these platforms for clicks. That is the whole relationship. None of them has approved or endorsed this site.

Article 5 / Consent Mode v2

Default stateBefore the first line of any ad or analytics tag runs, Google Consent Mode v2 is set with four signals, all denied: ad_storage, ad_user_data, ad_personalization and analytics_storage. The Microsoft UET tag follows the same default through its own consent setting.

On AllowAll four switch to granted. Tags may then write cookies, send conversion data and build remarketing audiences.

On Decline or withdrawalAll four are set back to denied the moment you press the button, and stay denied on every later page. In denied state Google may still receive cookieless pings that carry no identifier we can tie to you; that is how consent mode is built, and we say so rather than pretend otherwise.

Article 6 / Giving and changing consent

Giving itA strip appears at the foot of the screen on your first visit. It does not cover the page and you can read and use the site without touching it. Press Allow to grant, Decline to refuse.

Changing itEvery page has a "Cookie settings" button in the footer legal row, beside Privacy and Terms. Pressing it reopens the strip with the same two buttons. The new choice replaces the old one in site_consent_v2 immediately. Clearing your browser storage for salesforce.us.org also resets it, and the strip asks again.

Global Privacy ControlIf your browser sends the Sec-GPC signal, we record a Decline without asking.

Article 7 / If you decline

What still worksEverything a visitor actually uses. The inquiry form posts. The estimator calculates every band live in your browser. The chat opens and a person replies during business hours. Pages load at the same speed.

What stopsNo analytics or advertising cookie is written. Google, Microsoft and Meta cannot link your visit to a conversion or add you to a remarketing list. We lose some measurement of which ads work, which is our problem, not yours.

Article 8 / Platforms' own documents

GoogleHow Google uses data from sites that run its tags: policies.google.com/technologies/partner-sites, and its privacy policy at policies.google.com/privacy.

MicrosoftThe Microsoft privacy statement, which covers Microsoft Advertising and msclkid: privacy.microsoft.com/privacystatement.

MetaMeta's cookie policy: facebook.com/privacy/policies/cookies.

Article 9 / Questions

Asking about a cookieIf a name in your browser is not in Schedule A, tell us which one and on which page. Write to [email protected], call (415) 901-7000, or post to 415 MISSION STREET, 3RD FLOOR, SAN FRANCISCO, CA 94105. We answer during business hours, Pacific time, and update the schedule if we missed one. Engagement conditions are in the terms.