Data we process
When you sign in with Google, we receive the information needed for authentication from your verified Google identity: account identifier, name, email address and profile picture, if available.
Collaboration data may include invitees’ email addresses, invitation status and expiry, project memberships and roles, page URLs, screenshots of pages under review, annotation coordinates and content, task priorities and status, assignments, comments and dates.
We also manage session identifiers, temporary authentication tokens and technical connection information that the web server may log, such as IP address, time and requested URL.
Screenshots may contain personal information visible on external pages. Project creators should avoid including confidential or unauthorized content.
The optional Pinpoint Capture extension browses and captures pages in the user’s local Chrome browser. It temporarily applies the selected desktop, tablet or mobile resolution and sends a JPEG screenshot only after an explicit capture command. The screenshot passes through the Pinpoint server’s memory and is saved in the uploader’s Google Drive, in the Pinpoint folder, using that account’s storage. The server retains file identifiers and metadata, without saving new persistent image copies. Website cookies, credentials and browsing sessions normally stay in the user’s Chrome profile and are not uploaded to Pinpoint. Screenshots themselves may contain personal information visible on screen.
A temporary, single-use code valid for 5 minutes pairs the extension with the account. The extension stores a revocable access token locally, valid for up to 90 days, to list authorized projects and upload screenshots. The connection can be revoked in the app or disconnected in the extension. Earlier versions may have retained Chromium profiles on the server; administrators must remove any unneeded legacy profiles separately.