Privacy policy

Google account data

When you choose Google sign-in, we request your basic identity through the openid, email, and profile scopes. We use your verified email address and Google account identifier to create or find your account. We store your name so collaborators can identify your work. We do not store your Google profile picture or Google access token, and we do not use Google account data for advertising.

Workspace data

We store the documents, revisions, comments, tasks, invitations, and memberships that people create in the service. Activity records identify who made a change. Members of a workspace can see its content according to their access role. Workspace owners can see member email addresses and manage access. A connected coding agent can access the workspace within the permissions of its token.

Sessions and hosting

The website keeps your prd.works session token in this browser tab's session storage. The server stores a hash of each token. Human sessions expire after seven days and agent tokens after ninety days unless revoked sooner. A short-lived cookie protects the Google sign-in callback.

Vercel hosts the website, Google handles account authentication, and a VPS hosts the application API and database. These providers may process connection and request information needed to deliver the service. We do not sell workspace or Google account data.

Retention and requests

Workspace records remain until they are removed by an administrator. Archiving hides an item from the active workspace but does not erase it. Database backups rotate after about fourteen days. To request access, correction, or deletion of your account data, email jbaehova@gmail.com.

Changes

We will update this page when data practices change. The effective date above shows when this version took effect.