Privacy Policy
Last updated November 8, 2026
Draft: this page is waiting for a lawyer's review. Questions in the meantime go to hello@goldstandardweb.com.
Conversion Relay is an app made by Gold Standard Web LLC ("we") that a business installs in its CRM. It sends the business's booked appointments, pipeline stages, payments and won deals to the ad accounts the business connects (Meta, Google Ads, TikTok and Microsoft Ads), logs every send, and reports revenue against ad spend. This policy explains what we keep, what we never keep, what we send and for how long. Questions: hello@goldstandardweb.com.
Who is who
The business that installs Conversion Relay is the controller of its contacts' data: it decides what is sent, to which of its own ad accounts, and why. We are its processor: we handle that data only on its instructions and only to run the app. We don't sell it, rent it, or use it for our own advertising. Our Data Processing Addendum sets this out in full.
What we store
About the business's contacts (the people in its CRM):
- The CRM's record ids for contacts, opportunities, appointments, invoices and orders, with stage and status, dates, and amounts.
- Ad click IDs: gclid, gbraid and wbraid (Google), fbclid, fbc and fbp (Meta), ttclid (TikTok) and msclkid (Microsoft), plus li_fat_id, epik, rdt_cid and ScCid for platforms that are not live yet.
- UTM tags (source, medium, campaign, term, content), the landing page path and the referring site's domain.
- An anonymous visitor id the tracking script makes, and Meta lead-form lead ids where the contact has one.
- The contact's lead source in the CRM, and whether its consent field says yes or no.
- A one-way fingerprint (SHA-256) of each tag. It tells a new tag from an old one without keeping the tag's name.
- The delivery log. For every send it keeps the time, the rule, the platform, the event name, the value, the status and the reason in plain words. It also keeps the names of the match keys it carried (for example "email, phone, gclid") and our 0–10 match score.
About the business and its team:
- The account's settings, rules, connected ad accounts, alerts and plan.
- The CRM's and the ad platforms' access keys (OAuth tokens and pasted API tokens), encrypted.
- Team members' CRM user ids and their roles in the app (owner, manager or viewer).
- Email addresses people type in themselves: for alert emails, the daily summary, monthly client reports and company overview sign-in links.
- Ad spend, clicks and campaign, ad set and ad names and ids, read from the ad accounts or from a spend file the business uploads.
- An audit log of connects, disconnects, rule changes, resends and pauses, by user id.
- We email ourselves a notice when you install, with your business contact details.
What we never store
We never store any of these about a business's contacts, raw or hashed:
- names
- email addresses
- phone numbers
- street addresses
- IP addresses
- user agents (browser and device details)
The tracking script's visit record keeps click IDs, UTMs and the page path only. A visitor's IP address is used for a moment to stop abuse (rate limits) and is never saved. Our logs and error reports leave out tokens and personal data.
What we send to ad platforms
When a rule the business turned on fires, we read the contact from the CRM at that moment. We clean up the email, phone, first and last name, city, state, zip, country and contact id, and hash each one with SHA-256 in memory. We send the hashed values, the click IDs, the event name, time, value and currency and a fixed event ID only to the ad accounts the business connected. Then we drop them. Nothing is sent for a contact with the opt-out tag (default no-ad-sharing). Nothing is sent while sending is paused. When the business requires consent, nothing is sent for a contact without a yes in the consent field.
Outside health-safe mode, Meta and TikTok also get the rule's name (for example "Booked inspection"). Health-safe mode sends standard event names only, with value and currency and no service names or page addresses.
Once an ad platform receives an event, it handles it under the agreement between that platform and the business. The business must tell its own contacts about this sharing in its privacy policy and get consent where the law requires it.
Service providers
We use these providers, each only to run Conversion Relay:
- Netlify: hosting and file storage (United States).
- Neon: the database (United States).
- Resend: sending alert, summary, report and sign-in emails to the business's team.
- Sentry, only when enabled: error reports, with tokens, personal data, cookies and private links removed first.
We share data with others only if the law requires it, or to protect the app and its users from fraud or abuse.
How long we keep it
- The delivery log: 7 days on the Free plan, 13 months on Pro and Growth. Older rows are deleted every night.
- Tracking-script visits that never link to a contact: 90 days.
- Everything else: while the app is installed, so the rules, reports and history keep working.
- When a business uninstalls Conversion Relay or disconnects it, every CRM and ad-platform token is deleted at once, queued sends are canceled and the tracking script stops recording. The history stays readable for 30 days, then everything we hold for that account is deleted. The same 30-day clock runs when a paid plan lapses past its grace period.
- Our database host keeps short-term backups for recovery. Deleted data drops out of them as they roll over, within 30 days at most. One-time sign-in links and rate limit records are deleted within a day of expiring.
Security
Tokens are encrypted at rest (AES-256-GCM), all traffic uses HTTPS, and every page and job checks which business account it is working for. See our security page.
Your rights (GDPR, CCPA and similar laws)
People in a business's CRM should contact that business first, since it controls their data. We will help the business answer any request to see, correct or delete personal data, or to stop sharing it. We usually do that within days. We never store names, emails or phones. So a business can stop all future sharing for one person by adding the opt-out tag in its CRM. On request, we can delete the click IDs and ids we hold for that contact.
Under the CCPA, we are a service provider. We don't sell personal information or share it for cross-context advertising on our own behalf. We use it only to provide Conversion Relay to the business. Anyone can write to us at hello@goldstandardweb.com; we answer within 24 hours.
Health information
Conversion Relay is not a HIPAA-covered service and we don't sign business associate agreements. Health-safe mode limits what is sent, but it is not a compliance guarantee. See our terms.
Our own website
If you sign up for early access on our website, we keep your name, email, business name and your answers, only to contact you about Conversion Relay. Ask us to delete them at any time.
Changes
If we change this policy in a way that matters, we'll update the date above and tell installed businesses in the app or by email first.