Privacy Policy

1. Scope

This policy covers the QueueBond OS application and the customer workspaces within it. It describes the data QueueBond actually holds, why it holds it, and how you can make a request about it.

2. Data QueueBond holds

• Account and authentication: your email address, the display name supplied by your sign-in provider, the provider itself (Google) and an internal account identifier. Sign-in is Google-only; QueueBond does not issue, store or recover passwords.
• Profile: a display name for your account.
• Organization and access: the client organization your account is linked to and your role and status within it.
• Evidence you submit: documents you upload (stored in a private, organization-scoped bucket), their versions, file names and content hashes, and the candidate facts extracted from them with their provenance (for example page or cell).
• Operational records created by you or by a QueueBond operator: project identity, capital and security records, review decisions, detected changes, decisions, outcomes and reports.
• Audit and events: append-only records of significant actions, kept so the history of the record can be explained.
• Notifications: in-app notifications and your notification preferences. External email delivery is currently paused by configuration.

3. Cookies and local storage

QueueBond sets only necessary cookies: the authentication session cookie(s) from Supabase and a qb.workspace cookie that remembers which workspace you selected. There are no analytics, advertising or third-party tracking cookies. Your light/dark theme preference is stored in your browser only and is not sent to QueueBond.

4. Who processes your data

• Supabase — database, authentication and private file storage (our infrastructure processor).
• Google — the OAuth provider you sign in with.
• No advertising, analytics, data-broker or marketing services are used, and data is not sold.
• Public grid-source material (for example PJM or MISO exports) is source data about grid projects, not personal data.

5. Retention

QueueBond keeps historical records by design. Events and audit logs are append-only and are not edited or deleted; a document can be withdrawn (removed from active analysis while the record and its versions are retained); and an organization with history is archived (deactivated) rather than erased. No fixed retention period is stated here because none is configured in the product; retention follows the request process below and is subject to legal review.

6. Security

Access is authorized on the server and scoped to your organization (row-level security), originals are held in private storage addressed by organization-scoped paths, and server credentials are required to be rotated. No system is perfectly secure, and this is not a security certification.

7. Your requests (access, correction, deletion)

You can make a request through the QueueBond operator who manages your organization, or the contact below. A deletion request is handled as follows:

• Verify the request against your organization.
• Remove the mutable data QueueBond holds for you (documents, versions, extracted candidate facts and the stored objects).
• Archive the organization where immutable history references it.
• Retain the append-only audit and event history that records that the action occurred.
• Confirm to you what was removed and what was retained, and why.

Records that the architecture intentionally preserves — the append-only audit trail — are not destroyed. QueueBond does not invent a legal retention period.

8. Children

QueueBond is a business tool for grid-asset financing work and is not intended for use by children. QueueBond does not knowingly collect children's personal data.

9. Changes and contact

This is a draft reflecting the current implementation; the revision date is shown at the top. For any privacy request or question, use the contact shown in the footer of this page.