Privacy Policy

OmniPulse AEO ("OmniPulse," "we," "us") is an Answer Engine Optimization content platform. This policy explains what data we collect when you use omnipulseaeo.com and the OmniPulse dashboard, why we collect it, and how it's handled. We built this to describe what the product actually does, not a generic template — if something here changes, we'll update this page and adjust the effective date above.

1. What we collect

Account data. When you sign up, we (via Supabase Auth) store your email address and an encrypted password hash, or, if you use "Continue with Google," the basic profile info Google shares for authentication. We never see or store your Google password.

Workspace & campaign content. The seed topics, URLs, target personas, and brand-voice descriptions you enter to generate content, plus the content our pipeline generates from them (articles, scripts, social posts, schema markup, etc.) and any publishing-destination configuration you add (WordPress site URL, webhook URLs).

Billing data. Subscription plan and status. Payment card details are collected and stored directly by Stripe, our payment processor — OmniPulse never receives or stores your full card number.

Your AI provider API keys (BYOK). OmniPulse is bring-your-own-key: you supply your own Anthropic, ElevenLabs, and/or Replicate API keys so that content generation is billed directly to you by those providers, not marked up by us. Keys are encrypted at rest with AES-256-GCM before they touch our database and are only decrypted in server memory, transiently, at the moment a generation request is made — never logged, never visible to other customers, and never sent anywhere except the specific provider the key belongs to.

Marketing attribution. If you arrive via a tracked link (UTM parameters, an affiliate referral code, Facebook/Google click IDs), we record that in your browser's sessionStorage — not a cookie, and not shared with any ad network — so we can tell which channel a signup came from. It clears when you close the tab unless you sign up first, in which case it's attached once to your new workspace.

Lead-capture quiz data. If you complete the short qualification quiz instead of signing up directly, we store your answers and email address so we can follow up.

2. How we use it

• To create and operate your account and workspace.
• To run the content-generation pipeline you trigger, using your own configured provider keys.
• To process subscription billing and send billing-related notices, via Stripe.
• To send transactional email — signup confirmation, password reset — via Supabase Auth.
• To respond to support requests.
• To understand which marketing channels and referral partners drive signups, so we can improve them.
• To detect and prevent abuse of the platform (see our Terms of Service).

We do not sell your data, and we do not use your content to train any AI model.

3. Who we share it with

We use a small number of infrastructure providers to run the product. Each only receives the data it needs to do its job:

• Supabase — hosts our database and handles authentication (password hashing, session tokens, email confirmation).
• Vercel — hosts the application itself.
• Stripe — processes subscription payments and stores your payment method.
• Anthropic, ElevenLabs, and Replicate — only if and when you configure your own API key for that provider, we call their API on your behalf using your key to generate your content. We don't share your data with these providers for any purpose beyond fulfilling the specific generation request you triggered.

We don't share your data with data brokers or advertisers, and we don't sell it.

4. Data retention & deletion

We keep your account and content data for as long as your account is active. You can delete individual campaigns and content directly from your dashboard at any time. For full account or workspace deletion, or to request an export of your data, email support@omnipulseaeo.com — we'll confirm and process the request. Billing records are retained separately by Stripe as required for tax and accounting purposes even after account deletion.

5. Security

Data is encrypted in transit (HTTPS) and at rest where it matters most — your third-party provider API keys are AES-256-GCM encrypted before storage. Access to your workspace data is enforced at the database level via row-level security, so other customers cannot query your data even in the event of an application-layer bug.

6. Children's privacy

OmniPulse is a B2B tool intended for business use and is not directed at children. We don't knowingly collect data from anyone under 16.

7. Changes to this policy

If we materially change how we handle your data, we'll update this page and change the effective date above.

8. Contact

Questions about this policy or your data? Email support@omnipulseaeo.com.