AccessControl

By logging in, requesting access, or otherwise using this AccessControl dashboard, you acknowledge that the system records basic connection, session, and activity information for security, abuse prevention, account review, and system reliability.

1. When you visit the dashboard, submit an access request, log in, change account settings, use administrative tools, or interact with the reader API, the system may record session cookies, network-origin details, approximate country or region, request time, account username, account status, permission level, and the action that was attempted.
2. This information is used to decide whether a request appears normal, suspicious, automated, abusive, outside the allowed service area, or likely to be spam. In simple terms, the combination of your browser session and connection details helps the system tell the difference between a real user who is supposed to be here and traffic that looks like a bot, scam attempt, spam request, or unauthorized connection.
3. The dashboard may compare your session cookie, general connection source, allowed-country checks, recent access requests, repeated failed activity, repeated account requests, unusual request frequency, and other ordinary security signals. These checks are meant to keep the dashboard usable, protect reader controls, and reduce fake or harmful account activity.
4. If a request appears suspicious, the system may mark it as spam, deny access, hide it from normal approval flow, log the event, or prevent the request from continuing. This does not mean the system knows who you are personally; it means the traffic matched a rule designed to protect the service.
5. Access requests may be reviewed by an administrator. The administrator may see the username you requested, optional email address, request status, regional connection result, approval status, Roblox UserID if one is later associated, and permission level if the request becomes an account.
6. Reader scan logs are kept separately from account request logs. Reader logs may include scan status, reader activity, Roblox user details when available, timestamps, and connection metadata related to the reader event. These logs are used for auditing access-control behavior and troubleshooting reader communication.
7. The service does not use these connection details to sell data, advertise to you, or build a marketing profile. The purpose is operational security: keeping the dashboard, accounts, reader API, and Roblox-connected readers from being abused or taken over.
8. Because this is an access-control system, administrators may retain security logs for as long as needed to understand abuse, review account requests, investigate reader activity, diagnose errors, and keep the system stable.
9. You should not use the dashboard if you do not agree to this logging. If you continue by logging in or requesting access, you are acknowledging that session-based security checks, connection checks, and activity logs are part of how this system works.

This summary is intentionally direct: the dashboard records session, connection, and activity data so it can identify spam, bots, suspicious requests, and unauthorized behavior while still letting real approved users manage their own locations and readers.