Your context 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

Your account email, connection permissions, short shared briefs, source references, retrieval receipts, trial and purchase status, and the Gumroad license key used to verify access. The license key is kept in a private server-only table; payment card details are handled by Gumroad and are not stored by Share.

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 checks again after 30 days and periodically while the account is used.

What the AI accounts can access

Each authorized connection is limited to its assigned Share workspace. It can publish a brief, retrieve updates, and acknowledge context. It cannot manage your billing, view your license key, or access other workspaces.

Your controls

Pause or disconnect a connection, export your briefs, and remove individual briefs. Removal sends a deletion notice to connected accounts; it cannot erase copies already stored in an AI provider’s chat history or native memory.

Before launch

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