Security
Last updated November 8, 2026
Conversion Relay is built to hold as little as possible and to protect what it holds.
What we hold
Record ids, ad click IDs, UTM tags and a log of each send. Never contacts' names, emails, phone numbers, street addresses, IP addresses or user agents, raw or hashed. Details are in our Privacy Policy.
How it's protected
- Tokens encrypted at rest. Every CRM and ad-platform token (OAuth or pasted) is encrypted with AES-256-GCM before it is saved, and is never sent to a browser.
- HTTPS only. All traffic to the app and to the ad platforms uses HTTPS. Sign-in cookies are Secure and HTTP-only.
- Hashing at the edge. Emails, phones and names are read from the CRM at send time, normalized and hashed with SHA-256 in memory, sent, and dropped. They never reach our database or logs.
- Webhook checks. Every webhook from the CRM must carry a valid signature, checked against the CRM's public key, and each one is handled once even if it arrives twice. Workflow calls must carry our secret key and name the business account that installed us.
- Embedded page checks. The in-CRM page can be framed only by the CRM's own sites (and the white-label domains a company adds). Every other page refuses to be framed. Who is signed in comes from the CRM's encrypted user details, checked on our server.
- Roles checked on the server. Owners, managers and viewers can see and change only what their role allows, and only in their own business account. Every database query is scoped to that account.
- No personal data in logs. Our logs and error reports strip tokens, emails, phone numbers, cookies and private links before they are written. Logs name records by id.
- Fewest permissions. We ask each service for only what the app uses: Google for conversion uploads and reading your Google Ads account (accounts, conversion actions, spend); Microsoft for managing offline conversions and reading reports. Meta and TikTok use a token you make for one dataset or pixel. In the CRM, the app writes nothing except one hidden contact field.
- Safe sign-ins. Google and Microsoft sign-ins use PKCE and a signed state tied to your browser, which expires in 15 minutes. Company overview sign-in links are emailed, signed, used once and expire; we store only a fingerprint of each.
- Rate-limited public endpoints. The tracking script's endpoint, report links, sign-in links and workflow endpoints are rate-limited. The tracking key in your script can only record visits for your own account, and you can limit it to your own sites.
- Fail safe. When an ad platform refuses a token, that connection stops sending and alerts you; nothing is retried against it until it's fixed.
- Clean exit. When a business uninstalls or disconnects, its tokens are deleted at once and all its data 30 days later.
Reporting a vulnerability
Email hello@goldstandardweb.com with "Security" in the subject. Tell us what you found and how to reproduce it. We reply within 24 hours and fix confirmed issues quickly. Please don't access other businesses' data, send real conversions, or disrupt the service while testing. We won't take legal action against good-faith research that follows these rules.