1. Who we are and what this covers
Zharp Technologies Inc. ("Zharp", "we") runs Zharp: the website zharp.io, the dashboard, mobile apps, APIs, SDKs, agent and status pages. This policy explains what personal data we handle and why.
For your account, billing and our website we decide how data is used (we are the controller). For the data you and your systems send into a workspace (logs, traces, errors, session replays, status page subscribers and the like) we act on your instructions (we are the processor); the workspace owner is responsible for having a lawful basis to send it.
2. What we collect
| Data | Examples | Where it comes from |
|---|---|---|
| Account | Name, e-mail, password (stored hashed), timezone, language, two-factor settings; Google, GitHub or Apple account id if you sign in with them | You |
| Contact details for alerts | Phone number, mobile device push token, notification preferences | You and the mobile app |
| Billing | Plan, invoices, billing address and tax id. Card details are held by Stripe, never by us | You and Stripe |
| Workspace data | Monitor settings and results, incidents, comments, on-call schedules, team members' names and e-mails | You and your team |
| Telemetry you send | Logs, traces, errors, metrics and session replays from your apps and servers, which can contain your users' data | Your systems, via our SDKs, agent and APIs |
| Status page subscribers | E-mail addresses of people who subscribe to a status page | Those people |
| Integrations | Tokens for Slack, task trackers, code hosts and other services you connect (stored encrypted) | You |
| Messages | What you send through the contact form, support e-mail or a public report link | You |
| Usage of our own product | Pages viewed, clicks, errors and request timings in the dashboard; a share of dashboard sessions are recorded (see below); IP address and browser in server logs | Your browser and our servers |
3. Analytics and session replay on our own product
Website analytics. zharp.io uses Vercel Analytics to count page views. It doesn't use cookies or follow you across other sites.
Dashboard monitoring. We monitor the dashboard with Zharp itself: errors, page loads, clicks and the requests they make. About a quarter of dashboard sessions, and every session where an error happens, are recorded as a session replay so we can see what went wrong. A replay shows the pages as you saw them, including what they display. What you type is masked, and so are API keys, ingest keys and the setup snippets that contain them. Replays are only viewed by the Zharp team to fix problems, and are kept for 14 days at most.
4. How we use it
- To run the Service: run checks, store and show your data, open incidents and send the alerts you set up.
- To run Zharp AI when you or your workspace use it (see below).
- To bill you and keep the records tax law requires.
- To keep the Service secure: detect abuse, rate-limit, investigate incidents.
- To fix problems and improve the product, using our own usage data.
- To e-mail you about your account (verification, security, billing, alerts) and, if you leave "Product updates" on, a monthly summary of what's new. You can turn that off in your settings or from any such e-mail.
5. Zharp AI
When you ask Zharp AI a question or it investigates an incident, we send the data it needs (for example the incident, the monitor's recent results and matching log lines) to an AI model provider listed below, and show you the answer. The providers process it on our behalf under their API terms, which don't allow them to train their models on it. We keep your conversations so you can return to them; you can delete them.
6. Legal bases (EEA, UK and similar laws)
- Contract: to provide the Service you signed up for, and bill for it.
- Legitimate interests: security, preventing abuse, improving the product and monitoring our own dashboard.
- Legal obligation: tax and accounting records.
- Consent: product update e-mails, which you can withdraw at any time.
7. Service providers we use
We share data only with providers that help us run Zharp, under contracts that limit their use of it:
| Provider | What for | Location |
|---|---|---|
| Hetzner | Servers and databases for the API, checks and your data | USA (Virginia) |
| Vercel | Hosting the website and dashboard; website analytics | Global edge network |
| Cloudflare (R2) | Storing session replay recordings and uploaded files | Global |
| Stripe | Payments, invoices and tax | USA |
| Brevo | Sending e-mail | EU |
| Twilio | SMS and phone call alerts, when available | USA |
| Google Firebase | Delivering push notifications to the mobile app | USA |
| Cloudinary | Storing and resizing uploaded logos and images | USA |
| Google (Gemini) and Anthropic | AI models behind Zharp AI | USA |
Data also goes to services you connect yourself (Slack, PagerDuty, task trackers, code hosts and others), because you asked for it. We don't sell personal data or share it for advertising. We disclose data to authorities only when the law requires it.
8. International transfers
Our servers are in the United States. If you are outside the US, your data is transferred there. Where the law requires it, we rely on safeguards such as the European Commission's Standard Contractual Clauses with our providers.
9. How long we keep it
- Account and workspace data: while the account exists, then deleted within 30 days of deletion.
- Logs, traces and errors: for your plan's retention (7 to 90 days), then deleted automatically.
- Session replays from your apps: for your plan's retention; replays of our own dashboard: 14 days at most.
- Invoices and billing records: as long as tax law requires (usually 7 years).
- Server logs: only as long as needed to run and secure the Service.
10. Security
Data travels over HTTPS. Passwords are hashed, integration tokens are encrypted, and access to production is limited to the people who run it. No system is perfectly secure; if a breach affects your personal data, we'll tell you as the law requires. See our Security page, and report problems to security@zharp.io.
11. Your rights and choices
Depending on where you live, you can ask to see, correct, export or delete your personal data, object to or restrict how we use it, and withdraw consent. Most of this you can do yourself in the dashboard: edit your profile, turn off product updates, or delete your account. For anything else, e-mail privacy@zharp.io; we answer within 30 days. You can also complain to your local data protection authority.
If your data is in a Zharp workspace you don't own (for example in a customer's logs, or as a status page subscriber), ask that workspace's owner; we'll help them respond. Status page subscribers can unsubscribe from any e-mail.
California residents: we don't sell or share personal information as those terms are defined in the CCPA.
12. Children
Zharp is not for children. You must be at least 16 to create an account, and we don't knowingly collect data from children.
13. Changes
We may update this policy. For material changes we'll tell you by e-mail or in the dashboard before they take effect. The date at the top shows the current version.
14. Contact
Zharp Technologies Inc. · privacy@zharp.io · or use the contact form.