Data collected
- Your Torn ID, username, faction identity and key access summary.
- The relevant gym, item-use, refill, bust, travel and racing log records inside the event window.
- Your outgoing attacks inside the event window, including respect gained.
- Riddle attempts as one-way answer hashes, revealed-hint records, Christmas Cracker and Santa’s Grotto results, scores, prize requests and audit history.
- Faction chain reports needed to calculate hits and respect, including the Torn IDs and totals of faction members in those reports.
- For the admin-only Chain Bonus Hitters table: current faction member IDs and names, completed faction chain IDs and end dates, and the member and chain position for each bonus hit from the past three years. Other chain report details are not kept for this table.
- Basic security information such as sign-in time and administrator action IP address.
Purpose
The data is used to operate AK Christmas: verify eligibility, calculate progress, resolve scoring questions, display the leaderboard, generate participant/admin reports and let admins review faction chain bonus history. It is not sold, used for advertising or shared outside event administration except where required to operate the service or by law.
API key security
Your dedicated API key is encrypted before it is stored. The encryption secret is held separately in server configuration. Keys are sent only to Torn’s API over HTTPS, are never put in page URLs or exports, and are not shown back to admins. You can revoke the key at any time in Torn; the next sync will then ask you to provide a replacement.
Access
You can see your own scorecard, activity totals, riddle status and export. Other participants see leaderboard names and scores, not your raw records or key. Lone_Wanderer, Cassandra and Flying_Dutchman have administrator access to event reports, raw activity needed for verification, configuration, exports and the Chain Bonus Hitters table.
Storage and retention
Application data is stored in the configured MySQL database. The default retention period for event data is 90 days after an event; admins can change that period. Chain Bonus Hitters history uses a separate rolling three-year window based on each chain's end date; older chain and bonus records are removed during its scheduled check. Current member names and IDs are refreshed daily. Backups and server logs may take additional time to expire. The deployment runbook includes a scheduled clean-up procedure.
Your choices
Participation is optional. You may revoke the key in Torn, ask an admin to withdraw you, request a copy through your own Excel export, or ask an admin to correct or delete your record where event verification no longer requires it.
Contact
Contact Lone_Wanderer, Cassandra or Flying_Dutchman through Torn for privacy, access or scoring questions. Do not send an API key in a Torn message.