Privacy policy
Last updated 30 Oct 2026 · Version 0.1
In short: We store the events you send so your team can read them. A push message carries only the event title, channel and priority; the event body, data and links never go through Google or Apple, and lock-screen previews stay minimal. We do not sell data. You can export or delete your account yourself.
1. Who we are
PingLoom is operated by [OWNER: legal name of the seller], an individual doing business in India, at [OWNER: postal address] ("we", "us").
For privacy questions write to [OWNER: support email]. Our grievance officer under Indian law is [OWNER: grievance officer name and email].
2. What we hold
Account: your email address, display name, a hashed password (Argon2id) or the identity of the GitHub or Google account you sign in with.
Alert content: the title, body, data, channel and timestamps of every event your servers send to PingLoom, plus the status of each attempt to reach a device. We process this only to provide the service to you.
Devices and push: the phones and apps you sign in on, with a label, an install ID and notification permission state. Push (FCM) tokens are encrypted at rest and never shown in the dashboard.
Billing: plan, status and invoice references. Card and payment details are collected and held by Dodo Payments, not by us.
Audit and security records: admin actions in a workspace, request logs with IP address and request ID. We do not log API keys, passwords or push tokens.
Support: anything you send us when you write to us.
3. Abuse prevention (hashed identifiers)
To give one free trial per person, we store one-way hashes (keyed HMAC) of your normalised email, sign-in account ID, device, company email domain and network address. We cannot turn a hash back into the original value.
These hashes are kept after you delete your account, for abuse prevention only, so a deleted account cannot be used to claim another trial. They are not used for marketing.
4. Waitlist and referrals
If you join the waitlist we store your email address to tell you about launch and to tell you your place in line. We use it for launch news only and you can ask us to remove it at any time.
If you arrive through a referral link or a creator code, we store a referral cookie for 30 days and record the attribution (who referred you, plus the campaign parameters in the link) against your account so rewards can be given.
5. Analytics and cookies
We use PostHog (product analytics) and Microsoft Clarity (page recordings and heatmaps on public pages). Before you consent, PostHog runs without cookies and without session replay, and Clarity is not loaded. After you accept, full analytics and replay are enabled. You can change your choice from the cookie settings link. See the cookie policy for details.
What we send to PostHog: an internal account ID and workspace ID, page paths (never query strings), and a short list of product events (sign-up started and completed, email verified, workspace created, API key created, first event received, device ready, checkout started, subscription active, and waitlist or referral steps). We never send email addresses, API keys, tokens, notification titles or bodies, payload data or IP addresses to analytics, and recordings mask all form fields and never run inside the signed-in app. If your browser sends Do Not Track or Global Privacy Control, we treat it as a rejection. The Android app sends two events (device ready, first event viewed) only if you turn that on under Account, then Privacy; it is off by default.
We use Sentry for error reports. They are scrubbed of credentials, tokens, email addresses and request bodies before they leave our servers.
6. How push notifications are handled
A push carries a minimal preview. The event title can pass through Google Firebase Cloud Messaging (FCM) to reach a device. The event body never goes through FCM. The app fetches the full event from PingLoom after you sign in.
By default the lock screen shows a generic preview, not your event content.
7. Chat destinations (only if you turn them on)
If an owner or admin adds a Slack, Discord or Telegram destination to a project, PingLoom posts alerts from that project to it. Nothing goes to these services unless a destination is added. Each message carries the event title, its priority, the channel name and a link to the event in PingLoom. The event body is included only if the destination turns it on, and the event data fields are never sent.
Once a message is posted, Slack, Discord or Telegram holds it under its own terms and privacy policy. The webhook URL or bot token you give us is stored encrypted, shown to you only in masked form, and removed when you delete the destination.
8. Forwarded emails
If you forward emails to a PingLoom address, we keep only the subject, the first 300 characters of the plain-text part, the sender's domain and a masked sender (such as r***@bank.com), the time we received it and the message ID. We do not store the full message, HTML or attachments, and we never open links in them. Forwarding confirmation codes from Gmail are kept on the source page only until the next email arrives or you replace the address.
9. Who processes your data
We use these processors, each only for the purpose shown: Dodo Payments (payments, tax and invoicing, as merchant of record); Firebase and Google (push delivery and Android crash reports); our email provider [OWNER: email provider name] (account and alert emails); Cloudflare (network protection and DNS); PostHog (analytics); Microsoft Clarity (page recordings, with consent); Sentry (error reports); and our hosting provider [OWNER: hosting provider and region].
We do not sell personal data and we do not share it for advertising.
10. Transfers outside India and the EU
Our processors may store or process data outside India, including in the United States and the European Union. Where required we rely on the safeguards each processor offers, such as standard contractual clauses. [OWNER: confirm primary hosting region and any further safeguards.]
11. Retention
Event history is kept for the length of your plan: 7 days on Free, 30 days on Developer, 90 days on Team and 180 days on Business. Older events are removed. If a trial ends and your plan drops to Free, data beyond Free retention is removed by the normal retention job.
Waitlist emails are kept until launch communications are done or you ask us to remove them. Billing records are kept as long as tax law requires. Abuse-prevention hashes are kept as described above.
12. Your rights: access, export and deletion
You can download a JSON export of your account data and delete your account yourself from Settings, under Privacy & data. Deleting an account needs your password, and an owner must first transfer or delete any workspace they own that has other members.
Deleted data is removed from the live service straight away. Encrypted backups keep it for up to 35 more days before it is overwritten.
To correct data, withdraw consent, object to processing or make a complaint, write to [OWNER: support email]. We answer within 30 days.
13. India: Digital Personal Data Protection Act, 2023
For people in India we act as the data fiduciary for account data and as a data processor for the alert content your servers send. You have the right to access, correct and erase your personal data, to nominate someone to act for you, and to a grievance response from the officer named above. You may also complain to the Data Protection Board of India.
14. EU and UK: GDPR
If you are in the EU or UK, we process your data to perform our contract with you, for our legitimate interests in running and securing the service, to meet legal obligations, and on your consent for analytics cookies and marketing. You have the rights of access, rectification, erasure, restriction, portability and objection, and you can complain to your local data protection authority. [OWNER: confirm whether an EU or UK representative is required.]
15. Children and changes
PingLoom is for business use and is not directed at children under 18.
If we change this policy in a way that matters, we will update the date and version above and tell account holders by email.