Privacy

This privacy notice describes the production infrastructure used for the controlled private beta. It has not been reviewed by legal counsel.

Legal review pending: this notice must be reviewed and completed by qualified legal counsel.

Current production infrastructure

PULSEVATE uses Supabase for account authentication and tenant-isolated cloud state, Railway for the authenticated API, Netlify for the site and web app, and Resend for authentication email delivery. A user-matched local cache supports hydration and recovery; the authenticated cloud snapshot is the source of truth. Account export and deletion are available through authenticated API flows.

Claude requests

When Claude mode is enabled, the bounded context required for the requested feature is sent through the authenticated PULSEVATE API to Anthropic. Provider keys stay server-side. Operational AI usage records contain counts, token/cost estimates, model, result category, and timing only; they do not store raw prompts, onboarding prose, Pattern text, or generated Quest copy.

Payments and analytics

Stripe processes live checkout without granting access from a browser return URL. Subscription entitlement is derived only on the server from signed Stripe webhooks. First-party funnel analytics are stored server-side with an allowlisted event schema and bounded UTM attribution; free-form behavioral prose is not accepted.

Legal information still pending

A final policy must still identify the operator, lawful bases, all processors, retention periods, security measures, user rights, international transfers, age requirements, and the remaining legal notices. Those decisions require the user and qualified legal counsel and are not invented here.

Privacy contact

Privacy and account-data requests can be sent to support@pulsevate.com.

Professional correspondence address

138 avenue Victor Hugo, 75016 Paris, France