Privacy Policy

This policy explains how we handle your data and may be updated. Contact us with any questions.

1. What we collect

The public product collects only the categories below. We do not invent extra data types here.

Contact form fields (name, email, company, industry, budget, timeline, message, consent)
Account registration (name, email, password hash, organization membership)
Billing references (product ID, price snapshot, currency, Stripe session / payment status)
Workspace records the signed-in user creates (orders, projects, documents metadata, support threads)
Technical logs (request path, status, IP used for rate limits, user-agent)
Cookie and session identifiers (og_session, og_csrf, cookie preference)
Optional analytics / ad pixels when public IDs are configured and analytics cookies are accepted

2. Why we use data

To respond to inquiries, create accounts, confirm payments, deliver the purchased package, send transactional email, secure the platform, and — only when public analytics IDs are set — measure marketing performance.

3. Processors

These are the processors the current Omni Group Tech stack can actually send data to. A row being listed does not mean the integration is always on — see the “When” column.

Hosting / VPS
Serve the marketing site, client portal, and application logs
Data: Technical logs, session cookies, account and order records stored on the same stack
When: Always while the site is online
Application database
Accounts, organizations, orders, projects, CRM contact rows
Data: Name, email, company, order snapshots, project files metadata
When: After registration, checkout, or a contact submission that reaches CRM
Stripe
Card checkout, payment confirmation, and subscription billing
Data: Email, name, payment references, Stripe customer / session IDs
When: When the buyer starts card checkout
Resend
Transactional and inbound-contact email
Data: Name, email, message, order or contact metadata
When: When RESEND_API_KEY and contact/from addresses are configured
Slack (incoming webhook)
Operator notification for contact form submissions
Data: Contact form fields
When: When a Slack webhook is configured
Telegram (bot notify)
Operator notification for contact form submissions
Data: Contact form fields
When: When Telegram notify credentials are configured
Configured AI provider (OpenRouter or equivalent)
In-app assistant drafts for signed-in workspace users
Data: Prompts the signed-in user sends in the assistant
When: When a signed-in user uses the assistant and a provider key is present
HeyGen / D-ID (optional)
Video avatar renders for the AI support retainer
Data: Script text and render metadata
When: Only when those provider keys are configured and the retainer is active
Google Tag Manager / Google Ads / Meta Pixel
Marketing measurement and conversion events
Data: Page views, UTM values, begin_checkout / generate_lead events
When: Only if the matching NEXT_PUBLIC_* IDs are set and the visitor accepted analytics cookies

4. Retention

We keep account and invoice records as required for operations and legal obligations, and delete or anonymize other data when no longer needed.

5. Your rights