Law Enforcement Guidelines

Effective date: July 27, 2026

These guidelines explain how Dateagent responds to legal requests for user information. They are operational guidance, not legal advice, and do not create enforceable rights.

1. What data Dateagent holds

Dateagent is a date-planning app, not a messaging platform. Data we may hold about an account, described fully in our Privacy Policy:

  • Account/profile: phone number, name, username, optional email, profile photo, bio, social links, account creation date
  • Content: date options (venues, photos), availability, invitations and links, scheduled dates, private notes and feedback authored by the account holder
  • Contacts: contact entries the account holder created about other people
  • Guest RSVPs: names and optional contact details guests submitted to a host
  • Technical: first-party usage analytics, push tokens, crash reports; limited IP data (raw IP on abuse reports; hashed IP for invitation views; transient rate-limiting records)
  • Not held: chat or direct-message content (no chat/DM system exists — the only message-like content is the optional note on an invitation or RSVP, covered under Content and Guest RSVPs above), location history (none is collected), payment data (none exists), advertising identifiers (none are used)

2. What process is required

Consistent with the Stored Communications Act (18 U.S.C. §2701 et seq.) and other applicable law:

Data soughtRequired process (U.S.)
Basic subscriber information (phone number, account creation date, associated email)Valid subpoena
Records about the account other than content (analytics, technical logs)Court order under 18 U.S.C. §2703(d) or stronger
Content (date plans, notes, feedback, RSVPs, photos)Search warrant

We require legal process to be (a) issued by a court or authority with jurisdiction over Dateagent, (b) properly served, and (c) specific — identifying the account by phone number, username, or invitation link, the data categories sought, and a bounded time range. Overbroad requests will be narrowed or objected to.

Service: email [email protected] (subject "Legal Process"). Email service is accepted for convenience; it does not waive objections, including to jurisdiction.

3. Emergency requests

Where we believe in good faith that disclosure without delay is necessary to prevent death or serious physical injury, we may disclose limited information consistent with 18 U.S.C. §2702(b)(8) and (c)(4). Emergency requests must come from a law-enforcement official, be marked "Emergency Disclosure Request," and describe the emergency and why the ordinary process cannot be awaited. We review emergency requests urgently and prioritize them ahead of all other requests.

4. Preservation

Upon a valid preservation request under 18 U.S.C. §2703(f), we will preserve identified account records for 90 days, renewable once for an additional 90 days. Preservation does not disclose data; disclosure requires the process in Section 2.

5. User notice

Where permitted, we may notify users of legal requests for their information. We do not provide notice where we are legally prohibited (e.g., a §2705(b) non-disclosure order), where we believe in good faith that notice would create a risk of harm to any person or would compromise an active investigation involving child exploitation or threats to life, or where the account shows signs of compromise. Where a prohibition is time-limited, we may provide delayed notice after it expires.

6. International requests

Dateagent operates in the United States. Non-U.S. authorities should proceed via mutual legal assistance (MLAT) or letters rogatory; we do not disclose content in response to foreign process directly.

7. Costs, authenticity, and transparency

We may seek cost reimbursement where permitted (18 U.S.C. §2706). Records can be authenticated by declaration/affidavit on request. We reserve the right to publish periodic aggregate transparency statistics about requests received.

Safety matters to us. For urgent safety issues on the platform itself (threats, exploitation), our team also acts promptly on in-app reports — see the Safety Policy.