← Back to Orrio

Privacy Policy

Last updated: 26 October 2026 · Website and waitlist edition

This policy covers the Orrio website and waitlist only. It does not describe data processing in a future animal-record app or professional workspace; we will provide the relevant information before collecting data for those services.

1. Who is responsible

The controller is Orrio. For privacy questions and requests contact support@orrio.app.

2. Information we handle

The waitlist does not ask for passwords, payments, animal clinical records or personal medical information. Please do not include these in your registration. Future record-sharing features will need their own disclosures.

3. Purposes and legal bases

We manage the waitlist, understand interest by role and campaign, and contact you about Orrio’s launch based on your consent (Article 6(1)(a) GDPR). Signup is voluntary; without your email we cannot register or contact you.

Delivering and securing the site, preventing spam and handling ordinary support requests serve our legitimate interests in a reliable website and responding to enquiries (Article 6(1)(f)). Where we must meet a legal obligation, including responding to applicable data-rights requests, we rely on Article 6(1)(c). We do not use the waitlist for automated decisions with legal or similarly significant effects.

4. Providers and disclosure

Netlify hosts the website and stores form submissions. Its Forms service uses Akismet, operated by Automattic, to check submissions for spam. Authorised people working on Orrio may access submissions only as needed for the purposes above. We may disclose information where required by law or necessary to handle a legal claim. We do not sell waitlist information or share it with advertisers for their own marketing.

No email-marketing provider is connected to this waitlist. If we introduce another provider, we will update this notice before using it and obtain any additional consent required.

5. International transfers

Netlify and its providers may process data outside the EEA, including in the USA. Netlify describes mechanisms including the EU–US Data Privacy Framework where applicable and European Commission standard contractual clauses in its privacy information and data processing agreement. Contact us for information about the safeguards applying to your data and how to obtain a copy.

6. Retention

We keep registrations while needed for the waitlist and launch communications, until you withdraw consent, or until the project or that purpose ends, whichever occurs first, unless a legal obligation or the establishment, exercise or defence of legal claims requires limited further retention. We remove records that are no longer needed. Hosting and spam-prevention logs follow the providers’ retention schedules. Support correspondence is kept while needed to resolve the request and meet any applicable legal obligations.

7. Your choices and rights

You may leave the waitlist and withdraw consent at any time by emailing support@orrio.app from the address you registered. Withdrawal does not affect earlier lawful processing. Subject to applicable conditions, you can request access, correction, deletion, restriction and data portability, and object to processing based on legitimate interests. We may request proportionate information to confirm your identity.

8. Cookies, security and children

The landing page does not set analytics or advertising cookies or load tracking pixels. Campaign tags are submitted with your registration, not used for cross-site tracking. Netlify’s separate login or site-protection screens may use necessary authentication technologies under its own information.

We use reasonable access and hosting safeguards, but no online service is risk-free. Report suspected exposure to support@orrio.app. This waitlist is intended for adults aged 18 or over. If a child has registered, contact us so we can remove the registration.

9. Updates

We update this page when the website’s processing changes. We will provide additional notice or ask for consent when required; a policy update alone does not authorise unrelated use of your data.