Last updated 2026-11-16.
AllyLog is a personal project I run myself, not a company. I’m the one who decides what’s collected and why, and the one to contact about any of it — on Discord: birutek.
No email address is collected today. A field for one exists so a future password-reset feature can use it, but nothing writes to it yet. This page will be updated, with the change called out, before that field is actually used.
To run the app: show your alliance’s dashboard, match screenshot data to your roster, and keep an accurate participation/reward history — the service your leader asked me to set up. The accountability and security records exist to keep the app usable and abuse-resistant for everyone sharing it.
Access is scoped to your own alliance: members see their own dashboard and their alliance’s public info; deputies and leaders see and manage their alliance’s full roster and history. Nobody can see another alliance’s data. Only I can access the database and uploaded screenshots, and only for support you asked for, errors, security, abuse or legal reasons. Nothing here is sold or shared with anyone else.
On Railway, a hosting provider based in the EU (Amsterdam).
For as long as your alliance is active. An alliance with no real activity for 6 months or more may be disabled, and its data eventually removed (see Terms). Deleting a member removes their roster record; an event or reward they already took part in keeps just their display name as a snapshot rather than losing that piece of alliance history.
To see, correct, or delete your information: ask your alliance’s leader or deputy (they manage accounts and roster entries directly), or message me on Discord and I’ll help directly — including if you’re a leader yourself.
Everyone with an AllyLog account needs to be at least 16. A leader confirms this themselves the first time they log in — a self-declaration, not something AllyLog verifies against any ID. Deputy and member accounts have no login-time confirmation of their own, since those accounts are created and handed out by their leader rather than self-registered; the leader is responsible for only creating them for people who meet this requirement. See Terms for the full picture.
I’ll update this page as what AllyLog collects changes — the date at the top reflects the last edit.