Privacy Policy

This notice explains how AVIARY TECHNOLOGIES LTD handles personal information for its website, accounts, payments, support and Minecraft hosting. It includes information about players whose data is hosted on a customer’s server. It is a notice about our processing, not a request for blanket consent.

1. Who is responsible and how to contact us

AVIARY TECHNOLOGIES LTD, company number 17277024, is based at 124 City Road, London, EC1V 2NX, United Kingdom. Contact privacy@aviarytechnologies.co.uk about personal information, or write to that address. Support is available through Billing tickets.

We are the controller when we decide why and how information is used for our own account administration, billing, support, security and legal obligations. Where a customer controls personal information in a hosted server and data protection law applies, we act as processor for that hosted information on the customer’s instructions. The customer’s own privacy information also matters.

2. Information we handle

Account and contact information: your name, email, billing address and country, account identifiers, login credentials in protected form, and service preferences. We obtain these from you or someone authorised to act for your organisation.

Orders and payments: chosen plans, invoices, payment status, transaction references, refund records and limited payment-method information supplied by Stripe. Card details are entered into Stripe’s payment facilities. Aviary does not store your full card number or card security code. Stripe also processes information for its own payment, fraud-prevention and legal purposes.

Support and administration: messages, tickets, email correspondence and information you provide to resolve an issue. Staff and operational AI sessions may encounter relevant customer information while carrying out permitted support or operational work, as described below. Please do not send passwords, full card details or unnecessary sensitive information.

Security and technical records: IP addresses, timestamps, login attempts, account activity, device or connection information present in technical logs, and security events. Panel activity records include the email address or username attempted during a failed login, even if that account does not exist. We therefore may hold a mistyped identifier supplied by someone who is not our customer.

Hosted information: worlds, configuration files, plugins, server records and other content uploaded or generated on your server. Depending on the game and your configuration, these can contain player names, player IDs, IP addresses and chat messages. Hosting a file containing chat is different from staff being permitted to read it; our access rules restrict that reading.

Backups and recovery copies: copies of hosted information and systems maintained for recovery. Different backup and snapshot systems have different retention arrangements; section 7 identifies the present limits of what is known.

Policy acceptance records: a record that you accepted each policy, which version it was, and when. Each record holds your account identifier, the document, its version number, a fingerprint of the exact published text you were shown, and the date and time.

3. Why we use information and our legal bases

We use account details, order information and essential service communications to take steps you request before a contract and to perform our contract with you. If you are an organisation’s contact rather than our contracting customer, our legitimate interest is administering that organisation’s service relationship.

We use billing and tax records to meet legal obligations, as well as to administer payments under the contract. We use security records, necessary diagnostics and proportionate access records for our legitimate interests in protecting accounts, detecting abuse, maintaining reliable systems and investigating incidents. Those interests must be balanced against the rights of affected people, including non-customers whose identifiers appear in failed-login records.

We use correspondence to provide support and answer requests, on the contractual basis where applicable and otherwise our legitimate interest in responding appropriately. Compliance with a valid legal obligation is the basis where we must preserve or disclose information. Establishing or defending a legal claim may require proportionate retention or disclosure under our legitimate interests or a legal obligation, as applicable.

For staff-supervised operational AI assistance, the purpose is to operate and support the service. For our own controller data, we rely on our legitimate interest in administering and troubleshooting the service, subject to necessity, data minimisation and a balancing assessment. For player information we process on a customer’s behalf, use must be within that customer’s lawful instructions and the applicable processing agreement; our own legitimate interest does not replace those requirements.

We do not use customer information for advertising or marketing campaigns. Where a separate optional activity requires consent, we must ask specifically, and you may withdraw it without affecting earlier lawful processing. Accepting hosting terms is not blanket privacy consent.

We keep a record of the policies you accept for our legitimate interests in being able to show what was agreed and when, if that is ever questioned. Each record holds no more than your account, the document, its version, a fingerprint of the published text and the time, which we consider proportionate to that purpose.

Account, contact and payment information is needed to administer a paid service. If you do not supply necessary information, we may be unable to open or maintain the relevant account, process payment or resolve a request. We will explain any request for additional information.

4. Staff access and AI assistance

Access to customer files is limited to a specific, necessary support, operational, security or lawful-request purpose. We normally explain a proposed world-file inspection by email first and consider objections through a human decision. Staff must not join a customer’s game server without permission. Routine querying of console and chat logs is prohibited.

We use Anthropic’s Claude to help operate and support the service. Training on the data used in our operational sessions is disabled. This does not mean all processing stays on Aviary’s servers: information included in an operational session can be sent to and processed by Anthropic in the United States. Disabling training is not a promise of zero retention.

Our working practice requires staff approval before an AI agent accesses customer files. It is not currently enforced by a technical approval gate. File reads are audited on game nodes with alerts for undeclared reads, but logging does not cover every possible access route. Viewing the live console is not currently recorded. If we learn of unauthorised content access, we will notify the affected customer promptly with an explanation, subject to lawful restrictions.

We do not authorise use of customer content to train external models. We do not claim that a future Claude Team arrangement or zero-data-retention agreement is already in effect. Customer-facing AI ticket handling and proactive AI interventions require a separate review before activation.

Billing applies automated payment, overdue-suspension and deletion rules described in the Terms. Security systems apply login rate limits and temporary lockouts; failed-login monitoring also alerts staff to patterns of attempted access. An alert does not itself establish wrongdoing. Contact us through Billing or the contact details above to request human review of an action affecting your account. We do not describe these automated rules as decisions made by an AI model.

5. Suppliers and other recipients

Hetzner Online GmbH: infrastructure hosting for our systems, worlds, files, databases and backups in Germany and Finland. Hetzner Finland Oy is the identified subprocessor for the Finnish service. Our processing agreement with Hetzner was concluded on 21 September 2026. These suppliers host information on our behalf; a hosting agreement does not transfer ownership of customer worlds to them.

Stripe Payments UK Ltd and the relevant Stripe service entities: card collection, payment processing, billing-related records, refunds and fraud prevention. Stripe can act as a separate controller for its own purposes and performs processing internationally. Its UK contracting entity does not mean all processing remains in the UK. See the Stripe Privacy Policy for its activities and contact information.

mailbox.org: our business email service in Germany, handling correspondence and attachments. The exact contracting entity and completed order-processing agreement must be confirmed below.

Anthropic PBC: Claude assistance for operational and support sessions. Information included in those sessions is processed externally, including in the United States, with model training disabled for our use. The outstanding contractual and retention details are identified in section 4.

We may disclose necessary information to professional advisers or public authorities where there is a lawful basis and a specific need. Before responding to an external request for customer files or chat records, we verify identity, authority and legal basis, limit the information, and notify the customer unless legally prohibited. Receiving a request alone is not permission to disclose everything.

6. Where information is processed

Our hosting infrastructure is in Germany and Finland, and our business email is hosted in Germany. Aviary is a UK company. Movement of personal information between the UK and the EEA is cross-border processing; applicable UK and EU adequacy arrangements can cover those transfers. EU hosting does not mean there are no international transfers.

Stripe’s services involve international processing, and Anthropic receives operational-session information in the United States. Other countries may have different data-protection laws. For restricted transfers, the applicable law requires a valid transfer route, such as adequacy covering the recipient and processing, or appropriate contractual safeguards with the required assessment. We must identify the route actually used for our service.

7. How long information is kept

Policy acceptance records: kept indefinitely. When you accept our Terms of Service, confirm you have read this notice, or accept our Refunds and Cancellation Policy, we record your account, which document it was, its version number, a fingerprint of the exact text you were shown, and the date and time. We keep these as our evidence of what was agreed and when, including after an account is closed, because a question about what was agreed is most likely to arise after someone has left. If you ask us to erase your information we will normally keep these records, because information may be kept where it is needed to establish, exercise or defend legal claims.

Panel activity records: 90 days under the current pruning setting, including login activity, failed attempts, IP addresses and attempted email addresses or usernames, even for accounts that do not exist. This is the activity-log schedule, not a guarantee that every backup containing such a record disappears on day 90.

Game-node backups: approximately 30 days. This is the current approximate backup window, not a whole-service erasure deadline and not a guarantee of an exact daily restore point.

Storage Box snapshots: retention is not yet established. We cannot currently state a maximum time by which all snapshot copies are removed.

Live server content: available during the service, subject to the contract. For unpaid services, live-server deletion may follow at least fourteen days overdue as explained in the Terms. Voluntary-cancellation deletion timing, recovery access and any other retention triggers must be confirmed. Deleting the live server is not the same as deleting its backups, invoices or support records.

Other records: the full schedule for accounts, invoices and tax records, support tickets, email, file-access audit records, monitoring alerts and AI-session material remains to be completed. The relevant criteria include whether the account is active, an issue or payment remains unresolved, a record is needed for a specific legal claim, or a legal retention duty applies. These criteria do not establish a verified current deletion schedule.

8. Cookies and browser storage

Our marketing site set no cookies in the browser inspection reported on 21 September 2026. Billing and the hosting panel use first-party cookies for sessions and request security. The inspected cookies are:

Service	Cookie	Purpose	Reported lifetime
Billing	XSRF-TOKEN	Helps protect against forged requests	2 hours
Billing	paymenter_session	Maintains the billing session	2 hours
Hosting panel	XSRF-TOKEN	Helps protect against forged requests	12 hours
Hosting panel	aviary_hosting_session	Maintains the panel session	12 hours

These cookies use Secure and SameSite=Lax attributes. The session cookies are also HttpOnly; the XSRF cookies are not described as HttpOnly. Session activity may renew a cookie’s expiry. Blocking necessary cookies may prevent login or the service from working properly.

We use these necessary cookies without asking for optional-cookie consent. We do not use advertising, analytics or tracking cookies on the inspected Aviary properties. reCAPTCHA was removed on 21 September 2026. If we introduce optional storage technologies later, we will update this information and obtain consent where required.

Stripe’s own payment pages or components may use technologies governed by its own privacy and cookie information. The Aviary cookie inventory above is not a promise that every external payment-provider page is cookie-free. We do not treat a clean cookie list as proof that a page makes no external network requests.

9. Security

We use HTTPS for web and management interfaces, separation between customer environments, encrypted backups, restricted administrative access and mandatory two-factor authentication for administrators. Customer two-factor authentication is available but optional. Ordinary underlying disks are not separately encrypted, and we do not claim ISO or SOC certification.

Login rate limits and temporary lockouts reduce repeated attempts. Monitoring detects patterns of failed logins and alerts staff. The monitoring outputs described in the current configuration contain counts rather than attempted email addresses or usernames. The underlying activity log still contains the identifiers and IP addresses described above.

No system is completely secure. Tell us promptly about suspected unauthorised access. We will meet applicable duties to assess personal-data breaches and notify affected people and authorities where required. This statement of responsibility is not a claim that a documented incident or rights-fulfilment process has already been completed.

10. Your rights and complaints

Depending on the law and circumstances, you may request access to your personal information, correction, erasure, restriction or portability, and may object to processing based on legitimate interests. You may withdraw consent where consent is the basis. These rights have conditions and exceptions; for example, some information may be needed for a legal obligation or claim.

Contact privacy@aviarytechnologies.co.uk or write to us. We may ask for information reasonably necessary to verify your identity or understand the request, but will not routinely demand unnecessary identity documents. We will respond within applicable legal time limits, normally one month under UK/EU data-protection rules, and explain any lawful extension or refusal. A request does not normally attract a fee.

You may complain to the UK Information Commissioner’s Office and, where applicable, to the supervisory authority in your EEA country. You do not have to complete our complaints process before approaching a regulator.

11. If you play on a customer server

The server operator decides what happens on their server and what it records. We host that information for them. Your username, player ID, messages and connection address may be stored in the server’s files. Ask the operator what they keep and why, and how to exercise rights concerning their use of that information.

If you contact us about information held for an operator, we will help route the request to the appropriate customer, tell you that we have done so and share only what is necessary for that purpose. We handle requests about processing for which Aviary itself is controller directly. We do not ask players to accept this notice as a condition of being recognised as data subjects.

Account holders must be adults, but player information can concern children. Adult account ownership does not mean no children’s data is hosted. Server operators, including parents, schools and businesses, must consider their own obligations and the notices and safeguards appropriate for their players.

12. Changes to this notice

We will date updates and explain significant changes through an appropriate account or website notice. If a new use requires a new legal basis or consent, publishing a revised notice alone does not provide it. Contract changes remain subject to the notice and cancellation arrangements in the Terms.