Legal
Privacy Policy
Last updated: 13 October 2026
This Privacy Policy explains how Sagefire.cc handles personal information when you use the website, connect a Torn account, use faction tools, or interact with Sagefire services.
1. Who is responsible for your information
Sagefire.cc is owned and operated by Anth Richardson, who is the data controller for personal information processed through Sagefire.cc.
References to Sagefire in this Privacy Policy describe the Sagefire service and brand operated by Anth Richardson. Original Sagefire intellectual property is owned by Anth Richardson except where third-party rights are expressly identified. This ownership statement does not claim any Torn, Discord, Cloudflare or other third-party intellectual property.
Sagefire.cc is an independent faction service and is not operated by, endorsed by, or part of TORN LTD.
2. Who Sagefire is for
Sagefire is designed for authorised Torn players using Sagefire faction services. It is not designed or marketed specifically for children.
You must be at least 13 years old to use Sagefire. You must also meet any higher minimum age that Torn or the law applicable to you requires. If we become aware that an account belongs to someone below the applicable minimum age, access may be removed and personal information deleted or restricted where appropriate.
3. Information we collect
Information from your Torn account and the Torn API
- Torn user ID, player name, faction identity and membership information.
- Discord identity information exposed by Torn where available.
- Player status information used by Sagefire features, including bars, cooldowns, travel, refills, organised crime, personal statistics, perks, education, battle stats, net worth, bank investment and bounty presence.
- Personal inventory information used by supported features, including item names, Torn item IDs, quantities and whether an item is faction-owned. This information is not public to other Sagefire members through My Items.
- Trade information used for supported exchange workflows, including trade IDs, participants, items, quantities, cash values and completion timestamps where available.
- Faction, war, armoury, organised-crime and other game information used by the Sagefire services available to you.
- Metadata about the permissions and health of the Torn API key you connect.
Your Torn API key
Sagefire accepts a dedicated Torn Custom API key. The key is validated with Torn, encrypted before storage, and used by Sagefire services to make read-only Torn API requests. Sagefire does not ask for or store your Torn password.
Inventory and trade verification
Museum Access uses your authorised Torn inventory data to identify Museum-ready items and complete sets. Sagefire requests only the Museum-relevant inventory categories it needs for this feature: Artifacts, Flowers and Plushies. Torn may cache inventory information, so the snapshot shown by Sagefire may not reflect a change immediately.
When you create an eligible Museum request, Sagefire may retain the Torn item IDs, item names and quantities needed for that request so it can later compare them with a completed Torn trade. Marketplace and Museum workflows may also read recent trade summaries and individual trade details to verify that the correct people, items, quantities or payment were involved. Where a match is confirmed, Sagefire may retain minimal verification evidence such as the Torn trade ID, completion time, related Sagefire request or reservation and verification metadata.
These permissions are used to read and verify game data only. Sagefire cannot use them to create a Torn trade, accept a trade, transfer items or move Torn money on your behalf.
Sagefire account and activity information
- Sagefire account identifiers, account status, platform roles and permission grants.
- Browser session records used to keep you signed in securely.
- Events, RSVPs, attendance records and other participation information.
- Assignments, completion records and other faction workflow information.
- Faction activity observations and longer-term aggregated activity history used for operational reporting, faction health and authorised analytics.
- Administrative and security audit records.
Profile visibility defaults
Member profiles are visible to other authorised Sagefire members by default. Recent Progression is visible to other authorised Sagefire members by default, while your Ember balance is hidden from other members by default. You can change these settings from your own Sagefire profile. Your own profile continues to show information to you even where you have chosen not to share it with other members.
Private member metrics
Private metrics such as your battle stats, net worth, education and bank timers, and bounty presence are only visible to you. Sagefire does not expose these values through the member directory, member profiles, leadership views or administration screens.
Where Performance or Insights features use your authorised Torn data, Sagefire may retain periodic historical observations of selected private metrics and personal-stat counters so it can show changes, trends and comparisons over time. These longitudinal observations remain private to your account by default and are not made available to other members or leadership merely because Sagefire stores them. Sagefire records only the selected metric values needed for these features rather than retaining the raw Torn API response or your API key alongside each observation.
Your personal inventory snapshot is not exposed as general member-directory information. Where a Museum or Marketplace workflow is collaborative, authorised participants may see the request, reservation or verification state needed to complete that workflow, rather than unrestricted access to your wider inventory or trade history.
Discord information
Where Sagefire has a Discord identity for you, the service may process your Discord user ID, display name, server membership state and relevant Discord roles. Sagefire may obtain this from a direct Sagefire link, from Torn-provided Discord information, or from existing Sagefire bot mappings.
Merch purchase verification
If you choose to verify an official Sagefire merch purchase for an achievement, Sagefire temporarily processes the Printify order reference and checkout email address you provide. These details are used only to compare your claim with the corresponding Printify order and are not retained after verification.
For a successful verification, Sagefire retains your Sagefire account ID, a one-way keyed fingerprint of the Printify order ID, the number of items in the order, and verification timestamps. This prevents one order being used to verify multiple Sagefire accounts without retaining the raw order number or buyer contact and delivery details.
Technical information
Web hosting, security and infrastructure services may process technical information such as IP address, browser/device information, request timestamps, error information and server logs needed to deliver and protect Sagefire.cc.
We do not intentionally collect special-category personal information such as health, religion, political opinions, sexual orientation or biometric information through Sagefire.cc.
4. Torn API transparency
Torn requires API services that store keys or API data to clearly explain how the key and resulting data are used.
| Data Storage | Data Sharing | Purpose of Use | Key Storage & Sharing | Key Access Level |
|---|---|---|---|---|
| Persistent until your Sagefire account is deleted or your connection is revoked. Some derived faction, workflow, verification and audit records may be retained where necessary for platform integrity, security or legitimate faction records. | Sagefire service operators and authorised faction users where a Sagefire feature is specifically designed to share faction information. Your API key itself is not shared with faction members. | Sagefire member authentication, player-development tools, faction operations, readiness information, notifications, inventory-assisted Museum requests, Marketplace and Museum trade verification, and other Sagefire faction services described in the product. | Stored remotely in encrypted form and used only by Sagefire services. The key is not intentionally shared with faction members or unrelated third-party services. | Custom key only. Sagefire does not require or accept Full or Limited Access keys for the normal member connection. |
Current required custom-key selections are:
user → basic, faction, discord, bars, cooldowns, travel, notifications, refills, organizedcrime, personalstats, perks, education, battlestats, hof, money, bounties, trade, trades, inventory.
Sagefire also checks Torn's key-information endpoint to confirm permissions. Torn may report additional
default selections on Custom keys that the user cannot remove.
The inventory selection supports inventory-aware features such as Museum Access. The
trade and trades selections support read-only verification of eligible Marketplace
and Museum exchanges. Sagefire API access remains read-only: Sagefire does not use your Torn password and
does not automate non-API actions in Torn.
5. Where we get information from
We obtain personal information from:
- you, when you connect or use Sagefire;
- the Torn API and Torn account information you authorise Sagefire to access;
- Sagefire's own Discord bots and platform mappings where a Discord identity is already known;
- authorised Sagefire faction administrators when they create events, assignments, attendance records, roles or other faction workflows;
- Printify, when you ask Sagefire to verify an official merch purchase; and
- our web, hosting and security infrastructure when requests are made to Sagefire.cc.
6. Why we use your information and our lawful bases
Depending on the information and feature involved, Sagefire processes personal information to:
- create, authenticate and operate your Sagefire account;
- provide member dashboards, player-development tools and faction services;
- support wars, organised crimes, events, assignments, armoury and other faction workflows;
- provide inventory-assisted Museum requests and verify eligible Marketplace or Museum exchanges against completed Torn trades;
- privately verify official Sagefire merch purchases and award the related Sagefire achievement and progression rewards;
- show information to authorised faction users where a feature is designed to be shared;
- administer permissions and member access;
- detect faults, prevent abuse, secure accounts and investigate incidents;
- maintain audit records and protect the integrity of the service;
- respond to support, privacy and account requests; and
- comply with legal obligations.
Our lawful bases may include performance of our agreement with you where processing is necessary to provide the Sagefire service you request, legitimate interests in operating, securing and administering a faction platform, legal obligation where required by law, and consent where we specifically ask for it for an optional purpose.
7. Who we share information with
Personal information may be available to:
- Anth Richardson as the operator of Sagefire.cc;
- authorised Sagefire faction leaders or administrators where their role requires access;
- other faction members where a feature is intentionally collaborative or faction-visible;
- Cloudflare, which provides web delivery and security infrastructure;
- OVHcloud and related hosting infrastructure used to operate Sagefire services and databases;
- Torn, when Sagefire makes authorised API requests on your behalf;
- Discord, where a feature uses Discord integrations or Sagefire bots;
- Printify, where you request verification of an official Sagefire merch purchase; and
- law-enforcement, regulators or other parties where disclosure is legally required.
Sagefire does not sell your personal information and does not use your personal information for third-party advertising.
8. International transfers
Some infrastructure or third-party services used by Sagefire may process information outside the United Kingdom. Where UK data-protection law requires safeguards for an international transfer, we will rely on an appropriate lawful transfer mechanism or the safeguards provided by the relevant service provider.
9. Cookies and browser storage
Sagefire currently uses storage that is necessary for the service or its basic operation rather than advertising or behavioural tracking.
- Sagefire session cookie: a Secure, HttpOnly cookie used to keep an authenticated member signed in.
- Forge intro preference: local browser storage may remember that you have already viewed the Forge introduction so it does not replay unnecessarily.
Sagefire does not currently use advertising cookies, behavioural advertising pixels or third-party analytics cookies. If non-essential tracking is introduced later, this notice and any required consent controls will be updated first.
10. How long we keep information
We keep personal information only for as long as reasonably necessary for the purpose for which it is used, to maintain security and platform integrity, to preserve legitimate faction records, or to comply with legal obligations.
- Active account information is kept while your Sagefire account remains active.
- Torn API credentials are kept until revoked, replaced or removed as part of account deletion.
- Browser sessions are kept until they expire or are revoked.
- Private longitudinal Performance/Insights observations may be retained while your Sagefire account remains active so you can view meaningful historical trends. These observations are removed when the platform account is soft-deleted.
- Hourly faction activity observations may be retained for a limited rolling period and converted into smaller daily historical summaries for longer-term faction reporting.
- Event, assignment, attendance, war, armoury, Marketplace, Museum and similar workflow records may be retained as faction or service history where there is a legitimate operational reason to do so.
- For War Dibs claim-attempt tracking, identifiable claim and outcome evidence is retained for up to 180 days after the recorded end of a completed ranked war, then deleted or irreversibly anonymised. We do not infer missing war-end dates. Records without a reliably recorded end date are reviewed separately, not automatically treated as eligible for expiry. Older War History, underlying attack records, payout records and security/audit evidence may be covered by their own retention obligations and access restrictions.
- Trade-verification evidence may be retained with the related Sagefire workflow to prevent duplicate matching, support auditability and resolve disputes or errors.
- Merch verification retains a one-way order fingerprint and minimal verification metadata while needed to prevent duplicate achievement claims. The checkout email and raw order reference submitted for verification are not retained.
- Security and audit records may be retained for longer where needed to investigate incidents, maintain accountability or defend legal claims.
- Infrastructure logs are kept according to the operational and security needs of Sagefire and its infrastructure providers.
Sagefire currently uses a soft-delete model for platform accounts. When an account is deleted, active browser sessions and stored platform credentials are revoked, platform roles are removed and the direct platform Discord link is cleared. A minimal account record and historical references may remain where required to preserve auditability, security and faction records.
11. Security
Sagefire uses technical and organisational measures designed to protect personal information. This includes encrypted storage of Torn API credentials, Secure HttpOnly session cookies, least-privilege Torn keys, service-to-service authentication, role-based access controls and audit logging for sensitive platform operations.
No online service can guarantee absolute security. If you believe your Sagefire account, Torn API key or other information has been compromised, contact us promptly and revoke the affected Torn key.
12. Your data-protection rights
Depending on the circumstances, UK data-protection law may give you rights to:
- ask for access to personal information we hold about you;
- ask us to correct inaccurate or incomplete information;
- ask us to erase personal information in certain circumstances;
- ask us to restrict how information is used;
- object to processing based on legitimate interests;
- receive certain information in a portable format where the right applies;
- withdraw consent where processing is based on consent; and
- complain to the UK Information Commissioner's Office (ICO).
To exercise a privacy right, contact anth@sagefire.cc. We may need to verify your identity before acting on a request.
13. Automated processing
Sagefire may automatically prioritise or display game and faction information, such as items in Your focus. Sagefire may also automatically compare eligible completed Torn trades with a Marketplace reservation or Museum request and update that workflow when an exact match is found. Sagefire does not currently make solely automated decisions about you that produce legal or similarly significant real-world effects.
14. Third-party links, profile images and services
Sagefire links to and integrates with third-party services such as Torn and Discord. Their own privacy policies and terms apply when you use those services. Sagefire is not responsible for the privacy practices of third-party websites.
If you choose a direct Torn profile image for your Sagefire profile, Sagefire stores the image address and your browser makes a request to that image host when the profile is displayed. The image host may therefore receive ordinary request information such as your IP address and browser details. Custom profile images you upload are resized in your browser and then uploaded to Sagefire-managed storage. Images embedded in curated Sagefire Resources are served through Sagefire's managed media endpoint rather than arbitrary external image URLs.
External links in curated Resources may open a third-party website in a new browser tab. Sagefire applies link-safety controls to those links, but the third party's own terms and privacy practices apply once you leave Sagefire.
15. Changes to this Privacy Policy
We may update this Privacy Policy as Sagefire develops or legal requirements change. The current version will be published at /privacy with an updated date. Material changes may also be announced through Sagefire or faction communication channels.
16. Contact
Questions, privacy requests or concerns can be sent to:
© 2026 Anth Richardson. All rights reserved. Sagefire™.