Kingdom 4068 · Legal
Data Processing Overview
A technical-but-readable map of what happens to a submission from the moment you upload a screenshot to the day the record is deleted.
This document describes, in plain language, how information moves through the platform. It exists so applicants and leadership can see exactly what happens to a submission.
- You submit the form and screenshots
- Automated reading suggests field values you can correct
- The application is stored with your Governor ID as its key
- Leadership with matching access reviews it
- More information may be requested with a stated reason
- A human decision is recorded with the leader's identity
- Accepted governors receive an alliance placement
- The record is retained, then reduced or deleted on schedule
Access is granted per role and per kingdom. A leader sees only what their scope covers. The super administrator can manage access and configuration but private contact emails remain hidden from every role.
- Hosting: Not configured — provider pending
- Database and authentication: Not configured — provider pending
- Storage: Not configured — provider pending
- Automated analysis and voice: Not configured — provider pending
Row-level access rules on every table, private storage for screenshots, hashed passwords, session cookies that cannot be read by scripts, leadership action logging and restricted administrative functions.
Suspected incidents are investigated immediately, affected records are locked, and notification follows where the law requires it. Report a concern to Not configured — privacy email pending.