Privacy

ClaimBoard Privacy Policy

Effective: October 1, 2026 · Applies to the ClaimBoard Chrome extension and ClaimBoard web services at getclaimboard.com.

This policy explains what information ClaimBoard processes, why we process it, when information leaves your browser, and the choices available to you.

1. Information we process

Google account information

When you choose Sign in with Google, Chrome Identity obtains a Google OAuth access token. ClaimBoard sends that token to the ClaimBoard backend only to verify your identity and create an opaque ClaimBoard session. The Google OAuth access token is not stored by ClaimBoard. We store the verified Google account subject identifier and email address needed to identify your ClaimBoard account and workspace.

Freight claim information

ClaimBoard stores the freight claim information you provide, such as claim references, shipment identifiers, amounts, status, next actions, review decisions, and related activity history.

Claim documents

When you upload supporting claim documents, ClaimBoard stores those files in private application storage together with document metadata needed to associate them with the correct workspace and claim. Supported claim documents can include PDF, PNG, and JPEG files.

Browser context

ClaimBoard processes browser context only after you choose to capture the current page. That context can include the page title, page URL, selected text, and capture time. Browser context is stored as claim metadata. It is not treated as claim document evidence and is not silently collected while you browse.

Operational information

We may process limited technical and security information needed to operate, diagnose, protect, and maintain the service. ClaimBoard is designed not to expose authentication tokens in normal application logs.

2. How we use information

We use information only to provide and secure ClaimBoard, including to authenticate users, maintain workspaces, store and retrieve claims and documents, show next actions, support human review, prepare filing packets, diagnose failures, prevent unauthorized access, and respond to support or privacy requests.

3. AI-assisted document extraction

ClaimBoard includes an AI-assisted document extraction capability. When that capability is enabled by the service operator and you initiate document processing, claim document content may be sent to the configured AI service provider, currently OpenAI, solely to extract claim-related information for the ClaimBoard workflow. AI output remains provisional and does not become reviewed claim evidence without explicit human confirmation.

Browser context is metadata and is not used as claim document evidence in the AI review path.

4. Chrome permissions and user-initiated capture

The Chrome extension uses permissions required for its visible user-facing functions. The activeTab and scripting permissions are used when you explicitly choose Capture page so ClaimBoard can read the current page title, URL, and selected text. The sidePanel permission displays ClaimBoard next to the page you are viewing. The identity permission is used for Google sign-in, and storage is used for the opaque ClaimBoard session in trusted extension storage.

5. Sharing and sale of data

We do not sell your personal information, freight claim information, claim documents, or browser context. We do not use ClaimBoard data for advertising or cross-context behavioral advertising.

Information may be processed by service providers only when needed to operate ClaimBoard, such as infrastructure providers, Google for authentication, and OpenAI when AI-assisted document extraction is enabled and invoked. We may also disclose information when required by law or when necessary to protect the security and integrity of the service.

6. Google API and Chrome Web Store Limited Use

ClaimBoard's use of information received from Google APIs is limited to providing the user-facing authentication function described in this policy. Use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. ClaimBoard's Chrome Web Store disclosures and use of extension data are intended to remain consistent with this policy and the Chrome Web Store user data requirements.

7. Security

ClaimBoard uses HTTPS for the production API, tenant-scoped authorization, private document storage, and opaque ClaimBoard sessions. The server stores a cryptographic hash of the session token rather than the raw token. The Chrome extension keeps the active opaque session in extension storage restricted to trusted extension contexts.

8. Retention and deletion

We retain account, claim, document, and activity information for as long as reasonably needed to provide ClaimBoard, maintain security and integrity, and satisfy legitimate operational or legal requirements. Operational backups may retain deleted information temporarily until the relevant backup is rotated or removed.

You may request access to or delete your ClaimBoard account data by emailing privacy@getclaimboard.com or support@getclaimboard.com. We may need to verify your identity before completing a data request.

9. Filing packets and external transmission

ClaimBoard prepares filing packets for review and download. Creating or downloading a packet is not proof that a claim was filed, sent, emailed, uploaded, or received by a carrier. ClaimBoard does not automatically transmit filing packets to carriers in the current Open Beta.

10. Changes to this policy

If ClaimBoard's material data practices change, we will update this policy and its effective date. Where required, we will provide additional notice or obtain consent before using information for a materially different purpose.

11. Contact