Privacy

The website uses locally hosted fonts, images, scripts, and styles. Its code does not add advertising, third-party embeds, browser analytics, or non-essential cookies.

Cloudflare provides DNS for Aperture’s domains. The public website is served by Aperture’s hosting infrastructure, which receives network addresses and request information needed to deliver and secure the service.

You can create an Aperture account without an invitation. The support area uses an essential session cookie to keep you signed in and stores your account details and ticket conversations. If you use an email link, your email address, message, and normal mail metadata are sent to Aperture and processed by the mail provider.

For an onboarded tenant, Aperture needs account and contact details, authentication records, panel settings, machine and server identifiers, hostnames or network addresses, operational events, security logs, and support correspondence. Passwords are not stored as readable account passwords.

Game processes, files and Local game backups stay on the Linux machine you connect. Player traffic passes through Aperture’s TCP and UDP relay. Aperture also keeps private disaster-recovery backups of hosted account and panel settings; those snapshots do not include your game files.

• Provide, secure, diagnose, and improve the requested service.
• Authenticate users and connect authorized machines.
• Respond to support, security, and early-access enquiries.
• Maintain disaster recovery and prevent abuse.
• Meet obligations that apply to an accepted written order.

Aperture uses infrastructure providers where needed to deliver the service: Cloudflare for DNS, an email provider for account and support messages, and hosting providers for the control plane and game-traffic relay. Each processes the information needed for its role. No managed off-site game-backup storage is currently included.

Data is kept while it is needed for the enquiry, active service, security, dispute handling, or an applicable legal requirement. Deleted production tenant data may remain in private, access-controlled disaster-recovery snapshots until the rolling retention period expires. Those snapshots are not used for ordinary processing.

An unused workspace-name reservation expires after seven days. If no connected node is verified as working for 31 days, the hosted workspace becomes inactive. Its configuration and name remain recoverable for a further 365 days after inactivation. Aperture then permanently removes the retained hosted workspace configuration; game files on your machines are left untouched. Account, security and support records follow their applicable retention purposes. See the workspace policy for deadlines, warnings and recovery.

To ask what is held, correct it, request export or deletion, or raise a privacy concern, contact hello@aperture.sh. The operator and any jurisdiction-specific details are also identified in the written early-access order before a paid service begins.