Eyrie — Law Enforcement and Emergency Disclosure Guidelines
Effective date: 7 October 2026 Last updated: 29 October 2026
1. Purpose
1.1 These Guidelines explain how law enforcement, government agencies and other authorities can request data from the operator of Eyrie ("Eyrie"), what legal process we require, and how we handle requests. They supplement our Privacy Policy and Terms of Service.
1.2 We take the privacy and safety of families — and especially children — seriously. We require valid legal process, we construe requests narrowly, and we resist requests that are overbroad, unclear or unlawful.
2. Who may make a request
2.1 We respond to lawful requests from Australian law enforcement and government agencies acting within their authority, and to properly authorised requests from foreign authorities made through recognised channels (for example, a mutual legal assistance request). We may decline requests that do not come through proper channels.
3. The legal process we require
3.1 We disclose customer data only where we are permitted or required to by law and where a valid legal instrument compels or authorises it. Depending on the data sought, this generally means:
(a) Basic subscriber information — a lawful request or notice sufficient under Australian law to compel it (for example, an authorisation or notice under the Telecommunications (Interception and Access) Act 1979 (Cth) where applicable, or a subpoena or court order);
(b) Stored content and detailed records (for example, location history, messages, alerts) — a warrant or court order appropriate to the data sought; and
(c) Interception or prospective/real-time data — the specific warrant or authorisation the law requires for that category.
3.2 The precise instrument depends on the requesting agency's powers and the data sought under Australian law (which may include the Telecommunications (Interception and Access) Act 1979 (Cth), the Telecommunications Act 1997 (Cth), the Surveillance Devices Act 2004 (Cth) and State/Territory equivalents, the Crimes Act, and applicable court rules). We assess each request against the law that applies to it and require the appropriate instrument.
3.3 We do not accept a request as valid merely because it is urgent, informal, or asserts authority. Legal authority must be demonstrated.
4. Emergency / imminent-risk disclosures
4.1 Where we form a good-faith belief that there is an imminent risk of death or serious physical harm to a person, we may disclose information reasonably necessary to prevent or reduce that risk, to the extent permitted by law (including the "permitted general situations" and related exceptions under the Privacy Act). This is an exception we may exercise, not an obligation, and it is limited to what is necessary to address the emergency.
4.2 Emergency requests should be submitted using the process below and clearly marked URGENT — RISK TO LIFE, and must describe the nature and immediacy of the risk, the person at risk, and the specific information needed. We may require the requesting officer to confirm their identity and agency, and we keep a record of the request and our decision.
4.3 If a member of the public believes a person is in immediate danger, they should contact the emergency services where they are. Eyrie is not an emergency service.
5. How to submit a request
5.1 Send requests to legal@eyrie.au. A valid request should:
(a) be on the agency's letterhead and identify the requesting officer, agency, contact details and a matter/reference number;
(b) attach the legal instrument relied on (subpoena, court order, warrant, or statutory notice/authorisation);
(c) identify the target with specificity — for example, an Account email, Family or Child reference, or device identifier — rather than a broad or speculative description;
(d) specify the data sought and the date range, narrowly framed; and
(e) state any non-disclosure obligation and its legal basis.
5.2 We may ask for clarification, narrowing, or additional authority before responding. We may reject or seek to set aside requests that are overbroad, vague, disproportionate, or not properly authorised.
6. What data we can and cannot provide
6.1 We can only provide data we actually hold, in the form we hold it, subject to our retention periods (see the Privacy Policy). This may include, depending on the account and the period: account/subscriber details, subscription and billing records, device information, location history and place/visit records (within the plan's retention window), alerts, SOS events, check-ins and text messages, and audit/log data.
6.2 We cannot provide data we do not collect or that has been deleted or aged out under our retention policy. In particular, Eyrie does not collect the content of a Child's other messages, photos, calls, browsing or app activity, and does not use the microphone or camera — so we hold no such data to disclose.
6.3 Payment card data is held by our payment provider (Stripe), not by us; requests for full card data should be directed to the provider.
7. Notice to the user
7.1 Our policy is to notify the affected Account Holder of a request for their data before disclosure, so they can seek to protect their rights, unless we are legally prohibited from doing so (for example, by a non-disclosure order), or unless notice would endanger a person, a child, or an investigation. Where a non-disclosure obligation expires, we may notify the user afterwards.
8. Data preservation requests
8.1 We will consider a request to preserve specified data pending valid legal process. A preservation request should identify the data and target with specificity. We will preserve the specified data for a reasonable period (typically 90 days, extendable once on request) to allow the requesting agency to obtain the necessary legal instrument. Preservation does not mean disclosure — disclosure still requires the appropriate instrument.
9. Costs
9.1 We may charge a reasonable fee for the cost of responding to requests, to the extent the law permits. We will tell the requesting agency in advance where a fee applies. We do not charge for genuine emergency requests involving a risk to life.
10. Our approach — a note for users
10.1 We know how sensitive family and children's location data is. We commit to: requiring valid legal process; reading each request narrowly; providing only what is compelled or clearly authorised; resisting overbroad or unlawful requests, including in court where appropriate; and notifying you where we lawfully can. If you have questions about a request concerning your Account, contact privacy@eyrie.au.
11. Contact
- Law enforcement and legal requests: legal@eyrie.au
- Privacy questions: privacy@eyrie.au