Last updated: October 2026 · Scope: Constructora Admin (web), related APIs, and this Help Center.
This policy summarizes current data practices for the Constructora construction operations platform in plain language. It is an operational draft aligned with how the product works today — not legal advice. Counsel should review and replace it before general availability or public marketing use.
What this page covers
- What personal information Constructora processes in Admin
- Why that information is needed to run estimating, projects, accounting, and field operations
- Who can access it inside your organization
- How to request access, correction, or deletion
- Where to ask privacy questions
Information we process
| Category | Examples | Primary purpose |
|---|---|---|
| Account and identity | Name, email, phone, password hash, role | Sign-in and display in logs/notifications |
| Role and permissions | Profile, permission JSON, widget access, flags | Enforce module access (legacy parity) |
| Operational and audit | Application logs, admin notifications | Security, accountability, support |
| Business records | Projects, estimates, HR, field data you enter | Operate the product for your company |
| Technical | Session cookies, IP, request metadata | Session security and abuse detection |
Account and identity
Name, last name, email, phone (when provided), role/profile, and authentication credentials (stored as password hashes). Used to sign you in, authorize module actions, and show the correct name in logs and notifications.
Role, permissions, and preferences
Role assignment, permission JSON, widget access, and feature flags (for example estimator, bond, retainage). Used to enforce access control consistent with the legacy Constructora admin.
Operational and audit data
Application logs (operation, category, description, IP, user) and admin notifications. Used for security, accountability, and support when investigating who changed users, roles, or other records.
Business records you enter
Project, estimating, accounting, HR, and field-tracking data that your organization stores in Constructora. Personal data may appear inside those records (contacts, employees, subcontractors) according to how your teams use the modules. Constructora processes that content to operate the product for your company.
Technical data
Session cookies, request metadata, and IP address collected automatically while you use Admin. Used for session security and abuse detection.
How we use data
- Authenticate operators and enforce role-based permissions
- Deliver password-reset and transactional email when configured
- Record application logs for audit and troubleshooting
- Provide notifications inside Admin
- Improve reliability and diagnose incidents
Data sharing
Constructora does not sell personal information and does not share it with third parties for their advertising.
Data may be processed by infrastructure providers your deployment uses (database host, email/SMTP, hosting) solely to run the service. Within your organization, access follows the roles and permissions configured by administrators.
Retention
- Active accounts remain while your organization keeps them enabled.
- Application logs are retained according to your company’s retention practice for the deployed environment.
- Hard-delete of a user (Users maintainer) removes that account and related cleanup rows per the legacy
EliminarInformacionDeUsuariobehavior — this cannot be undone.
Your choices
| Request | How |
|---|---|
| Access or update your profile | My profile in Admin, or ask an administrator |
| Correct directory data | Admins use Access → Users / Profiles |
| Request deletion | Ask an administrator — hard-delete via Users maintainer |
| End session | Sign out from the user menu |
- Access or update your profile — use My profile in Admin when available, or ask an administrator.
- Correct user directory data — administrators use Access → Users (and roles) with the same fields as the legacy admin.
- Request deletion — ask a Constructora administrator; they may delete the user account via the Users maintainer. For organization-wide privacy requests, contact the address below from an authorized company email.
- Sign out — end your session from the user menu.
Contact
Privacy questions for this deployment: privacy@constructora.local (replace with your organization’s privacy contact in production).
Support for product usage: see Contact support.
See also: Terms of service.