Scan on your PC
Open Forge Master at War Progress or Clan Tech Tree Rankings. Close the Excel output, run START.bat and select your scan types. Daily/Weekly Points are player rankings; Days & Results stores clan totals for Days 1–6.
Turn individual rankings into the bigger picture.
Run the scanner on your PC. Automatic sync uploads selected scans when enabled. For manual import, upload history/dashboard_upload.json using ‘Add scans’. Every snapshot is saved online.
See what changed between two scans.
| RANK | PLAYER | DONATIONS | RECOMMENDED | CHANGE | RANK CHANGE | OCR |
|---|
Open the race event popup in BlueStacks, select Clan Tech Race in the Windows scanner and enable Upload to website. Use the same Race period label when updating this event; choose a new label for the next event.
| RANK | CLAN | SERVER | DONATIONS | REWARD | CHANGE | RANK CHANGE | OCR |
|---|
Each upload adds a snapshot. Previous scores remain available.
| CAPTURED | CLANS | STATUS |
|---|
| PLAYER | RECORDED DAILY MAX | DERIVED FINAL ESTIMATE | STATUS | EVIDENCE / REVIEW |
|---|
Use the Windows scanner to capture Daily Points, Weekly Points or Days & Results. Historical day results contain clan totals only; player history comes from scans recorded on that war day.
Compare recorded days or different wars for the same clan.
| RANK | PLAYER | WAR POINTS | MVP | POINT CHANGE | RANK CHANGE | OCR |
|---|
Published clan totals for Days 1–6. These are not player rankings.
| DAY | OWN CLAN TOTAL | OPPONENT TOTAL | WINNING POINTS | WINNER | STATUS | CAPTURED |
|---|
| WAR / DAY | RANKING | RANK | WAR POINTS | CAPTURED | STATUS |
|---|
Every selected war keeps its own days, clans and snapshots.
| WAR / DAY | CLAN | CATEGORY | PLAYERS | CAPTURED | STATUS |
|---|
Your scans are preserved, including those that still need review.
| DATE | RANKING | PLAYERS | STATUS | REVIEW |
|---|
Donations at each recorded snapshot. Weekly scores can restart after a reset.
| DATE | RANK | DONATIONS | RECOMMENDED | STATUS |
|---|
Failed scans remain in history and do not replace a useful result.
| TYPE | RECORDS | CAPTURED | STATUS |
|---|
| NAME | TAG | SERVER | STATE | ID | ACTION |
|---|
These permissions are limited to the active clan. Adding a member here does not send an email or grant hosting access.
| MEMBER | ROLE | STATE |
|---|
Confirm additivity only after checking the game counters across resets. Inferred daily values remain labelled estimates.
Private by default. Hosting access still applies. Member administration is never shared with allies or visitors.
| WHEN | ACTION | ACTOR |
|---|
The original scan is immutable. An officer proposes a correction; a Clan Manager reviews and approves it before derived calculations use it.
Names do not prove permanent game identity. Duplicate identities remain excluded.
Use the source scan and player selected above. A finalized contribution or baseline is never guessed from a missing earlier day. Approval by a Clan Manager is required.
| TYPE | PROPOSED CHANGE | REASON | STATE | REVIEW |
|---|
Shown once. Enter this in the Windows scanner connection dialog. It grants upload access to this clan only.
| NAME | ID | STATE | REGISTERED | ACTION |
|---|
Open Forge Master at War Progress or Clan Tech Tree Rankings. Close the Excel output, run START.bat and select your scan types. Daily/Weekly Points are player rankings; Days & Results stores clan totals for Days 1–6.
Automatic website sync runs after scanning when enabled. Failed uploads stay queued and can be retried. As a manual fallback, choose ‘Add scans’ and upload history/dashboard_upload.json from the scanner folder. Scans are saved online. Uploading again does not create duplicates.
Open this website and sign in with an account that has access. Uploaded scans are stored online, so your PC can be switched off while you browse them.
The site starts private. The owner can invite specific members through the sharing settings. Invited members can view and compare rankings; only the owner can import scans.
Donations and War Points are separate. Choose two compatible snapshots. War comparisons can span recorded days or wars for the same clan. A missing player may reflect an incomplete scan or a name change, rather than someone leaving.
Your original Excel workbook and local database remain on your PC. Download the online JSON archive regularly as another backup. CSV opens in Excel; the scanner also continues to create a formatted XLSX workbook.
Retention starts in preview mode. Existing data is preserved.
Destructive cleanup is disabled.
Account identifiers and verified email addresses link your Clerk login to clan invitations, roles and access. Player names, game scores, clan details and capture times support history, comparisons, corrections and reports. Weekly notes support restricted clan planning. Minimal security and administrative records support access protection and review of changes. Publication follows the clan leader’s visibility choices; a login or cookie acknowledgement does not authorize public publication.
Existing scores and history are preserved. The following periods describe the earlier retention design for review; they are not active expiry rules while data preservation is enabled. Dates use UTC; the game week starts Tuesday at 00:00 UTC. Public visibility is always a separate clan permission.
| Data | Target | Clock starts |
|---|---|---|
| Individual scores and donation observations | 2 calendar years: 730 or 731 days | Original capture time, not upload, correction or account activity. A leap-day expiry clamps to 28 February. |
| Weekly member notes and their revisions | 90 days | The end of the relevant game week. Editing does not restart the clock. |
| Inactive accounts | 12 calendar months, then a 30-day warning period | Last meaningful sign-in or deliberate signed-in interaction. The 30 days start only after confirmed warning delivery. Ownership and provider failures need review. |
| Routine application security and administrative audit logs | 90 days | Each event. Provider logs have their own verified limits; they are not automatically 90 days. |
When expiry enforcement is enabled, authorized users can regenerate weekly reports while their underlying observations are available. Boundary weeks can be partial. The rolling window does not guarantee two complete previous calendar years plus the current year. Annual reporting is planned, not yet an active feature.
“All Time” is the game's cumulative donation counter. It does not mean ForgeClans stores every observation forever. Missing, expired or deleted records are not zero scores.
Reports are generated on demand in your browser. This workflow stores no PDF or Excel file on the server. The proposed maximum for any future temporary server file is 24 hours; its expiry must not delete valid source scores. Files you already save to your own device remain your copies and cannot be recalled by changing website access.
The current application keeps the latest 14 scheduled backup snapshots, not a guaranteed number of days. Manual and pre-restore backups currently have no automatic expiry. A rolling maximum of 30 days is a proposal pending provider and recovery review, not an activated guarantee.
No final raw screenshot/video retention period has been adopted. A 30-day period after processing is proposed for review. Existing originals on the scanner PC and uploader's device are not deleted by this website update.
Clerk manages login and account recovery. Game-player records can exist without an account. Deleting an account does not automatically erase independently collected player scores. A privacy or deletion request may need earlier action than the normal retention schedule. Trash hides a snapshot; it is not complete erasure.
Clan Managers control publication for their own clan. Private notes are restricted by role and should contain minimal planning information, not unnecessary sensitive personal details.
The operator is based in the Netherlands. English text or a .com address does not replace the EU privacy baseline. Cloudflare hosts the site and databases; current database placement was observed in Western Europe without an enforced EU jurisdiction. Clerk describes US-hosted authentication. Storage placement does not establish every processing or support location.
Necessary login/security cookies keep authentication working. No optional advertising or analytics integration has been added. Optional tracking must remain off until a separate opt-in is provided. Necessary cookies are not permission to publish player data.
The cookie notice acknowledgement is valid for 180 days; an expired acknowledgement is removed on your next visit. Existing clan/time preferences stay in browser storage until you clear them; clearing them resets those preferences. Actual Clerk cookie lifetimes depend on provider configuration and still require verification.
Operator details are awaiting confirmation.
This is a factual draft, not a claim of worldwide compliance. A formal operator identity, privacy-request contact, lawful-basis assessment and provider terms must be finalized before wider launch. Contact your Site Manager through your existing clan communication channel in the meantime. Never send game passwords or login tokens.
Review counts before any activation. This page does not enable deletion or change retention settings. Preview pages contain at most 50 objects; continue through all pages for a complete inventory.
Adopted targets, unresolved proposals and active enforcement are separate. Legacy timestamps and related identity records can require review. Holds remain restricted and need a review date.
No preview requested.