6HL / 2026.10.07

Privacy policy

6HL is an early-access HTML hosting service for existing authors. Public registration is not open. Google sign-in is available to linked author accounts; email sign-in is not open. Operator contact details and account deletion procedures will be added before public registration.

Data we store

We store author accounts, password hashes, uploaded projects, grants, access sessions, MCP credential hashes and necessary service records. Active visitor codes have an encrypted copy so their authors can view them. Full MCP credentials are provided only at creation.

How data is used

Data is used for file storage, project display, authorization, quota accounting and service operation. 6HL pages do not load third-party analytics or ads. Projects with CDN assets enabled may connect visitors to those third-party services.

Operational records

Operational metrics retain hourly totals of request categories, status codes, response times and successful actions for 90 days. They store no visitor IP addresses, raw URLs, query parameters, user agents or visitor identifiers, and use no analytics cookies. The admin console can view basic author details, linked Google email addresses, storage usage and login times recorded since monitoring began for account support and service operation.

Access and retention

Projects are private by default and require a valid visitor code. Authors can replace, export or delete projects, and revoke grants or MCP connections. Deletion removes online files; backups rotate on a seven-day retention period. The server and backups are in Seoul. Same-server backups do not protect against loss of the entire server.

Google identity verification

Google sign-in requests basic identity information only, with no access to Gmail, Drive or contacts. 6HL stores your stable Google identifier, account email and sign-in time to sign you in to the project space you explicitly linked. Email is display information and is never used to merge accounts automatically. Google access tokens are not stored persistently.

Limits of sharing

Authorized visitors can save loaded content or forward codes. Revocation blocks future access but cannot reclaim saved copies.