1. Scope and operator
This policy covers the Mason Labs websites at masonlabs.app and appempire.masonlabs.app, the App Empire launch waitlist, and the current App Empire iOS game. “Mason Labs” is the brand used on these sites. The legal entity and location responsible for the service have not been confirmed and must be added before public launch.
2. Information collected
Waitlist. When you join, the server stores your email address, the time you consented, the consent wording version, and the time the signup was created. The form asks for no name or other profile information. A keyed hash of the request IP may be kept temporarily to apply abuse limits; the waitlist database does not store the raw IP address.
Website operations. The web server’s access and error logs may record an IP address, user agent, requested path, time, and response status to operate and protect the service. Request bodies, including the email address entered in the form, are not part of the configured access-log format. Exact log rotation and retention must be confirmed on the production host before launch.
Game saves. The current App Empire app saves game progress locally on your device and does not require an account. The current build does not use this website waitlist database for game saves. Sign-in and cross-device play are planned for later, not currently available.
Cookies and analytics. The current website uses no analytics, advertising pixels, marketing cookies, or third-party font and tracking scripts. If those tools are added, this policy and the site behavior must be updated first.
3. How information is used
- To keep a record of people who asked for App Empire launch updates.
- To record that the signup form’s email-update consent was given.
- To protect the form from repeated automated submissions.
- To respond to support, privacy, unsubscribe, or deletion requests through the published support contact.
Waitlist email addresses are separate from game progress. Joining the waitlist does not create an App Empire account or connect a website identity to a game save.
4. Storage and retention
Waitlist signups are stored in a server-side SQLite database on the configured host. The service is set to delete signup records after 24 months unless they are removed sooner following an unsubscribe or deletion request. Temporary abuse-limit hashes expire within one hour. Server logs follow the host’s log-rotation policy; the production retention period still needs confirmation.
At signup, the site does not send a confirmation email. Launch-update email delivery is not configured yet, and no launch updates will be sent until a sender and unsubscribe process are in place. If infrastructure backups are enabled on the host, deleted data may remain in a backup until that backup expires; the backup schedule and retention period must be confirmed before launch.
5. Service providers and sharing
The site uses the server host, its operating-system services, Nginx, and the local SQLite store to deliver the websites and maintain the waitlist. These infrastructure providers may process technical request data as part of hosting. No email marketing provider, analytics vendor, or advertising provider is configured in this project. No email address is sold or shared for third-party advertising. If a mailing provider or other processor is added, its role and the related data use must be documented here before it is used.
6. Unsubscribe, access, correction, and deletion
You may ask to stop future launch emails or request access, correction, or deletion of your waitlist address by emailing [email protected] from the address concerned. No launch email is sent at signup. Before launch updates are sent, each message must include a working unsubscribe method or clear opt-out instructions.
7. Children’s privacy
The website waitlist is not intended for children under 13, and we do not knowingly ask children under 13 to submit an email address. If you believe a child has joined the list, contact [email protected] to request removal. Age requirements and any additional protections must be reviewed for the markets where the game is offered.
8. Security
The waitlist service limits request size, validates email input, applies rate limits, stores addresses server-side, and avoids placing email values in access logs. The domain must have working HTTPS certificates before public launch. No internet service can guarantee perfect security; the operator should maintain access controls, updates, backups, and an incident-response process for the host.
9. Changes to this policy
This policy should be updated when data collection, storage, retention, service providers, email delivery, analytics, accounts, cloud saves, advertising, or payments change. The revision date at the top will be updated when a new version is published.
10. Contact
For support, access, correction, unsubscribe, or deletion requests, email [email protected]. The legal operator’s identity and location still need to be confirmed before this draft is published as final.