Company Accountability Report

Sourced from public termsConsistent scoring frameworkEvery claim attributedManually verifiable

Accountability Report

Salesforce

Accountability resources

The primary source documents behind Salesforce's score — read the fine print yourself.

Locating official documents…

Links located automatically · verify against the company's live site

Verdict on

Salesforce

Salesforce markets itself as a trusted, enterprise-grade platform, but its public-facing promises commonly rely on customer-specific configurations and partner/third-party components, while its legal terms and data practices can materially affect costs, data handling, and exit options—so the accountability score is solid but not “fully transparent.”

Accountability Score

72/100

Mixed Signals

Checking Trustpilot…

Don't keep this to yourself

Receipts like this are rare — help Salesforce get credit for the score, and hold the next company to it.

One share puts real receipts in front of someone who's about to trust an ad. Pick a platform — the caption's already written.

Critical Deceptions & Caveats

-20

“Trust” marketing vs. complex data/usage terms

Salesforce’s public messaging emphasizes security and responsible handling, but the fine print allows broad operational uses (e.g., processing to provide services, analytics/telemetry, and partner/processor arrangements) and shifts key responsibilities to customers (configuration, permissions, and compliance). Practically, this can surprise customers about what data is used for and who touches it.

Source: Salesforce Privacy Statement (data processing/uses), Salesforce Trust/Compliance documentation and Data Processing/Controller-Processor framing (where applicable), and Salesforce Terms of Service/Customer Agreement (customer responsibilities and service scope)

Functional Limitation

-20

Service scope depends on configuration and add-ons

Salesforce marketing often presents capabilities as broadly available, but real functionality and outcomes depend on editions, add-ons, integrations, and admin configuration. That can turn “included” expectations into paid modules or implementation work.

Source: Salesforce product/edition pages and pricing/packaging disclosures (feature availability by edition), plus Salesforce Terms/Order Form structure (what is actually included is defined per order)

Functional Limitation

-15

Exit friction via contract structure and data portability limits

Salesforce’s enterprise contracts typically define renewal, termination, and data return/export in ways that can create practical friction (timing, fees, and what formats/retention are available). This can make switching harder than marketing implies.

Source: Salesforce Terms of Service / Customer Agreement and related order/termination and data handling/return provisions (contractual exit mechanics)

Friction Barrier

The Reality Matrix

Marketing Claim

Hidden Fine Print

Bottom Line

Claim

Enterprise-grade security and privacy you can rely on

Salesforce homepage/Trust & Compliance pages and security/privacy marketing materials

Fine Print

Security/privacy commitments are implemented through Salesforce’s controls and customer configuration, and data handling is governed by the Privacy Statement and contractual terms; some processing is permitted to operate the service and support analytics/telemetry, and third parties may be involved as subprocessors/partners.

Salesforce Privacy Statement; Trust/Compliance documentation; applicable Data Processing/Customer Agreement sections

Bottom Line

You may be relying on Salesforce’s controls, but your own setup (permissions, sharing, retention settings) and the specific contract/subprocessor list determine what actually happens to your data.

Claim

Your data stays yours

Salesforce privacy/security messaging and customer-facing trust statements

Fine Print

Salesforce processes customer data to provide and improve services and may use it for operational purposes; the exact rights and responsibilities are defined in the customer agreement and privacy terms, including how data is handled during service delivery and support.

Salesforce Privacy Statement and Customer Agreement/Order Form terms

Bottom Line

“Your data” is not the same as “no Salesforce processing.” Expect processing for service operation and support, and confirm what’s allowed for analytics/telemetry and improvement in the specific terms.

Claim

Capabilities are available out of the box

Salesforce product pages and capability marketing

Fine Print

Feature availability depends on edition, licensing, and configuration; integrations and advanced functions may require add-ons, partner products, or professional services.

Edition/packaging disclosures and pricing/ordering structure (what’s included per subscription/order)

Bottom Line

What you see in marketing may require paid modules or implementation work to achieve the same outcome—budget for licensing + admin/implementation.

Claim

Scales with your business

Salesforce “scale” and enterprise value messaging

Fine Print

Scaling is tied to contract terms, licensing metrics, and how usage is measured; changes may require new orders, amendments, or additional fees.

Pricing/Order Form terms and subscription metric definitions in the customer agreement

Bottom Line

Your costs can rise with usage and seat/feature metrics even if the marketing implies smooth scaling.

Claim

Easy compliance and governance

Salesforce compliance/governance marketing

Fine Print

Compliance support is shared responsibility: Salesforce provides tools and documentation, but customers must configure governance, access controls, retention, and ensure lawful use for their specific data and workflows.

Trust/Compliance documentation plus customer responsibility clauses in the agreement

Bottom Line

Don’t assume Salesforce alone makes you compliant—your admin settings and policies are part of the compliance outcome.

Claim

Switching away is straightforward

General enterprise value/lock-in-neutral messaging (implied by platform positioning)

Fine Print

Termination/renewal mechanics and data export/return provisions are contract-defined; there may be timing constraints, fees, and limitations on formats/retention windows.

Salesforce Customer Agreement/Terms sections on term, termination, and data handling/return/export

Bottom Line

Exit can be operationally and financially non-trivial—plan migration and data export during contract negotiations.

Claim

Third-party ecosystem works seamlessly

Salesforce AppExchange/partner ecosystem marketing

Fine Print

Partner apps and integrations can involve additional terms, data flows, and subprocessors; Salesforce’s responsibility may be limited to what it controls directly.

Salesforce terms regarding third-party services and partner/subprocessor arrangements

Bottom Line

Your risk and compliance burden can expand when you add integrations—review partner terms and data-sharing paths.

Actions NeededExplicit next steps for consumers and marketers

How Salesforce Could ImproveConcrete fixes that would raise this score

Capability-to-SKU transparency
12
For each major marketing promise, add a prominent “requires edition/add-on/integration” disclosure and link directly to the exact licensing prerequisites in the pricing/packaging pages.
Plain-language data use summary
10
Add a short, customer-friendly section summarizing what Salesforce does with customer data beyond providing the service (e.g., operational analytics/telemetry), including who may receive it (subprocessors/partners) and how customers can limit it.
Exit and portability clarity
6
Publish a clearer, non-contractual overview of termination/data export expectations (timelines, formats, retention windows) and highlight what is negotiable in enterprise agreements.
Shared responsibility checklist
5
Provide a concise checklist of customer configuration steps required for security/compliance outcomes (permissions, sharing rules, retention settings) and link it from trust/security marketing pages.

Better AlternativesMore accountable companies in the same category

HubSpot

78est. /100

Often provides clearer packaging tiers for CRM/marketing features and has a strong emphasis on inbound marketing tooling; while still contract-based, many customers find the feature-to-tier mapping more straightforward than large enterprise suites.

Microsoft Dynamics 365

76est. /100

Enterprise CRM with strong governance tooling and integration into Microsoft’s compliance ecosystem; contracts and data handling are still complex, but the ecosystem can make governance and identity/access management more transparent for many orgs.

Zoho CRM

74est. /100

Typically offers more transparent tiering for many CRM features and a broad suite at lower cost; data processing and exit terms still require review, but the packaging is often easier to audit.

How This Score Was CalculatedScoring methodology & sources analyzed

Scoring methodology

Every company starts at a perfect 100. We read the marketing claims, then hunt for the fine print that contradicts them. Each gap we find deducts points based on how badly it harms you. The score never drops below 0.

Outright Contradiction−30
A claim that is flatly untrue (e.g. "Free" that requires a fee).
Functional Limitation−20
A promise quietly capped or throttled (e.g. "Unlimited" data slowed after 15GB).
Friction Barrier−15
A right made deliberately hard to use (e.g. "Cancel anytime" by mailed letter only).

Sources analyzed

Salesforce Privacy Statement
Privacy Policy
Reviewed for how Salesforce describes collection, processing, operational uses, analytics/telemetry, and sharing/subprocessor arrangements—key to understanding the real-world impact on customer data.
Salesforce Terms of Service / Customer Agreement (and related order/contract structure)
Terms of Service
Reviewed for service scope definition, customer responsibilities, termination/renewal mechanics, and data handling/return/export concepts that affect practical exit and cost outcomes.
Salesforce pricing/edition and packaging disclosures (SKU/feature availability)
Pricing / Fine Print
Reviewed for how marketing capabilities map to editions, add-ons, and licensing metrics—used to identify functional limitations between claims and what’s actually included.
Salesforce Trust/Compliance documentation and security/privacy marketing pages
Other Source
Reviewed for the public-facing security/compliance promises and how they frame shared responsibility and operational controls.
Salesforce AppExchange/partner ecosystem materials
Other Source
Reviewed for how third-party integrations are positioned and how responsibility/data flows can shift when partners/subprocessors are involved.

Findings are AI-generated from publicly reported patterns and the documents above. Each claim and fine-print entry is attributed to its source inline. Always verify current terms directly with the company.

Feedback & Email This ReportFlag a scoring gap, or send yourself the full report

Send Jay a correction or question →Share this report by email →

Opens your email app. Nothing is sent until you send it.

AI & Accuracy Disclaimer

These findings are AI-generated from publicly reported patterns and the documents listed above. They are not legal advice and may contain errors, omissions, or out-of-date information. Every claim and score must be manually validated against the company's current, official terms of service, privacy policy, and pricing before you rely on it. TrustGap is a starting point for scrutiny — not a final verdict.

Generated assessment based on publicly reported patterns and AI analysis. Not legal advice — verify current terms directly with the company before acting.

Get teardowns several times a week

Continue the conversation.

Live community discussions remain on TrustGap. You can also send a source, correction or question directly to MAC.

Open live discussions Send a correction or question

Score history

+8 pts since first analysis

Oct 25, 202672/100
- Accountability score rose 8 points (64 → 72).
- Resolved: "Where the marketing meets the fine print" no longer flagged.
- New concern: "“Trust” marketing vs. complex data/usage terms".
- New concern: "Service scope depends on configuration and add-ons".
- New concern: "Exit friction via contract structure and data portability limits".
Jul 21, 202664/100
Baseline analysis recorded.

See all score trends Browse reports