Privacy

Anchor is designed around context: memories, presence signals, identity preferences, consent records, device state, and the continuity records people choose to create.

We treat this information as sensitive by default. Public pages may collect ordinary technical data such as browser, device, approximate location, and log information needed to keep the service reliable and secure.

We use context to provide Anchor products, synchronize shared state, prevent abuse, maintain security, support users, and improve the reliability of continuity infrastructure.

Anchor does not need every moment to become data. Product surfaces should make it clear when context is private, shared, provisional, archived, or awaiting review.

People should be able to inspect, export, correct, delete, or restrict context where product and legal constraints allow. Shared records may preserve audit trails so other participants can understand what changed.

Enterprise and institutional deployments may add retention, export, and review policies set by the organization that administers the workspace.

Anchor keeps personal context only as long as needed for the product, safety, security, legal obligations, or user-selected archive settings.

We may work with vendors, infrastructure providers, auditors, and support partners under appropriate contractual controls. We do not sell shared memory or presence context.

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or export personal information. Anchor will evaluate requests according to applicable law, product capability, and the rights of other participants in shared records.

Some requests may require identity verification. If a record includes multiple participants, Anchor may preserve enough information to maintain auditability, prevent fraud, or explain why a shared record changed.

Anchor products are not directed to young children. Workspaces involving minors, care relationships, health information, education records, or family archives require additional care and may be subject to institutional policy.

Sensitive context should be collected only when it is necessary for the product or deployment and when the participant has appropriate notice, authority, and control.

Anchor services may be operated, supported, or processed in countries other than where a participant lives. When data moves across borders, Anchor uses appropriate legal, contractual, and technical safeguards.

Regional privacy laws may provide additional rights or limitations. Workspace administrators are responsible for configuring deployments in line with their own obligations.

Privacy questions, data requests, and concerns about shared context should include the relevant account, workspace, product area, and the action requested.

Anchor will not disclose private context in response to a request unless the requester is authorized to receive it or the disclosure is legally required.