A Hebrew translation of this page is provided for convenience. If the versions differ, the English version prevails.
Law Enforcement Guidelines
Last updated: 2026-10-15 · How we handle subpoenas, court orders, emergency disclosure requests, and preservation requests
1. Who this page is for
This page is for law enforcement officers, prosecutors, government agencies, and civil litigants seeking to compel StreamLive Pro to produce user records or take action on user accounts.
If you are a user requesting your own data, please use our GDPR data rights portal instead — that's the right channel for self-service access, export, and deletion.
If you wish to report content (harassment, CSAM, copyright), use /abuse or /dmca — those routes are reviewed faster than the legal mailbox.
2. Where to send requests
We do not accept legal process via Twitter, support tickets, contact forms, or phone calls. Email-only ensures a verifiable audit trail.
3. What we accept
| Request type | What we'll do |
|---|---|
| Preservation request | Hold relevant records up to 90 days (extendable on renewed request). No content disclosed. |
| Subpoena (basic subscriber info) | Disclose name, email, account creation date, last login IP, billing address (if any). No content. |
| Court order (non-content metadata) | Above + transactional logs, IP history, OAuth-connected accounts. |
| Search warrant (content) | Above + recordings, uploaded files, project content, support messages, as scoped by the warrant. |
| National Security Letter (US) | We respond per US law. We commit to publishing redacted statistics in our annual transparency report where permitted. |
| Emergency Disclosure Request | Per ECPA §2702(b)(8) / equivalent: we may disclose voluntarily to law enforcement when we believe in good faith that there is an imminent threat of death or serious physical injury. |
| Civil subpoena (party in litigation) | Reviewed for jurisdiction and validity. We may move to quash overbroad requests. |
4. Jurisdiction & cross-border requests
StreamLive Pro is operated from Israel. Our application servers are in Israel (Tel Aviv) and operated by us. The primary database is hosted on Neon (EU — Frankfurt, AWS eu-central-1), the job queue on Upstash Redis (EU — Frankfurt), and object storage on Cloudflare R2 (US / global). See our Subprocessors page for the full list.
- Israeli law enforcement: served per Israeli Criminal Procedure Code; we comply with valid Israeli court orders directly.
- EU member state law enforcement: served via mutual legal assistance (MLAT) or directly when permitted by national law and GDPR Article 6(1)(c). Direct civil subpoenas from EU member states are reviewed for GDPR compliance.
- US law enforcement: we generally require a request issued under valid US legal authority. We do not voluntarily produce content of communications without a US search warrant, except in genuine life-threat emergencies. CLOUD Act requests reviewed individually.
- Other jurisdictions: served via MLAT, Hague Convention, or letters rogatory. Direct foreign requests for content are generally declined unless aligned with international law.
5. What a valid request must include
- Issuing authority (court name, agency name, case number).
- Specific account identifier — email address, user ID, stream URL, or recording filename. We cannot search by partial name.
- Time window for records (broad "everything since signup" requests will be narrowed).
- Verifiable contact — issuing officer's name, badge number, agency phone, and an email at the agency's official domain.
- Legal basis — the statute, rule, or court order under which the request is issued.
- Signature from the issuing authority (PDF with court seal preferred).
Requests that lack any of the above will be rejected with an explanation. Resubmission is welcome.
6. User notice
Our default policy is to notify affected users of legal requests targeting their account, with the request's content, so they may seek to quash or oppose.
We will delay or withhold notice only when:
- A valid non-disclosure / gag order accompanies the request, OR
- Notice would create a credible risk to life or active criminal investigation, OR
- Applicable law prohibits notice (e.g., NSLs, certain wiretap orders).
When the gag period ends, we will notify the user retroactively where lawful.
7. Costs
We may charge reasonable cost-recovery fees for processing legal requests that involve manual data collection or extensive log retrieval, as permitted by 18 U.S.C. §2706 (US) and equivalent local statutes. Emergency / life-threat requests are processed without fee.
8. What we can NOT produce
- Decrypted card data — we never see or store full card numbers; card details are held by our PCI DSS–certified payment processor (listed on our Subprocessors page). Requests for card data must be directed to the payment processor. We hold only an encrypted token, the expiry date, the last 4 digits and transaction records.
- Real-time wiretap of streams — we are not technically configured for live interception. Past recordings (if retained) can be produced under warrant.
- Content of streams not recorded — if the user did not record, the audio/video was not stored beyond brief transcoding buffers (deleted within minutes).
- Data older than retention windows — see Trust Center for periods. Backups are purged on a 30-day rolling cycle.
- Plaintext passwords — passwords are stored as bcrypt hashes only; no recoverable form exists.
9. Transparency report
Beginning calendar year 2026, StreamLive Pro publishes an annual transparency report on this page covering:
- Number and type of legal requests received (subpoenas, warrants, court orders, NSLs).
- Country of origin (where disclosable).
- Compliance rate (full / partial / declined).
- Number of accounts affected.
- Aggregate counts of emergency disclosures.
2026 H1 report will be published by September 2026.
10. Contact
- Legal: [email protected]
- Data Protection Officer: [email protected]
- Trust Center: /trust · Privacy: /privacy · Terms: /terms