Privacy & Data Policy
Effective October 25, 2026 • Version 1.3
1. What IsleMap collects
IsleMap collects only information reasonably needed to operate the map service, server-owner membership program, security controls, and optional live integrations. This can include server-owner contact information, server/community name, region, membership status, connector/server identifiers, plan, connector version, detected map, player count, health status, timestamps, security/audit events, and private session/group state.
2. RCON and server credentials
The IsleMap connector is designed so the RCON host, RCON port, and RCON password are configured and stored on the participating server host. The RCON password is not intentionally transmitted to or stored by the central Ohio Annex IsleMap service. Permanent IsleMap server tokens are stored by the service only as cryptographic hashes. Activation codes and server tokens should be treated as secrets by server owners.
3. Player location and group data
Live player location data is used to provide requested map functionality. A browser receives the viewer's own permitted location data and the locations of group members explicitly authorized for that session. IsleMap is designed not to expose the entire server player-location feed to ordinary map users. Manual coordinate entries are processed for map placement and are not intended as a public location directory.
4. How information is used
Information is used to operate, secure, troubleshoot, improve, and administer IsleMap; review and manage server memberships; authenticate connectors; provide live map features; prevent abuse; and maintain operational/security logs.
5. Email and contact information
Server-owner email addresses and other contact information are stored to administer the requested IsleMap server membership, communicate about that membership, security, support, service changes, and future plan administration. Ohio Annex does not sell, rent, or provide server-owner email addresses or contact information to advertisers or data brokers and does not use membership contact information for unrelated third-party advertising. Security-sensitive membership messages, including an approved replacement server token, may be delivered to the verified email address on file.
6. Your data rights and choices
Server owners may use their private application credentials to request correction of the membership email address or deletion of their stored contact/profile information. Changing the email address keeps the membership attached to the same application and server. A request to delete the contact identity associated with an active server will revoke that server membership because Ohio Annex cannot safely administer an ownerless integration. A server owner who wants to keep service should change the membership to the replacement email before requesting deletion. Ohio Annex may verify the requester before completing a privacy request.
7. Security metadata, IP addresses, and retention
IsleMap may record the network address presented to the service, browser/connector security metadata, authentication attempts, and related identifiers for fraud prevention, abuse prevention, security, troubleshooting, and enforcement of service restrictions. Depending on hosting, VPN, proxy, or network-address-translation configuration, the address visible to IsleMap may be a shared gateway or proxy address rather than a person's unique public IP. This information is not sold or used for advertising. When a contact-data deletion request is completed, IsleMap removes the application contact/profile fields used for membership administration and revokes any associated active server. Limited non-contact security records, one-way identifier hashes, server/application identifiers, revocation status, consent records, IP/security metadata, and audit events may be retained when reasonably necessary for fraud or abuse prevention, security, legal obligations, dispute handling, or enforcement. Reasonable technical and organizational safeguards are used, but no Internet-connected service can guarantee absolute security.
8. Tenant moderation and browser client identifiers
On tenant server maps, IsleMap may assign an opaque browser/map client identifier and record recent activity, source/security metadata, moderation status, and tenant-admin audit events. Approved tenant administrators may view recent clients for their own tenant and may block or unblock a client from that tenant map for abuse prevention or rule enforcement. Tenant administrators cannot use IsleMap admin tools to access another tenant. If future chat or communication features are enabled, moderation actions and related tenant-scoped logs may be retained as reasonably necessary to investigate abuse and enforce server rules.
9. No sale or advertising redistribution
Ohio Annex does not sell, rent, or redistribute server-owner contact information, private server integration data, RCON credentials, server tokens, or player-location data to advertisers or data brokers. Information may be disclosed to infrastructure/service providers only as reasonably necessary to operate or secure IsleMap, to comply with lawful process, to investigate abuse, or with the affected party's authorization.
10. Third-party reference and infrastructure services
IsleMap may use independent third-party services, public technical references, hosting providers, or coordinate/calibration resources to validate compatibility and map alignment. VulnonaMAP is one independent coordinate/calibration reference that may be consulted for Gateway compatibility. VulnonaMAP and other referenced providers are not owned, operated, sponsored, endorsed by, or affiliated with Ohio Annex unless expressly stated. IsleMap does not require a third-party map-art service to render the Ohio Annex Gateway basemap, and Ohio Annex does not intentionally send private RCON credentials or private player-location feeds to third-party calibration/reference services.
11. Server-owner responsibilities
Server owners are responsible for securing their own RCON service, local connector host, RCON password, IsleMap token, operating system, firewall, and game-server configuration. Do not expose RCON publicly unless independently required and properly secured.
12. Changes and privacy requests
This policy may be updated as IsleMap adds features or paid services. Material changes use a new policy version and may require renewed acknowledgement. Server owners can use the private application-status area to change their membership email or request deletion of their contact information. Additional privacy or access requests can be submitted through the IsleMap server-owner/support channel.