This page is maintained by the operator of this GridCheck deployment and describes how the application handles the data you provide. It is an application template and should be reviewed by qualified counsel before production use.
What we store
- Your account email and display name from the authentication provider you sign in with.
- Organization membership, role assignments, and organization-scoped audit history.
- Project records, ceiling condition entries, and lighting reviews you create.
- Fixture submittal PDFs you upload, held in private object storage and served only through short-lived signed URLs to authorized organization members.
- AI extraction candidates and evidence excerpts referenced back to the source PDF page.
- Field confirmations, corrections, variant selections, and reviewer notes you submit.
- Immutable review runs, findings, printable report metadata, and audit events tied to your organization.
What we do not do
- We do not sell your data.
- We do not use your submittals or project data to train third-party AI models.
- Uploaded PDFs are never made public; direct object URLs are not exposed.
Third-party processors
GridCheck relies on a small number of processors to operate: authentication, database, private object storage, hosting, and an AI gateway used only to extract structured fields from PDFs you upload. Only content you explicitly submit is sent to those processors, and only while a request is being served.
Access controls
Data is scoped to your organization and enforced at the database with row-level security. Only active members of an organization can read that organization's projects, reviews, evidence, and audit history, and only Reviewers and Organization Admins can create or modify records.
Retention
Review inputs, runs, findings, and audit events are retained as immutable records so past reviews remain reproducible. Organization Admins may archive reviews. Deletion requests should be sent to the contact address on the Contact page.
Security
Authentication tokens are handled by the identity provider and never persisted in the application database. Uploaded documents are stored in private buckets. Server-side privileged operations are executed only after the caller's organization role has been verified.
Changes
Material changes to this policy will be reflected by updating the "Last updated" date at the top of this page.