Loading
API Terms of Service
| Data Storage | Data Sharing | Purpose of Use | Key Storage & Sharing | Key Access Level |
|---|---|---|---|---|
| We store account identity and access-check results. If you enable Member Roster, we persist member IDs, names, levels, positions, status, last-action time and first/last observation times in our cyon database. Departed members are retained for up to 30 days after last observation and removed on the next successful refresh after that period. Member Activity compares saved rosters to record joins, returns, departures and faction position changes. Event details are visible to faction leadership and eligible for cleanup on roster refresh after 90 days from observation or classification. Unresolved departure work stays available until resolved. For a verified departure we keep its Torn news ID and event time. For a verified kick we also keep the linked officer ID and up to 240 characters of the stated reason. Raw membership-news responses are transient. Private backups can retain expired detail temporarily. Current roster data stays until replaced or the faction dataset is removed; deleting a web account does not delete shared faction records. Attack records from access checks are not saved. After you agree to the updated terms, the foundation also records hashed key fingerprints, verified ownership, request attempts, quota/backoff and permission metadata. Request-attempt metadata becomes eligible for lazy removal after the applicable quota windows, on subsequent requests; ownership and blocked-key metadata may persist until replaced or administratively removed. Malformed responses may be kept encrypted outside the webroot for diagnostics, limited to 32 files, with each source response capped at 1 MiB before encoding, compression and encryption. Files older than 24 hours are removed on the next rejected response; this is not a guaranteed deletion time. Account deletion removes account-bound ownership/proofs, but per-player request-limit and key-fingerprint records may remain. Encrypted diagnostic files follow the same lazy-expiry policy after account deletion. Chain Analytics stores chain reports, finished attack records and compressed source records in an isolated database. Records in the retained pilot are kept privately until the hosting administrator removes them. A time-limited preview shows its storage deadline. Unified Import can save incoming and outgoing faction attacks for the selected dates. Opening Import, changing dates and checking saved coverage use local data. Torn requests begin when you explicitly check access, find chains, import or re-verify.Opening Chains → Import may recheck expired faction access with Torn after consent. Viewing a saved report does not fetch chain or attack records. Participation keeps verified monthly membership intervals for historical reports. Cached membership transitions and incomplete monthly checks become eligible for removal after 90 days. | Your account profile and key-check result stay private to your account. Authorized users in the same faction can reuse saved chain results. Raw source records stay private. Membership News and departure classification are limited to verified faction leadership. The enabled roster is shared with signed-in, currently verified CoC members who enable this feature. The hosting administrator can access stored data for maintenance. We do not publish roster data or send keys to other members or services. | Link your Torn identity, verify CoC membership and check faction attack access. After you enable Member Roster, opening Faction overview or Members may check your membership and refresh the shared roster if older than five minutes. Member Activity uses saved roster observations. With current leadership and faction API access, opening Home or refreshing the roster may request Torn faction membership news using your saved key to verify departures. No scheduled polling runs. Other checks run when requested. Remember me restores login only, not current faction membership or leadership. Fixture-only access never grants live chain data or monthly approval permissions. | Your key is encrypted on our cyon server and sent to Torn for the identity, access checks and enabled roster described here. The saved key is visible in your signed-in account. You can remove it in your account settings. | Public access supports identity and the basic member roster (key/info and faction/members). This roster does not use private revive settings. Reading faction attacks in the separate Check action requires a Limited key and Faction API Access permission. |
tofato counts requests it sends across features separately for each Torn player. Torn counts all requests for that player across their keys and apps. Reading saved faction data uses no Torn data requests, though tofato may need to recheck access.
The private Faction API calls counter keeps a cumulative total for your web account. It counts requests tofato sends to Torn faction endpoints, including failed attempts. The total is deleted with your account.