Privacy policy

1. This public website

The pages on memento.bezosapp.uk provide product, setup and policy information. They contain no analytics scripts, advertising trackers, third-party fonts or memory database connection. The site does not set application cookies or provide a sign-in form.

The hosting and network providers may process ordinary connection information, such as IP addresses, request paths, browser information and access times, to deliver HTTPS traffic and operate or secure the service. Their infrastructure practices are separate from the absence of tracking code on these pages.

2. Data in a Memento installation

When its native integration is enabled, Memento captures conversation records and associated source, conversation and time metadata. Explicit history import processes the local files selected by the operator. The system can also store submitted artifacts, including images, audio, video and documents.

Processing may derive memories, scope labels, relationships and follow-up markers from that evidence. These records can include original quotes, source offsets, change history and known processing-model or usage metadata. Raw evidence and derived assertions remain distinct.

This information is used for the installation’s memory capture, retrieval, provenance, correction, follow-up, archival and recovery features. The public website does not publish it.

3. Optional Google Drive access

The Google Drive integration is connected through an explicit Google consent flow. Memento requests the https://www.googleapis.com/auth/drive.file scope. It does not request blanket access to all files in your Google Drive.

• Account verification: Memento verifies that the connected Google account matches the account specified during setup.
• Dedicated storage: it creates its own Memento folder and app-accessible files for cold archives and owner-requested backups.
• Archive and recovery: it uploads, retrieves and verifies those artifacts and backup snapshots to support the installation’s storage and recovery features.

A private connection file retains the authorization information required for future access, together with the verified account and folder identity. The installation protects that file with owner-private filesystem permissions. It must not be committed to source control or shared through this website.

Google API information is used to deliver Memento’s user-facing memory, archive and recovery features, not to sell data or target advertisements. Memento’s use and transfer of information received from Google APIs must adhere to the Google API Services User Data Policy, including its Limited Use requirements.

4. Model providers and other services

Memory extraction and consolidation use the operator’s configured native agent CLI and its existing model account. Conversation content supplied for those operations may be processed by that model provider. Its policies and the operator’s account settings govern that processing. Memento has no model-training feature; this does not make a promise about an independently selected provider’s retention or training practices.

The operator is responsible for choosing compatible providers, permissions and account settings. Optional Google Drive transfers send the selected archive or backup data to Google. Memento itself does not add an advertising or data-sale integration.

5. Storage, security and retention

The memory service is designed to run on private infrastructure with restricted access. This public site is separate from the unauthenticated memory API; deploying that API directly to the public internet is not supported. Operators must maintain the documented service ownership and network protections.

Memento does not provide application-level encryption for Drive archive or backup contents. Drive copies are plaintext to the application, and retained versions consume the owner’s storage quota. Filesystem permissions and private networking do not replace an operator’s responsibility for disk, account, backup and transport security.

Records remain until the installation’s operator removes them under its retention and recovery procedures. There is no universal automatic deletion period. Native CLI histories, exported files and provider-side copies may have separate retention rules.

6. Your choices and deletion limits

• Enable only the native integrations you intend to use, and select history-import paths explicitly.
• Use evidence and history tools to inspect the source of a memory and its subsequent changes.
• Correct or refine inaccurate memories through the supported tools.
• Disconnect Memento through your Google account’s third-party connections to revoke future Google access. Revocation does not automatically delete files already stored locally or in Drive.
• Ask the installation operator to carry out owner-only administrative actions and any necessary manual data or backup removal.

“Forget” is not a promise of complete erasure. The owner-only forget action removes active memory and suppresses re-extraction, but it retains raw history, artifacts and existing backups. An old backup can restore previously forgotten content. Separate removal is needed when those copies must also be erased.

7. Contact and policy changes

For questions about a particular installation or its retained data, contact that installation’s operator. For product or policy questions, contact the maintainer through the Memento issue tracker. Do not post private conversations, authorization files or other sensitive data in a public issue.

Material changes to this policy will be reflected on this page with an updated date. The actual deployment configuration and the policies of independently used providers still matter.