Legal
Privacy, terms, and security
How GeoPulse handles your data, what you agree to by using the platform, and how the service is secured.
Privacy policy
Last updated 1 August 2026
What we collect
Account details you provide (name, work email, company), the prompts and brands you configure for tracking, and product usage telemetry. We do not collect personal data about the individuals who appear in AI responses.
What we crawl
GeoPulse queries public AI search engines with the prompts you configure. Responses are stored against your workspace so trends can be measured over time. We do not submit your prompt set to any engine for training.
Who we share it with
Sub-processors used to operate the service: cloud hosting, error monitoring, and the AI engines being crawled. We do not sell workspace data, and we do not share one customer’s data with another.
Your controls
Export or delete a workspace at any time from Platform settings. Deleting a workspace removes its prompts, crawl history, and reports within 30 days of the request.
Terms of service
Last updated 1 August 2026
Your subscription
Plans are billed monthly or annually in advance. Upgrades take effect immediately and are prorated; downgrades take effect at the next renewal. Cancelling stops future billing and ends access at the end of the paid period.
Acceptable use
Do not use GeoPulse to impersonate another brand, to generate misleading comparative claims, or to circumvent the rate limits of the AI engines we crawl. Prompt credits are consumed per engine per crawl.
Accuracy of AI output
GeoPulse reports what generative engines said in response to a prompt at a point in time. Those engines can be wrong, and their answers change without notice. Metrics are a measurement of model output, not a statement of fact about any brand.
Availability
We target 99.5% monthly availability for the dashboard. Crawl frequency depends on the upstream engines and may be delayed when a provider rate limits or changes its interface.
Security architecture
Last updated 1 August 2026
Data in transit and at rest
All traffic is served over TLS 1.3. Workspace data, crawl history, and exports are encrypted at rest with AES-256. API keys are stored hashed and shown in full only once, at creation or rotation.
Access control
Workspace roles are enforced server side on every request. Permissions run from read-only through full admin, and revoking access takes effect on the next request rather than at session expiry.
Isolation
Every query is scoped to a workspace at the data layer. A credential for one workspace cannot read another, including through the public API.
Reporting a vulnerability
Send findings to security@geopulse.ai. We acknowledge reports within one business day and do not pursue legal action against good-faith research.