Summary in plain English
Enzonic Send is built to keep very little data for very little time. Files are permanently deleted when a transfer expires, at most 10 days after upload. We require valid legal process before disclosing user data, except in genuine emergencies involving danger of death or serious physical injury. Requests go to admin@enzonic.com with the subject line "Law Enforcement Request".
Last updated: October 17, 2026
1. Scope
These guidelines are for law enforcement officials and government agencies seeking information about users of Enzonic Send (the "Service"), operated by Enzonic LLC, a limited liability company formed in the Commonwealth of Kentucky, USA. They are provided for information only. They do not create any rights for any person, and we may change them at any time.
Users and their representatives should not use these channels. Civil litigants should serve process through the appropriate legal channels; see section 4.
2. What data may exist
The Service is designed for short-lived transfers, so the data we hold is limited and often no longer exists by the time a request arrives.
| Data | Description | How long it exists |
|---|---|---|
| File contents | Files uploaded in a transfer (multiple files are zipped on the sender's device before upload) | Until expiry (1 hour to 7 days, plus up to 3 days of extensions), or earlier if deleted by the sender or by us. Deleted files cannot be recovered. |
| Transfer metadata | File names, sizes, title, message, creation and expiry timestamps, download count, download limit, whether a password is set | Deleted together with the transfer |
| Transfer password | Stored only as a salted hash; the password itself is not known to us | Deleted together with the transfer |
| Hashed uploader IP address | A salted hash of the uploader's IP address. We do not store the raw IP address with the transfer and cannot reverse the hash. It can be compared only against an IP address you provide. | With the transfer and for up to 30 days after upload |
| Account data (signed-in users only) | Email address, name, user ID, and sign-in method (email/password or Google), held by our authentication provider Clerk | While the account exists |
| Server and security logs | Request data processed by our infrastructure provider Cloudflare | Limited period under Cloudflare's standard retention |
| Abuse and DMCA reports | Reports received about transfers, and related correspondence | As long as needed for enforcement and legal purposes |
What we do not have:
- files or metadata of transfers that have expired or been deleted;
- the raw IP address of an uploader linked to a transfer;
- passwords for transfers or accounts;
- payment information (the Service is free);
- the contents of files in a decrypted form protected by the user's own encryption; and
- data about anonymous senders beyond what is listed above.
Many transfers are made without an account, in which case there is no email address or name associated with them.
3. Requirements for valid legal process
We disclose user data only in response to valid legal process that is appropriate for the data requested and that complies with applicable law, including the U.S. Stored Communications Act (18 U.S.C. § 2701 et seq.).
As a general guide, under U.S. law:
- a subpoena may be required for basic subscriber information, such as the email address and name associated with an account;
- a court order under 18 U.S.C. § 2703(d) may be required for other non-content records, such as transfer metadata and logs; and
- a search warrant issued under the procedures of the Federal Rules of Criminal Procedure or equivalent state procedures, upon a showing of probable cause, is required for the contents of files, titles and messages.
Every request should:
- be on official letterhead and signed by the requesting official, or be served through an official government system;
- identify the requesting agency, the official's name, badge or identification number, official email address and telephone number;
- identify the specific transfer by its full share link (beginning with
https://send.enzonic.com/) and/or 6-digit receive code, or the email address of the account concerned; - describe the specific data requested and the relevant date range; and
- allow a reasonable time to respond.
We review each request carefully and may reject requests that are overly broad, vague, not legally valid, or not properly served. We may seek clarification or narrowing before responding.
4. Requests from outside the United States
Enzonic LLC is a US company. Non-US authorities should generally seek data through a Mutual Legal Assistance Treaty (MLAT), letters rogatory, or another mechanism recognized under US law, such as an agreement under the CLOUD Act. In exceptional cases, we may voluntarily respond to a non-US request where we believe it is consistent with US law, applicable international standards and our users' rights.
Civil litigants must obtain a subpoena or court order enforceable in the Commonwealth of Kentucky, USA, and must serve it on Enzonic LLC through proper channels. We cannot disclose the contents of communications in response to civil process, as the Stored Communications Act does not permit it.
5. Emergency requests
If you believe there is an emergency involving danger of death or serious physical injury to any person that requires disclosure of information without delay, you may submit an emergency disclosure request under 18 U.S.C. § 2702(b)(8) and § 2702(c)(4).
Email admin@enzonic.com with the subject line "EMERGENCY Law Enforcement Request" and include:
- the nature of the emergency and why it involves imminent danger of death or serious physical injury;
- why the normal legal process would cause harmful delay;
- the specific transfer link or 6-digit code, or account email, concerned;
- the specific information needed to address the emergency; and
- the requesting official's name, agency, badge or identification number, and contact details.
We review emergency requests as quickly as possible and disclose information on a voluntary basis where we believe in good faith that the legal standard is met. Emergency requests that do not meet this standard will be declined, and the requester will be asked to provide legal process.
6. Preservation requests
Because transfers are deleted automatically within days, preservation requests should be sent as early as possible.
We will honor requests to preserve records under 18 U.S.C. § 2703(f) for 90 days, pending receipt of formal legal process, and will extend preservation once for an additional 90 days upon a renewed request. Preservation requests should:
- be signed by the requesting official and sent from an official government email address;
- identify the transfer by its full share link and/or 6-digit code, or the account by its email address; and
- specify the records to be preserved.
We can only preserve data that still exists when we receive the request. Files and metadata that have already been deleted at expiry cannot be recovered.
7. User notification
Our policy is to notify affected users of requests for their data before disclosure, where we have a way to contact them (for example, the email address of an account holder), so they have an opportunity to seek legal protection.
We will not notify users where:
- we are legally prohibited from doing so, for example by a court order issued under 18 U.S.C. § 2705(b) or another non-disclosure order;
- the request relates to an emergency involving danger of death or serious physical injury;
- notice would be counterproductive, such as where the account itself is being used to endanger a child, or to distribute malware or carry out fraud; or
- we cannot contact the user, which is often the case for transfers made without an account.
Requests for non-disclosure should be accompanied by a court order or a clear explanation of the legal basis.
8. Child safety
We report apparent child sexual abuse material to the National Center for Missing & Exploited Children (NCMEC) as required by 18 U.S.C. § 2258A, and preserve related information as the law requires. Law enforcement agencies seeking information connected to a CyberTipline report should reference the report number in their legal process.
9. Costs
We may seek reimbursement of reasonable costs incurred in responding to requests, as permitted by law (for example, under 18 U.S.C. § 2706). We may waive costs in emergencies or in cases involving child safety.
10. Testimony
We do not provide expert testimony. Where records custodian testimony is required, we generally provide a signed declaration of authenticity of records instead, as permitted under the Federal Rules of Evidence.
11. Contact
Enzonic LLC Attn: Legal / Law Enforcement Requests Commonwealth of Kentucky, USA Email: admin@enzonic.com (subject line "Law Enforcement Request", or "EMERGENCY Law Enforcement Request" for emergencies)
Requests sent without these subject lines may be delayed. The "Law Enforcement Request" subject lines are reserved for law enforcement and government officials; users with other questions should see our Privacy Policy or Terms of Service.