Privacy policy
Apphelm is built to explain product behavior without turning people into profiles. This policy explains what we process, why, for how long and the choices available to you.
Effective 22 September 2026 · Version 1.31. Scope and roles
This policy applies to apphelm.dev, the Apphelm operator console, support channels and our product telemetry services. Apphelm is the controller for account, billing, website and support data. When a customer sends telemetry about its own users, Apphelm acts as that customer’s processor under our Data Processing Addendum; the customer remains responsible for its notices, lawful basis and configuration.
2. Information we process
- Account data: name, email, role, workspace membership, authentication events and session/device metadata.
- Customer configuration: products, domains, outcomes, monitors, integrations, schemas, retention settings and access policies.
- Telemetry supplied by customers: event names, pseudonymous IDs, route and interaction descriptions, coarse device/geographic context, performance, grouped exceptions, heatmap coordinates, feature-flag evaluation identifiers and consent state. Autocapture records clicks, submits and field-change types only after the customer’s configured analytics consent; input values, passwords and element text are not collected. Full IP addresses are not retained as analytics properties.
- Optional replay: DOM and interaction events recorded only after configured consent and sampling. Inputs and text are masked by default; payment, password, health, government-ID and token fields are prohibited.
- Commerce and support: subscription status, plan, invoices/references received from our commerce provider, messages and diagnostic context you choose to share.
- Service records: security, audit, rate-limit, incident and delivery logs needed to protect and operate the service.
3. Purposes and legal bases
| Purpose | GDPR/UK GDPR basis |
|---|---|
| Provide accounts, analytics, reliability, support and requested exports | Contract; legitimate interests |
| Authenticate users, prevent abuse and maintain audit records | Contract; legitimate interests; legal obligation |
| Send operational and account communications | Contract; legitimate interests |
| Optional product analytics and replay on apphelm.dev | Consent where required; otherwise legitimate interests with opt-out |
| Billing, tax, dispute and legal compliance | Contract; legal obligation |
| Improve aggregate service quality | Legitimate interests, using minimized or aggregated data |
We do not use customer telemetry for cross-context behavioral advertising and do not train general-purpose models on it without an explicit written opt-in.
5. International transfers and residency
Apphelm runs on Cloudflare's global infrastructure. A workspace can record a region preference, but Apphelm does not currently offer EU-only storage or processing. Where personal data moves outside the EEA, UK or Switzerland, we use an adequacy decision or contractual safeguards such as Standard Contractual Clauses.
6. Retention
Workspace owners choose telemetry retention within plan limits. Default account and configuration data remains while the workspace is active; audit/security records are kept up to 24 months; support records up to 24 months after closure; billing records as required by tax law; optional website analytics up to 13 months; replay uses the plan’s shorter, separately configured period. Deletion enters a bounded backup expiry cycle, normally completing within 35 days unless law requires preservation.
7. Your choices and rights
Depending on location, you may request access, correction, deletion, portability, restriction, objection, withdrawal of consent, or an appeal. California residents also have rights to know, delete, correct, opt out of sale/sharing, limit certain sensitive-information uses and receive equal service. Apphelm does not sell personal information or share it for cross-context behavioral advertising. See the GDPR and California rights matrix or submit a request there.
8. Security and contact
We use least-privilege access, encryption in transit and at rest, short-lived signed access, audit trails, tenant-scoped authorization, secret rotation and incident procedures. No system is risk-free. Submit security reports through the support form using the Security report topic. Submit privacy questions and rights requests through the privacy request center. You may also complain to your local supervisory authority.
9. Changes
We will post material changes here and provide advance account notice when they materially reduce rights or introduce a new processing purpose. The effective date and version at the top identify the governing revision.