Privacy Policy

What we can and cannot see, what we collect, and your rights over it.

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. Our approach to privacy

Aureum Growth Solutions LLC ("Solipsis," "we," "us") operates the Solipsis Service. This Privacy Policy explains what information we handle and your rights. For business customers, our Data Processing Addendum also applies.

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.

Our business model is selling seats · not data. We do not sell or rent personal information, we do not serve advertising, and we do not use third-party analytics or tracking on the application. We collect the minimum needed to run the Service and bill for it.

2. Information we handle

Account information

Your email address (used to sign in and for essential Service and billing notices).
Your display name.
Your password is sent to our authentication provider (Supabase) over an encrypted connection when you sign up or sign in, and is stored only as a salted hash. We never store your password in plaintext, and your password is never used to derive your encryption keys. We never receive your private keys or your master seed.
Your public keys and salted authentication material · the public halves used to seal content to you and to verify sign-in.

Workspace metadata (not encrypted)

Workspace, channel, and room names; roles; membership and the invite graph (who invited whom, who belongs to which workspace); and thread structure. These are stored in the clear so the Service can route and display them — they are not encrypted content, and people in your workspace can see them.
An audit log of workspace administrative actions (metadata only · who did what and when, never content).

Content · ciphertext only

Messages and files are encrypted on your device. We store only the ciphertext and the minimal routing metadata required to deliver it (for example: which encrypted blob belongs to which channel, message timing, thread structure, and message/file size and type). We cannot read this content.
Calls are peer-to-peer where the network allows and are encrypted in transit · we do not record or store them. Establishing a call reveals the participants' IP addresses to the public STUN server we use, and where a direct connection is impossible and we have enabled a relay (TURN), the encrypted media passes through that relay. Both are listed on our Subprocessors page.

Importing from Slack · a transient exception

If you use the Slack importer, the files you select are fetched from Slack by our server and streamed straight back to your browser, which encrypts them before they are stored. For the length of that single request those file bytes are in our server's memory in the clear. We do not write them to disk, to our database, or to our logs, and nothing about them survives the request.
That import can use a Slack API token that you paste in. We send it only to Slack, only to authorize those downloads, and only for that one request · we never store it, log it, or reuse it. You can revoke it in Slack once the import is done.
The importer also hands you a plain, unencrypted zip of your files to drop back into the app. That file sits on your own device until you delete it.

Billing information

Payments are processed by Stripe. We do not store full card numbers. We retain limited billing metadata such as your plan, seat count, subscription status, and a Stripe customer/subscription identifier. Stripe processes your payment details under its own privacy policy.

Technical and log information

Standard server and security logs, which may include IP address, timestamps, and basic device/browser information, used to operate, secure, and debug the Service and to prevent abuse.
If you enable push notifications, a push subscription token from your browser/OS push provider; notifications we send contain only metadata (for example, a channel name), never message content.

Support information

If you contact support, the information you choose to share. Support attachments you submit are encrypted to a support key; we open them only to help you.

3. What we do NOT collect

The content of your messages, files, or calls (we hold only ciphertext, and calls are never stored). The one exception is the Slack importer described in Section 2, where imported files pass through our server's memory in the clear during a single request and are never retained.
Your password in plaintext (our authentication provider stores only a salted hash), your private keys, or your master seed.
Third-party advertising or cross-site tracking identifiers.
Analytics profiles built from your behavior in the app.

Our internal administrative tools let us view the account, workspace, membership, invite, billing, and support metadata described above · to operate the Service, help you, and comply with law. They cannot show your message or file content or your encryption keys: that plaintext does not exist on our servers.

4. How we use information

To provide, maintain, and secure the Service and route encrypted content.
To create and administer accounts and workspaces and enforce roles and limits.
To process payments, manage subscriptions, and send billing and transactional emails.
To respond to support requests and to detect, prevent, and address abuse, fraud, or security incidents.
To comply with legal obligations and enforce our Terms and Acceptable Use Policy.

5. Legal bases (EEA/UK)

Where the EU or UK GDPR applies, we rely on: performance of a contract (to provide the Service you request); our legitimate interests (to secure and improve the Service and prevent abuse), balanced against your rights; compliance with legal obligations; and, where required, your consent (for example, optional push notifications), which you may withdraw at any time.

6. Sharing and subprocessors

We share information only with the service providers ("subprocessors") whose infrastructure and services we use to run the Service, listed on our Subprocessors page, each bound by contract to protect it. We may also disclose information if required by valid legal process (see our Law Enforcement Guidelines) or to protect rights, safety, and the integrity of the Service, and in connection with a merger, acquisition, or asset sale (with notice). We do not sell personal information.

7. International transfers

We and our subprocessors are based in the United States, and information is processed there. Where we transfer personal data from the EEA, UK, or Switzerland, we rely on appropriate safeguards such as the European Commission's Standard Contractual Clauses. Contact [email protected] for details.

8. Data retention

We keep information for as long as it is needed to run the Service. We would rather tell you what actually happens than quote a schedule we do not run, so: except where stated below, nothing is deleted on a timer · it stays until it is deleted, by you or with the workspace or account it belongs to.

Account information (email, display name, public keys): kept while the account exists.
Encrypted content (message and file ciphertext): kept until you or your workspace administrator delete it, or the channel or workspace it belongs to is deleted. It is not deleted on any schedule unless a workspace owner turns on the optional retention setting · available on our Studio and Enterprise plans, off by default · which deletes messages older than the number of days that owner chooses, together with the files sent alongside them. A workspace owner may also arm an inactivity switch or idle-room expiry, which delete on the terms shown in-app.
Workspace metadata and the administrative audit log (metadata only, never content): kept for the life of the workspace and deleted with it.
Billing records (plan, seat count, subscription status, and payment-processor identifiers): kept for as long as we need them to meet tax and accounting obligations · normally several years, and outlasting the account. Your card details are held by Stripe, not by us, under Stripe's own retention.
Support tickets and the messages in them: kept until we delete them. We do not delete them on a schedule today. Email [email protected] to ask us to delete a support conversation.
Server, network, and security logs: the request and container logs on the servers we run are rotated daily and deleted after 90 days. Beyond those, the logs kept by the hosting, database, and network providers on our Subprocessors page are held under those providers' own retention schedules. We do not operate a separate long-term log archive of our own.

Deletion is irreversible and removes the ciphertext and metadata we hold, except for records we are legally required to keep (such as billing and tax records). Copies may also persist for a time in our providers' automatic infrastructure backups until those backups age out under the providers' schedules; content in them is ciphertext we cannot read.

9. Security

Security is the core of the product. Content is end-to-end encrypted; server-side access is governed by row-level security so that keys sealed to you are readable only by you; transport is encrypted in transit. No system is perfectly secure, and you play a critical role by protecting your password, device, and transfer code.

If we become aware of a personal-data breach affecting you, we will notify affected users and, where required, the relevant authorities without undue delay and consistent with applicable law. Because your message and file content is end-to-end encrypted, a breach of our servers would expose ciphertext we cannot read rather than your content; it could, however, expose the metadata described in this Policy, such as email addresses and workspace membership.

10. Your rights

EEA / UK (GDPR)

You may request access to, correction of, deletion of, or a copy (portability) of your personal data; object to or restrict certain processing; and withdraw consent. You may also lodge a complaint with your local data-protection authority.

California (CCPA/CPRA) and other U.S. states

You may request to know, access, correct, and delete your personal information, and to opt out of "sale" or "sharing" of personal information and of targeted advertising. We do not sell or share personal information and do not use it for cross-context behavioral advertising. We will not discriminate against you for exercising these rights.

Deleting your account yourself

You do not need to ask us. Settings → Account → delete my account removes it directly: we immediately erase your profile, your memberships, your keys, and every message and file you authored — including in workspaces you have already left. You must first delete or hand over any workspace you own, because deleting an owner would destroy the other members' data with them; the screen names the workspaces still blocking you. Two things survive by nature rather than by choice: billing records, which we keep as described above, and anything other members have already decrypted onto their own devices or saved as a backup, which is outside our reach — that is a property of end-to-end encryption, not a retention policy.

How to exercise

Email [email protected]. We will verify your request and respond within the time required by law. Note that, because of end-to-end encryption, we cannot access or provide the plaintext of your content · only the limited account and metadata described above. If your data lives in a workspace administered by someone else, we may direct your request to that administrator (controller).

11. Children

The Service is not directed to children. You must be at least 18 years old to use it, and we do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us information, contact [email protected] and we will delete it.

12. Cookies and local storage

We use only strictly-necessary cookies and browser storage to keep you signed in and to hold your encrypted vault on your device. We do not use advertising or analytics cookies. See our Cookie Policy for details.

13. Changes

We may update this Policy. Material changes will be posted here with a new date and, where appropriate, notified in-app or by email.

14. Contact

Data controller: Aureum Growth Solutions LLC, 1000 Brickell Avenue, Suite 715, Miami, FL 33131, United States.

Privacy requests and questions: [email protected].