Privacy Policy
This policy explains what data PingNodes collects, how it is used, and how it is protected. PingNodes is designed to collect operational monitoring metadata rather than customers' underlying business data. Diagnostic information returned by connected services may occasionally contain limited information included in error messages or service responses.
What we collect
- Account information and authentication identifiers: email address and account identifier collected during signup via Supabase Auth.
- Workspace metadata: workspace name, timezone, selected monitoring modules, and Telegram chat ID (not the bot token).
- Integration configuration: registered integration names, types, and connection status. Protected credential references (API keys, tokens) are stored in a secrets vault, never in plain application tables.
- Monitoring / check metadata: automated monitoring events, health check records, and check-run metadata (timestamps, counts, severity levels) — not raw customer workflow payloads.
- Operational events and alerts/incidents: alert records, incident state, and daily digest summaries generated from monitoring activity.
- Billing / payment metadata and subscription state: if payment is processed, Razorpay payment IDs, subscription IDs, payment status, and your workspace's current-access / payment / subscription state (for example, free, paid, support, scheduled). Raw card data is never stored by PingNodes — this is handled entirely by Razorpay.
- Notification preferences: your chosen alert channels (Telegram, email, push) and related delivery settings.
- Push notification tokens: device tokens for push notifications, stored with the user's consent.
- Support / admin adjustments: records of support or admin actions taken on your account, such as a manual billing adjustment or a courtesy access extension, so the change is auditable.
- Audit logs: system-generated audit entries for lifecycle state changes and key operational events.
- Technical logs: request and error logs used to operate and secure the platform, retained for operational and security purposes.
What we do not collect
- Underlying customer business records, database contents, or application payloads beyond diagnostic metadata necessary for failure detection
- Medical, financial, or personally sensitive business records
- API keys or bot tokens in plain application tables (these are vault-backed)
- Data beyond the operational monitoring scope described above
How your data is used
- Delivering monitoring alerts and daily digest reports to your configured Telegram target
- Showing operational status and history in your PingNodes dashboard
- Processing subscription payments through Razorpay
- Sending push notifications or email alerts if configured
- Maintaining security audit logs for your account
Third-party services
PingNodes uses the following categories of third-party service. Each has its own privacy policy. PingNodes does not publish internal credential IDs, workflow IDs, database project IDs, or secret names — these are implementation details, not data about you.
- Supabase — authentication and database host
- Razorpay — payment processing (card data handled entirely by Razorpay)
- Cloudflare — web and edge delivery
- n8n infrastructure — automation and monitoring execution (self-hosted or cloud)
- Telegram / email / push providers — notification delivery
Data retention
Operational metadata is retained for a period sufficient to provide monitoring history, alert records, and diagnostic reporting. PingNodes implements routine data retention and cleanup processes that prune aged records automatically.
Your rights
You may request access to, correction of, or deletion of your personal account data by contacting support at support@pingnodes.com. Requests are handled in accordance with applicable data protection regulations.
Contact
For privacy inquiries, contact: support@pingnodes.com.
Last updated: 16 August 2026 · pingnodes.com · support@pingnodes.com