Law Enforcement Guidelines

What we can and cannot produce · and the process for valid legal requests.

LAST UPDATED · August 18, 2026Aureum Growth Solutions LLC

This document is provided for transparency and does not constitute legal advice. Your use of Solipsis is governed by its full text. Questions? [email protected].

1. What end-to-end encryption means for legal requests

Solipsis is end-to-end encrypted. Your messages and files are encrypted on your device before they reach us; we · and our infrastructure providers · store only ciphertext we cannot read. Calls are peer-to-peer wherever the network allows, are encrypted in transit, and are not recorded or stored by us; connecting a call does disclose the participants' IP addresses to a public STUN server, and where a direct connection is impossible and we have enabled a relay (TURN), the still-encrypted call media passes through that relay — both are named on our Subprocessors page. One further, narrow exception: if you use the Slack importer, the files you choose to bring across are fetched by our server and passed back to your browser in the clear, which then encrypts them; those bytes (and the Slack API token you may supply to authorize the download) exist only in our server's memory for the length of that one request and are never written to our disks, our database, or our logs. Your private keys and master seed never leave your devices and we never receive them; the per-workspace keys that let members read shared content are themselves encrypted to each member's device (and if you generate an incoming-webhook URL, that URL embeds a channel key and passes through our servers transiently — treat it as a secret). Apart from that transient import path, we cannot access, disclose, monitor, moderate, or recover the content you send, and we cannot restore it if you lose all of your devices and your transfer code.

Because message and file content is encrypted with keys that stay on users' devices, Aureum Growth Solutions LLC does not possess and cannot produce the plaintext of user content, and cannot decrypt it, in response to any legal request. We have no mechanism to produce user content in plaintext; doing so would require fundamentally re-engineering the client software that runs on users' devices.

The single exception noted above · the Slack importer, where files a user chooses to bring across pass through our server's memory in the clear · is transient by construction: those bytes exist only for the duration of one user-initiated request and are never written to disk, to our database, or to our logs. We therefore hold nothing from it to preserve or produce after the fact, and we have no way to retrieve a past import.

2. What we can provide with valid legal process

In response to valid legal process, and only to the extent we hold it, we may be able to provide limited non-content account information, which may include: the email address on an account, workspace membership and role, account and workspace creation timestamps, and billing metadata (plan, seat count, and a payment-processor identifier; card details are held by Stripe, not us). We may hold basic security logs (such as IP addresses) for a limited time.

3. Valid legal process

We require legal process appropriate to the request and to U.S. law. We disclose non-content records only pursuant to a valid subpoena, court order, or other lawful demand, and content · which we cannot decrypt in any event · only where required by a valid warrant or its equivalent. We may object to, narrow, or seek to quash overbroad or improper requests.

Send requests to [email protected] from an official law-enforcement email address, including the requesting agency, the legal basis, the specific account identifier (email), and the records sought.

4. Emergency requests

In emergencies involving a risk of death or serious physical harm, law enforcement may submit an emergency request to [email protected] describing the emergency. We may voluntarily disclose limited information we hold where we believe in good faith that an emergency requires it, consistent with law.

5. Notice to users

Our policy is to notify affected users of requests for their information before disclosure so they may seek to protect their rights, unless we are legally prohibited (for example, by a court-ordered nondisclosure), or in an emergency, or where notice would be counterproductive or create a risk to safety.

6. Preservation and jurisdiction

We may honor valid preservation requests for records we hold for the period required by law. Aureum Growth Solutions LLC is a Wyoming, U.S. company; we evaluate requests under U.S. law. Requests from outside the United States generally must proceed through mutual legal-assistance treaties or letters rogatory, except for emergencies.

7. Transparency

We are committed to transparency about the requests we receive, consistent with our legal obligations. Direct questions to [email protected].