Privacy Policy

This policy explains what data Elis AI collects, how it is used and stored, and the choices you have — including for the Elis Token Saver connector for Claude, ChatGPT, and Codex.

Last updated: November 8, 2026

Data we collect

  • Account data — email address, name, organization membership, and authentication identifiers.
  • Content you submit — chat messages, uploaded files, and other content you provide to the platform.
  • Token Saver planner inputs — when a host app (Claude, ChatGPT, Codex) calls the Elis Token Saver connector: the plan goal, task titles and instructions, host capability flags, and reported task results.
  • Usage and measurement data — token usage metrics reported by the host, model identifiers, and plan outcomes. Reported usage is recorded as measurement and estimation data. Depending on the active Token Saver settlement mode and report, it can also affect the amount charged. Missing or unusable reports may fall back to the reserved estimate and be flagged for review. Settlement details show the basis applied.
  • Feedback — ratings, feedback facets, and free-text notes you choose to submit.
  • Operational data — service logs, request metadata, and referral or campaign attribution parameters where present.

How we use and store your data

We use the data above to operate the service: planning and executing your requests, metering usage, billing, support, and improving estimate accuracy.

Proven-chain storage (Token Saver): for authenticated users, plans that finish successfully may be stored privately in your organization or personal scope so similar future goals can reuse the proven task chain. Stored chains are private to your tenant by default and are never shared with other customers unless you or your organization explicitly opt in to community sharing. Organization-scoped tokens store chains in the organization's scope and settle from the organization wallet, drawing first on that wallet's own pooled daily free grant; organization admins can view member runs on the organization's observability page. Personal tokens store chains in your personal scope and settle from your personal wallet, drawing first on that wallet's own daily free grant. You can opt any plan out by passing constraints.no_store when starting it; anonymous local/dev trial plans are not stored.

Community sharing (Settings → Data Privacy): community sharing is off unless you turn it on. The “Share redacted proven chains, graduated agents and task results with the community (opt-in)” option starts cleared on the terms-acceptance and setup screens — accepting the Terms does not enable it — and you can switch it on or off at any time in Settings. Organizations likewise remain off until explicitly turned on. While it is on, proven task chains and agent templates from your scope may be shared with other participants who have also opted in, and you may in turn recall theirs. Chains and agents are always redacted and safety-scanned first, and only task structure and agent templates are shared from them. Task results may be shared too, to improve model size suggestions for everyone who shares: for each task a numeric fingerprint of its text, the model it ran on, its cost and whether it passed. No task text is shared. Nothing that is shared contains raw prompts, uploaded files, secrets, or identifiers that could reveal you or your organization to other participants. If you opted in before task results were added to these terms, your chains and agents keep being shared as before, and no task results are shared, or used for your suggestions, until you accept the updated terms in Settings. Only other opted-in participants can see or recall shared items; a scope that has not opted in cannot see or recall the community pool (reciprocity). Turning the setting off stops any new sharing going forward and removes your task results from the pool; you can also exclude a single plan from sharing at any time with constraints.no_community even while the scope-level setting is on.

Learning signals: feedback and outcome grades are used as tenant-scoped learning data to improve planning and routing for your account or organization. If community sharing is enabled for your scope, outcome grades on chains and agents shared to or recalled from the community pool also contribute to cross-tenant proving (promotion to active status) for that shared copy only — your private tenant-scoped chain and its learning signals are unaffected.

Third-party sharing

We do not sell personal data. We share data with service providers acting on our behalf — including payment processing (Stripe) and cloud infrastructure providers. For AI generation requests made through the Elis AI platform, the content needed to process the request is sent to the selected miner allowed by your account or organization settings.

Data retention and deletion

Account data and stored content are retained while your account is active. Idle Token Saver plans expire automatically. To request deletion of your account or specific data, contact support@tryelisai.com.

Security

Data is encrypted in transit. Connector access uses OAuth 2.1 with scoped tokens: tokens issued to the Token Saver connector carry a limited scope and are rejected by the general Elis API.

Contact

Questions about this policy or your data: support@tryelisai.com. See also our terms of service.