PII & Data Handling
This document describes the personal data (PII) processed by the RevSure MCP integration, where it comes from, and the controls RevSure provides to classify and mask it.
Overview
The RevSure MCP integration exposes a tenant’s go-to-market (GTM) marketing and sales attribution data through MCP tools. The data model consists of ~1,200+ dimensions (fields). The large majority are non-personal business and analytics data — funnel-stage metrics, pipeline and opportunity values, campaign spend and performance, attribution scores, and aggregate journey data.
A subset are personal data relating to identifiable people. This document covers what that subset is and how it is handled.
Data source & ownership
All data exposed by the integration originates from the customer’s own connected source systems — CRM, marketing automation platforms (MAP), enrichment vendors, and web tracking. RevSure does not introduce third-party personal data of its own. The data remains the customer’s data; RevSure processes it to produce attribution analytics.
Personal data (PII) categories
The personal data processed is limited to business/professional contact information used for B2B marketing attribution:
Category | Examples |
|---|---|
Contact name | First/last/full name of contacts, leads, visitors, and internal users |
Business email | Contact, visitor, and internal-user email addresses |
Phone | Contact phone number |
Mailing / geographic location | City, state, country, postal/zip, street address, latitude/longitude |
Social / public profile | LinkedIn/Facebook/Twitter/GitHub profile URLs, profile photo URL |
Online & advertising identifiers | Web-visitor IP address, ad click IDs (LinkedIn/Facebook), visitor-to-lead linking IDs |
Web-activity / browsing behavior | Pages/URLs visited and referring URLs, when associated with an identified lead or contact |
Demographic | Salutation, gender, age, date of birth (where provided by source systems) |
Sensitive / special-category data
No special-category data under GDPR Art. 9 (health, biometrics, race/ethnicity, religion, sexual orientation, etc.), and no government IDs or financial-account numbers, are intended to be processed.
A few fields warrant awareness:
Gender, date of birth, age — demographic attributes; not GDPR special-category on their own but often treated as sensitive.
Activity subject / description — free-text fields; content is customer-controlled and could in principle contain incidental sensitive text.
IP address and precise latitude/longitude — treated as personal data under GDPR/CCPA.
These are populated only from the customer’s connected sources and remain under the customer’s control.
PII classification & masking
RevSure identifies which fields contain personal data and can automatically redact them in tool output when your tenant enables the privacy control.
How PII fields are identified
A field is treated as personal data when it is explicitly classified as PII in RevSure’s data catalog.
Masking behavior
Masking is a tenant-configurable privacy control, set in Config Center → Reli Config → Privacy.
It activates when you turn off Show Contact Name and/or Include Email Address.
When active, matching personal values in tool output are redacted to
***. Crucially, this happens inside the RevSure MCP server, before results are returned to the AI assistant — so the AI model never receives the raw values.Tool responses include a note indicating that masking is in effect, so masked values are not inferred or guessed.
Scope of masking
Masking is a data-minimization control focused on directly-identifying contact details (names and email addresses) plus any field explicitly classified as PII. Fields that are personal data but not covered by the masking control (for example, geographic location, social-profile URLs, or web-activity data) are processed and displayed; access to them is governed by the customer’s authentication, role-based access control (RBAC), and tenant isolation.
Custom dimensions
The categories above reflect RevSure’s standard supported dimensions. Tenants can define their own custom dimensions on top of the standard set, mapped from their source systems. Any data types — and any PII — introduced by custom dimensions are determined by what the tenant chooses to bring in, and fall under the tenant’s own data classification and governance.
Field inventory
The complete list of PII-classified dimensions (name + description) is below. This covers RevSure’s standard dimensions classified as personal data. Custom dimensions are not included and should be classified by the tenant.
Field | Description |
|---|---|
Account Email | The email ID associated with an account |
Account ENR 6 Sense Resolved IP Address | IP address associated with account related to the web traffic |
Account ENR POSTAL CODE | Account data enriched with postal code |
Account First Contact Activity Contact Name | The name of the contact for the first contact activity associated with a lead |
Account First Contact Activity Description | Description of the first contact activity of the account |
Account First Gtm Activity Contact Name | Name of the contact who performed the first GTM activity associated with the account |
Account IPs | IPs associated with an account |
Account Last Contact Activity Contact Name | Name of the latest contact activity associated with the account |
Account Last Contact Activity Description | Description of the latest contact activity associated with the account |
Account Last Gtm Activity Contact Name | Name of the contact who performed the last GTM activity associated with the account |
Account Last Gtm Activity Owner Name | Name of the owner of the last GTM activity associated with the account |
Account Owner Email | Email of the account owner |
Account Owner Name | Name of the person who is marked as the owner of the account |
Account Owner Username | Username of the account owner |
Account Zip | The zip code of the address for the account |
Activity Description | Description of the activity |
Activity Subject | Subject of the activity |
Campaign Owner Email | Email ID of the owner of a campaign |
Campaign Owner Name | Name of the owner of the campaign |
Campaign Owner Username | Username for the owner of the campaign |
Contact Email | Email address of the contact |
Contact Name | Name of the contact |
Country | Country associated with the person |
Email ID of the person | |
Internal User Name | Name of the person owning the lead/ opportunity/ account record |
Internal_user Email | Email ID of the internal user |
Internal_user First Name | First name of the internal user |
Internal_user Id | Unique ID of the internal user |
Internal_user Last Name | Last name of the internal user |
Internal_user Manager Id | ID of the manager of the internal user |
Internal_user Parent Role | Parent role of the internal user in the organization |
Internal_user Role | Role of the internal user in the organization |
Internal_user Teams | Teams associated with the internal user |
Internal_user Title | Title of the internal user |
Internal_user User Name | User name of the internal user |
Invitee Emails | Email addresses of meeting invitees |
Invitee Names | Names of meeting invitees |
Lead First Contact Activity Contact Name | Contact name for the first contact activity associated with the lead |
Lead First Contact Activity Description | Description for the first contact activity associated with a lead |
Lead First Gtm Activity Contact Name | Contact name who performed the latest GTM activity associated with a lead |
Lead Last Contact Activity Contact Name | Name of the contact for the latest contact activity associated with the lead |
Lead Last Contact Activity Description | Description for the last contact activity associated with a lead |
Lead Last Gtm Activity Contact Name | Contact name who performed the latest GTM activity associated with a lead |
Lead Last Gtm Activity Owner Name | Name of the owner who performed the latest GTM activity associated with a lead |
Lead Name | Name of the lead |
Opportunity Owner Name | Name of the user who owns the opportunity |
Opportunity Owner Role | Role of the user who owns the opportunity |
Person Address 1 | Line 1 of the address of the person |
Person Address 2 | Line 2 of the address of the person |
Person Age | Age of the person |
Person City | City (address) of the person |
Person Country Code - 2 Letter | 2-letter country code based on the address of the person |
Person Country Code - 3 Letter | 3-letter country code based on the address of the person |
Person Date Of Birth | Date of birth of the person |
Person Email List | All professional/business email addresses associated with this contact/person in the system |
Person ENR 6Sense City | 6sense enriched data for the city of the person |
Person ENR 6Sense Country | 6sense enriched data for the country of the person |
Person ENR 6Sense Email | 6sense enriched data for the email ID of the person |
Person ENR 6Sense Email Confidence | 6sense enriched data for the confidence score of the email ID for a person |
Person ENR 6Sense Facebook Url | 6sense enriched data for the Facebook profile URL of the person |
Person ENR 6Sense First Name | 6sense enriched data for the first name of the person |
Person ENR 6Sense Full Name | 6sense enriched data for the full name of the person |
Person ENR 6Sense Last Name | 6sense enriched data for the last name of the person |
Person ENR 6Sense Linkedin Url | 6sense enriched data for the LinkedIn profile URL of the person |
Person ENR 6Sense Phone | 6sense enriched data for the phone number of the person |
Person ENR 6Sense Postal Code | 6sense enriched data for the postal code (address) of the person |
Person ENR 6Sense State | 6sense enriched data for the state (address) of the person |
Person ENR 6Sense Twitter Url | 6sense enriched data for the URL of the Twitter profile of the person |
Person ENR CITY | Enriched data with the city (address) of the person |
Person ENR COUNTRY | Enriched data for the country of the person |
Person ENR EMAIL | Enriched data for the email ID of the person |
Person ENR FACEBOOK URL | Enriched data with the Facebook URL of the person |
Person ENR FIRST NAME | Enriched data for the first name of the person |
Person ENR GITHUB URL | Enriched data with the GitHub URL of the person |
Person ENR LAST NAME | Enriched data for the last name of the person |
Person ENR LINKEDIN URL | Enriched data for the LinkedIn profile URL of the person |
Person ENR NAME | Enriched data for the name of the person |
Person ENR PHONE NUMBER | Enriched data for the phone number of the person |
Person ENR PHOTO URL | Enriched data with the URL to a photo of the person |
Person ENR STATE | Enriched data for the state (address) of the person |
Person ENR TWITTER URL | Enriched data with the Twitter URL of the person |
Person First Name | First name of the person |
Person Gender | Gender of the person |
Person Last Name | Last name for the person |
Person Latitude | Latitude of the location associated with the person |
Person LinkedIn Profile Pic URL | URL of the person’s LinkedIn profile picture |
Person LinkedIn URL | LinkedIn profile URL for the person |
Person Longitude | Longitude of the location associated with the person |
Person Name | Name of the person |
Person Phone | Phone number associated with the person |
Person Region | Region (address) for the person |
Person Salutation | Salutation used with the name of the person |
Person State | State (address) of the person |
Person Zip | Zip code (address) for the person |
Primary Contact Email | Email of the primary contact |
Primary Contact Name | Name of the primary contact |
Visitor City | City the visitor is at the time of the visit |
Visitor Country | Country the visitor is at the time of the visit |
Visitor Email | Email ID of the visitor |
Visitor Email List | List of email addresses associated with the visitor |
Visitor First Name | First name of the visitor |
Visitor Last Name | Last name of the visitor |
Visitor Name | Name of the website visitor |
Visitor State | State the visitor is at the time of the visit |
Visitor User Name | User name for the visitor |