Data Compliance

Construction Tracking System is structured as a reusable business platform for construction operations. It can be deployed with tenant-specific branding while keeping data isolated per client account.

1. Data roles

• JMendoza IT Solutions acts as platform operator for the software environment.
• Each client tenant acts as the owner of its operational records and company data.
• Authorized tenant users access only the data permitted by role and tenant scope.

2. Isolation and access controls

• Tenant separation is enforced through tenant-scoped application logic and row-level security.
• Role-based permissions restrict access to owner, admin, accounting, engineer, purchaser, and related workflows.
• Audit events are used for sensitive changes and operational accountability.

3. Security baseline

• Hosted infrastructure uses encrypted connections in transit.
• Secrets are stored outside source control and configured per deployment environment.
• Production deployments can use dedicated Supabase and Vercel projects per client.

4. User rights and requests

Privacy, correction, export, and deletion requests should be routed through the tenant's administrator or the platform operator depending on the request. Response handling depends on the deployment agreement and applicable law.

5. Subprocessors

• Supabase, including database, authentication, and storage.
• Vercel, including application hosting and deployment delivery.
• Resend, when alert or notification email delivery is enabled.

6. Commercial ownership model

This project is intentionally maintained as a reskinnable base product. Ranay Construction may use a branded deployment, but the reusable system architecture, code, and platform rights remain with JMendoza IT Solutions unless a separate assignment agreement is signed.