Your memory belongs to you.

Prelaunch information. The operator’s contact details and final retention policy must be added before public sign-up opens.

What Share is being built to store

The planned first release stores your account email, connection permissions, source references, raw conversation packets a permitted connection synchronizes, extracted memory candidates, memories you approve or review, legacy shared briefs, retrieval receipts, and trial and purchase status. The Gumroad license key used to verify access is kept in a private server-only table. Payment card details are handled by Gumroad and are not stored by Share.

Raw processing and long-term memory

A raw conversation packet may contain conversation text and metadata selected by the connected AI. The first release is designed to keep these packets for up to 30 days for extraction, retries, and audit, then schedule them for deletion. Approved or reviewed memories are deliberately durable and remain available until you edit or forget them. The final policy will document backup deletion timing and retention for the legacy brief exchange before launch.

Automated processing

Share is being designed to extract concise memory candidates from synchronized packets through a private workflow. If an external AI model processes that content, the final policy will identify that provider and the information sent to it. A candidate may be incomplete or inaccurate, so important memories should be reviewed.

Purchase checks

Share sends the product identifier and your license key to Gumroad to confirm the purchase, matching email, refund, dispute, and chargeback status. It is designed to check again after 30 days and periodically while the account is used.

What connected AIs can access

Each connection is limited to its assigned Share workspace and to the capabilities you explicitly enable. Reading memory, proposing memory, synchronizing conversations, and handling sensitive memories are separate permissions. The Share authorization does not grant billing management, license-key access, or access to another workspace.

Coverage limits

Consumer ChatGPT and Claude do not provide Solum Share with a guaranteed automatic export of every chat. Memory capture there depends on the connector being available and invoked. Hermes hooks and chats you operate through an API can be connected deterministically. Disconnecting Share does not delete copies already present in an AI provider’s chat history or native memory.

Your controls

The first release is intended to let you pause or disconnect a connection, change its capabilities, review candidates, edit or forget approved memories, and export your data. Forgetting a memory removes its content from future Share retrieval; a minimal non-content audit marker may be retained to prevent replay, subject to the final retention policy.

Before launch

The final policy must name the operator and contact, deployment regions, service providers and processors, retention and backup deletion periods, security contact, and the account deletion process. The current sample dashboard contains illustrative data only.