Legal

Pathizer Privacy Policy

Version
2026-05-16
Effective Date
May 16, 2026
Last Updated
May 16, 2026

Updated to describe current account, project, schedule, support ticket, billing, telemetry, email, retention, service provider, and administrative access practices.

1. Information We Collect

Pathizer may collect account identity information such as name, email address, user ID, authentication status, organization membership, role assignments, profile details, phone number if provided, and login or security metadata.

Pathizer may collect uploaded schedule and project data, including XER files, schedule logic, activities, relationships, calendars, WBS information, update history, contractor coding references, turnover selections, liquidated damage inputs, project documents, generated operational state, analysis outputs, reports, diagrams, simulations, and related project metadata.

Pathizer may collect support ticket content, support category, message text, user and organization context, project context, timestamps, transactional email metadata, billing metadata, usage activity, onboarding progress, feature interactions, device/browser information, logs, diagnostics, and security telemetry.

2. How Information Is Used

Pathizer uses information to authenticate users, provision organizations and projects, manage roles and permissions, process uploaded schedules, generate XER workspace summaries, create operations workspace state, run analysis, generate reports, support onboarding, send notifications, provide support, administer billing, enforce access controls, secure the platform, prevent abuse, debug issues, and improve reliability.

Pathizer may use operational telemetry, logs, and administrative metadata to understand whether setup steps are complete, whether required generated state exists, whether tools should show guidance, and whether support or maintenance action is needed.

3. Uploaded Project Data and Derived Outputs

Uploaded project data may include commercially sensitive schedule and project-control information. Pathizer processes this information to provide forensic schedule intelligence and supporting outputs to authorized users within the applicable organization and project.

Derived outputs, generated workspaces, reset state, cache records, report drafts, and analysis artifacts may be stored with the project so authorized users can review, reproduce, refresh, audit, or support the workflow.

4. Support Tickets and Communications

When users submit in-app support tickets or contact Pathizer, Pathizer may process the submitted message, selected category, user identity, user email, display name, phone number if available, organization and project context if available, timestamps, and related diagnostics needed to respond.

Support tickets may be emailed to [email protected] and handled by Pathizer personnel or service providers. Billing-related support may use [email protected]. Legal and privacy communications may use [email protected] and [email protected].

5. Sharing and Service Providers

Pathizer may share information with service providers that help operate the platform, including cloud infrastructure and storage providers, Firebase or other authentication providers, Stripe or payment processors, Resend or email delivery providers, logging, monitoring, analytics, security, support, and administrative tooling providers.

Pathizer may also share information with organization administrators and authorized project users according to workspace roles, with professional advisers where appropriate, in connection with business transfers, or when required for legal, safety, compliance, billing, or security purposes. Pathizer does not sell customer project data.

6. Billing and Transactional Data

Billing workflows may involve organization name, project status, selected coverage, pricing version, subscription tier, invoice and payment metadata, billing portal status, cancellation or reactivation events, and administrator contact information. Payment details may be processed by third-party payment providers rather than stored directly by Pathizer.

Transactional emails may include account, invitation, legal acceptance, support, billing, engine completion, project setup, security, and administrative messages. Email delivery metadata may be retained to troubleshoot delivery and maintain records.

7. Administrative and Security Access

Pathizer personnel and verified Platform Super Admins may access customer environments, project metadata, support records, billing records, logs, and uploaded or derived data when needed for support, security, legal compliance, abuse prevention, maintenance, debugging, migration, demo reset, incident response, or service operation.

Administrative access is intended to be limited to legitimate operational purposes and may be logged, audited, reviewed, or restricted by internal controls.

8. AI and Model Training

Customer uploaded schedule and project data is not used to train public AI models unless a separate written agreement or approved policy states otherwise. Pathizer will not materially broaden project-data use without appropriate notice or consent where required.

9. Retention and Deletion

Pathizer retains account, project, uploaded, derived, audit, billing, support, legal acceptance, operational, and security records for as long as needed to provide the Services, meet legal or contractual obligations, maintain backups, resolve disputes, enforce agreements, and protect platform security.

Documents stored on Pathizer servers for a project may be permanently deleted after eighty-four (84) consecutive months, or seven (7) years, without an active subscription for that project. Archived, completed, inactive, suspended, or deactivated projects may retain certain records for legal, audit, backup, billing, support, security, or contractual purposes.

Deletion or export requests may be limited by organization control, legal holds, contracts, billing records, audit requirements, backups, security needs, or the rights of other authorized users. Privacy requests may be sent to [email protected].

10. Security

Pathizer uses reasonable administrative, technical, and organizational safeguards to protect information. No system is perfectly secure, and users remain responsible for protecting credentials, reviewing workspace access, and using appropriate project-data controls.

Security reports may be sent to [email protected].

11. User Rights and International Processing

Depending on applicable law, users may have rights to access, correct, export, restrict, or request deletion of certain personal information. Some requests may need to be made through an organization administrator and may be subject to legal, contractual, security, backup, audit, or operational limitations.

Pathizer and its service providers may process information in jurisdictions other than where you are located. Where required, we use appropriate safeguards designed to protect personal information consistent with applicable law.

12. Changes and Contact

We may update this Privacy Policy from time to time. If we make material changes to how we collect, use, or share personal information or customer project data, we may provide notice and/or request renewed acknowledgement before the changes apply where required by law or appropriate for the nature of the change.

Privacy questions or requests may be sent to [email protected]. Support questions may be sent to [email protected]. Legal notices may be sent to [email protected].