Privacy Policy

Last updated: September 4, 2026

This policy explains what PulseGuard collects, why we collect it, and your choices. PulseGuard is an uptime / RPC monitoring service operated at https://pulseguard.top.

1. What we collect

Account data — email address; optional password (stored as a hash); Google account ID if you sign in with Google; optional email verification status.
Telegram — Telegram chat ID when you link the bot or create an account via Telegram.
Monitoring config — URLs, hosts/ports, probe settings, HTTP headers/body you configure, pulse rules, and related check results needed to run the service.
Alert channels — Discord webhook URLs and custom webhook URLs you provide.
Billing — plan tier, ASAP credits, payment/donation records (e.g. invoice IDs, cryptocurrency transaction hashes, amounts, chain). We do not store card numbers; crypto checkout may be handled by NOWPayments.
Technical data — server logs (IP address, user agent, request paths, errors) for security and reliability; a session token stored in your browser (localStorage) after login.

2. Google Sign-In

If you choose Continue with Google, we request Google’s basic profile scopes (openid, email, profile) and receive your Google user ID, email, and whether Google marks that email as verified. We use this only to create or sign in to your PulseGuard account. We do not use Google data for advertising. See also Google’s Privacy Policy.

3. How we use data

Provide and improve monitoring, alerts, pulses, and billing.
Authenticate you and secure accounts.
Send operational messages (alerts, verification emails when configured).
Prevent abuse, debug outages, and comply with law.

We do not sell your personal information.

4. Third parties

Depending on features you use, data may be processed by:

Google — OAuth sign-in.
Telegram — bot messages and linking.
Discord / your webhooks — alert delivery to URLs you configure.
NOWPayments — optional crypto invoices for Pro.
Blockchain explorers / RPC nodes — optional donation verification.
CoinGecko (or similar) — market price data for pulses.
Email provider (e.g. Resend) — optional verification email delivery.
Hosting / database — infrastructure that stores and serves the app.

Those providers process data under their own terms. Alert destinations you configure receive only what is needed to deliver the alert.

5. Cookies and local storage

We primarily use browser localStorage for your login token (not advertising cookies). Essential server-side session or CSRF mechanisms may be added for security. We do not run third-party ad trackers on the product pages.

6. Retention

We keep account and configuration data while your account is active. Probe history and logs may be retained for a limited period for debugging and product limits, then deleted or aggregated. You may request deletion of your account data (see Contact).

7. Security

We use HTTPS in production, hashed passwords, and access controls on the server. No method of transmission or storage is 100% secure; please use a strong password and protect your Telegram / Discord tokens.

8. Children

PulseGuard is not directed at children under 16. Do not create an account if you are under 16.

9. International users

The service may be hosted and operated from locations outside your country. By using PulseGuard you understand your data may be processed in those locations.

10. Changes

We may update this policy. The “Last updated” date at the top will change. Continued use after an update means you accept the revised policy.

11. Contact

Privacy questions or deletion requests: PulseGuard Support via Telegram bot @TradingPulseGuardAI_bot (send /support); or in-app Support at https://pulseguard.top/app/support.