Privacy notice

This notice covers the Zippytal Projects CRM at projects.zippytal.com. For the shared Zippytal account, login session, and the JWT cookie used across every Zippytal subdomain, see the parent zippytal.com privacy policy.

Three account types interact with the CRM, with different data visibility:

• Super-admin — sees every project across the workspace, manages teams, grants access.
• Business-admin — runs their own projects and is invited into others.
• Project client — external user, scoped to the projects they're explicitly attached to via a per-project membership row.

• Projects — name, description, color, dates, status, who created it.
• Tasks — title, description, status, priority, schedule, time-tracking entries, comments, an internal visibility flag (private vs. team-visible).
• Phases & features — roadmap groupings and backlog items inside a project.
• Documentation — markdown pages and uploaded file attachments. Files live under our upload directory on the server (never on a public CDN); access is gated by the same project-membership check as the rest of the project.
• Calendar events — project-scoped events with optional Zippytal Meet room links.
• Project-client memberships — which client accounts are attached to which projects, plus a flag indicating whether they have editor permissions on that project.

Connecting Google Calendar is opt-in. When you click Connect Google, we go through Google's OAuth consent screen, exchange the returned authorisation code for a refresh token and an access token, and store both encrypted at rest (AES-256-GCM) on a row bound to your Zippytal account id. Tokens never leave the server. We request the calendar.events and calendar.readonly scopes — enough to push CRM events to your calendar and pull events back for the window the user is viewing. Disconnect any time from the calendar tab; that drops the integration row immediately.

Tasks marked private are visible only to their creator, their assignee, and super-admins. Tasks marked team-visible (the default) are visible to every member of the project. Clients see only the projects they have memberships on — no other project metadata leaks across the boundary.

Project, task, and document rows live in the same shared accounts database used by the rest of the Zippytal ecosystem. Hosting provider and region are described in the parent privacy policy at zippytal.com/privacy.

Project data is retained while the project exists. Super-admins (or the project creator) can delete a project, which removes the project row and cascades to its tasks, comments, time entries, documentation, attachments (including the bytes on disk), and calendar events. Removing a client membership revokes the client's access without deleting their account.

The same rights described in the parent policy apply to data stored here: access, rectification, deletion, portability, restriction, and the right to lodge a complaint. Reach us at privacy@zippytal.com.

privacy@zippytal.com for privacy questions about projects.zippytal.com.