Privacy Policy

ZOS stores account identity information, such as an approved user’s email address, and the service data the user enters or connects to operate calendar, task, training, school, meal, and work features.

Operational records may include settings, connection status, synchronization timestamps, and error logs needed to maintain and secure the service.

When a user connects Google Calendar, ZOS receives the Google account email, OAuth access and refresh credentials, and the list of calendars available to that account. The user chooses which calendars ZOS mirrors.

For selected calendars, ZOS stores calendar identifiers and settings plus event details needed for the local mirror. Those details may include event title, description, start and end time, all-day status, location, Google event link, color, ZOS tags, and synchronization metadata.

ZOS uses this data to display a personal calendar, understand availability and planning constraints, keep the local mirror current, and perform event operations the user directs. Those operations can include creating, updating, moving, or deleting an event.

When a user requests a Calendar write, ZOS sends Google the event details needed for that request. Depending on the requested change, those details can include attendees, recurrence, reminders, visibility, and a Google Meet option.

ZOS no longer reads Gmail. For a short period it offered an optional read-only Gmail connection (the gmail.readonly scope) for Networking, and that feature has been retired: ZOS does not read, sync, or classify email, and it never sent email or changed messages, labels, or read status.

If a user connected Gmail during that period, ZOS may still hold the connection’s stored credentials and, for messages it matched, the message and thread identifiers, date, direction, sender address and name, subject, and a short snippet. Settings → Integrations → Disconnect deletes the stored Gmail credentials; the user can ask ZOS to delete the stored message details at the support address below. Gmail data was never used to train AI models.

Google OAuth credentials are stored in server-only database records that are not available to the unauthenticated public or the signed-in browser. ZOS uses the refresh credential on the server to obtain short-lived access credentials for background synchronization and user-requested calendar operations.

ZOS uses HTTPS in production and limits credential access to server processes that need it to operate the connection. No online service can guarantee perfect security.

ZOS does not sell Google user data or other personal information. ZOS does not use Google Calendar data for behavioral advertising or for purposes unrelated to the user-facing features described in this policy.

ZOS uses service providers to run the application: Vercel provides application hosting and related infrastructure, Supabase provides authentication and database infrastructure, and Google provides the Calendar API and OAuth service. When a user chooses an AI-assisted planning feature or connects ZOS to an AI client, relevant planning context, which may include calendar commitments, is sent to the provider handling that user-requested operation.

Providers receive information only as needed to perform services for ZOS. Information may also be disclosed when required by law or when necessary to protect the service, its users, or others.

ZOS’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Disconnecting Gmail in ZOS Settings deletes the stored Gmail credentials and stops synchronization; conversations and application updates already recorded remain in ZOS until deleted.

A user can stop future Google Calendar access by removing ZOS from the third-party connections page in their Google Account. Revoking access stops future synchronization but does not by itself delete information already stored in ZOS.

To delete the ZOS account, stored Google Calendar mirror, or OAuth credentials, email zacharynguyen04@gmail.com. Deletion requests are completed within 30 days.

ZOS keeps account and service data while it is needed to provide the service, maintain security, or meet legal obligations. Requested deletions are handled as described above.

If ZOS changes how it uses Google user data, this policy and any relevant in-product disclosure will be updated before the new use begins. Affected users will be asked for consent when required.

Questions, support requests, and privacy or deletion requests can be sent to zacharynguyen04@gmail.com.