Privacy Policy

Information the service handles

Account and sign-in information. The service handles account identifiers, your name and email address, email-verification state, authentication records, and session information such as session expiry. Where supplied by your browser, session records may also include an IP address and user-agent string. If Google sign-in is enabled for the deployment and you choose it, Google returns the identity and profile information needed to create or use your account.

Project and workspace content. This includes project names; user-supplied BEP checklist entries, references, notes, evidence and review status; Model Review checklist items and their source details; coordination records; issues, clashes and BCF topics, comments, viewpoints and imported metadata; meeting dates, attendees, agendas, decisions and action items; deliverables and their owners or status; comments; team membership and invitation email addresses; and attachment files and related names, types, sizes and storage references. Content you provide may include personal or confidential project information, so include it only when you are authorized to do so.

Google Drive connection and selected-file information. If you connect Drive, the service handles the connected Google account email, encrypted OAuth tokens, configured folder and file identifiers, file names and types, modification or revision details, and sync status. For supported registers, it reads workbook content needed to import or map coordination records and may write mapped updates back to the files bound to a project.

Billing information. The app records the selected plan, trial and subscription state, and checkout or subscription references needed to check access and display billing status. Payment details are entered through Stripe-hosted billing pages.

How information is used

Plumbwright uses this information to create and secure accounts, maintain sign-in sessions, provide BEP and Model Review checklists and the Coordination Dashboard, save project decisions and evidence, apply account and team access, process plan access and billing, run user-configured Google Drive import and writeback, and send service communications such as password resets, invitations and trial notices. It is also used to operate and troubleshoot those features.

Connected services

• Google sign-in, when configured. If enabled for the deployment, Google processes the sign-in request and returns account identity details. Google sign-in is not an always-on requirement for using Plumbwright.
• Google Drive, when connected. Google processes folder and file listing, register reads, and any writeback requested by the configured sync. The app uses the Drive permission granted during connection to support those operations; you choose the project folder binding in the workspace.
• Stripe billing. When you select a paid plan or authorize trial renewal, the checkout and billing portal are hosted by Stripe through the app’s billing integration. Stripe processes checkout and payment details; Plumbwright receives the plan and billing status and keeps the references needed to verify access.
• Transactional email. The app sends account and service messages through the Polsia email service, including password resets, email-verification messages, team invitations, issue notifications and trial notices.
• File storage. Attachments use the Polsia file-storage integration. Plumbwright keeps the project’s attachment records and references so the files can be used in the workspace.
• Analytics, only when enabled. Deployment configuration may enable a Polsia visitor beacon or PostHog page-view capture. The PostHog configuration captures page views and limited browser, device, referrer and page-path details; query strings and URL fragments are removed, and automatic interaction capture and session recording are disabled. The visitor beacon uses a browser identifier in local storage. These analytics are not mounted when their deployment configuration is absent.

Access and safeguards

Private workspace features require an account and use server-side account, project and team access checks. Google Drive access tokens are encrypted before they are stored by the app. These safeguards describe current application controls; no online service can promise that every risk is eliminated.

Choices and retention

Connecting Google Drive is optional. You can configure or remove a project’s Drive binding and disconnect the Google account from the workspace. Disconnecting stops the connection; it does not by itself remove project records already imported into Plumbwright. Account owners can manage team invitations, and billing can be reviewed or canceled through the account Billing area.

The application does not publish a fixed retention schedule. Account, project, sync and billing records are stored to support the corresponding service functions; available editing, archiving and removal controls vary by record type. This policy does not state a fixed deletion timeframe.