1. Information we process
LateMate may process user account information, company workspace information, shipment records, tracking numbers, invoice details, carrier account metadata, claim workflow records, evidence packet data, credit reconciliation records, and support communications.
2. How we use information
We use client data to operate the recovery workflow, evaluate service-failure eligibility, prepare evidence packets, track submissions, reconcile carrier credits, maintain audit trails, support security, improve product reliability, and provide customer support.
3. Carrier credentials
Carrier credentials and API secrets are used only for authorized server-side workflows. They are not exposed in browser storage, exports, screenshots, or customer-facing dashboards. Credential metadata may be stored separately from sealed secret payloads for audit and rotation workflows.
4. Sharing
LateMate may share limited workflow information with carriers, infrastructure providers, authentication providers, database providers, and support vendors as needed to provide the service. We do not sell client shipment or invoice data.
5. Retention
LateMate keeps records as needed to operate the service, preserve audit trails, support billing, resolve disputes, comply with legal obligations, and honor client deletion or export requests where applicable.
6. Security
LateMate uses tenant-scoped access controls, server-side mutation boundaries, authentication checks, and credential isolation to reduce data exposure risk. No security program can guarantee that unauthorized access will never occur.
7. Client responsibilities
Clients are responsible for uploading only data they are authorized to process, managing workspace users, protecting account credentials, and notifying LateMate when access should be changed or revoked.
8. Contact and updates
Questions, deletion requests, access requests, and security concerns should be routed through the LateMate support channel designated in the customer agreement. Material updates will be posted with a revised effective date.
Final production privacy language should be reviewed by counsel before paid launch.