EFFECTIVE 2026-08-09
Privacy summary
Plain-language behavior and limits for the manual founder pilot.
Data collected
Account email, organization name, closeout project metadata, checklist status and notes, files an authorized user uploads, and qualified pilot-request details.
Purpose
To authenticate users, isolate organization workspaces, provide checklist and manifest features, store private evidence, review pilot fit, and investigate reliability or security failures.
Storage and processors
The release is designed for Supabase Auth, Postgres, and private Storage, with Next.js hosting on a verified deployment target. No advertising tracker, payment script, or checkout is enabled.
Tenant and file controls
Database rows use organization-scoped Row-Level Security plus explicit server checks. Files use organization/project paths in a private bucket and authorization-checked server-proxied downloads. Service-role credentials stay server-side.
Minimize sensitive data
Upload only evidence required for closeout. Do not upload passwords, API keys, payment-card data, export-controlled material, government identifiers, or unnecessary personal/medical information.
Retention and deletion
Self-service deletion and a tested retention schedule are not yet available. Approved pilots must use the founder channel for an access or deletion request and retain their own originals.
Current limit
This summary describes intended founder-release behavior. It is not a claim of certification, formal compliance, or a completed legal/privacy review for every jurisdiction.