What we store, and what we do not

Account name, billing email, Stripe customer ID, billing mode, seat limit, and account status. For each user: email and role. For each subscription: SKU, tier, Stripe subscription ID, and current period end.

API keys are stored hashed. When a key is first issued, the plaintext value is held server-side for up to two minutes, solely to display it to you once at creation, then deleted; it is never stored beyond that window. We also keep the key's label and last-used timestamp. Magic-link sign-in tokens are stored hashed in the same way. Sessions record the IP address and user-agent used to sign in, plus an expiry.

For each connected machine: hostname, OS, a device fingerprint, and timestamps. For each skill run: which skill ran, its mode, and when. This is metadata only, never the content of what ran.

We record account-level actions (sign-ins, upgrades, cancellations, and similar) as an action name plus metadata. These records have no automatic expiry. Two of these actions include free text you type yourself:

• Submitting the portal's upgrade request form stores your note under the account.upgrade_requested action.
• Submitting the portal's feedback form stores your message under the account.feedback_submitted action.

We keep both indefinitely, with no automatic expiry, as part of the audit log.

TigerTiger does not store your vault content, conversation transcripts, prompts, model responses, or file contents from skill executions. This applies across the platform, for every account. Skill runs are logged as metadata only (which skill, which mode, when), never as content.

Email hello@tigertiger.ai with any privacy question.