FAQ
What is Revenue Proven's GDPR and data privacy posture?
Revenue Proven processes only the data needed to deliver attribution insights, does not sell customer data, and provides deletion mechanisms to support your GDPR obligations.
Revenue Proven is a data processor operating on the data you share through your integrations. It pulls LinkedIn Ads engagement data and CRM records on your behalf, processes them to produce attribution insights, and stores the results in your workspace. Revenue Proven does not sell, rent, or share your data with third parties for advertising or any commercial purpose.
What data Revenue Proven processes
- LinkedIn organization IDs and engagement metrics from your ad account
- Company and deal records from your connected HubSpot or Salesforce
- Matched attribution associations between LinkedIn companies and CRM records
- IP subnet ranges from website visitors (AI Discovery pixel), not full IPs
- User account details such as email and hashed password
Your rights and controls
You can disconnect any integration at any time, which stops new data from being pulled. You can export your attribution data as CSV. You can delete your account and all associated data from account settings, which triggers a full cascading delete of all data tied to your workspace. Revenue Proven's Data Processing Agreement (DPA) is available on the legal pages for customers who require a signed DPA for compliance purposes.
Current help workflow
This answer was refreshed against the current Revenue Proven product and its exact /dashboard/settings route. It is written for the Shawn Brown demo workspace, whose pages contain real connected-system data in some areas and seeded examples in others.

Use this screenshot as the route-specific visual reference for “What is Revenue Proven's GDPR and data privacy posture?”. Labels, plan gates, roles, asynchronous loading, permissions, and available controls can vary with the signed-in workspace.
When troubleshooting, first confirm the active workspace, selected account, connections, date range and entitlement. Treat Save, Send, Sync, Publish, Resume, Reconnect and Delete controls as state-changing actions, and consult the current route before relying on older screenshots or navigation instructions.

