Privacy Policy
This draft describes the current Phase Track service and requires business details and qualified legal review before public launch. Effective date: to be confirmed.
1. Operator and contact details
Phase Track is a construction project management service. The legal operator name, business address and verified privacy contact are not yet supplied and must be completed before launch. This document does not select a jurisdiction or claim regulatory certification.
2. Registration and account information
Registration asks for your name, company name, email address and password. Supabase Authentication processes credentials, email verification, sign-in sessions and password recovery. Phase Track uses account and profile information to provide your workspace and determine authorized access. Do not send passwords or authentication tokens in support requests.
3. Company and construction project data
Your workspace may contain project names, locations, planned budgets, phases, tasks, dates, notes, milestones, team contact records, document folders and document metadata. These records support the project views, schedules and derived reports. Team contacts are project records, not automatically invited account holders. Only provide personal information you are entitled to use.
4. Actual service providers and AI
The configured external Supabase project provides account authentication and stored workspace records. Lovable provides application hosting and the AI Gateway used for optional AI Analyze requests. AI Analyze sends selected project, phase, task and milestone names, dates, status and progress facts; it is designed not to send budgets, people, email addresses or descriptions. The underlying AI model provider receives the analysis input through the gateway. Provider contracts, processing locations and retention arrangements require confirmation before launch. No new analytics or tracking service is introduced by these pages.
5. Storage and protection
Workspace access is checked through authentication and caller-scoped database access policies. These safeguards do not constitute a guarantee of absolute security or a certification. Sign-in session information is stored in the browser to maintain access across refreshes. Legacy browser-only project records and settings may also remain on your device. Document features currently store metadata only; private file upload, preview and download are not connected. The public demo uses separate fictional sample records and contains no customer projects or private files.
6. Retention, access and deletion requests
A final retention schedule, backup deletion process and request-response procedure must be confirmed before launch. Depending on applicable law, you may have rights to access, correct, export or request deletion of your personal information. Account deletion is not currently a self-service control. A verified privacy contact must be published before requests can be submitted; no contact email has been provided yet. Deleting a project is not the same as deleting an authentication account or provider backups.
7. Changes and launch review
Material changes should be reflected in an updated policy with an effective date. Before launch, complete the operator and contact details, confirm provider handling and retention, and obtain legal review of the obligations that apply to the service.