AI Relationship Map — Security & Data Privacy Overview
The AI Relationship Map feature in PROLIFIQ CRUSH allows users to generate draft Relationship Maps from Account Plan data using artificial intelligence. This document explains how the feature works, how your data is protected throughout the process, and what information is — and is not — shared with the AI service.
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 It Works — The High-Level Flow
When a user clicks Generate with AI on an Account Plan, the following steps occur:
- Data collection — Salesforce gathers relevant CRM signals from the Account Plan (contacts, roles, recent activities, and team members).
- Anonymization — All 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.
- 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 directly in the Account Plan.
Data Anonymization — What Is Sent and What Is Not
What the AI Service Receives (anonymized)
| Data Type | What Is Sent | Example |
|---|---|---|
| Contact identity | An anonymous token (e.g., Contact-1, Contact-2) | 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 (e.g., acme.com); the local part (the person's name/alias before the @) is never sent |
| Activity details | Subjects, descriptions, notes, and comment bodies are excluded — only the activity type (e.g., "Email", "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 — A Concrete Example
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 securely in a Salesforce record and never leaves your org. When the AI result comes back, Salesforce uses this mapping to restore real names into the generated Relationship Map.
Authentication & Secure Communication
All communication between Salesforce and the AI service is protected by multiple layers of security.
Outbound Request (Salesforce → AI Service)
- Named Credentials — Salesforce's built-in Named Credential framework is used to authenticate the outbound request. The API key is stored securely by the Salesforce platform and is never exposed in code or configuration files.
- HTTPS encryption — All data is transmitted over HTTPS (TLS-encrypted connections), ensuring that data in transit cannot be intercepted or read.
- No hardcoded secrets — Authentication credentials are managed entirely by Salesforce's credential management infrastructure.
Inbound Callback (AI Service → Salesforce)
- OAuth 2.0 JWT Bearer — The AI service authenticates back to Salesforce using the industry-standard OAuth 2.0 JWT Bearer flow. This uses digital certificate-based authentication (public/private key pair), which is more secure than password-based methods.
- Dedicated integration user — The callback operates under a dedicated Salesforce user with the minimum permissions required, following the principle of least privilege.
- Anti-replay protection — Each request includes a unique, cryptographically generated correlation ID. The callback is only accepted if the correlation ID matches a pending request in the Salesforce database, and the request has not already been processed (preventing replay attacks — once a request moves past "Submitted" status, no further callbacks are accepted for it).
Summary of Security Layers
| Layer | Protection |
|---|---|
| HTTPS / TLS | Encrypts all data in transit |
| Named Credential (outbound) | Secures the API key using 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 |
Access Controls
The AI Relationship Map feature includes multiple levels of access control to ensure it is only available to authorized users and organizations.
| Control | Description |
|---|---|
| Package-level feature flag | The AI feature must be explicitly enabled for your organization at the package license level (AI Access). |
| Organization-level toggle | A CRUSH administrator must enable the "Enable AI Map Generation" setting in the CRUSH Settings page. The feature is off by default. |
| User license verification | Only users with the appropriate CRUSH license assignment can access the AI generation functionality. |
| Permission sets | Salesforce Permission Sets control which users and integration accounts have access to the AI-related classes, objects, and credentials. |
If any of these controls is not satisfied, the Generate with AI button is not visible to the user.
Data Residency & Retention
- The token map stays in Salesforce. The mapping between anonymous tokens and real identities is stored in a Salesforce record within 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, allowing administrators to audit what was sent and received.
- Your Salesforce data governance applies. All data involved in the AI generation (requests, results, and draft maps) is stored as standard Salesforce records, subject to your organization's existing data retention policies, sharing rules, and access controls.
Frequently Asked Questions
Q: Are my contacts' names shared with the AI?
No. All names (contacts, account team members, and the account name) are replaced with anonymous tokens like Contact-1 or User-1 before any data leaves Salesforce.
Q: Are email addresses shared with the AI?
No. Only the domain portion of email addresses is sent (e.g., acme.com). The personal part of the email (the part before the @) is never included.
Q: What about activity data — are email subjects or meeting notes shared?
No. Only the activity type (e.g., Email, Call, Meeting) and the date are sent. Subjects, descriptions, notes, and any attached content are excluded.
Q: Can someone intercept the data being sent to the AI?
All communication is encrypted using HTTPS/TLS, the same standard used by banks and financial institutions. Additionally, authentication tokens ensure that only authorized systems can send or receive data.
Q: 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 of the specific Salesforce request that generated them. The token-to-name mapping exists only in your Salesforce org.
Q: How do I enable or disable the feature?
A CRUSH administrator can enable or disable AI Map Generation at any time from the CRUSH Settings page. When disabled, the "Generate with AI" button is hidden from all users.
Q: Does this feature require any additional licenses?
Yes. The AI feature requires the AI Access entitlement to be enabled for your organization, along with the appropriate CRUSH user license assignment.
