← Back to Pulse

Privacy Policy

This privacy policy explains how Pulse Monitoring Ltd ("we", "us", "our") collects, uses, and protects your personal data when you use Pulse commercial services, including self-hosted Relay/Pro plans and Pulse Cloud.

What Data We Collect

We collect the minimum data necessary to provide our services:

Email address: Used to deliver your license or activation key and important service updates.
Name: Collected during checkout for invoice generation.
Billing address: Required for payment processing and invoicing.
Company name & VAT ID: Optional, collected if you provide them for business invoices.
License or activation key: A unique identifier generated for your purchase or migration.
Anonymous Pulse telemetry: Coarse install, version, platform, and feature-use fields sent by self-hosted Pulse if anonymous outbound telemetry is enabled. Telemetry rows do not store hostnames, credentials, infrastructure identifiers, prompts, chat messages, or IP addresses. Request IP addresses may be used transiently for rate limiting and abuse prevention.

How We Use Your Data

License delivery: We email your license or activation key to the address you provide.
Invoice generation: Your billing details are used to create invoices.
License validation: Pulse validates your license or activation key against our server.
Aggregate product health: Anonymous telemetry helps us understand active installations, release uptake, and feature use without identifying your infrastructure.
Support: We use your email to respond to support requests.

We do not sell, rent, or share your personal data with third parties for marketing purposes.

Third-Party Services

We use the following GDPR-compliant services to operate Pulse commercial services:

Stripe: Payment processing. Stripe handles all payment card data securely. See Stripe's Privacy Policy.
Resend: Email delivery for license and activation keys. See Resend's Privacy Policy.
Cloudflare: Website hosting and analytics. We use Cloudflare Web Analytics, which is cookieless and privacy-friendly. See Cloudflare's Privacy Policy.

Data Retention

Retention depends on the record type and the legal or operational reason for keeping it:

License and activation records: Kept while needed to provide access, support migrations, honour lifetime or legacy entitlements, prevent fraud, or process a verified deletion request.
Invoices: Retained as required by tax and accounting laws (typically 7 years).
Support emails: Retained for 2 years after your last interaction.
Anonymous telemetry rows: Purged after 90 days.

Your Rights (GDPR)

If you're in the EU/EEA, you have the following rights under GDPR:

Right to access: Request a copy of all data we hold about you.
Right to rectification: Request correction of inaccurate data.
Right to erasure: Request deletion of your data ("right to be forgotten").
Right to portability: Receive your data in a machine-readable format.
Right to object: Object to processing of your data.

To exercise these rights, use our self-serve data request page to request and confirm export or deletion by email verification. Alternatively, email support@pulserelay.pro with "Data Request" in the subject line.

Data Deletion

You can request deletion using our self-serve data request page, or email support@pulserelay.pro. After email verification, deletion will:

Permanently remove your license records from our systems
Immediately revoke your license or activation key

For Stripe payment data deletion, email us and we will submit a deletion request on your behalf.

Note: We may retain certain data as required by law (e.g., invoice records for tax purposes).

Cookies

We do not use cookies for tracking or advertising. Cloudflare Web Analytics does not use cookies and does not collect personal data.

The Pulse Application

The Pulse desktop/server application:

Does not include third-party analytics SDKs or advertising trackers.
May send anonymous outbound telemetry to the Pulse license server on startup and daily heartbeat. Operators can disable telemetry, preview the exact payload, or reset the local telemetry ID in Pulse settings.
Contacts our license server for license or activation validation, update/service checks, and anonymous telemetry when enabled.
Pulse intelligence features (Pulse Assistant and Pulse Patrol) communicate directly with your chosen LLM provider (OpenAI, Anthropic, etc.) using your own API keys. We do not proxy, store, or have access to these communications.

The Pulse Mobile App

Supported Pulse Mobile releases connect to your self-hosted Pulse instance via Pulse Relay:

End-to-end encryption: All communication between Pulse Mobile and your Pulse instance is encrypted using X25519 key exchange and AES-256-GCM. The relay server routes encrypted frames and cannot read your data.
Device tokens: If you enable push notifications, your device token (Apple APNs or Google FCM) is stored on the relay server to deliver alerts. No other device identifiers are collected.
Camera access: Used solely to scan QR codes when pairing with a Pulse instance. No photos or videos are captured or stored.
Biometric data: Face ID, Touch ID, and fingerprint authentication are processed entirely on your device by the operating system. We never receive or store biometric data.
Local storage: Connection credentials and encryption keys are stored in your device's secure keychain (iOS) or keystore (Android). They are not transmitted to our servers.
No analytics or tracking: Pulse Mobile does not include any analytics SDKs, advertising identifiers, or usage tracking.

Security

We protect your data using:

HTTPS encryption for all communications
Ed25519 cryptographic signatures for license and activation tokens
Secure, isolated infrastructure
Access controls and regular security reviews

Contact

For privacy-related questions or data requests, contact us at:

Email: support@pulserelay.pro

Last updated: April 2026
Pulse Monitoring Ltd (Company No. 16939106, England & Wales)