Privacy Policy

Last Updated: November 10, 2026

1. Introduction

Enhanced Conversions ("we," "our," or "us") is a server-side conversion service. It connects an advertiser's CRM (RD Station) to Google Ads and Meta Ads and sends them the conversion events the advertiser chooses. This Privacy Policy explains what data we access, why, how long we keep it, who we share it with, and how to delete it — including data obtained through Google APIs.

2. Google API Services & Limited Use

Our use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements. We do not use Google user data for serving advertising, building user profiles, or training machine-learning or AI models, and we do not allow humans to read this data except as required for security, to comply with law, or with your explicit consent.

3. Data We Access

When you connect Google Ads, you sign in with Google and grant access to Google Ads (https://www.googleapis.com/auth/adwords) and to your Google account email. We store:

  • The OAuth tokens Google issues, so our server can upload conversions on your behalf;
  • The Google Ads account / customer ID you choose;
  • Your Google account email, only to fill the dashboard contact email when it is empty.

When you connect Meta Ads, you sign in with Facebook Login for Business. We store:

  • The access token Meta issues;
  • The name and ID of your ad account and the names and IDs of its pixels (datasets);
  • The pixel and the events you choose.

We do not access your email contents, contacts, or advertising performance reports. Separately, we receive conversion event data from your CRM via webhooks. It may include email addresses, phone numbers, names, values, and click identifiers such as gclid, plus Meta click identifiers (fbc and fbp).

4. How We Use Data

We use the Google authorization only to upload the conversion events you choose — such as leads marked as opportunities in your CRM, with their value — to your own Google Ads account, using the Google Ads API (uploadClickConversions).

We use the Meta authorization only to send the events you choose to your own pixel, using the Meta Conversions API. Each event contains the hashed email and phone number, Meta click identifiers (fbc and fbp) when available, the event name, the event time, the value and currency when present, and a technical event ID.

Email addresses and phone numbers are normalized and hashed with SHA-256 before they are sent to Google or Meta; plain email and phone never reach them. We also store the contact data that the RD Station webhook sends, encrypted, to run and improve the lead filtering of the service.

If you choose to give us a contact email in the dashboard, we use it only to send you important notices about your account and integration. You can remove it at any time.

5. How We Share Data

We do not sell your data, and we do not share Google user data with third parties for their own purposes. We use a small set of service providers (sub-processors) only to run the service:

  • Hetzner Online GmbH — servers for the application and the database (Germany).
  • Cloudflare — DNS, proxy, and the scheduled delivery trigger.
  • Stripe — payments.
  • Resend — notice emails to your contact email.

Hashed conversion data is sent to the Google Ads API and to the Meta Conversions API at your direction. That transmission is the purpose of the integration.

6. Data Storage & Protection

OAuth tokens and other platform credentials are encrypted with AES-256 before they are stored. Conversion data is stored in a PostgreSQL database on our own server, with no public access and row-level security enabled. All data in transit between your CRM, our servers, Google, and Meta is encrypted with HTTPS/TLS. Only the server processes that upload conversions can read credentials. Contact data sent by the RD Station webhook is stored encrypted with AES-256 while your account exists; authenticated account deletion erases it and keeps only anonymous statistics.

When a merchant installs the optional browser script, it processes a visitor email only in the browser: the email is normalized and SHA-256 hashed before transmission. Nexopath receives the hash, Google click identifiers, and Meta click identifiers (fbc and fbp), never the plaintext email, and keeps these captures for up to 90 days to match later conversions. Merchants remain responsible for providing the appropriate notice and legal basis.

7. Data Retention & Deletion

We keep platform tokens only while that platform stays connected. When you click "Desconectar" (Disconnect) in the dashboard, we try to revoke our access at the platform and delete the token. For Google Ads, we also delete the chosen account and conversions. For Meta Ads, we also delete the ad account and the pixel list; the chosen pixel and events are kept for a later reconnection.

We keep conversion-event history while your account exists. Cancelling a subscription does not delete your account or its event history. Authenticated account deletion removes your account, its event history, and all Google and Meta connection data.

You can also remove our access to your Google account at https://myaccount.google.com/permissions, and remove our app from your Meta business settings. You may also request deletion of your data by emailing us at the address below, and we will complete deletion within 30 days.

8. Your Rights

You have the right to access, correct, or delete your personal data at any time. If you are located in the European Economic Area or Brazil, you have additional rights under the GDPR or LGPD, respectively, including the right to data portability and the right to withdraw consent.

9. Contact Us

If you have questions about this Privacy Policy or how we handle your data, please contact us at [email protected].