1. Your choices and the data involved

Local Vault files remain on your devices. Cloud Memory is optional. When you authorize synchronization for an account-owned Vault, Monolithos receives the authorized source content, source paths, titles, revision and time information, structured retrieval evidence, search indexes and available vectors, plus the account, Vault, device and authorization references needed to provide the service. A project is not required; project filtering is optional.

Each external application requires its own authorization. The connector receives a recall query and search options. It can return source excerpts, paths, locators, revision markers, cloud freshness and coverage information. It does not edit or delete your original Vault. We do not request the surrounding Claude or ChatGPT conversation for recall.

2. Sanctum and authorization

Registered Sanctum private content is excluded from Cloud Memory and external recall. A folder name alone does not establish Sanctum. If previously synchronized content is moved into Sanctum, its cloud withdrawal is applied by the next successful publication; until that publication succeeds, the previously published cloud state can remain available.

Before releasing results, the service checks account identity, Vault ownership, synchronization authority and the external application's grant. Content is encrypted in storage and decrypted by the service after those checks. This is not a zero-knowledge or end-to-end encryption claim against Monolithos as the service operator.

3. Purposes and providers

• We use authorized cloud data to synchronize changes, build and operate retrieval indexes, return evidence-backed search results, enforce access controls and maintain service continuity.
• Keyword recall does not make an embedding-provider call. Hybrid recall sends the search query to Google Gemini for an embedding and uses the account's existing query embedding allowance.
• Google Cloud KMS provides encryption-key wrapping. It is separate from the external application's recall access.
• Selected result excerpts and evidence are sent to the external application you authorized. That application's privacy policy governs its handling of the returned data.
• The connector does not insert sponsored results or use retrieved memory to advertise. It does not generate images, video or audio.

4. Processing locations

The active server is hosted by BandwagonHost in California, United States. The configured Google Cloud KMS region is us-west2 (Los Angeles, United States). Encrypted offsite backups use a private Cloudflare R2 bucket configured for Asia-Pacific (APAC). An R2 location setting is not a promise that every provider operation stays in one country. The active Cloud Memory database is on the VPS; the separate R2 business-storage bucket is not its live store. Provider and connected-application processing may involve other locations under their respective policies.

5. Retention and deletion

Revoking a connector blocks its authorized access. If active-copy cleanup cannot complete, the service can report a pending deletion rather than a completed purge. We do not describe a revoked grant or paused synchronization as proof that every backup has been deleted.

6. Requests and changes

Contact [email protected] for access, correction, export, account or cloud-copy deletion requests, questions about remaining copies, or privacy concerns. We verify ownership before releasing or deleting account data. This optional-feature notice does not replace applicable privacy rights or the existing notice and acknowledgment commitments for material policy changes. Future material changes will follow those commitments.