GivePeace Legal Process & Estate Requests Policy

Version 1.0 — Effective July 30, 2026

This Policy explains how Give Peace Inc., a Delaware corporation ("Give Peace," "we," "us"), responds to requests for member information and member messages — from courts, from law enforcement, from lawyers, from executors and personal representatives, and from grieving families. It is part of our Terms of Service.

We wrote this Policy for four kinds of reader at once: attorneys and their staff, court-appointed personal representatives, law enforcement, and families who have just lost someone. If you are reading this in grief, we are sorry for your loss. The rules below exist to protect the person you lost — including the choices they recorded while they were alive — and we apply them with care, not coldness.

GivePeace holds some of the most personal words a person ever records: video messages sealed until after they pass away, addressed to the specific people they chose. Because of that, our answer to most requests is shaped by one fact above all others: the member already told us, in a recorded agreement, exactly who should receive their messages. We honor that.

1. What This Policy Covers

1.1 Scope. This Policy governs requests to Give Peace for: the contents of a member's messages; records about a member's account; preservation of either; deletion or suppression; and any other demand made by legal process or by a person claiming authority over a member's account or estate.

1.2 Who "you" is in this Policy. In this Policy, "you" means the person making a request — an attorney, an executor or personal representative, a law-enforcement officer, or a family member. "Member" means the GivePeace account holder, as defined in our Terms of Service.

1.3 Related documents. This Policy works alongside our Terms of Service, Privacy Policy, Death Verification & Posthumous Release Policy, Trustee & Recipient Terms, Digital Legacy Designation Agreement, Copyright & DMCA Policy, SMS & Communications Terms, and Community Guidelines. Where this Policy summarizes retention or deletion, the Privacy Policy owns the full retention details.

2. The Words This Policy Uses

2.1 Member. The GivePeace account holder.

2.2 Trustee. A person a member appoints for death notification and confirmation only. Section 8 explains why trustees have no standing under this Policy.

2.3 Recipient. The person a member chooses to receive a specific message after the member passes away. A recipient is the "intended recipient" of that message in the sense federal law uses that phrase.

2.4 Armed message. A recorded message set to be released after the member passes away.

2.5 Release. Our delivery process after death verification completes, including the 48-hour final call, as described in the Death Verification & Posthumous Release Policy.

2.6 Contents. When this Policy says "the contents" of a message or communication, it uses the term the way federal law does: the message itself — the video, the words, what was said. Everything else — who, when, to what address, account details, logs — is a record, not contents.

2.7 Catalog. A list of a member's communications showing who the member communicated with, when, and at what electronic address — without the contents. Understand what a catalog means on GivePeace before you request one: on this Service it is, in substance, a list of the member's trustees and recipients and how to reach them. Section 7 explains when we can and cannot provide it.

2.8 Designation Agreement. The Digital Legacy Designation Agreement — the separate agreement, with its own acceptance, in which a member records who their trustees are and who receives each of their messages. A member can change or delete those directions at any time while alive. The member's recorded directions in the Designation Agreement control how their messages and records are handled after death.

3. Our Commitments on Every Request

3.1 We require valid legal process or lawful consent. We do not disclose member information voluntarily. Every disclosure rests on one of two bases: legal process that is valid for what it seeks, or lawful consent recorded by the member.

3.2 We honor the member's recorded directions. A member's directions recorded in the Designation Agreement are the first thing we check on any estate or family request, and they control. No provision of our Terms of Service overrides a member's recorded direction, and we will not treat a request — however sympathetic — as a reason to disregard one.

3.3 We read every request narrowly. We review each request for validity, scope, and the authority of the person making it. We produce what the process properly compels and no more. Where a request is overbroad, vague, or seeks material beyond the requester's entitlement, we object and ask that it be narrowed (Section 19).

3.4 We tell the affected person when the law allows. Our policy is to give notice to the affected member — or, if the member has passed away, to the member's personal representative — before we disclose their information, except where the law prohibits notice or an emergency requires disclosure without delay (Section 10).

3.5 We act in good faith, and we document. We handle every request in good faith, keep records of what was requested, by whom, and what we did, and rely on the good-faith protections that federal and state law give providers and custodians who follow these procedures.

4. Encryption, and What We Are Able to Produce

4.1 The honest technical picture. As our Terms of Service and Privacy Policy tell every member:

Your videos and messages are encrypted in transit and at rest. Each account has its own encryption key, protected by a hardware-backed key management service, and every video is sealed with authenticated AES-256 encryption derived from that key, with an additional layer of server-side encryption on our storage. Give Peace holds and controls these keys — that is what makes it possible for us to deliver your messages after you pass away. It also means Give Peace is technically able to access encrypted messages, and can be required to produce them in response to valid legal process. GivePeace is not end-to-end encrypted.

4.2 What this means for requesters. We will never tell you that production is technically impossible, because it is not. Give Peace holds the keys. What stands between a member's sealed messages and a requester is not cryptography — it is law: the federal Stored Communications Act, state fiduciary-access law, and the member's own recorded directions. This Policy explains how those apply.

5. The Federal Framework: The Stored Communications Act

5.1 The statute. The federal Stored Communications Act, 18 U.S.C. §§ 2701–2712, restricts when a provider like Give Peace may disclose stored communications, and it applies to every request we receive, from anyone, in every state.

5.2 Contents require a search warrant or lawful consent. We disclose the contents of a member's messages only: (a) in response to a search warrant issued on a showing of probable cause; or (b) with the lawful consent of the sender or an intended recipient of the message, as the Stored Communications Act provides; or (c) under another exception the Act itself enumerates, such as the emergency exception described in Section 11. A subpoena is not sufficient for contents. A civil discovery request is not sufficient for contents. We apply the warrant standard to contents regardless of the age of the message.

5.3 Records require appropriate legal process. Non-content records are also protected, at a tiered standard: (a) basic account records — such as a member's name, email address, phone number if provided, account-creation date, and similar subscriber information — require a subpoena or equivalent valid legal process; (b) other records, such as audit-log entries or catalog-type information, require a court order issued on the specific-and-articulable-facts standard the Act sets, or a search warrant.

5.4 Court orders directing contents must carry the required finding. Where a court order directs us to disclose the contents of a member's messages, we ask that the order include a finding that compliance does not violate 18 U.S.C. § 2702. If we receive an order without that finding, our practice is to go back — to the requesting party or to the court — and seek the finding before we comply, rather than treating a bare order as an answer to the federal question.

6. Designation Is Consent: The Lawful Basis for Delivery

6.1 How release is lawful. Federal law permits a provider to disclose the contents of a communication to its intended recipient, and with the lawful consent of its sender. GivePeace's entire delivery architecture rests on both permissions at once: when a member records a message and designates a recipient for it in the Designation Agreement, the member is the sender consenting to disclosure, and the person they named is the intended recipient. Delivery after verified death is therefore not an exception we carve for ourselves — it is precisely the disclosure the member authorized, to precisely the person the member chose.

6.2 Consent runs to that recipient — and no one else. A member's designation of a recipient is their consent that that recipient receive that message. It is not consent that anyone else receive it. Designating a daughter to receive one message is simultaneously a direction that the member's other messages, addressed to other people, do not go to her — and that none of them go to an executor, a sibling, or anyone the member did not name. We read every designation this way: as a direction to disclose to the named person, and a direction not to disclose to anyone else.

6.3 What this means in practice. Delivery to designated recipients proceeds under the Death Verification & Posthumous Release Policy and follows the member's recorded directions. Any request for messages beyond that designated delivery — by an estate, a family member, or anyone else — requires the member's recorded consent to that broader disclosure, or a court order directing disclosure, as Section 7 describes.

7. Requests from Executors, Personal Representatives, and Estates

7.1 Start here: the member's recorded directions control. Most U.S. states have enacted a fiduciary-access law modeled on the Revised Uniform Fiduciary Access to Digital Assets Act ("RUFADAA"), and those laws share a priority rule we have built the Service around: a direction the member recorded in an online tool — for GivePeace, the Designation Agreement — controls over a contrary provision in the member's will, and over anything in our Terms of Service. Where such a law applies, we follow its procedure. Where no such law applies, we apply the same standard voluntarily and uniformly, nationwide, so that every member's recorded choices get the same respect regardless of the state they lived in.

7.2 What an estate request cannot do. There is no informal path. We do not disclose messages or records, delete accounts, or alter a member's arrangements based on a phone call, an emailed letter, a scanned death certificate, or a relationship to the member — no matter how close. An emailed request with a scanned certificate attached will be declined in writing, with a copy of the checklists below. This is not bureaucracy for its own sake: it is how we make sure that what a member sealed for one person is never opened by another.

7.3 Records and catalog requests — what we require. A personal representative requesting a catalog of the member's communications or other non-content records must provide all of the following, which may be submitted electronically:

(a) a written request; (b) a certified copy of the member's death certificate; and (c) a certified copy of the letters testamentary, letters of administration, or other court order appointing the requester as personal representative of the member's estate.

We may also require: the account identifier (the email address on the account), evidence linking the account to the member, and an affidavit stating that disclosure of the records is reasonably necessary for administration of the estate.

7.4 The catalog and the people in it. Remember what Section 2.7 says a catalog is on GivePeace: the identities and electronic addresses of the member's trustees and recipients. Members are promised — in the Trustee & Recipient Terms and throughout the Service — that those relationships stay private. A member's recorded directions in the Designation Agreement therefore defeat a catalog request just as they defeat a contents request: where the member directed that their messages go only to their designated recipients, we treat that direction as a prohibition on disclosing the catalog to anyone else, and we honor it unless a court directs otherwise.

7.5 Contents requests — what we require. A personal representative requesting the contents of the member's messages must provide all of the following, which may be submitted electronically:

(a) a written request; (b) a certified copy of the member's death certificate; (c) a certified copy of the letters testamentary, letters of administration, or other court order appointing the requester as personal representative of the member's estate; and (d) evidence of the member's consent to disclosure of contents to the estate: if the member recorded a direction in the Designation Agreement, that recorded direction controls — and it may bar the disclosure entirely; if the member recorded no direction, a copy of the will, trust, or power of attorney evidencing the member's consent to disclosure of the contents of their electronic communications.

We may also require: the account identifier, evidence linking the account to the member, and a court order that includes findings that the member had the account, that disclosure would not violate 18 U.S.C. § 2701 et seq. or other applicable law, and that disclosure of contents is reasonably necessary for administration of the estate.

7.6 How we disclose when we disclose. When a qualifying request succeeds, we provide a copy in a record — an export of the specific material the requester is entitled to. We never provide login credentials or live access to a member's account, for anyone, under any showing. A member's account contains things no estate showing reaches: the identities of trustees and recipients, unreleased messages addressed to other people, and the member's proof-of-life history. Copy-out of what is properly compelled protects the estate's entitlement without breaching everyone else's.

7.7 Our sixty-day commitment. When we receive a complete estate request — every required item in Section 7.3 or 7.5 — the clock starts, and we will comply, or state in writing why we cannot, within 60 days. If a request is incomplete, we will tell you what is missing; the clock starts when the request is complete. If we do not comply within the required time, a requester under an applicable fiduciary-access law may apply to the court for an order directing compliance.

7.8 Partial requests and undue burden. Where a request seeks a subset of messages or records and segregating that subset would impose an undue burden — for example, where per-recipient encrypted material cannot reasonably be separated — we may seek a court order resolving the scope before producing.

7.9 Fiduciaries get the member's rights, not more. A personal representative stands in the member's shoes. Fiduciary-access law does not give an estate any right the member did not have, and the member's own choices — including deletions the member made while alive — bind the estate. We do not disclose messages the member deleted.

8. Trustees Have No Standing to Request Anything

8.1 The boundary. As the Trustee & Recipient Terms state:

A trustee's only role is to tell us a person has passed away, and to confirm or contest what others have reported. A trustee is not a fiduciary, does not hold or inherit anything, and can never see who a person's recipients are, which messages exist, or what any message says.

8.2 What follows from it. Trustee status confers no authority under this Policy — none. A trustee cannot request the contents of messages, a catalog, account records, deletion, or changes to a member's arrangements, and being a trustee adds nothing to a request made in some other capacity. A trustee who is also a court-appointed personal representative may make an estate request under Section 7, but the appointment, not the trusteeship, is what counts. A trustee has no standing to submit or respond to copyright notices for a member's material (Section 14).

9. Requests from Law Enforcement

9.1 What we require. Consistent with Section 5:

(a) Basic subscriber records — name, email address, phone number if provided, account-creation date, and similar basic account information — require a valid subpoena; (b) Other non-content records — audit-log entries, catalog-type information, and similar records — require a court order on the specific-and-articulable-facts standard, or a search warrant; (c) Contents of messages — the videos and words themselves — require a search warrant issued on probable cause, or the lawful consent of the sender or an intended recipient.

9.2 How to submit. Law enforcement may serve legal process as Section 20 describes. Include the account identifier (email address or phone number), the specific records sought, the date range, and the legal authority for the request. We respond to valid process; we do not respond to informal requests for member information.

9.3 Requests from outside the United States. The Service is offered for use in the United States. Legal process from a non-U.S. authority should come through a U.S. court — for example, through a mutual legal assistance treaty or letters rogatory — unless a U.S. statute expressly provides another path.

9.4 Text-messaging consent records. We keep records of consent to receive text messages, as our SMS & Communications Terms describe, and we produce those consent records to telecommunications carriers and regulators on lawful request.

10. Notice Before We Disclose

10.1 Our default is notice. Before disclosing a member's information in response to legal process, our policy is to notify the affected member — or, if the member has passed away, the member's personal representative if one is known to us — and to give a reasonable opportunity to object, where the law allows us to do so.

10.2 The exceptions. We do not give advance notice where: (a) a court order or statute prohibits it, such as a valid nondisclosure order — in which case we give notice when the prohibition expires; (b) the request falls under the emergency standard in Section 11; or (c) we conclude in good faith that notice would create a risk of harm to a person, or of destruction of evidence, in connection with the matter.

11. Emergency Disclosure

11.1 The standard. If we believe in good faith that an emergency involving danger of death or serious physical injury to a person requires disclosure without delay, we may disclose the information we believe necessary to prevent that harm, as the Stored Communications Act permits. This is a judgment we make case by case; the law permits emergency disclosure but does not compel it.

11.2 How to submit an emergency request. Email support@givepeace.co with the subject "Attn: Legal — Emergency Disclosure Request." Include: your identity and agency or role, a call-back contact, the nature of the emergency, whose information is needed, and why disclosure cannot wait for legal process. We prioritize these requests and respond as quickly as we are able. We keep a record of every emergency request and what we disclosed, and we may ask the requester to follow up with legal process after the fact.

12. Preservation Requests

12.1 What we preserve. On a valid preservation request from a governmental entity, we will preserve a snapshot of the specified records and message material, pending issuance of legal process, for 90 days. We will extend the preservation once, for one additional 90-day period, on a renewed request.

12.2 Preservation is not disclosure. A preservation request does not entitle the requester to the preserved material. Disclosure still requires the process this Policy describes, at the standard appropriate to what is sought.

12.3 Litigation holds. Where we receive notice of litigation or a dispute in which our records are reasonably likely to be evidence, we preserve relevant material as the law requires, independent of any request.

13. We Do Not Confirm or Announce a Death

13.1 Death is the family's news, not ours. Whether a member has passed away is private information until the member's family chooses to share it. A memorial on GivePeace becomes visible only when the family takes that step — never automatically because a report was filed or a verification step completed. Before the family has made a memorial visible, we do not confirm or deny to anyone — a caller, an employer, an insurer, a reporter, or a person claiming to be family — that a member has passed away, that a death has been reported, or that a verification process is underway.

13.2 The exception. We disclose death-status information where valid legal process requires it, under the standards in this Policy, and in the ordinary operation of the Service itself — for example, to the trustees and recipients involved in a verification and release, as the Death Verification & Posthumous Release Policy describes, and to a court-appointed personal representative whose estate request under Section 7 necessarily involves the death.

14. Copyright Subpoenas and Related Proceedings

14.1 Section 512(h) subpoenas. A copyright owner may seek a subpoena from a federal court clerk directing us to identify an alleged infringer, as 17 U.S.C. § 512(h) provides. We respond to valid § 512(h) subpoenas in accordance with their terms. We ask requesters to remember what identification means on this Service: the person identified may be recently bereaved, and where the material was posted by a member who has since passed away, the subpoena may in practice reach a grieving family or an estate. That does not change the law; it does change how carefully we handle the response. Where lawfully permitted, we notify the affected person before complying.

14.2 Injunctions. The Digital Millennium Copyright Act preserves limited injunctive relief against service providers even where the safe harbors apply. We respond to any such proceeding as the statute provides.

14.3 Posthumous counter-notices. As our Copyright & DMCA Policy states: where material posted by a member who has passed away is removed on a copyright notice, we accept a counter-notice only from the court-appointed personal representative of the member's estate, acting in a representative capacity, supported by documentation of the appointment — such as letters testamentary or letters of administration — and a copy of the member's death certificate. Trustee status alone confers no authority to submit one.

14.4 Copyright Claims Board. Proceedings before the Copyright Claims Board are separate from the notice-and-takedown process, and the CCB's service-agent directory is separate from the DMCA designated-agent directory. Notices of CCB proceedings should be served as Section 20 describes; we track and respond within the CCB's deadlines, including its opt-out deadline.

15. Deletion Requests from Estates and Families

15.1 There is no informal deletion channel. Account deletion on GivePeace is available to the member, in the app, while the member is alive, with a 30-day grace period — as the Terms of Service and Privacy Policy describe. We do not delete a member's account or messages at the request of an executor, trustee, or family member, through support or otherwise.

15.2 A deceased member's account is preserved — that is the Service. When a member passes away, their account is preserved so that the messages they sealed can be delivered to the people they chose and the memorial choices they made can be honored. Refusing posthumous deletion requests is not an oversight; it is the promise every member relied on when they recorded their messages. A court order directing otherwise will be handled under this Policy.

15.3 Objections to public memorial material. A family member who objects to something publicly visible on a memorial — a comment, a prayer, a tribute — does not need this Policy: report it in the app, or write to support@givepeace.co, and our Community Guidelines govern review, quarantine, and removal.

15.4 What survives any deletion. Even when a member deletes their own account, some narrow categories survive, for as long as they must and no longer: a minimal delivery archive (an encryption key and message references) kept solely so that armed messages the member acknowledged should still deliver can do so; messages already delivered to recipients, which became theirs on delivery; audit logs, including IP addresses; payment and tax records; and any material subject to a legal hold, a preservation request under Section 12, or preservation duties under the Copyright & DMCA Policy. The Privacy Policy is the authoritative statement of these categories and their retention periods; nothing in this Policy expands them.

16. Stopping Messages to a Phone Number or Email Address

16.1 "Please stop texting this number — he passed away." If you have inherited, been reassigned, or are managing a phone number or email address that receives GivePeace messages — or you are a carrier or estate representative asking on someone's behalf — write to support@givepeace.co with the subject "Attn: Legal — Suppression Request," identifying the number or address. You do not need legal process for this.

16.2 Our commitment. We honor suppression requests within 10 business days — the same standard we apply when a recipient revokes text-message consent under the SMS & Communications Terms. We record who requested each suppression and when, and we keep the number or address suppressed unless its owner later asks us, verifiably, to resume. Suppressing a contact point may mean a message addressed to it cannot be delivered; the Death Verification & Posthumous Release Policy explains that delivery is never guaranteed and the ways delivery can fail.

17. When Claims Compete

17.1 The order we apply. Requests sometimes collide: a personal representative demands messages, a family member objects to a memorial, a recipient exercises rights over what they received, and the member's recorded directions point somewhere else entirely. We resolve collisions in this order:

(a) The member's recorded directions come first. Directions recorded in the Designation Agreement control disclosure and non-disclosure of the member's messages and records, over a contrary will and over anyone's preference, as Section 7.1 describes. (b) The statutory path comes second. Where the member recorded no direction on the question, the fiduciary-access showings in Section 7 govern what an estate can obtain, and the Stored Communications Act governs everyone. (c) A court order resolves the rest. Where parties genuinely dispute entitlement, we may ask a court to resolve the dispute before we act, and a valid court order — with the finding Section 5.4 describes, where contents are directed — controls.

17.2 What competing claims never reach. A message already delivered to its recipient became the recipient's on delivery; a dispute between relatives does not claw it back through us. And a recipient's own rights — to claim or decline a message left for them, to request deletion of their own data — belong to the recipient and are not diminished by an estate's request about the member.

18. Unspent Tokens of Deceased Members

18.1 Tokens are not money. Tokens are prepaid, non-expiring credits used to seal messages; they have no cash value and are not transferable, as the Terms of Service state. An estate cannot redeem, transfer, or spend a deceased member's tokens.

18.2 Unclaimed property. Delaware's unclaimed-property law may nonetheless treat the unspent balance of a deceased member's tokens as reportable property. Our practice: when a member's death is confirmed, we record that date; five years after it, any unspent token balance becomes eligible for reporting to the State of Delaware, measured and reported as the statute directs, in the annual filing Delaware requires. Before reporting, we send the advance notice the law requires to the estate's personal representative where one is on record with us, rather than to the deceased member's own address. Questions about a specific balance may be directed to support@givepeace.co with the subject "Attn: Legal."

19. Fees, and Objections to Overbroad Requests

19.1 Fees. Where the law allows, we may seek reimbursement of the reasonable costs of searching for, assembling, and producing records in response to legal process, and we may assess a reasonable administrative charge for processing an estate request under Section 7. We will state any charge before we incur it; emergencies under Section 11 are never billed.

19.2 Overbreadth. We review every request for scope. Where a request is overbroad, vague, seeks material beyond the requester's entitlement, or would sweep in the messages or identities of people who are not its proper subject — recipients, trustees, other members — we object, seek to narrow it, and if necessary ask a court to limit it before we produce. Narrow requests get faster answers; that is not a threat, it is arithmetic.

20. How to Serve Legal Process on Give Peace Inc.

20.1 By email. Requests, correspondence, and process that may be served electronically should go to support@givepeace.co with the subject line "Attn: Legal" (adding the specific tag this Policy gives for emergencies and suppression requests). Email is our fastest channel, and the one we monitor most closely.

20.2 Formal service. Give Peace Inc. is a Delaware corporation. Formal legal process may be served on our registered agent in Delaware, whose name and address are on file with the Delaware Division of Corporations.

20.3 What to include. Every request should identify: the requester and their authority; the member or account at issue (email address or phone number); the specific records or messages sought and the date range; the legal basis for the request; and how we can reach the requester with questions or objections. Incomplete requests slow everyone down — including, for estate requests, the 60-day clock in Section 7.7, which starts only when a request is complete.

20.4 Acceptance of process is not agreement. Accepting service, preserving material, or corresponding about a request does not waive any objection, and does not concede that any particular process is valid or sufficient.

21. Changes to This Policy

21.1 We may update this Policy as the Service and the law evolve; the version and effective date appear at the top, and we archive prior versions and provide them on request. Material changes are announced as the Terms of Service describe. The commitments in Sections 3, 6, and 7 — legal process or lawful consent, narrow reading, and honoring members' recorded directions — are the spine of this Policy, and no revision will quietly remove them.

22. Contact Us

Give Peace Inc. support@givepeace.co — subject "Attn: Legal" givepeace.co

For emergencies: subject "Attn: Legal — Emergency Disclosure Request." For suppression of a phone number or email address: subject "Attn: Legal — Suppression Request." Formal process: our registered agent in Delaware, on file with the Delaware Division of Corporations.

If you are a family member trying to do right by someone you lost, and this Policy feels like a wall: write to us anyway. We will tell you plainly what we can do, what we cannot, and exactly what the path looks like. The rules protect the person you are grieving. That is why we keep them.

Legal Process & Estate Requests Policy v1.0 — Effective July 30, 2026