Privacy Policy

AI Reserve (operated by Audacity Advisory Corp) provides an enterprise AI platform: organizations fund a wallet and their people use AI models from many providers through one gateway, one set of keys, and one ledger. This policy explains what we collect, why, and the controls you and your organization have. Where your organization has signed a Terms of Service or Data Processing Addendum with us, those agreements govern.

• Account information — name, work email, organization, role, and authentication identifiers.
• Usage metadata — for every request: model, token counts, cost, latency, status, and which user, key, and team it belongs to. This is billing and spend-governance data; it contains no message text.
• Prompt and response content — by default we store message text to power chat history, search, audit, and usage analytics. Your organization can turn this off entirely (see "Content storage controls").
• Documents — files you or your organization upload in the web app for use with AI features; you can delete these at any time from the web app. Files attached through other interfaces (for example Claude Desktop or an API integration) are not uploaded to or stored by us as documents — they pass through to the model provider as part of the request, covered by the content storage controls below.

• Providing the service: routing requests, chat history, document features.
• Metering and billing: every request is attributed and counted against your organization's budgets.
• Security and abuse prevention: authentication, rate limiting, anomaly detection.
• Usage analytics for your organization's administrators, including optional business-function classification of usage. Classification categorizes spend by the standing purpose of each API key and team, read from its name, description, and organizational context (details your organization sets itself, like team names, structure, and which user or team a key belongs to) — it does not read message text. Text snapshots captured by an earlier, retired version of the classifier remain included in content purges and account deletion. Classification is off for new organizations until an administrator enables it, and administrators can disable it at any time.

We do not use identifiable customer data to train AI models, and we do not sell personal information.

Enterprise administrators can disable prompt and response storage for their whole organization ("Store prompt & response content" in the admin console). While off, no message text is persisted — only the usage metadata above. Administrators can also permanently delete all previously stored content for their organization on demand (including legacy classification text snapshots), or set an automatic retention window that deletes stored content older than a chosen number of days.

Your prompts are processed by the AI provider serving the model you chose (for example OpenAI, Anthropic, Google, or AWS Bedrock). Each provider's retention and training posture differs; we document them per provider on our Data Handling page, and we list all subprocessors on the Subprocessors page.

Data is encrypted in transit and at rest. Access is role-based and scoped to your organization (tenant isolation). The platform runs on infrastructure certified to SOC 2 Type II and ISO 27001 (Google Cloud). Requests are processed in the United States.

We use a small set of first-party cookies to keep you signed in and to remember your preferences. We do not use analytics, advertising, or third-party tracking cookies, and we do not track you across other sites.

• __session — keeps you securely signed in. Strictly necessary; expires after 12 days.
• aud_session_hint — a companion to the sign-in cookie that lets our site send a signed-in browser straight to the app instead of the landing page. It contains no personal data and expires with the sign-in cookie. Strictly necessary; expires after 12 days.
• NEXT_LOCALE — remembers your language choice. Preference; expires after 1 year.
• sidebar_state and sidebar_width — remember how you arranged the app's sidebar. Preference; expire after 7 days.
• __impersonation — set only in our own staff administrators' browsers during an authorized, audit-logged support session; never set for regular users. Expires after 4 hours.
• share_gate — remembers that you entered a share page's access password so you are not asked again; the unlocked link you are given is the primary way back in, and this cookie is a convenience. Set only on that page; expires after 24 hours.

Beyond cookies, we use your browser's local storage for similar interface state — for example panel sizes, which chat you last had open, and your sign-in state (kept by Firebase Authentication). These values exist to run the product: most never leave your device, and the rest (like the id of the chat to reopen) reach our servers only as part of the feature they power. None are used for analytics, advertising, or tracking.

You can view, block, or delete cookies at any time in your browser's settings. Because we set no tracking cookies, there is nothing to opt out of: blocking the strictly necessary cookies prevents sign-in, and blocking the preference cookies only means your language and layout choices are not remembered.

• Delete your data — from your profile you can delete all your chats and documents while keeping your account, or delete your account entirely.
• Organization-level deletion — enterprise administrators can purge all stored message content for their organization.
• Access and correction — contact your organization's administrator or our team to access or correct your account information.

Depending on where you live, you may have additional rights under laws such as GDPR or CCPA/CPRA; we honor verified requests consistent with those laws.

Usage metadata is retained for the life of the account for billing integrity and audit. Stored message content (including legacy classification text snapshots) remains until you or your organization deletes it, until an organization-configured retention window removes it, or immediately stops accruing when content storage is turned off. Deleting a user account deletes that user's stored content. Deleted content is removed from production systems promptly and from backups on their rotation schedule.

We will update this page when our practices change, and material changes will be communicated to organization administrators. Questions or requests: contact your AI Reserve account team through the portal.