I’m building PULSE to make Torn’s public stats easier to follow over time. The idea is to turn player progress and faction activity into charts the community can explore.
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 other Torn players and build community dashboards in Grafana, run by me through 7ZP.
That includes activity such as travel, trading, consumable use, racing and revives, alongside public faction membership and ranked-war results. Some comparisons will be calculated from those records. I’m still working out the features and checking how much history is available, so I can’t promise a complete year of data.
I’m keeping the full feature list under wraps for now. What I’ll do with your key is set out below.
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 · 30 September 2026
Data storage
Data sharing
Purpose of use
Key storage & sharing
Key access level
Today: your Torn player ID, encrypted key, consent version and dates, a hashed management code and contribution expiry. No player statistics are collected. Contribution records are held for up to 90 days unless withdrawn sooner. Future public observations and derived charts are planned to remain for the life of PULSE, including after a contributed key is withdrawn. No off-host contribution backups are created in this release.
Contribution details are private to the 7ZP operator. Your key is never published or supplied to Grafana, Jobs or OBSIDIAN. Later, selected public records and derived charts are intended for community viewing; that does not make your key public.
One immediate Torn /key/info request verifies your key’s owner and permissions. After that, it is held unused. Proposed later use: background requests for other players’ selected public statistics and public faction records, only for PULSE analysis and community dashboards.
Encrypted on the server using AES-256-GCM. Only the 7ZP operator can administer stored keys. One active key per player. Withdraw below to delete the retained key immediately, or revoke it in Torn. No cross-service 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?
Proposed PULSE limit: 10 requests per contributing player per rolling 60 seconds, including verification and any later collection, across all supplied keys—not 10 per key. This release makes no background requests.
Other services’ requests are additional and use the same Torn account allowance. Torn currently documents 100 requests per user per minute across their keys. Ten PULSE requests do not reserve the rest. Existing shared 7ZP Jobs/OBSIDIAN accounting and its 50-request limit remain unchanged.
If you change your mind
Save the private management code shown after submission. Use it below to check or withdraw your contribution. Withdrawal removes the stored key immediately; revoking the key in Torn also prevents access. Expired contributions cannot be used.
Withdrawing your key stops future use and deletes your contribution record. If collection starts later, 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 or permissions will require new consent. No statistics are stored today.
Read Torn’s current official API terms and limits and API documentation. The PULSE programme and its 10-request ceiling are our proposal, not Torn requirements or Torn approval of a pooled-key programme. Questions or lost management code? Contact the 7ZP operator without sending your key.
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 key is saved for later.
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.
