Revenue privacy policy

Data we access

Google sign-in provides the identity information needed to authenticate your Revenue account, such as your Google account identifier, email address, and profile information. Reporting access is requested separately and only covers the Google permissions you approve.

For configured reporting sources, Revenue accesses Google Ads account and campaign identifiers and performance metrics; aggregated Google Analytics website, acquisition, campaign, and event reports; and Search Console site identifiers, search queries, landing pages, and search performance metrics. Revenue stores authorization credentials to maintain connections you have approved.

How we use Google data

Revenue uses Google identity data for sign-in and account access. It uses reporting data to display marketing results and support analysis, planning, and prioritization within the connected Revenue workspace. Imports run when an authorized user starts a synchronization or enables a schedule.

The reporting integrations read data without creating or changing Google Ads campaigns, bids, budgets, or advertisements. Google's Ads authorization permission also permits account management; Revenue uses that permission for its reporting functionality.

Revenue does not sell Google user data or use it to serve personalized advertisements.

Predictive models and Google reporting data

Revenue provides predictive features based on CRM data and business outcomes. Data received through Google's reporting integrations is used for reporting and analysis, not for training machine learning models.

Storage and access

Imported reporting records are stored in Revenue's production database and associated with the connected workspace. Authorized workspace users can view its reports according to their application access. OAuth credentials are stored encrypted by Revenue, and connections use HTTPS.

Hosting and infrastructure providers, including DigitalOcean, process information as needed to operate and maintain Revenue. Application administrators may access information when necessary to operate the service, investigate an issue, or respond to a user request. Information may also be disclosed when required by law.

Retention, revocation, and deletion

Revenue retains imported reports so the workspace can review historical performance. Revoking a connection prevents further authorized access to Google but does not automatically delete records already imported into Revenue.

You can revoke Revenue's Google access from your Google Account connections. To request deletion of stored Google data or connection credentials, contact [email protected] and identify the Revenue workspace and connected account or property. Do not send passwords or access tokens by email.

Google API Services User Data Policy

Revenue's use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.

Contact and changes

For privacy questions and requests, contact Haim Barabi at [email protected]. Changes to this notice will be published on this page.