Subprocessors

The third-party providers that help us run Solipsis, and what each handles.

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].

Third-party subprocessors

We engage the following subprocessors to provide the Service. Each is bound by contract to protect the data it processes. Because content is end-to-end encrypted, providers that store or transmit content handle only ciphertext they cannot read.

Supabase · managed Postgres database, authentication, file storage, and realtime messaging. Handles: account records, public keys, membership, encrypted content (ciphertext), and metadata. United States.
Stripe · payment processing and subscription billing. Handles: billing contact and payment details, plan and seat data. United States.
OVHcloud (OVH US LLC) · server infrastructure on which we host and run the application. Handles: application delivery and server logs (including IP addresses). United States.
Postmark · transactional email delivery (welcome, invitations, receipts, security notices). Handles: recipient email address and the metadata shown in the message; never content or keys. United States.
Cloudflare · DNS, reverse proxy, and content delivery for our domain, and identity checks (Cloudflare Access) in front of our internal administrative panel. Handles: DNS resolution, network-layer request data (including IP addresses), and caching of static application assets. United States.
Google · the public STUN server (stun.l.google.com) our calls use to discover how two browsers can reach each other. Contacted by your browser whenever you start or join a call. Handles: your IP address and the fact and timing of a connection attempt · never call media, message content, or keys.
TURN relay provider · used only where we have enabled a relay and a direct connection between participants is impossible (typically a restrictive corporate or mobile network). Handles: the relayed call media, which stays encrypted between participants and cannot be read by the relay, and participants' IP addresses. Where we run a relay, the provider operating it is named here.
Browser/OS push providers (Apple, Google, Mozilla) · only if you enable push notifications. Handle: a push token and metadata-only notifications (never message content).

One data flow that is not a subprocessor, but that you should know about: if you use the Slack importer, our server fetches the files you select from Slack (using credentials from your own Slack export, or a token you paste in) and passes them straight back to your browser without storing them. Slack is your provider under your agreement with them, not ours. See Section 2 of our Privacy Policy for exactly what our server touches during that request.

Changes

We may update this list as our infrastructure evolves. Business customers under our DPA can subscribe to advance notice of new subprocessors and may object on legitimate data-protection grounds. Questions: [email protected].