EmuControl Companion Privacy Policy
Last updated: 5 October 2026
Overview
EmuControl Companion is an EmuControl userscript for Torn faction war coordination. It adds shared call buttons, rally pings, war row enhancements, and war event logs for EMU faction members.
Data Used
- Torn API key entered by the user.
- Torn player names and IDs visible on supported Torn pages.
- Faction IDs, ranked war IDs, war status, member status, hospital timers, travel indicators, and attack-page rally events.
- For the dashboard Raid Room, raid attack IDs and times, attacker and defender names, player IDs and factions, results, respect gained, and derived faction/member attack counts.
- While a Companion user has an active attack page during a tracked raid, automatic short-lived check-ins may include that user's name, player ID and faction, the target's name and ID, a reported battle-stat estimate (not verified exact stats) if available, and the last report time. Other fighters may not be visible.
- Optional Energy, Drug cooldown, Booster cooldown, and Medical cooldown values read from the user's Torn page or fetched with that member's stored API key, then shared only with authenticated users in the same faction.
- Local userscript settings such as enabled state, auto-sort, and travel speed mode.
- If device notifications are enabled, the browser push endpoint, browser-generated public encryption keys, device label, alert preferences, authenticated Torn player ID, and faction ID.
- If the user presses Quick Revive, their authenticated Torn player ID is used as both the requester and revive target ID.
API Keys
The userscript stores the API key locally in the browser or TornPDA script storage. If a key is submitted to EmuControl services, server-side storage follows EmuControl's API pool behaviour. EmuControl may use that member's stored key to refresh their Energy, Drug cooldown, Booster cooldown, and Medical cooldown values for same-faction war coordination. API keys are never returned in the telemetry response or shown publicly in the userscript UI.
An optional FFScouter key is stored locally and sent directly to FFScouter for key validation and battle-stat estimates. It is not sent to EmuControl.
How Data Is Used
Data is used to authenticate the user, verify faction access, sync shared war calls, send rally notifications to other active script users, deliver optional background chain and assistance alerts, display war status, support leadership event review, and build the shared dashboard Raid Room feed and totals.
Sharing
War calls, rally events, and the latest optional cooldown labels may be visible to other authorized users in the same faction who are using EmuControl tools. EmuControl does not sell userscript data.
The Raid Room's named attack records and derived faction/member counts are stored on the private EmuControl server for the current or last tracked raid and shown to approved Emu and Nameless dashboard viewers. Short-lived Companion-reported fight check-ins and participant names may also be shown to those viewers while a raid fight is recently reported; these are not a complete or Torn-confirmed live participant list. A new raid session replaces the prior raid cache. Torn API keys are never included in the raid feed.
When device notifications are enabled, encrypted messages are delivered through the push service operated by the member's browser or device vendor. Torn API keys are not included in push subscriptions or notification messages.
Quick Revive is an optional Pennywise Medical integration. Only when the user presses the button, the Companion sends the requester and target Torn player IDs directly to Pennywise Medical at torntraders.com. The user's Torn API key is never sent to Pennywise Medical. Pennywise Medical's revive availability, payment terms, and handling of the request apply.
Automation Limits
EmuControl Companion does not auto-attack, auto-buy, auto-mug, or automate gameplay actions. The user remains responsible for all Torn actions.
Contact And Removal
Device notifications can be disabled per device from dashboard Settings. The local browser subscription is removed immediately; expired push subscriptions are also removed automatically. For access removal or privacy questions, contact EMU HQ leadership or the EmuControl administrator.