Law Enforcement Guide

This guide is intended for law-enforcement agencies seeking records from Tiger LLC, the operator of the Divine application. Records are produced in accordance with the United States Electronic Communications Privacy Act (18 U.S.C. § 2701 et seq.), the Stored Communications Act, our user-facing Privacy Policy, and applicable law. This guide is not legal advice.

1. Who we are

Divine is operated by Tiger LLC, a limited-liability company based in California, United States. Tiger LLC is the data controller for user information collected through the Divine application and the website at divineapp.io.

2. How to serve legal process

Tiger LLC currently accepts service of valid legal process by email only. A dedicated submission portal is on the roadmap for higher request volume. Send process to:

support@divineapp.io

Subject line: “Legal Process — [agency name]”. We will respond to confirm receipt and assign a tracking reference.

Process must be issued by an authority with proper jurisdiction over Tiger LLC. We do not accept service via in-app reports, customer support tickets, voicemail, social media, or any channel other than the email address above (and a physical address that we will provide on request for hard-copy service). We do not waive any jurisdictional or procedural defects by responding.

Foreign agencies must use the Mutual Legal Assistance Treaty (MLAT) process, a letter rogatory, or other recognized legal-cooperation channel, except for emergency disclosure as described in Section 6.

3. What we require, by request type

3.0 Mapping to the Stored Communications Act

3.1 Basic subscriber information

Required: a subpoena, court order, search warrant, or equivalent valid process. We may disclose, where it exists:

• The account’s display name and date of account creation.
• The email address used to register.
• Date and IP address of the most recent sign-ins (where retained).
• Sign-in provider (Apple, Google, or email).
• App Store / Google Play purchase records (per RevenueCat receipts).

3.2 Non-content transactional records

Required: a court order under 18 U.S.C. § 2703(d) or equivalent. We may disclose:

• IP-address access logs to the extent retained.
• Voice match call metadata: participants (by account ID), start and end timestamps, call duration. We do not record voice match audio — it is not stored on our servers.
• Message metadata: sender, recipient, conversation ID, timestamps, delivery state.
• Push notification delivery metadata.
• Action logs (block events, report submissions, moderation actions).

3.3 Content records

Required: a search warrant issued upon probable cause under Federal Rule of Criminal Procedure 41 or equivalent state-level warrant. We may disclose:

• Direct message content (text and voice messages, where retained).
• Posts and Stories created by the account, including those that have expired from public view but remain in archival storage.
• Profile photos and other uploaded media.
• Reports the account submitted or that other users submitted about the account, and the content referenced therein.
• Moderation-queue copies of flagged content.

We do not have access to the content of voice match calls or to live audio broadcast in Spaces — that audio is routed in real time through our voice-infrastructure partner and is not persisted.

4. Preservation requests

Tiger LLC accepts preservation requests under 18 U.S.C. § 2703(f). Send a written request to the email address above identifying:

• The Divine account by display name, registered email, or @-handle.
• The category of records you wish preserved.
• The date range, if known.

We will preserve responsive records for 90 days from the date of receipt, extendable on written request for one additional 90-day period. A preservation request does not authorize disclosure — that still requires valid legal process as described above.

5. Identifying the right account

Provide as much of the following as you have:

• The account’s @-handle or display name.
• The email address the account is registered to.
• Any URL or in-App link.
• Approximate dates of the activity at issue.
• Apple-issued or Google-issued user identifier, if available.

Requests with only a real name, location, or photograph are very difficult to resolve, because most Divine users do not register with their legal name.

6. Emergency disclosure

In an emergency involving a risk of death or serious physical injury to any person, Tiger LLC may voluntarily disclose limited information without process pursuant to 18 U.S.C. § 2702(b)(8) and 2702(c)(4). Submit an emergency request to support@divineapp.io with the subject line “EMERGENCY DISCLOSURE REQUEST” and include:

• The nature of the emergency and the specific risk of death or serious physical injury.
• The Divine account(s) involved.
• The agency, officer name, badge or ID, and contact phone for verification.
• The records you need, narrowly tailored to what is necessary to address the emergency.

We evaluate emergency requests independently and may decline any request we cannot verify or that does not meet the statutory standard.

7. Cross-border requests, the CLOUD Act, and EU e-Evidence

Under the CLOUD Act, Tiger LLC may be required to produce stored data regardless of where it is located. We evaluate each request on the merits and may seek modifications where compliance would conflict with foreign law. US v. Microsoft (2018) provides relevant background.

We accept European Production and Preservation Orders issued under EU Regulation 2023/1543 at the email address in §2. We evaluate each per the Regulation’s procedure, including its cross-border applicability and the carve-outs for designated service categories.

Non-US agencies without a CLOUD Act executive agreement should generally proceed through the Mutual Legal Assistance Treaty (MLAT) process or by letter rogatory. The U.S. Department of Justice Office of International Affairs is the conventional point of reference for outbound MLAT requests to the United States.

8. Retention of records we DO hold

For law-enforcement audiences, the retention schedule for the categories of records we hold mirrors the Privacy Policy:

• Basic subscriber information: while the account is active, and approximately 30 days after account deletion.
• IP-address access logs: up to 90 days.
• Server logs: up to 90 days.
• Direct messages and voice messages: while the account is active, deleted with the account; preserved when subject to a preservation request.
• Profile media (photos): while the account is active.
• Moderation copies (content flagged by moderation): up to 12 months in restricted-access storage.
• Call metadata (participants, timestamps, duration): up to 24 months.
• Voice match audio / Spaces audio: NOT retained.

9. Child-safety reports

Reports of CSAM and child sexual exploitation are escalated immediately. We report apparent CSAM to the NCMEC CyberTipline as required by 18 U.S.C. § 2258A and cooperate with subsequent investigations. See our Child Safety policy.

10. Cost reimbursement

Tiger LLC may seek reimbursement of reasonable costs of producing records in response to legal process where authorized by 18 U.S.C. § 2706 or applicable law. We will identify expected costs prior to production.

11. User notice

We will notify users of legal process seeking their information before disclosure where we are not legally prohibited from doing so (e.g., by a sealing order or non-disclosure order under 18 U.S.C. § 2705). Exceptions: (a) any matter involving CSAM, (b) any matter we believe presents a risk of physical harm to a person, and (c) matters where we are otherwise legally prohibited from giving notice.

12. Authenticity of records

On request, Tiger LLC can provide a certification of authenticity for produced records sufficient to qualify them as self-authenticating business records under Federal Rule of Evidence 902(11). We do not provide live testimony or affidavit support outside of that certification absent further legal process.

13. Production format

Production sets are delivered as PDF (for narrative summaries and authentication certificates) and CSV (for structured data such as IP-log extracts). We provide a SHA-256 hash for each artifact in the production set.

For any production above basic subscriber information we deliver via encrypted email (S/MIME or PGP) or an equivalent secure transfer method agreed in advance.

14. What we do not have

Categories of information that Divine does not collect or retain, and therefore cannot produce:

• Voice match call audio — not recorded.
• Spaces audio — not recorded by Divine.
• Credit card numbers, bank details, or other payment-instrument data — payments are processed by Apple and Google; we receive only entitlement receipts via RevenueCat.
• Government-issued ID documents — we do not store ID documents from face verification; we retain only the verification decision and the timestamp.

15. Conflicts of law

We will work with the requesting agency to identify lawful alternatives where compliance with legal process would conflict with applicable law in the jurisdiction where a user resides, and may decline production where complying would violate applicable law.

16. National security process and transparency

Tiger LLC reserves the right to publish aggregate counts of National Security Letters and FISA Section 702 directives received, in our transparency reporting, to the extent permitted under the USA FREEDOM Act and any applicable gag rules.

17. Contact

Tiger LLC — Legal
California, United States
Email: support@divineapp.io