AI Relationship Map security and data privacy
In this article
In this article group
This article is for admins, security reviewers, and anyone who needs to know what happens to CRM data when someone clicks Generate with AI. When you finish, you should know what is anonymized in Salesforce, what the AI service never receives, and how the request and callback are authenticated.
To turn the feature on, use Configure AI map generation. You do not need Crush or an Account Plan to generate a map.
Key principle: Personal names, email addresses, and other personally identifiable information (PII) are never sent to the AI service. All personal data is anonymized inside Salesforce before any external communication takes place.
How generation works
When a user clicks Generate with AI:
- Data collection — Salesforce gathers relevant CRM signals for the account (contacts, roles, recent activities, and team members).
- Anonymization — Personal identifiers (names and emails) are replaced with anonymous tokens before the data leaves Salesforce.
- Secure submission — The anonymized data is sent to the AI service over an authenticated, encrypted connection. The callout uses a Named Credential you create in the org. Each customer uses their own API key.
- AI processing — The AI service analyzes the anonymized data and produces a suggested Relationship Map structure.
- Secure callback — The AI service sends the result back to Salesforce through an authenticated endpoint.
- De-anonymization — Salesforce restores the real names using the token map (which never left Salesforce) and creates the draft Relationship Map.
- User review — The user reviews and edits the generated map. A generated map is a start, not a finished committee.
What the AI service receives (anonymized)
| Data type | What is sent | Example |
|---|---|---|
| Contact identity | An anonymous token | Contact-1 instead of Jane Smith |
| Job title | The contact’s job title (not a personal identifier) | VP of Sales |
| Department | The contact’s department | Sales |
| Email domain only | Only the company domain — never the full email address | acme.com instead of jane.smith@acme.com |
| Opportunity roles | The role a contact plays in a deal, referenced by token | Contact-3 is Decision Maker |
| Activity summary | Activity type and date only — no subjects, descriptions, or notes | Task — Email — 2026-08-15 |
| Account Team | Anonymous tokens for team members with their team role | User-1 is Account Manager |
| Org configuration | Your organization’s influence, support, and relationship type labels | Champion, Mentor, Blocker |
What the AI service never receives
| Data type | Protection |
|---|---|
| People’s names | Replaced with anonymous tokens (Contact-1, User-1, Account-1) |
| Email addresses | Only the domain is extracted (for example acme.com). The local part (the person’s name or alias before the @) is never sent |
| Activity details | Subjects, descriptions, notes, and comment bodies are excluded — only the activity type (for example Email or Call) and date are sent |
| Attachment content | No files or documents are sent |
| Financial data | Opportunity amounts, forecasts, and revenue data are not included |
| Free-text notes | Account Plan notes, SWOT analysis content, and similar text fields are not sent |
How anonymization works
Before anonymization (inside Salesforce)
- Contact: Jane Smith, VP of Sales, jane.smith@acme.com
- Contact: John Doe, CTO, john.doe@acme.com
- Account: Acme Corporation
After anonymization (what the AI service sees)
- Contact-1, VP of Sales, acme.com
- Contact-2, CTO, acme.com
- Account-1
The mapping between tokens and real identities is stored in a Salesforce record in your org and never leaves the org. When the AI result comes back, Salesforce uses that mapping to restore real names on the generated Relationship Map.
Authentication and secure communication
All communication between Salesforce and the AI service uses more than one security layer.
Outbound request (Salesforce → AI service)
- Named Credentials — Salesforce’s Named Credential framework authenticates the outbound request. The API key is stored by the Salesforce platform and is never exposed in code or configuration files. The package cannot ship the credential; you create it after install.
- HTTPS encryption — Data is transmitted over HTTPS (TLS), so data in transit cannot be read if intercepted.
- No hardcoded secrets — Authentication credentials are managed by Salesforce’s credential management infrastructure.
Inbound callback (AI service → Salesforce)
- OAuth 2.0 JWT Bearer — The AI service authenticates back to Salesforce with the OAuth 2.0 JWT Bearer flow. That uses digital certificate-based authentication (a public/private key pair), not a password.
- Dedicated integration user — The callback runs as a dedicated Salesforce user with the minimum permissions required.
- Anti-replay protection — Each request includes a unique, cryptographically generated correlation ID. The callback is accepted only if that ID matches a pending request in Salesforce and the request has not already been processed. Once a request moves past Submitted status, no further callbacks are accepted for it.
Security layers
| Layer | Protection |
|---|---|
| HTTPS / TLS | Encrypts all data in transit |
| Named Credential (outbound) | Stores the API key in Salesforce’s managed credential store |
| OAuth 2.0 JWT Bearer (inbound) | Certificate-based authentication for the callback |
| Correlation ID | Ensures the callback matches a legitimate request |
| Anti-replay check | Prevents the same callback from being processed more than once |
| Dedicated integration user | Limits the callback’s Salesforce access to only what is necessary |
How to create the credentials, permission set, and callback user is in Configure AI map generation.
Access controls
The feature is available only when every control below is satisfied. If any one is not, Generate with AI is not visible.
| Control | Description |
|---|---|
| Package-level feature flag | AI must be enabled for your organization at the package license level (AI Access). Contact Prolifiq to enable it. |
| Organization-level toggle | An administrator must enable Enable AI Map Generation. The feature is off by default. |
| User license | Only users with the appropriate Crush or Relationship Map license can generate. |
| Permission sets | Salesforce permission sets control access to AI-related classes, objects, and credentials. People who generate, and the integration user, also need the unmanaged CRUSH_AI_Credential_Access set you create in the org. |
Data residency and retention
- The token map stays in Salesforce. The mapping between anonymous tokens and real identities is stored in a Salesforce record in your org. It is never transmitted to any external system.
- Audit trail. Each AI generation request is logged in Salesforce with the anonymized request payload and the raw result, so administrators can audit what was sent and received.
- Your Salesforce data governance applies. Requests, results, and draft maps are stored as Salesforce records, subject to your organization’s data retention policies, sharing rules, and access controls.
Frequently asked questions
Are my contacts’ names shared with the AI?
No. All names (contacts, account team members, and the account name) are replaced with anonymous tokens such as Contact-1 or User-1 before any data leaves Salesforce.
Are email addresses shared with the AI?
No. Only the domain portion is sent (for example acme.com). The part before the @ is never included.
Are email subjects or meeting notes shared?
No. Only the activity type (for example Email, Call, or Meeting) and the date are sent. Subjects, descriptions, notes, and attached content are excluded.
Can someone intercept the data being sent to the AI?
Communication is encrypted with HTTPS/TLS. Authentication also ensures that only authorized systems can send or receive data.
Can the AI remember or store my data?
The AI service processes the anonymized data to generate a result and returns it. The anonymized tokens have no meaning outside the Salesforce request that created them. The token-to-name mapping exists only in your Salesforce org.
How do I enable or disable the feature?
An administrator can enable or disable Enable AI Map Generation at any time. When it is disabled, Generate with AI is hidden from all users. Credential setup is in Configure AI map generation.
Does this require an additional entitlement?
Yes. The feature requires the AI Access entitlement for your organization, plus the appropriate Crush or Relationship Map user license. Contact Prolifiq to enable AI Access and to complete administrator settings and user permission assignment.
Is there a limit on the number of AI Relationship Maps?
To start, there is no limit on how many maps customers can generate. Prolifiq monitors usage and may limit customers case by case.
The public security statement is also on prolifiq.com.