I’m building PULSE so Torn players can follow progress over time, not just look at today’s totals. If you’d like to help make it happen, contributing API access is one practical way to support the project.
I want to make it easier to see how things change in Torn: who is making progress, how activity compares, and what happens over time. The plan is to use contributed keys to request selected public statistics about you and other Torn players and build community dashboards on PULSE, run by me through 7ZP.
The permitted categories are public player identity and activity snapshots for population discovery; employment; points bought and sold, trades, auctions and bazaar activity; combat outcomes and money mugged; drugs, overdoses, rehabilitation and consumables; travel, racing, revives, crime and jail activity, bounties, missions and progression; total networth; and public faction membership and ranked-war results. Only fields needed for configured datasets are collected. Historical availability and metric definitions are checked before publication; a complete year of data is not promised.
Dashboard designs are still being developed. The data categories we may collect are disclosed above. Collection uses the Torn API; this permission does not authorise page scraping or in-game actions.
What you’re agreeing to
Before you contribute
This is the scope of your permission today. A Public-access key describes its permissions; the key itself is confidential. Do not post it or send it in a message.
PULSE API-use disclosure · 2 October 2026
Data storage
Data sharing
Purpose of use
Key storage & sharing
Key access level
Your Torn player ID, encrypted key, consent version and dates, chosen request allowance, hashed management code and expiry are stored privately. Your key and contribution record are retained for up to 12 calendar months from submission, unless withdrawn sooner. Expired keys cannot be used and expired contribution records are automatically removed. Selected public observations, consent provenance and derived results are retained for the life of PULSE, including after withdrawal. Private PULSE data backups may retain that history; they exclude contributed keys. This contribution service does not configure off-host key backups.
Contribution details and individual source observations are private to the 7ZP operator and authorised PULSE server processes. Public dashboards show approved grouped statistics. Your key is never published or supplied to Grafana, Jobs, OBSIDIAN or another service. Grafana presents approved aggregate releases and receives no Torn keys. Player-level source records are not publicly released under these terms.
Non-malicious statistical analysis and public community dashboards on PULSE. Each submission sent for verification makes one Torn /key/info request to check ownership and permissions. Replacing a contribution may require a second submission and check. Eligible keys may then support operator-activated background API requests about you and other players within the categories disclosed above, including population discovery and public faction records.
Keys are encrypted on the server using AES-256-GCM and decrypted only in authorised PULSE processes when needed. Only the 7ZP operator can administer them. One active contribution per Torn account. Withdraw below to delete the retained key and contribution record, or revoke the key in Torn to prevent access. No cross-service key reuse or general-purpose access is authorised.
Only Public Only keys are accepted. Minimal, Limited, Full and Custom keys are not accepted. No private faction permissions are requested. Create a separate key for PULSE and keep it confidential.
How much of your API allowance?
Choose a maximum of 15, 30, 45, 60 or 75 requests per rolling 60 seconds. The default is 15. This is a limit for your Torn account across all keys supplied to PULSE, including verification and collection; it is not a separate allowance for each key.
Your choice is permission for up to that rate, not a promise of continuous use. Selecting an allowance does not activate collection.
Torn currently documents 100 requests per account per minute across all keys. Other tools share that allowance; PULSE cannot measure all their traffic or reserve the remaining capacity. Choose a limit that leaves room for your other tools. Existing Jobs and OBSIDIAN limits are unchanged. Raising your chosen allowance requires your explicit consent.
If you change your mind
Save the private management code shown after submission. Use it below to check or withdraw your contribution. Withdrawal deletes the stored key and stops new use. A request already sent to Torn may finish. Revoking the key in Torn also prevents further access. Expired contributions cannot be used.
Withdrawing your key stops future use and deletes your contribution record. Previously collected public observations and charts may remain for the life of PULSE; withdrawing a key will not automatically erase that public history. Contact 7ZP about corrections or removal. A material change to purpose, retention, sharing or permissions, or an increase above your agreed request allowance, requires new consent. Collection stores only the selected public observations needed for the configured datasets.
Create a key just for PULSE. Choose Public Only in Torn’s API settings. Keep the key private.
Read the terms and contribute below. One key per player. It is for PULSE alone, not Jobs, OBSIDIAN or another service.
Save your management code. You can check the expiry or withdraw your key here whenever you want.
Already contributed? Existing 90-day contributions keep their original expiry and remain ineligible for statistics collection. Existing 12-month contributions retain their original expiry, disclosed purpose and agreed request allowance; older contributions without a selected allowance remain limited to 10 per minute. To accept this disclosure or change your allowance, submit your key, choose a limit and explicitly confirm replacement. Replacement starts a new 12-calendar-month period and invalidates your old management code. Save the new code. Existing contributions are never upgraded automatically.
01 / Contribute
Contribute a key
This key is for PULSE only. It won’t be used by Jobs, OBSIDIAN or any other project, and submitting it won’t sign you in anywhere.
Your contribution is saved.
Shown once. Anyone with this code can check or withdraw your contribution. Keep it private; it is not stored in this browser.
02 / Your contribution
Manage your contribution
Use your private management code. No shared login and no need to enter your API key again.
Ending this session clears the codes displayed here. It does not withdraw a contribution or sign you out of Jobs or OBSIDIAN.
