Privacy Policy

01Service Availability — EU/UK Notice

During our beta, the Service is not offered to users located in the European Economic Area or the United Kingdom, and access from those regions is geo-restricted. We do not intend to process EEA/UK personal data during beta. Before general availability in those regions, we will appoint an EU and UK representative under Article 27 GDPR / UK GDPR (DataRep) and update this policy with their contact details, applicable transfer mechanisms (EU Standard Contractual Clauses and the UK Addendum/IDTA), and your regional rights. If you access the Service from the EEA/UK despite these restrictions, you do so on your own initiative and this policy applies as written.

02Information We Collect

Information you provide:

• Account information (name, email, organization). Consumer chat uses self-hosted Better Auth on Cloudflare, with password access, passkeys, and Google sign-in where enabled. Verification and recovery emails are sent through Cloudflare. Developer services that have not migrated continue to use Supabase Auth.
• Questions, prompts, documents, or other content you submit to run a debate.
• Waitlist and invite information (email address, product interest, and any use-case description you choose to share) if you join our beta waitlist.
• Payment information, processed by Stripe — we do not store full card details on our servers.
• If you are an enterprise customer with your own dedicated deployment, any AI provider credentials associated with your environment (see Section 5).

Automatically collected information:

• Usage data: debates initiated, models selected, round counts, timestamps, token usage, credit consumption.
• Technical data: IP address, browser type, device information, and server logs, used for security, abuse prevention, rate limiting, and performance monitoring.
• Session cookies and similar technologies necessary to keep you signed in and to operate the Service securely (see our Cookies page). We use only essential cookies — no advertising or cross-site tracking cookies, and no third-party analytics cookies.

Information from third parties:

• Outputs and metadata returned by the AI model providers used for your debate, limited to what's necessary to run and bill it.

03Privacy Controls Built Into the Service

• Staff access restriction. Mavenn personnel and administrative tools cannot view the content of your private debates. Our administrative systems are technically restricted to content you have explicitly published, plus account, billing, and aggregate usage records.
• Incognito debates. Your question, the models' responses, and any attachments are stored temporarily while the debate runs. We automatically delete this content from our systems after the debate finishes, fails, or is cancelled, and retry unfinished deletions. After cleanup, only billing and usage records are retained. Incognito content is not saved to your debate history.
• Deletion. Once a debate has stopped, you can delete it from the app or API. It is hidden immediately, and we remove its content and attachments from our systems, retrying unfinished deletions. Billing records of amounts already charged are retained as required for accounting.
• Model training transparency. We flag models whose providers disclose that they retain or train on submitted prompts, and provide a filter to exclude them. Where a provider has not disclosed its policy, we treat it as unknown and say so.

04How We Use Your Information

We use information to:

• Provide and operate the Service, including running multi-model debates and generating attributed consensus outputs.
• Authenticate users and enforce plan/usage limits.
• Process billing and manage subscriptions or credit purchases.
• Generate audit trails and attribution within debate outputs.
• Communicate with you about the Service (updates, support, security notices) and, if you joined the waitlist, about beta access.
• Detect, investigate, and prevent abuse, fraud, or violations of our Terms of Service.
• Meet the compliance and audit requirements associated with our AWS partner status.

We do not train or fine-tune any AI models on your data. Your inputs are used only to run the specific debate you request.

05AI Providers and Model Routing

To run a debate, we transmit your prompt, any documents you attach, and (for follow-up questions) the relevant prior context of that conversation to the AI model providers you select. We do not send your name, email, or account identifiers with debate content.

Models are served through the following providers, depending on your selection:

• Direct providers: OpenAI, Anthropic, Google, and xAI.
• OpenRouter: an AI model marketplace through which we offer a wide catalog of additional models from many vendors. When you select an OpenRouter-served model, your debate content is processed by OpenRouter and the underlying model vendor under their respective terms.
• Enterprise deployments only: Amazon Bedrock or Azure OpenAI within the customer's own cloud environment.

Each provider processes debate content under its own terms and data policies. Providers we pay under commercial API terms do not use API submissions to train their models per their published policies; some third-party models available through OpenRouter (particularly free models) may retain or train on submissions — these are the models our training-transparency flag and filter address (Section 3).

Provider credentials. Mavenn is credits-based: for consumer and standard SaaS accounts, you do not supply your own AI provider API keys, and we do not store per-user provider credentials. For enterprise customers on a dedicated deployment, the customer's designated AI provider account is used under that customer's separate enterprise agreement; where any provider credentials are stored on our infrastructure in that context, they are encrypted at rest using AES-256-GCM, access-restricted to the customer's organization, and rotatable or revocable on request.

06Data Sharing and Disclosure

We do not sell or share your personal data for advertising purposes (including as "sell" and "share" are defined in the California Consumer Privacy Act).

We disclose data only to:

• The AI model provider(s) involved in your debate, solely to fulfill your requests (Section 5).
• Infrastructure and service providers acting as our processors under data processing agreements: Cloudflare (consumer chat and website hosting, consumer database, file storage, authentication email, DNS, and network security), Stripe (payments), and Amazon Web Services (developer API compute and file storage; also enterprise deployments). Developer services that have not migrated continue to use Supabase (authentication and database) and Vercel (developer portal hosting). Microsoft Azure is used for enterprise deployments only.
• Regulators or authorities as required by law, or as needed to protect our rights, safety, or property, or those of our users.
• A successor entity in connection with a merger, acquisition, or sale of assets, in which case this policy continues to apply to previously collected data.

07Data Retention

• Debate content (prompts, responses, summaries, attachments) is retained until you delete it, so your debate history works as a product feature. You can delete a debate once it has stopped. Incognito content is stored temporarily for processing and then automatically deleted as described in Section 3.
• Waitlist records are retained until you are admitted or ask to be removed.
• Usage and billing records are retained for as long as required for accounting, tax, security, or compliance purposes, including records reviewed as part of our AWS partner compliance obligations.
• You may request deletion of your account and associated data at any time (Section 9).

08Security

We apply industry-standard safeguards, including encryption in transit (TLS) and at rest, role-based and organization-scoped access controls, and regular internal review. Developer API keys issued by Mavenn are stored only as cryptographic hashes (SHA-256); we display the full key once, at creation, and it cannot be retrieved afterwards. No system is 100% secure, and we cannot guarantee absolute security.

09Your Rights

Depending on your location, you may have rights to access, correct, delete, or export your personal data, or to object to or restrict certain processing. To exercise these rights, contact privacy@mavenn.ai. We will verify your request and respond consistent with applicable law. We do not discriminate against you for exercising your rights.

California residents (CCPA/CPRA). We collect the categories of personal information described in Section 2 (identifiers, commercial information, internet activity, and user-provided content) for the purposes in Section 4. We do not sell or share personal information, and we do not use or disclose sensitive personal information for purposes requiring a right to limit. You have the rights to know, access, correct, delete, and port your personal information, and to not receive discriminatory treatment, exercisable via privacy@mavenn.ai. Authorized agents may submit requests on your behalf with proof of authorization.

EEA/UK residents. The Service is not currently offered in your region (Section 1). Upon general availability we will update this section with the applicable legal bases, our Article 27 representative's contact details, transfer safeguards, and your rights to lodge complaints with a supervisory authority.

10Children's Privacy

The Service is intended for users 18 years of age or older, consistent with our Terms of Service. We do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us data, contact privacy@mavenn.ai and we will delete it.

11International Data Transfers

We are a US company. Our developer API uses AWS and Supabase infrastructure in US regions. Consumer chat and the marketing website use Cloudflare's global network, so processing is not restricted to the United States. Enterprise customers using a dedicated deployment control the region of their own cloud environment. When we open the Service to EEA/UK users, transfers will be safeguarded by EU Standard Contractual Clauses and the UK Addendum/IDTA with each processor, and this policy will be updated accordingly.

12Automated Processing Transparency

Mavenn's outputs are generated by AI models. The Service orchestrates debates between the models you select and synthesizes their positions; it does not make automated decisions producing legal or similarly significant effects about you. Outputs may be inaccurate and should be independently verified before reliance (see our Terms of Service).

13Changes to This Policy

We may update this policy from time to time. Material changes will be communicated via the Service or by email to registered accounts, with the "Last updated" date revised. Continued use of the Service after changes take effect constitutes acceptance.

14Contact Us

JAMAEDGE Group LLC (dba Proticom)
16835 Algonquin St, Suite 205
Huntington Beach, CA 92649, USA
privacy@mavenn.ai