Site privacy notice
How CareGTM handles information from this site.
Last updated: May 19, 2026. This is a plain-language engineering notice for the public CareGTM marketing site. It is not legal advice and is not a formal compliance or regulatory certification.
What this notice covers
This notice describes what CareGTM collects when someone uses one of the two public forms on caregtm.com: the lead-capture forms on caregtm.com that request CareGTM beta access, and the privacy request form on this privacy notice page. It also describes what request and security metadata the public marketing site retains when those forms are submitted. It does not cover the CareGTM product application or any authenticated workspace.
Information you provide
- Work email: required so we can reply about beta access, launch updates, or your privacy request.
- Optional company: included from the “Company” field on the lead-capture request form when you choose to share it.
- Optional name: included when a form variant requests a name and you choose to share it.
- Privacy request details: required when you submit the privacy request form so CareGTM understands what you are asking about. CareGTM asks you not to include sensitive medical details, identifiers, or protected health information in this field.
Site request and security metadata
When a request form is submitted, the CareGTM marketing site also records request metadata that helps us understand where the request came from and operate the site safely:
- page path of the form that was submitted (for example,
/). - UTM / campaign fields from the URL when present:
utm_source,utm_medium,utm_campaign,utm_term, andutm_content. - referrer as reported by the browser.
- user agent as reported by the browser.
- bot-challenge and request-admission metadata from CareGTM’s lead-capture and privacy-request abuse controls when those controls are enabled, including Cloudflare Turnstile processing described in Cloudflare’s privacy policy. CareGTM uses this metadata to reject automated abuse and protect the public forms; it is not used for advertising profiling.
How your information is used
CareGTM uses the information you provide to follow up about beta access, product launch notes, and any privacy request you submit on this page. CareGTM uses the request and security metadata above to operate the site, reject automated abuse, and understand which channels referenced the page. CareGTM does not run advertising pixels or marketing-automation pixels on the public marketing site.
Site traffic analytics
CareGTM may use Google Analytics 4 on public marketing pages to understand aggregate site traffic, such as page views, referrers, device/browser category, approximate location, and campaign parameters. CareGTM does not send form field values such as work email, company, name, or message contents to Google Analytics, and the page tag is configured without advertising personalization signals.
Google Analytics may use cookies or similar identifiers for site measurement. CareGTM uses analytics only to understand public marketing-site traffic, not to determine product eligibility or to make automated decisions about visitors.
Service providers and limited disclosures
CareGTM uses service providers to operate this public marketing site: Vercel for hosting and request handling, Supabase for lead and privacy-request storage, Google Analytics 4 for site traffic measurement, and Cloudflare Turnstile for bot and abuse prevention when enabled. These providers may process the categories of information described in this notice so they can provide their services to CareGTM.
CareGTM does not sell personal information from the marketing site and does not share it for cross-context behavioral advertising. CareGTM may disclose information if needed to operate the site, protect the service, comply with law, or handle a business transfer such as financing, acquisition, or corporate reorganization.
Where it is stored
The fields above are stored in a CareGTM-controlled Supabase database. Lead submissions use first-touch and latest-touch attribution and a per-email submission count; privacy requests are stored as append-only records for operator handling. Server-only Supabase credentials never leave CareGTM’s server environment.
How it is protected
The production marketing site is served over HTTPS, uses source-controlled security headers including a Content Security Policy, and keeps database credentials server-side. These safeguards reduce risk, but no internet transmission or storage system can be guaranteed to be completely secure.
How long it is kept
CareGTM keeps marketing lead records, privacy request records, and related request metadata only as long as needed for beta-access follow-up, privacy-request handling, attribution, abuse prevention, site operation, and reasonable business records. CareGTM may delete, de-identify, or aggregate records when they are no longer needed for those purposes.
What CareGTM does not collect
The CareGTM marketing site does not request, collect, or store patient data, clinical records, or protected health information (“PHI”) through the public marketing forms. This notice is not a HIPAA-compliance statement and CareGTM does not claim regulatory readiness or certification on the basis of this notice.
The CareGTM marketing site does not include advertising pixels or marketing-automation pixels. The only public forms that submit to the CareGTM server are the lead-capture forms on the home page and the privacy request form on this notice page.
Privacy requests and updates
CareGTM offers a dedicated privacy request path directly on this page. Use the privacy request form below to describe a privacy request or question about information submitted through this site. You can also still use any CareGTM communication channel where you already received beta access, launch, or onboarding correspondence.
Please do not include sensitive medical details, identifiers, or protected health information in the request. CareGTM responds from a CareGTM-controlled address; the privacy notice page does not display a public email address.
CareGTM may revise this notice as the lead-capture flow, privacy request flow, analytics configuration, and marketing site change.
← Back to CareGTM