Privacy Policy

1. Information We Collect

We collect information necessary to perform uptime monitoring and alert notifications. This includes:

• User Profile Data: Email addresses, user IDs, and metadata provided by Clerk during user sign-in processes.
• Registered Target Data: Target URLs and optional Discord webhook URL strings registered to user monitoring channels.
• Telemetry Log Records: Status codes, HTTP response headers, check latencies, check timestamps, and target accessibility metrics logged to PostgreSQL.
• Billing Details: Subscription status, payment references, and plan limits processed securely by Razorpay. We do not store raw card numbers.

2. How We Use Information

Information is processed exclusively to:

• Instantiate and execute automated endpoint check cron tasks.
• Dispatch Markdown failure embeds to your Discord channel targets when health rules are breached.
• Generate the dashboard console charts, stats matrices, and check histories.
• Manage subscription records, verify signatures, and upgrade plan capacities.
• Verify user authorization inside monitors server actions.

3. Service Infrastructure and Database Storage

Data is stored durably on Neon PostgreSQL servers utilizing Prisma 7. The database records are protected by encryption at rest. Internal database queries are strictly constrained to ensure that users may only view telemetry data matching their authenticated Clerk identity signature.

4. Telemetry Log Retention and Purges

Uptime logs (PingLogs) are stored for:

• Free Plan (₹0 INR / $0 USD): 90 days of check history, after which logs are permanently deleted.
• Pro Plan (₹499 INR / $7 USD) or Business Plan (₹1,499 INR / $20 USD): 365 days of check history, allowing for long-term SLA reporting.
• Deleted Monitors: When a website monitor is deleted, all dependent PingLog entries are purged from the database immediately to preserve integrity.

5. Security notice and Warning Interception

To protect your operational metrics, all dashboard and server pipelines intercept database driver event outputs. Database warnings are caught and sanitized before logs are written to external diagnostic consoles, preventing credentials or configurations from leaking.

6. Billing and Checkout Security

All payment operations are handled by Razorpay's PCI-DSS compliant standard web checkout framework. Under sandbox and production profiles, checkout fields utilize dynamic data sanitization: customer contact details inside prefill objects are restricted to mock credentials (9876543210 / test.premium@pulseping.io) to protect your real profile information.

7. Cookies and Authentication Identifiers

We do not set tracking or advertising cookies. Access tokens and session keys are managed natively by Clerk using secure HTTP-only cookie parameters to validate route routing configurations.

8. Data Sharing and Third-Party API Hooks

We do not sell user data. Target check metrics are dispatched to third-party endpoints (e.g. Discord servers) solely when a webhook URL is configured by the user. These requests are sent over HTTPS with payload signatures.

9. Your Rights and Access Controls

You have the right to access, edit, or delete any monitors registered to your account at any time via the console. If you wish to delete your entire profile and database record archive, you may contact support.

10. Children's Privacy

PulsePing does not knowingly collect or solicit personal data from children. The Service is restricted to developers and professionals managing online endpoints.

11. Changes to this Privacy Policy

We may revise this policy periodically. The version marker will be updated, and significant updates will be communicated on the homepage footer status bar or via email.

12. Contact Information

For questions about this policy or database practices, contact support at support@subharup.com.