ZAK OS

Privacy Policy

Effective October 4, 2026

About ZAK OS

ZAK OS is its owner's private personal AI operating system for organizing personal information, projects and website performance. It is currently a single-owner system, not a public account-registration service. These legal pages are public; the operating system requires owner authentication.

Google access and purpose

Google connections are optional and require the owner's authorization. The integrations below request read-only permissions for the connected account. They do not send email, edit files or contacts, change calendar events, or modify Analytics or Search Console settings.

Storage, AI and memory

OAuth access and refresh tokens are encrypted before storage in a server-side credential vault using a server-held key. Tokens are used by the server to read Google APIs and refresh authorized access; their values are not returned to the web interface.

Synchronization stores source metadata and derived entities and relationships in the application's database. These records can inform the owner's dashboards, Chief assistant and permitted agents. The current deployment uses owner-operated AI and embedding services for assistant processing; relevant Google-derived information may be included in that context. Personal integration access is restricted by agent permissions.

Synchronization does not automatically turn Google records into curated long-term memories. Inferred commitments, deadlines and follow-ups are suggestions that require owner acceptance before becoming personal items. Separately, information the owner explicitly asks ZAK OS to remember can enter its curated memory system; memory changes retain history.

The inspected implementation has no Google-data advertising, sale, or model-training workflow. This policy does not promise that data is never processed by another service: Google receives authorized API requests, and the owner's AI services process relevant assistant context.

Retention and revocation

There is no general automatic expiry or fixed deletion period for synchronized Google records, derived knowledge, suggestions, conversations or audit history. A source lookup window is not a retention deadline. Records no longer found during synchronization are marked removed rather than erased.

The owner can revoke access in Google Account connections or use ZAK OS's authenticated integration disconnect operation. ZAK OS disconnect deletes the connection's stored OAuth token, stops future scheduled reads and marks its synchronized resources removed. It attempts Google-side revocation and reports whether it succeeded; Google Account settings remain available if that attempt fails.

Disconnecting does not automatically erase previously derived entities, relationships, accepted personal items, memories, conversations or audit history. The implementation does not provide a complete Google-data erasure operation or a guarantee of deletion from every stored copy.

Contact

Privacy questions about this private system should be directed to its owner through the existing direct contact channel used to obtain access. ZAK OS currently has no public support inbox or registration service.