Privacy ledger / 19 clauses

Your inquiry is kept 36 months, server logs 30 days, and ad cookies wait for your yes.

Effective 28 September 2026 Applies to salesforce.us.org Answers within 10 days

Clause 00 / Effective date

This policy took effect on 28 September 2026 and is the version in force today.

Salesframe is a small CRM implementation studio on Mission Street. We set up pipelines, migrate records and train sales reps. The site you are reading does four things with personal data: it takes inquiries, it runs a support chat, it records the paid-ad click that brought you here, and it keeps the server logs every web host keeps. The ledger below lists each clause once, says what it means without the legal wording, and says why it applies to this particular site. Where a table cannot carry the point, a paragraph follows it.

Who is responsible

Clause	In plain words	Why it applies
1.1Controller	The site is operated by Salesforce, trading at salesforce.us.org, under the studio name Salesframe. Postal address: 415 MISSION STREET, 3RD FLOOR, SAN FRANCISCO, CA 94105, United States.	Whoever decides why and how your data is used has to be identifiable by name and address. That is us.
1.2Reaching a person	Email [email protected] or call (415) 901-7000 during business hours, Pacific time.	A privacy question sent to an unmonitored address is not a route. This inbox is read by the same people who reply to project inquiries.

What the site records

Clause	In plain words	Why it applies
2.1Inquiry form	Name, phone, email, company or city (the `address` field), the kind of inquiry, your message, any estimator settings copied into the `spec` field, and whether you ticked the consent box.	Without a name and a way to reply we cannot answer a scoping request. The spec field saves a second round of questions about seat count and record volume.
2.2Captured with the form	Your IP address, the browser user-agent string, the referring URL, the moment the page rendered and the moment the form was sent.	Timing and origin are how we tell a person from a script filling forms. A form sent 0.8 seconds after rendering is not a person.
2.3Support chat	The messages you type, any name, phone or email you choose to add, and a conversation token stored in your browser so you can come back to the same thread.	The token is the only thing linking your browser to your conversation. Clear your browser storage and the link is gone.
2.4Consent choice and cookie identifiers	Your Allow or Decline choice, kept in the browser under `site_consent_v2`. If you allow storage, the ad and analytics cookies listed in the cookie policy.	We have to remember a refusal, or we would ask on every page. Nothing else on the site persists a choice.
2.5Ad click identifiers	When you arrive from a paid ad, the link carries a `gclid`, `msclkid` or `fbclid` parameter.	It tells the platform which ad produced the visit. Clause 06 covers what happens to it.

There is no account on this site, no password, no payment and no card data. Nothing is sold here. Estimates from the cost estimator are calculated in your browser and only reach us if you copy them into the form and send it.

What each record is used for

Clause	In plain words	Why it applies
3.1Replying and scoping	Form and chat data are used to answer you, book the 45-minute scoping call and write a quote if you ask for one.	That is the only reason the form exists. We do not add you to a newsletter and we do not sell or share lists.
3.2Keeping the site working	Logs and form timing are used to block spam, trace errors and keep the server secure.	A form left open to scripts fills up with junk, and the real inquiries get buried under it.
3.3Measuring paid ads	Click identifiers and, if you allow them, ad cookies tell Google, Microsoft and Meta whether an ad led to an inquiry.	We pay per click. Knowing which search terms produce real conversations is how we stop paying for the ones that do not.
3.4Site analytics	With your permission, aggregate page counts and paths.	It shows which pages people actually read, such as the process page or the estimator.

The legal basis for each use

Purpose	Legal basis	Why that basis
4.1Answering an inquiry or chat	Steps taken at your request before a contract, and consent given by the tick box.	You asked us to reply. The tick box records that you agreed to us storing the message.
4.2Delivering a signed engagement	Contract.	Once a quote is signed, contact data is needed to do the work.
4.3Logs, spam control, security	Legitimate interest.	Running a secure site is expected by any visitor, and the data is kept 30 days only.
4.4Ad measurement and analytics cookies	Consent.	Nothing in this category is stored until you press Allow, and it stops when you withdraw.

Advertising platforms that send traffic here

Platform	In plain words	Why it applies
5.1Google Ads	We run search ads on Google Ads for phrases such as "crm implementation consultant san francisco". A click adds `gclid` to the link.	Google Ads receives the consent signals described in clause 06 and, with consent, the conversion.
5.2Microsoft Advertising	We run ads on Microsoft Advertising, shown on Bing and partner sites. A click adds `msclkid` to the link.	Microsoft uses it to match a visit to an ad. Its handling is covered by its own statement, linked in clause 07.
5.3Meta Ads	Where a campaign runs on Facebook or Instagram through Meta Ads, a click adds `fbclid` to the link.	Meta uses it for the same attribution purpose, and only sets its cookies with your consent.

These platforms send us paid clicks today. Running ads with them does not mean any of them has reviewed or endorsed this site, and we do not say otherwise. The identifier in the link is visible to you in the address bar; you can delete it before the page loads if you prefer.

Consent Mode v2: four signals, denied by default

Signal	In plain words	Why it applies
6.1`ad_storage`	Whether ad cookies may be written. Denied until you press Allow.	No Google Ads, Microsoft or Meta ad cookie is set while it is denied.
6.2`ad_user_data`	Whether data about you may be sent to the ad platform for measurement. Denied until you allow.	Required by Google since Consent Mode v2 for any user data sent with a conversion.
6.3`ad_personalization`	Whether your visit may be used to show you tailored ads later. Denied until you allow.	Remarketing is off for anyone who has not agreed to it.
6.4`analytics_storage`	Whether analytics cookies may be written. Denied until you allow.	Page counts without consent are cookieless pings only.

Consent mode starts every visit with all four signals denied. Pressing Allow in the banner sets them to granted. Pressing Decline, or withdrawing later through the "Cookie settings" button in the footer, sets all four back to denied at that moment and the choice is saved under site_consent_v2. A browser sending the Global Privacy Control signal is treated as a Decline without the banner asking.

Who else receives data, named

Recipient	What they receive	Why it applies
7.1Google Ireland Ltd / Google LLC	Google Ads click data, `gclid`, consent signals and, with consent, conversions and analytics.	Advertising and measurement. See policies.google.com/privacy.
7.2Microsoft Ireland Operations Ltd	Microsoft Advertising click data and `msclkid`, with consent the UET cookies.	Covered by the Microsoft privacy statement at privacy.microsoft.com/privacystatement.
7.3Meta Platforms Ireland Ltd	Meta Ads click data and `fbclid`, where a campaign runs there.	Attribution of Facebook and Instagram ads.
7.4Hosting provider	Everything the site stores: the inquiry database, chat transcripts, server logs.	It serves the site and holds the data on our instructions only.
7.5Mail provider	The notification email copy of each inquiry sent to our inbox.	It carries the message from the form to the person who answers it.

Transfers across borders

Clause	In plain words	Why it applies
8.1Data leaving Europe	If you write to us from Europe, your data travels to the United States, where we work. The ad platforms may move it between their EU and US entities.	Those transfers rely on the EU Standard Contractual Clauses and, where a recipient is certified, the EU-US Data Privacy Framework.
8.2Data inside the US	Visitors in the United States: your data stays under US law with the providers named in clause 07.	No further transfer mechanism is needed, but the retention limits below still apply.

How long each record is kept

Record	Period	Why that long
9.1Inquiries and their email copies	36 months from the last message.	Teams come back a year or two later for a second pipeline or a data cleanup, and the original scope saves both sides time.
9.2Chat transcripts	18 months.	Long enough to follow a conversation into a project, then deleted.
9.3Server and access logs	30 days.	Enough to trace an attack or an error. Older logs have no use.
9.4Record of a consent choice	12 months, then the banner asks again.	A choice should not be assumed forever.

How the data is protected

Measure	In plain words	Why it applies
10.1Encryption in transit	Every page, form post and chat request travels over HTTPS.	Form contents are never sent in clear text.
10.2Restricted access	The inquiry store sits outside the public web root, behind a login used only by the people who answer inquiries.	Fewer people with access means fewer ways for a record to leak.
10.3Minimal collection	We ask for contact details, a company or city, and your message. No date of birth, no job title list, no budget dropdown.	Data we never take cannot be lost. The same rule applies to CRM forms we build: if nobody reads a field, it goes.

Rights under the GDPR, for visitors from Europe

Right	In plain words	Why it applies
11.1Access and portability	A copy of everything we hold on you, as a readable file (CSV or JSON) you can take elsewhere.	GDPR articles 15 and 20.
11.2Rectification and erasure	Correct a wrong detail, or have your inquiry and chat deleted.	Articles 16 and 17. We keep only what a law requires us to keep after erasure.
11.3Restriction and objection	Ask us to stop using your data while a dispute is settled, or object to use based on legitimate interest.	Articles 18 and 21.
11.4Withdrawing consent	Press "Cookie settings" in the footer and choose Decline, or write to us. Withdrawal is as easy as giving it.	Article 7(3). Past processing stays lawful; future processing stops.

Rights under US state law, California first

Right	In plain words	Why it applies
12.1Know, delete, correct	California residents can ask what we collected and have it corrected or deleted, under the CCPA as amended by the CPRA.	Residents of other states with privacy laws in force, Colorado, Connecticut and Virginia among them, get the equivalent rights.
12.2Opt out of sale or sharing	We do not sell personal data for money. Letting ad platforms use cookies for cross-context advertising can count as "sharing"; pressing Decline opts you out.	The CCPA treats ad sharing separately from sale, so we name it.
12.3No penalty	Using a right changes nothing about how we answer you or what we quote.	Non-discrimination is part of every state law listed.

Global Privacy Control is honoured

Clause	In plain words	Why it applies
13.1The `Sec-GPC` signal	If your browser or extension sends Global Privacy Control, we treat it as a Decline: all four consent signals stay denied and the banner does not ask again.	California regulations require a GPC signal to be honoured as a valid opt-out of sale and sharing.

Children

Clause	In plain words	Why it applies
14.1Not for under-16s	This site is for businesses buying CRM work. It is not aimed at children and we do not knowingly take data from anyone under 16.	If a child has written to us, a parent can ask and we delete the record within 10 days.

Where to complain

Clause	In plain words	Why it applies
15.1US regulators	You can complain to your state Attorney General. In California you can also go to the California Privacy Protection Agency.	Both enforce the state laws in clause 12.
15.2European authorities	Visitors from Europe can complain to the data protection authority where they live or work.	GDPR article 77. Writing to us first is usually faster, but it is not required.

Clause 16 / Data request route

Ask for your data, a correction or a deletion

Write to us with the email address or phone number you used in the form or chat, and say what you want: a copy, a correction, a deletion or an opt-out. We check that the request comes from the same address, then answer within 10 days. No form to fill, no fee.

Email: [email protected]
Post: 415 MISSION STREET, 3RD FLOOR, SAN FRANCISCO, CA 94105, United States
Phone: (415) 901-7000
Answer time: Within 10 days of receipt
Format: CSV or JSON by email, or a letter if you ask for one
Agent: An authorised agent may write on your behalf with signed permission

When this policy changes

Clause	In plain words	Why it applies
17.1Announcing a change	The effective date at the top of this page changes, and a note under this clause says what moved. If a change adds a new recipient or a new use, the cookie banner asks you again.	Consent given to one version does not stretch to a wider one.

Privacy contact

Clause	In plain words	Why it applies
18.1A human reads it	Email [email protected], phone (415) 901-7000, or post to 415 MISSION STREET, 3RD FLOOR, SAN FRANCISCO, CA 94105.	Same inbox as project inquiries, answered during business hours, Pacific time. Cookie detail sits in the cookie policy; engagement terms in the terms.

Questions about a CRM project rather than your data?

Book a scoping call See the six services