Minimal collection
QuadPulse collects the information needed to operate accounts, workflows, billing, integrations, and product support.
This page explains what QuadPulse collects, how it is used, and how data is protected across account access, product workflows, billing, and integrations.
QuadPulse handles data so users can access the platform, configure workflows, review activity, manage billing, and operate supported integrations with clearer boundaries.
QuadPulse collects the information needed to operate accounts, workflows, billing, integrations, and product support.
Credentials, keys, and sensitive integration details are handled through encrypted storage and protected backend systems.
Users can request access, deletion, portability, and notification preferences through support and security channels.
QuadPulse uses data to keep accounts accessible, workflows configured, activity reviewable, billing operational, and integrations functioning inside the platform.
Name, email, and profile details used for sign-in, account access, and platform communication.
Model tier, symbols, risk settings, execution preferences, and product configuration choices.
Workflow states, execution logs, scan results, approval decisions, and product audit records.
Subscription, invoice, and payment status handled through secure payment providers.
The same privacy posture is visible across sign-in, product configuration, activity review, billing, and support requests.
QuadPulse respects your privacy. This policy explains what data we collect, why we collect it, and how we protect it. We keep collection focused on what is needed to operate the platform.
QuadPulse does not sell user data. Information is shared only where needed to operate the platform.
To exercise these rights, use the security and contact form.
We may update this policy from time to time. Significant changes will be communicated by email or in-app notice. Continued use after changes means the updated policy applies.