You choose the connection
Cloud OAuth access is tied to workspaces and collections. The standard authorisation grants access to your current normal personal-memory collections; it does not offer per-line choices.
Security and ownership
Your memory. Clear access boundaries.
Where the alpha keeps memory, what a connected agent can read, and which controls are available today.
Who can read it?
Access is checked before retrieval
Document browsing, source reads and search are restricted to permitted material.
The agent still uses a model provider
Unforgetter uses OpenAI for classification, memory maintenance and embeddings. Retrieved material also enters your connected agent’s context, where that agent provider’s terms and settings apply.
Where is it stored?
| Component | Cloud alpha |
|---|---|
| Service | The current application and Postgres deployment uses an EU Railway region. This does not mean all AI providers, support access or onward processing are EU-only. |
| Serving memory | Published document generations in Postgres, with retrieval indexes. Source material remains readable Markdown. |
| Publication | Cloud supports checked source publication and permissioned proposals. Automatic capture and maintenance run for explicitly enabled pilot collections; new-user setup remains guided. |
| Original pilot | Separate Markdown gateway and an owner-controlled publisher. Its 15-minute cycle does not describe every Cloud workspace. |
| Website applications | Sent through Resend to the Unforgetter inbox for a personal reply. Product memory is not submitted through this form. |
Choose a small starting scope.
Start with project notes, decisions and preferences suitable for an early product. We agree the material and access before onboarding. Keep passwords, API keys and other credentials out of the memory and application.
Sensitive personal material is outside the external alpha scope. Business use involving ordinary personal data also requires an appropriate processing agreement and lawful customer instructions. Tell us about your requirements before connecting the material.
How do changes and leaving work?
Changes
Cloud retrieval is read-only. A connection with memory:propose permission can append pending proposals to a writable collection. A separate scoped worker validates and activates updates only for enabled collections; a proposal cannot directly overwrite active memory.
Export
The source memory is Markdown. Packaged Cloud export is still in build; discuss the available handover process with us before joining.
Revoke and delete
Pausing stops this companion’s capture and automatic recall. Device disconnection and team archival close the relevant access; they do not erase saved memory. Contact hello@unforgetter.com for access, export or deletion. Complete self-service Cloud deletion is not available.
What a standard agent connection can read.
When you authorise a Cloud agent, the standard connection receives access to the normal personal-memory collections you own at that time, for public and internal data classes. The requested scopes determine reading and proposed updates. These technical class names do not mean information is published on the public internet.
This is collection-based access, not a self-service choice of individual lines for each agent. Team membership and companion source approval are checked separately. Review the scope before connecting an agent.
Before wider access.
Team access checks exist in the code. Independent isolation verification, a tested backup/restore lifecycle, complete export and erasure operations, and customer/provider processing agreements must be verified for the intended use. We do not claim SOC 2 or ISO 27001 certification or an independent penetration test.
This page describes the Cloud alpha and identifies the separate original pilot where relevant. Setup and supported controls are agreed before an invitation.
Private alpha
Pick up where you left off.
Free during the private alpha. We help you connect your first agent.