Privacy

Overview

This Privacy Policy explains how AI Council collects, uses, shares, protects, and deletes information when you use the website, dashboard, API, command-line tools, checkout flow, and support channels.

AI Council is built for software and AI-agent workflows. The product is designed to meter usage and operate account access without storing raw prompt or response bodies in the customer account database.

Information You Provide

• Account information, including email address, password hash, selected plan, account status, and created-at timestamps.
• Support information, including messages, screenshots, account identifiers, troubleshooting details, and any files or logs you choose to send.
• Checkout and billing information submitted through Stripe, such as payment method details, billing email, invoices, customer IDs, subscriptions, and payment status. AI Council does not store full card numbers.
• API key labels and dashboard actions such as creating, revoking, or using keys.

Information Collected Automatically

• Usage metadata, including request time, account ID, host label, selected review mode, billing mode, credits charged, and request outcome.
• Technical metadata, including IP address, user agent, device/browser type, error events, response status, and security logs.
• Website metadata needed for hosting, analytics, abuse prevention, debugging, and traffic reliability.

Prompt and Model Processing

When you send a council-review request, AI Council may transmit the submitted prompt, instructions, metadata, and related context to one or more AI model providers so they can generate review feedback. Those providers process the content according to their own service terms and privacy commitments.

AI Council does not intentionally store raw prompt bodies or raw model response bodies in the customer account database. We may store usage metadata, error metadata, routing decisions, credit charges, and aggregate operational data so the product can bill, debug, enforce limits, and show dashboard history.

You should not submit passwords, private keys, production secrets, regulated personal data, health data, payment card data, or confidential third-party material unless your organization has approved that use and the relevant provider terms allow it.

How We Use Information

• Provide the website, dashboard, API, checkout, and support experience.
• Authenticate users, issue API keys, meter credit usage, enforce plan limits, and prevent abuse.
• Route requests to model providers and return council-review results.
• Process subscriptions, invoices, failed payments, refunds, and customer portal sessions through Stripe.
• Debug errors, monitor reliability, secure the service, investigate fraud, and improve product quality.
• Communicate about account issues, support requests, policy updates, billing events, and service changes.

How We Share Information

We do not sell personal information. We share information only where needed to run the service, comply with law, protect users, or support business operations.

• Stripe processes payments, subscriptions, invoices, checkout sessions, webhook events, and customer portal activity.
• Railway hosts the production API and related backend infrastructure.
• Vercel hosts the public website and static policy pages.
• AI model providers process council-review prompts and return model feedback.
• Service providers may help with security, logging, email, analytics, support, or infrastructure operations.
• We may disclose information if required by law, legal process, fraud investigation, chargeback review, or to protect rights, safety, and service integrity.

Cookies and Local Storage

The website and dashboard may use cookies, browser storage, or similar technologies to keep users signed in, remember endpoints, store local dashboard tokens, maintain UI state, and protect against abuse. You can clear browser storage, but doing so may sign you out or remove local settings.

Retention

We keep account and billing metadata for as long as needed to provide the service, comply with tax/accounting obligations, resolve disputes, enforce policies, and maintain security. Usage metadata may be retained for dashboard history, billing verification, analytics, and abuse prevention.

Support messages are retained while needed to resolve the request and maintain customer history. We delete or de-identify data when it is no longer reasonably needed, unless retention is required for legal, security, fraud-prevention, or accounting reasons.

Security

AI Council uses reasonable technical and organizational safeguards such as hashed passwords, hashed API keys, HTTPS, scoped credentials, access controls, and infrastructure security controls. No internet service can guarantee perfect security, so you should protect your account, rotate exposed keys, and avoid submitting secrets unless necessary.

Your Choices

• You can request account help, billing help, or data deletion through Support.
• You can revoke API keys in the dashboard and create new keys when needed.
• You can cancel subscription renewal through the dashboard or support flow when billing portal access is available.
• You can clear local browser storage to remove local tokens and dashboard settings from a device.

Children

AI Council is not directed to children under 13 and is intended for professional software and AI-agent workflows. Do not create an account or submit information if you are under 13.

Changes

We may update this Privacy Policy as the product, providers, or legal requirements change. The updated version will be posted on this page with a new effective date.

Contact

Privacy requests can be sent through Support.