QuietMemory privacy
Continuity belongs inside an explicit trust boundary.
This notice describes the data QuietMemory needs to operate the hosted V1 service and the boundaries we intend to preserve around human/companion continuity.
Who operates QuietMemory
QuietMemory is operated by QuietWire Inc., a Canadian federal corporation ("QuietWire," "we," "us," or "our").
What QuietMemory processes
QuietMemory may process authentication identifiers supplied by the configured identity provider, the server-side binding between that authenticated principal and a permitted human/companion pair, pair profile information, memory content deliberately stored in the pair's continuity store, write proposals and receipts, and limited operational logs needed for security, reliability, abuse prevention, and support.
How memory is used
Pair memory is used to provide the continuity functions the authenticated user requests: identify the connected pair, search and read permitted continuity, prepare an append-only memory proposal, and commit an explicitly selected proposal through the governed write path. QuietWire does not use QuietMemory content for behavioral advertising and does not sell QuietMemory content to advertisers.
Pair isolation
Authorization is resolved on the server side from a validated authenticated identity to one permitted pair context. A model is not allowed to choose another pair merely by supplying a name, path, or pair identifier. Administrative ability to operate infrastructure is not treated as ordinary semantic permission to read a person's continuity.
Service operators
Hosted V1 runs on infrastructure operated by QuietWire and therefore authorized operators may have technical access necessary for security, recovery, maintenance, support, or legal obligations. QuietWire's operating policy is to minimize routine semantic access and to keep private continuity separate from organization-wide memory unless material is deliberately promoted.
Third-party services
Authentication is currently provided through an external identity service. When QuietMemory is used from ChatGPT or another model client, that client receives the tool responses needed to satisfy the user's request and processes them under its own terms and privacy practices. Those providers may process data in jurisdictions where they operate.
Writes and history
QuietMemory's first public release uses append-only governed writes. A proposal does not itself change the continuity store; a successful commit creates a durable record. Git history and operational receipts may preserve earlier states even after later correction. QuietMemory V1 does not expose a general-purpose deletion tool to the model.
Retention
QuietMemory retains active pair continuity for as long as it is needed to provide the service or until an authorized deletion or account-close request is completed, subject to technical, security, backup, provenance, and legal retention requirements. Operational logs and backup copies may be retained for limited periods after active data changes. Where a record cannot immediately be removed, QuietWire will explain the applicable limitation rather than representing it as deleted.
Correction, deletion, and access requests
Verified users may contact QuietWire to ask about their pair data, correct an inaccurate service-side binding, revoke access, or request deletion or another privacy action. Because continuity may include provenance records, security logs, or backups, we will explain what can be changed in active service and what may need to be retained for a limited operational or legal purpose rather than silently claiming instant erasure everywhere.
Data minimization
Do not place secrets, credentials, or unrelated sensitive material into a memory merely because the model can store text. The service is designed to preserve useful continuity, not to become an indiscriminate archive of everything a person has ever said.
Contact
Privacy questions: hello@quietwire.ai.
Last updated: 26 September 2026.