Privacy Policy

Last updated · May 15, 2026

Clerxi LLC (“Clerxi,” “we,” “us,” “our”) provides the Clerxi web platform, the Clerxi mobile application, and the Worksite Sentinel mobile application (together, the “Service”) to authorized users of construction-industry organizations that subscribe to Clerxi. This policy explains what data the Service collects, how we use it, the third parties we share it with, and the choices you have.

The Clerxi mobile app is published as com.clerxi.mobile on Google Play and com.clerxi.app on the Apple App Store. The Worksite Sentinel mobile app ships under the Clerxi developer account on both stores. The web platform is served at clerxi.ai with the application at app.clerxi.com and an API at api.clerxi.com.

01Who controls your data

Clerxi acts as a data processor on behalf of the construction-industry organization (your “Organization”) that subscribed you to the Service. Your Organization is the data controller of the project data you create, view, or upload while using the Service. Requests to access, correct, or delete project data should be directed to your Organization’s administrator. Clerxi will assist on the controller’s instructions.

For account-level data (your name, email address, password hash, communication preferences), Clerxi acts as the controller. You may contact us directly about that data at support@clerxi.com.

02Data we collect

Account and profile data

• Email address. Passwords are stored as salted one-way hashes on our servers and are never stored on the device or accessible to Clerxi staff.
• Display name, job title, phone number, and profile photo, where you choose to provide them.
• Authentication session tokens, stored locally on the device using the operating system’s hardware-backed secure keystore (Android Keystore or iOS Keychain).
• Organization membership, role, and permissions assigned by your Organization administrator.

Project content you create or upload

• Projects, RFIs, daily reports, submittals, punch list items, time-and-materials tickets, change orders, claim events, notice letters, safety inspections, certified payroll records, clock-in / clock-out events, messages, and any text you enter into the Service.
• Photos and video: when you tap a capture or attach control in either mobile app, we request camera and/or photo-library permission. Only images and video you select are uploaded to your Organization’s tenant. Neither app scans your photo library or files automatically.
• Documents: when you tap an attach-file control, we request access to the file you pick. Only files you select are uploaded.
• Voice memos: where the Clerxi mobile app offers a voice-capture feature, the app requests microphone permission, records audio while the control is engaged, and uploads the audio to your Organization’s tenant for transcription. We do not record audio in the background or at any time the capture control is not engaged.

Location data

Service features that use device location operate only with your operating-system permission and are described below.

• Clock-in / clock-out and active shifts: when you are clocked in through the Clerxi mobile app or the Worksite Sentinel mobile app, the app uses GPS coordinates to verify your clock-in against the project’s defined work area, to attach time entries to a station or location within the project, and to report your location to your supervisor at approximately one-minute intervals so the project page reflects who is on site in real time. Location reporting stops automatically when you clock out. This supports your Organization’s labor-compliance records, including prevailing-wage and certified-payroll requirements.
• Field capture: when you take a photo, record a voice memo, or log an event using the Clerxi mobile app’s field-capture feature, the app records the device’s GPS coordinates and the time at the moment of capture and attaches them to the resulting artifact. This is used for evidence integrity (matching photos and reports to project locations and timestamps) and for recoverable claim documentation. You can disable location at the OS level if you do not want GPS attached to your captures; the capture itself will still work.
• Fleet telematics: where your Organization deploys Clerxi’s Fleet module with telematics integration, location data is transmitted from the equipment (not from your personal device) to the Service during operating hours. This is governed by your Organization’s fleet-management policy.

Neither mobile app uses background-location tracking outside the contexts described above. You can revoke location permission at any time in your device’s app-permissions screen; the app will continue to function for everything except features that depend on location.

Device and technical data

• Device model, operating system version, and app version, used for support and debugging.
• Push-notification tokens, used to deliver alerts about project events you or your Organization administrator have subscribed you to.
• Network connection status, used to handle offline mode.
• Real-time channel identifiers, used to keep the app in sync with the server.
• Server-side error traces generated when the Service encounters an unexpected error, used to debug and improve reliability.

Cookies and analytics (web platform only)

The Clerxi web platform at clerxi.ai and the application at app.clerxi.com use only the following:

• Strictly necessary cookies for authentication, session management, and load balancing. These cannot be disabled without breaking the Service.
• First-party form cookies on clerxi.ai for handling demo-request and contact submissions. The marketing site does not load third-party ad-tracking SDKs.

We do not currently use third-party product-analytics SDKs (such as Google Analytics, Plausible, PostHog, Mixpanel, or Amplitude) on the web platform. If we add one in the future, we will update this policy before enabling it. Mobile apps do not use cookies and do not contain third-party analytics SDKs.

03Data we do not collect

• Contacts and calendar: the mobile apps never request access to your contacts or calendar.
• Advertising identifiers: the apps contain no advertising and no ad-tracking SDKs. We do not request or collect IDFA (iOS) or AAID (Android).
• Third-party analytics or crash SDKs in mobile: the mobile apps contain no third-party analytics or crash-reporting SDKs — no Google Analytics, Firebase Analytics, Sentry, Mixpanel, Amplitude, Segment, Heap, or similar.
• Biometric data: we do not collect or store biometric identifiers. If you enable Face ID or fingerprint unlock for the app, the biometric data stays on your device and is handled by the operating system.
• Browsing history: we do not track your activity on other websites or apps.

04How we use your data

We use the data we collect to:

• Authenticate you and keep you signed in.
• Display your Organization’s project data to authorized users in accordance with the access controls and role permissions configured by your Organization administrator.
• Deliver push notifications and email alerts that you or your Organization administrator have enabled.
• Provide AI-powered features (document analysis, claim classification, notice drafting, evidence linking, anomaly detection) — described in detail in §5 below.
• Provide customer support, debug errors, and improve the reliability of the Service.
• Process subscription billing and comply with applicable tax, audit, and other regulatory obligations.
• Enforce our Terms of Service and prevent abuse, fraud, and unauthorized access.
• Comply with applicable law, including responding to lawful requests from public authorities.

We do not sell your data. We do not share your data with advertisers, ad networks, or data brokers, and we do not use your data for advertising or to profile you for advertising purposes.

05AI-powered features

Several Service features use large-language-model (LLM) inference to analyze project content, classify claim events, generate draft notice letters, suggest evidence links, and detect operational anomalies. These features rely on Anthropic’s Claude models, served through Anthropic’s API and through AWS Bedrock, as processors.

What data is sent for AI inference

When you invoke a feature that uses AI inference, the relevant project content is transmitted to Anthropic’s API or AWS Bedrock to produce the inference result. Depending on the feature, this may include:

• Text content from RFIs, daily reports, change orders, notices, and other Service artifacts.
• Contract excerpts and parsed Standard Specifications / Special Provisions for the project.
• Photos you have attached to an event or report, where the feature analyzes images.
• Metadata identifying the project, the artifact, and the user requesting the inference (used to enforce tenant isolation on Clerxi’s side; not used by Anthropic or AWS).

How the AI providers handle the data

Clerxi operates Anthropic and AWS Bedrock under enterprise terms that include:

• Anthropic does not retain prompts or responses beyond the duration of the API request under its zero-retention enterprise terms.
• Neither Anthropic nor AWS uses submitted content to train or improve foundation models.
• Data is processed in US infrastructure under written Data Processing Addenda with Clerxi.

Clerxi’s own use of your data

Clerxi does not train foundation models. Clerxi may build per-Organization or per-project operational baselines and anomaly-detection models — for example, learning what “normal” production looks like on a given project so that Clerxi can surface anomalies (idle equipment, schedule slippage, unresolved RFIs) to your team. These baselines are scoped to a single Organization or project, are not shared across customers, and are not used for any purpose other than serving that Organization.

Human in the loop

AI features in Clerxi are designed to draft, suggest, and surface — not to send, file, or commit on your behalf. Notice letters, recovery packages, and statutory filings always require explicit human review and signoff before they leave the platform. Every inference is recorded in the audit trail with the source data and the user who confirmed (or rejected) the result.

06Who we share data with

Clerxi engages the following subprocessors to deliver the Service. All operate under written data-processing agreements that limit them to the purposes listed and require the same security and confidentiality commitments Clerxi makes to you.

We do not share your data with advertisers, social networks, or third-party analytics providers.

07International transfers

Clerxi is operated from the United States, and the Service stores and processes data in the United States. If you access the Service from outside the United States, your data will be transferred to and processed in the United States, which may have data-protection laws different from those in your country.

Where required by applicable law, Clerxi relies on the European Commission’s Standard Contractual Clauses (the 2021 module-2 SCCs) or the UK International Data Transfer Addendum for the lawful transfer of personal data from the EU, UK, or Switzerland to the United States. A copy of the executed SCCs is available to enterprise customers under NDA upon request to support@clerxi.com.

08Data retention

• Project content is retained for as long as your Organization maintains an active Clerxi subscription, plus the retention period required by your Organization’s policy or applicable law. Public-works claim records are commonly retained for 7+ years to satisfy statute-of-limitations and recordkeeping requirements; your Organization sets the specific retention windows.
• Account data is retained while your user account is active. On account deletion, account data is removed within 30 days, except where retention is required by law (for example, tax records and anti-fraud records may be retained for the period required by the applicable statute).
• Authentication tokens on the device are removed when you sign out or uninstall the app.
• Backups are encrypted and rotated on a rolling schedule; deletion requests propagate to backups in accordance with that schedule.
• Audit logs are retained for at least 12 months for security and compliance purposes.

09Data security

Clerxi implements technical and administrative safeguards designed to protect your data from unauthorized access, alteration, disclosure, or destruction. These include:

• Encryption in transit: all network traffic between the Service and api.clerxi.com is encrypted using TLS 1.2 or higher.
• Encryption at rest: application databases, object storage, and backups are encrypted using AES-256 via AWS-managed keys.
• Hardware-backed mobile keystore: authentication session tokens on mobile are stored in the device’s hardware-backed keystore (iOS Keychain / Android Keystore).
• Password hashing: account passwords are stored only as salted one-way hashes; Clerxi staff cannot read your password.
• Access control: access to production systems is restricted to authorized engineering personnel, requires multi-factor authentication, and is logged.
• Audit logging: material actions on the Service — claim state transitions, notice generation and delivery, evidence linking, AI inference results, and administrative changes — are recorded in an append-only audit log.
• Vulnerability management: we run automated dependency scanning, perform periodic third-party penetration testing, and triage responsible-disclosure reports submitted to support@clerxi.com.
• Incident response: we maintain a documented incident-response plan and will notify affected customers and applicable regulators in accordance with law in the event of a data breach affecting personal information.

SOC 2

Clerxi is actively pursuing SOC 2 Type II certification. We have implemented the technical and administrative controls required by the Security, Availability, and Confidentiality Trust Service Criteria, and the third-party Type II audit is in progress. Once the audit report is issued, it will be available to enterprise customers under NDA on request. Until the Type II report is issued, we do not represent ourselves as SOC 2 Type II certified.

10Your choices and rights

Access, correction, deletion

For project data and profile data, contact your Organization administrator. For account-level data (name, email, password hash), contact support@clerxi.com.

Account deletion

To request deletion of your Clerxi user account, email support@clerxi.com from the email address on your account and include “Account deletion request” in the subject line, or follow the steps at Account deletion instructions. We will confirm and complete deletion within 30 days, subject to legal retention exceptions.

Disable push notifications

Turn off notifications for the Clerxi app or Worksite Sentinel app in your device’s system Settings, or sign out of the app.

Revoke camera, photo, microphone, or location access

Go to your device’s app-permissions screen and toggle the relevant permission off. The app will continue to work for every feature that does not depend on the revoked permission. Disabling location may limit clock-in / clock-out verification and the field-capture feature’s GPS tagging.

Marketing email opt-out

You can unsubscribe from Clerxi marketing email at any time using the unsubscribe link in any marketing message. Transactional and account-related email (notice-delivery confirmations, security alerts, billing) cannot be opted out of while your account is active.

Rights under regional law

Residents of the European Union, the United Kingdom, Switzerland, and California have specific rights regarding their personal data, including the right to access, correct, delete, port, and (in the EU/UK) object to certain processing. To exercise these rights, contact support@clerxi.com. You also have the right to lodge a complaint with your local data-protection authority.

California residents: Clerxi does not sell or share personal information for cross-context behavioral advertising as defined under the California Consumer Privacy Act (CCPA / CPRA). California residents may exercise the rights to know, delete, correct, and limit the use of sensitive personal information by contacting support@clerxi.com.

11Children

Clerxi is a workforce tool for construction professionals. The Service is not directed to children under 18, and we do not knowingly collect personal information from anyone under 18. If you believe a minor has provided us information, contact support@clerxi.com and we will delete it.

12Changes to this policy

We may update this policy as the Service or our legal obligations change. When we make material changes, we will update the “Last updated” date at the top and, where required by law, notify you in-app or by email. Material changes affecting how we collect or share personal data will be communicated at least 30 days before the changes take effect, unless a shorter period is required by law. Continued use of the Service after the effective date of an updated policy means you accept the changes.

13Contact