Law Enforcement, Government, Civil Process, and Emergency Request Guidelines

1. Purpose and Scope

These Law Enforcement, Government, Civil Process, and Emergency Request Guidelines explain how Spark Rack receives, authenticates, evaluates, preserves, and responds to legal demands for Customer information or action involving the Spark Rack Network and Services.

These Guidelines are intended for law-enforcement agencies, governmental entities, attorneys, litigants, Customers, and other persons seeking records, preservation, testimony, or action.

These Guidelines do not provide legal advice and do not waive any objection, right, privilege, jurisdictional requirement, or legal protection.

2. Spark Rack’s General Approach

Spark Rack respects Customer privacy and complies with valid legal obligations.

Spark Rack does not voluntarily disclose private Customer Content or records merely because a person, company, attorney, investigator, or governmental employee requests them.

Requests must use the legal process appropriate to the requested information, jurisdiction, and applicable law.

3. Service of Legal Process

Legal process should clearly identify Spark Rack, the issuing authority, the legal basis, the requested records, the relevant Account or identifier, the date range, and a reliable official contact.

Unless another method is required by law or expressly accepted by Spark Rack, service should be directed to:

Spark Rack
Attn: Legal Process and Compliance
PO Box 2215
Valdosta, GA 31604
United States

Mailing a document does not establish that service is legally sufficient. Spark Rack may designate an agent, counsel, electronic service method, or physical service location separately.

4. Required Request Information

A request should include:

1. The requesting agency, court, party, or attorney;
2. The name, title, badge or bar number where applicable, and official contact information of the requester;
3. The case, investigation, docket, or reference number;
4. The legal authority supporting the request;
5. A copy of the signed and complete legal process;
6. The exact Account, domain, email address, IP address, hostname, payment identifier, or other target;
7. For IP-based requests, the exact date, time, time zone, source or destination port, and protocol where relevant;
8. The precise categories of information requested;
9. The requested date range;
10. Any nondisclosure or delayed-notice authority;
11. Any preservation request;
12. The production deadline;
13. The requested production format; and
14. A method for secure production.

5. Requests Must Be Specific

Requests should be narrowly tailored to the legitimate investigation, proceeding, or claim.

Spark Rack may object to, seek clarification of, or move to narrow a request that is vague, overbroad, unduly burdensome, technically impossible, disproportionate, inconsistent with law, or directed to information Spark Rack does not control.

6. Different Categories of Information

Different forms of legal process may be required for different categories of information.

1. Basic subscriber information may include name, address, contact information, length of service, and certain account identifiers;
2. Transactional or noncontent records may include login records, assigned IP information, service records, and available metadata;
3. Content may include stored communications, files, messages, or Customer Content and generally requires more protective legal process;
4. Real-time interception or prospective collection requires specific lawful authority and technical feasibility;
5. Domain records may also be held by a registrar, registry, privacy provider, or reseller; and
6. Payment records may be held primarily by a payment processor.

Spark Rack determines the category and available records based on actual systems and applicable law, not solely on the label used by the requester.

7. Stored Communications Act and Other Law

Requests for electronic communications and related records may be governed by the Stored Communications Act, other federal law, state law, constitutional requirements, foreign law, and applicable provider obligations.

Spark Rack may require a subpoena, court order, search warrant, consent, emergency basis, or another legally sufficient process depending on the information requested.

8. Jurisdiction and Authority

A requester must have lawful authority to compel Spark Rack and the requested information.

Spark Rack may reject or challenge process issued by a court or authority lacking jurisdiction, process not properly domesticated, foreign demands not supported by an applicable mechanism, or requests inconsistent with controlling law.

9. Customer Notice

Spark Rack’s general practice is to notify the affected Customer before disclosure when legally permitted and when notice would not create an emergency, security, fraud, or evidence-preservation risk.

Notice may allow Customer to seek legal protection or provide relevant information.

Spark Rack may disclose without prior notice when prohibited from notifying Customer, when immediate disclosure is legally permitted in an emergency, when Customer consents, or when notice is impractical or would create material risk.

10. Nondisclosure and Delayed Notice

A request for secrecy should identify the specific statutory or judicial authority and duration.

Spark Rack may seek clarification, modification, or expiration of an indefinite, unsupported, or overbroad nondisclosure requirement where legally permitted.

When a restriction expires, Spark Rack may notify Customer unless another lawful restriction applies.

11. Preservation Requests

A governmental entity may request preservation of records pending issuance of legal process where authorized by law.

A preservation request should identify the Account or target precisely, the relevant date range, the legal authority, and the requesting official.

Preservation ordinarily preserves records already in Spark Rack’s possession and does not require prospective collection, creation of new records, retention beyond lawful periods without renewal, or preservation of data outside Spark Rack’s control.

12. Preservation Limitations

Preservation does not guarantee that:

1. The requested information exists;
2. Every relevant record was logged;
3. The Account identifier is accurate;
4. Historical data is still retained;
5. Deleted data can be recovered;
6. Backups are searchable or restorable;
7. Dynamic addressing can be attributed without complete timestamps and ports;
8. A third-party provider will preserve its records; or
9. Information can be produced in the requested format.

13. Emergency Requests

Spark Rack may disclose information without delay when permitted by applicable law and Spark Rack in good faith believes an emergency involving danger of death or serious physical injury requires disclosure.

An emergency request should include:

1. The nature of the emergency;
2. The person or people at risk;
3. The specific and immediate danger;
4. How the requested information relates to preventing harm;
5. Why ordinary legal process cannot be obtained in time;
6. The exact information requested;
7. The target identifiers;
8. The requesting official’s identity and agency;
9. A twenty-four-hour official contact number;
10. Supervisor approval where applicable; and
11. A signed certification of accuracy and lawful authority.

14. Emergency Review

Spark Rack evaluates emergency requests case by case and may contact the agency through independently verified channels.

Submitting an emergency form does not guarantee disclosure. Spark Rack may request additional information, narrow the request, disclose limited information, preserve records, or require formal process.

False emergency requests may be referred for investigation.

15. Civil Subpoenas and Private Litigation

A civil subpoena or attorney request does not automatically entitle a private party to Customer Content or records.

Spark Rack may require proper jurisdiction, service, notice to Customer, an opportunity to object, a protective order, cost reimbursement, and a sufficiently narrow request.

Parties should ordinarily seek information directly from the Customer when the Customer has possession, custody, or control.

16. Search Warrants and Court Orders

A warrant or court order should identify the issuing court, legal authority, target, scope, date range, and items to be seized or disclosed.

Spark Rack may seek clarification or challenge process that is facially invalid, technically impossible, excessively broad, or inconsistent with applicable law.

17. National Security Requests

Spark Rack will evaluate national-security process according to applicable law and may consult counsel.

Spark Rack may be legally prohibited from disclosing receipt, scope, or response.

Nothing in these Guidelines promises publication of aggregate or transparency information that law prohibits.

18. Foreign Government Requests

Foreign authorities should use an applicable treaty, letters rogatory, CLOUD Act executive agreement, domestic process recognized in the United States, or another lawful mechanism.

A foreign request sent directly to Spark Rack may be rejected when it lacks compulsory effect or conflicts with applicable law.

19. Authentication and Fraud Prevention

Spark Rack may verify requests by independently contacting the issuing court, agency, attorney, or official using published contact information.

Spark Rack may reject requests sent from personal email addresses, unsigned forms, unverifiable accounts, altered documents, inconsistent domains, or suspicious communication channels.

20. Production Format and Security

Spark Rack will choose a reasonable production format based on available systems, volume, security, and legal requirements.

Production may use encrypted files, secure transfer, physical media, or another protected method.

The requester is responsible for protecting produced information and credentials.

21. Data Minimization

Spark Rack will attempt to disclose only information responsive to valid legal process and reasonably available in Spark Rack’s systems.

Spark Rack may redact unrelated Customer information, secrets, privileged material, security information, and data outside scope.

22. No Continuous Surveillance by Default

Spark Rack does not provide prospective surveillance, continuous monitoring, packet capture, communication interception, location tracking, or ongoing reporting merely because a party requests it.

Such assistance requires applicable legal authority, technical feasibility, reasonable scope, and any required reimbursement.

23. Technical Limitations

Spark Rack may not be able to identify a person from a domain, shared IP address, proxy, VPN, NAT address, dynamic address, email alias, compromised Account, or incomplete timestamp.

Attribution may require source and destination ports, protocol, exact timestamp, time zone, provider records, Customer records, and other evidence.

An Account record identifies the subscriber information provided to Spark Rack and does not prove who personally performed an action.

24. Deleted, Expired, and Unavailable Data

Spark Rack cannot produce data that does not exist, was never collected, has expired under ordinary retention, was deleted, is encrypted without an available key, or is controlled by another provider.

Spark Rack is not required to reconstruct records, restore backups, create reports, or develop software unless legally required and technically feasible.

25. Domain and Registrar Records

Some domain information is controlled by a sponsoring registrar, registry, privacy provider, or reseller.

Spark Rack may refer the requester to the appropriate provider or produce only records Spark Rack actually maintains.

26. Payment Records

Spark Rack may retain invoice, payment-token, transaction, and billing records, while full card or bank information may be held by a payment processor.

Requests should be directed to the entity that controls the requested information.

27. Content Removal and Account Action

A request to remove content, suspend a domain, block a Service, preserve data, or terminate an Account must identify lawful authority and precise scope.

Spark Rack may also act independently under the Terms of Service, Acceptable Use Policy, DMCA Policy, or Abuse Policy.

28. Testimony and Custodian Declarations

Requests for testimony, depositions, affidavits, certifications, declarations, or expert explanation require reasonable notice and may be subject to objection, scheduling, scope limits, and reimbursement.

Spark Rack does not provide expert testimony merely because it produced business records.

29. Cost Reimbursement

Spark Rack may seek reimbursement for costs of searching, preserving, retrieving, restoring, reviewing, redacting, exporting, certifying, transmitting, or testifying, to the extent permitted by law.

Extraordinary requests may require advance payment or agreement on reasonable costs.

30. Confidentiality and Restricted Systems

Spark Rack will not provide requesters with access to internal systems, administrative portals, credentials, source code, other Customer Accounts, security controls, or unrestricted databases merely to simplify a request.

Spark Rack will produce responsive records through a controlled process.

31. Customer Consent

Customer consent may permit certain disclosures but must be informed, authentic, sufficiently specific, and legally effective.

Spark Rack may require identity verification and may decline consent that appears coerced, forged, outdated, ambiguous, or inconsistent with another person’s rights.

32. Requests From Customers for Their Own Information

Customers should use the Customer Portal, privacy process, account export, support process, or other ordinary access method rather than law-enforcement channels.

Identity and Account authority must be verified before disclosure.

33. No Informal Disclosure

Spark Rack personnel are not authorized to provide private Customer information through informal calls, direct messages, social media, personal email, or off-record conversations.

Requesters should not contact individual employees to bypass these Guidelines.

34. No AI Training or Secondary Use

Spark Rack does not use legal requests, produced Customer records, preservation data, or law-enforcement communications for AI or model training.

A requester receiving information is responsible for its own lawful use, security, retention, and disclosure.

35. Changes and Case-Specific Requirements

Spark Rack may update these Guidelines and may impose additional case-specific requirements based on law, risk, volume, jurisdiction, or technical circumstances.

Nothing in these Guidelines limits Spark Rack’s right to object, seek protection, notify Customer, or require a different legal process.

36. Contact

Legal process and official emergency requests should use Spark Rack’s published legal-process channel and may also be mailed to:

Spark Rack
Attn: Legal Process and Compliance
PO Box 2215
Valdosta, GA 31604
United States

37. Requester Acknowledgment

A requester should understand that:

1. Spark Rack requires valid and appropriately scoped legal authority.
2. Different information categories may require different legal process.
3. Spark Rack may notify Customer when legally permitted.
4. Preservation does not guarantee that records exist or can be restored.
5. Emergency disclosure is discretionary within applicable law and requires credible immediate danger.
6. Spark Rack may verify, narrow, object to, or challenge requests.
7. Spark Rack cannot produce information it does not possess or control.
8. Account records do not necessarily identify the individual who performed an action.
9. Extraordinary requests may require reimbursement.
10. No informal communication creates a right to Customer information.