Rose 1 production benchmarks are liveView API docs

How Adola handles account, prompt, and usage data.

Effective May 17, 2026. This policy explains what Adola collects, why we collect it, how we use processors, and how account deletion works.

Information we collect

Account information: your email address, name if provided, authentication method, workspace name, organization ID, project IDs, and session cookies.
Product information: API-key metadata, request timing, compression receipts, token counts, latency, billing plan, and dashboard usage needed to run the workspace.
Prompt information: the query, input context, model name, compression settings, and output produced when you use the hosted API, playground, or public demo.
Site information: page views, referrers, browser metadata, approximate request metadata, and analytics events used to understand product usage and abuse.

To provide prompt compression, return receipts, validate project-scoped API keys, enforce usage limits, and keep the dashboard accurate.
To secure the service, debug incidents, prevent abuse, investigate failed requests, and maintain reliable production infrastructure.
To operate billing, usage metering, checkout, billing portals, customer support, and product analytics.
To improve Adola and Rose 1 based on aggregate usage patterns and product feedback.

The public demo is meant for representative test snippets. Do not submit secrets, credentials, regulated data, private customer records, or anything you are not allowed to process through a hosted service.
Production workflows should use a signed-in workspace and project-scoped API key. Your downstream model-provider keys are not required by Adola.
We may retain request metadata and receipts for metering, debugging, billing, and abuse prevention. We do not sell prompt data.

We share information with service providers only as needed to run Adola, including hosting, storage, logging, analytics, authentication, payments, email, monitoring, and security tooling.
Payment processing and billing portals may be handled by Stripe or another payment processor. Their systems may retain billing records required for tax, fraud prevention, dispute, and compliance purposes.
We may disclose information if required by law, to protect the service, or to investigate security and abuse issues.

You can delete your account from Dashboard Settings. Deletion removes your user account, owned workspace, projects, API keys, usage events, and local billing account record from the Adola application database.
After deletion, Adola clears the active session. Analytics events are detached from your user and organization identifiers so aggregate counts can remain without pointing back to the deleted account.
Some records may remain outside the application database where retention is required or controlled by third-party processors, such as payment invoices, bank records, backups, security logs, and legally required audit records.

Adola uses HTTPS in production, HTTP-only session cookies, hashed passwords for password signup, bearer API keys, scoped project access, rate limits, and operational logging.
No internet service is perfectly secure. Keep API keys server-side, rotate keys if they may have leaked, and avoid submitting secrets to the public demo.

You can sign out, revoke API keys, delete your account, or contact us about access, correction, export, or deletion questions.
You can block cookies in your browser, but account sessions and some product features may stop working.
For privacy questions, contact privacy@adola.app from the email associated with your workspace when possible.