Back home

Privacy Policy

Last updated: May 16, 2026

This policy explains what data this AI agency SaaS platform collects, why it is used, and how it should be protected. Deployment owners should update contact details, processor lists, and jurisdiction-specific language before production launch.

Data We Collect

  • Account data: email address, profile settings, workspace role, billing status, and authentication identifiers.
  • Workspace data: clients, websites, social URLs, content briefs, generated drafts, workflow definitions, chatbot/voice-agent settings, and publishing configuration entered by users.
  • Operational data: usage events, credit ledger entries, workflow runs, API request metadata, error logs, and security/audit events.
  • Payment data: billing and subscription status handled through Stripe. Full card details are not stored by this application.

How Data Is Used

  • To provide content generation, scheduling, publishing, chatbot, voice-agent, automation, billing, and administrative features.
  • To meter usage, enforce plan limits, prevent abuse, debug failures, and improve product reliability.
  • To send content to third-party destinations only when a user configures and triggers that destination, such as WordPress, Meta platforms, or a client-provided API.

Where Data Is Stored

  • Application records are stored in Supabase project tables protected by authentication and role checks.
  • Secrets and provider credentials must be stored server-side in environment variables, OAuth storage, or secure integration records, not in public frontend code.
  • Logs may be stored by the hosting provider and should be redacted before leaving the application logger.

Security Controls

  • The application applies security headers, authentication checks, role-based access controls, rate limits, and secret redaction for logs and API errors.
  • API keys and service-role credentials are not intentionally exposed to browser code.
  • Users are responsible for entering only data they are authorized to process and for configuring client API destinations correctly.

Retention And Deletion

  • Workspace records are retained while an account or workspace is active unless deletion is requested or required by law.
  • Users may request deletion or export of account/workspace data by contacting the platform operator.
  • Some billing, security, and audit records may be retained for compliance, fraud prevention, and dispute handling.

Contact

  • For privacy, security, or deletion requests, contact the platform operator using the support channel configured for this deployment.