Privacy
BetonX handles account, organizational, and analysis-related data in support of secure housing decision workflows. Our privacy posture is designed for enterprise and professional users who expect transparency, purpose limitation, and accountable handling of personal information.
What data we collect and why
BetonX collects information necessary to authenticate users, administer organizational workspaces, generate housing analysis outputs, maintain the service, and respond to support or trust-related requests. The specific categories of data processed depend on the customer relationship, the user’s role, and the workflows used in the platform.
- Identity and account data such as name, professional email address, password or federated sign-in information, organization membership, and role assignments.
- Workspace and analysis data such as project parameters, prompts, comparison outputs, report exports, and operational artifacts generated while using the housing decision framework.
- Security and platform telemetry such as authentication events, session activity, service diagnostics, and operational logs required to protect the platform and maintain reliability.
- Support, onboarding, and commercial contact data when a user requests platform access, receives an invitation, or engages the BetonX team on privacy, security, procurement, or deployment matters.
How data is stored, processed, and protected
BetonX processes personal and workspace data to deliver the platform, enforce role-based access, generate analysis results, provide exports, and maintain operational integrity. Data is handled within controlled systems and workflows intended to support confidentiality, tenant separation, and auditability.
We process personal information only for defined platform functions such as account administration, organization membership, analysis delivery, service communications, and platform security.
Data is protected through encrypted transport, controlled infrastructure, and role-aware platform access patterns that reduce unnecessary exposure of customer or user information.
Workspace records and analysis outputs are associated with organization context so authenticated users can only access data permitted by their active role and organization membership.
Platform monitoring, access logging, and incident response workflows are used to detect misuse, investigate issues, and maintain a trustworthy operating environment.
Retention and deletion
BetonX retains information only for as long as needed to deliver the service, preserve security and auditability, meet legal or contractual obligations, or support an active customer relationship. Retention periods may vary by data type and operational purpose.
- Account and membership data may be retained while the organization relationship remains active or while necessary for access governance and audit trails.
- Analysis records, exports, and project-related artifacts may remain available while the associated organization continues to use the platform and requires those records for business continuity or review.
- Security and operational logs may be retained longer than general session data where justified for abuse detection, troubleshooting, incident review, or platform reliability controls.
- When retention is no longer justified, data is deleted, anonymized, or otherwise removed from active use in accordance with the applicable platform process and legal obligations.
User rights and applicable frameworks
BetonX privacy practices are designed to support enterprise expectations under major privacy regimes relevant to software platforms serving Canadian and international users. This includes alignment with GDPR principles, PIPEDA requirements, and applicable regional laws such as provincial private-sector privacy obligations where relevant.
- Users and customer organizations may request access to personal information associated with their account or organizational participation, subject to verification and applicable law.
- Users may request correction of inaccurate or incomplete account information where BetonX is the relevant handler of the information.
- Deletion or restriction requests can be assessed where information is no longer required for platform operation, security, or legal retention obligations.
- Questions, objections, or complaints can be raised through BetonX support and trust review channels, and where applicable may also be escalated to the relevant privacy authority.
Privacy contact
Privacy questions, customer diligence requests, or data rights inquiries can be raised through BetonX support and trust workflows. Enterprise and institutional customers may also use this path for data processing, procurement, and regional privacy reviews tied to their deployment or organizational obligations.