Law Enforcement, Government Requests & Transparency

1. Scope & Our Approach

Grace Unworthy Ministries, LLC ("we," "our," or "us") operates multiple web properties and services. This document applies to the properties listed in our Covered Properties notice, which is incorporated by reference.

This policy explains how Grace Unworthy Ministries, LLC responds to subpoenas, court orders, search warrants, and other requests for user information from law enforcement, government agencies, and civil litigants. It applies across all of our properties and services, including The Story Haven.

We comply with valid, legally binding legal process. At the same time, we ask that requests be properly issued and served, and we may object to, narrow, or seek to quash requests that are legally deficient, overbroad, vague, or unduly burdensome. Nothing in this policy waives any objection, defense, or right available to us or to our users, and nothing here is legal advice to any requesting party.

2. Requirements for Valid Legal Process

We generally require the following before disclosing user information:

• Subpoena: a validly issued and properly served subpoena is generally required for basic subscriber information, such as the name and email address associated with an account and the dates an account was created or last used.
• Court order: a court order issued under an applicable legal standard is generally required for non-content records beyond basic subscriber information, such as account activity logs and connection records.
• Search warrant: a search warrant issued upon a showing of probable cause by a court of competent jurisdiction is generally required for the contents of communications, including private messages and non-public user content.
• Civil requests: civil subpoenas must be validly issued and served under the applicable rules of procedure, and we may require notice to the affected user before producing records.

Every request should include, at minimum:

• The specific account identifier at issue (email address, username, or account URL) — we cannot process requests that ask us to search for users by general description
• The specific records sought and the relevant date range, narrowly tailored to the investigation
• The name of the issuing authority or court, the case or matter number, and the name, title, agency, direct telephone number, and official email address of the requesting official
• A response deadline that allows a reasonable time for review — we generally cannot accommodate deadlines shorter than fourteen (14) days absent an emergency

Requests for records concerning users outside the United States may require process issued through a mutual legal assistance treaty (MLAT), letters rogatory, or another recognized channel.

3. Notice to Affected Users

Our policy is to make a good-faith effort to notify users when we receive legal process seeking their information, so that they have an opportunity to object or seek protective relief. Where we provide notice, we generally do so before producing records, unless doing so would be impracticable or unlawful.

Notification is a policy commitment carried out by our team, not an automatic technical feature of our platform. It is subject to the exceptions above and to the practical limits of the contact information we hold for an account.

4. What Information We May Have

The records we hold vary by service and by how a person has used our products. Depending on the account, we may have some or all of the following:

• Basic subscriber information: name, email address, account creation date, and last activity date
• Profile and community content: profile details, posts, comments, reactions, group memberships, and uploaded media on The Story Haven
• Transaction records: order history, course enrollments, subscription status, and billing metadata. Full payment card numbers are held by our payment processor, not by us.
• Communications: support correspondence and, where applicable, direct messages
• Technical and log data: IP addresses, device and push-token records, and application logs, each retained only for a limited period

We retain records only as long as described in our Privacy Policy and Data Deletion & Retention Policy. We cannot produce records that have already been deleted or that were never collected, and we do not create new records in order to respond to a request.

5. What We Typically Do Not Produce Without Appropriate Process

• Contents of private communications, non-public posts, and private media, absent a search warrant or other legally sufficient process
• Bulk or unbounded requests for information about groups of users who are not individually identified
• Records outside the scope, subject matter, or date range of the process actually served
• Payment card numbers and comparable financial instrument data, which our payment processor holds and which should be sought from that processor
• Prospective or real-time interception of communications, absent process expressly authorizing it

6. Encryption, Hashing, and Practical Limits

As described in our Security Policy, we hash account passwords using bcrypt, which means we cannot recover or produce a user's plaintext password. We also apply application-level encryption to certain fields, such as some message content and stored integration tokens.

We do not claim that our staff are technically incapable of accessing user data. Our systems necessarily process personal information in plaintext for legitimate operational purposes — including customer support, content moderation, safety and fraud investigations, debugging and error diagnosis, and generating data exports at a user's request. Authorized personnel may therefore be able to access information that is encrypted at rest, and we may be compelled to produce such information in response to valid legal process.

What we can produce in any given case depends on what our systems actually retain at the time we receive the request, not on a promise about what is or is not technically reachable.

7. Emergency Disclosure Requests

If we receive a request from a law enforcement agency asserting an emergency involving an imminent danger of death or serious physical injury, we may disclose information we believe in good faith is necessary to prevent that harm, without legal process and without prior notice to the affected user.

Emergency requests should be submitted to [email protected] with "EMERGENCY DISCLOSURE REQUEST" in the subject line, and should describe the nature of the emergency, the person at risk, the specific information needed, and how that information will help prevent the harm. We evaluate each such request individually and are not obligated to disclose information in response to any particular request.

8. Preservation Requests

We will honor properly submitted preservation requests from law enforcement to preserve records associated with a specified account for ninety (90) days, and may extend that period for an additional ninety (90) days upon a renewed request, pending service of valid legal process. Preservation captures records as they exist when the request is received; it does not obligate us to collect information we do not already retain, and it does not by itself result in disclosure.

9. Costs, Format, and Authentication

Where permitted by law, we may seek reimbursement for the reasonable costs of responding to legal process. Records are typically produced in electronic form. Requests for certified or authenticated business records, or for testimony or a declaration from a custodian of records, must be stated expressly and served with sufficient advance notice.

10. Related Policies

• Privacy Policy — what we collect, why, how long we keep it, and when we disclose it
• Security Policy — the technical measures protecting our systems
• Data Deletion & Retention Policy — deletion, retention, and export of user data
• The Story Haven Community Guidelines — content standards and moderation on The Story Haven
• Terms of Service — the agreement governing use of our services

11. How to Serve Legal Process

We do not accept service of legal process by voicemail, social media, or through customer support channels. Legal process should be directed to [email protected] or served at the mailing address below. Acceptance of a document at that address is not a waiver of any objection, including objections regarding jurisdiction, service, or scope.

12. Changes to This Policy

We may update this policy as our practices, systems, or legal obligations change. Material changes will be reflected in the "Last Updated" date shown at the top of this page.