ZhenMem Privacy and Data Boundary

ZhenMem does not ask you to send your entire context to the cloud first. Local memory assets stay local, and only the information needed for the current opportunity is approved for matching. This page explains what stays local, what enters matching, and where purchases and later signed-in actions continue.

Back to Home Opportunity Engine Upgrade Path Documentation Center

1. Local Memory Boundary

Contacts, notes, relationship context, and long-term memory assets should remain in local Skills or user-controlled environments first. ZhenMem does not default to cross-user or cross-tenant context sharing.

Those local memory assets are not decorative background; they are the source of matching quality. The cloud should receive only authorized tags, profiles, relationship signals, and the minimum business metadata required for opportunity matching, explainability, and later service execution.

We do not describe raw-memory backflow, cross-user tag pools, or default long-term signal recycling as launched behavior.

2. Public Frontend, Uploads, and Matching

Public pages explain what the product does, how it works, and where to go next. Authenticated matching requests, uploaded assets, and chat threads are processed only to deliver the requested functionality.

Users should not upload material they are not permitted to share. If content is regulated or highly sensitive, the uploader remains responsible for securing the required approvals and legal basis.

3. Matching Results, Collaboration, and File Exchange

The result view only shows candidates, report preview state, and collaboration entry points. If a user enters chat threads, file exchange, or follow-up delivery, those materials stay scoped to the current match and current authorization rather than syncing all local memory into the cloud.

Activation details, recovery actions, and other signed-in tasks created during collaboration continue on later pages instead of being managed on the public site.

4. Accounts and Purchases

Authenticated activation details, API keys, recovery actions, and other signed-in tasks continue on later pages.

This site can handle registration, upgrade explanation, and matching entry, but it does not turn into your full signed-in management center.

5. Retention and Incident Response

Operational records still required for billing, security, anti-abuse, or incident response may be retained for a limited period after deletion requests. That retention exists to protect the system and satisfy legal obligations, not to broaden public access.

When account deletion, credential revocation, or privacy incidents occur, the formal account and operations process should take priority, with only the minimum evidence retained for recovery, audit, and legal review.