FreightAudit Product Schedule

Product-specific Android schedule. This schedule supplements the separate Terms and Privacy Policy for package com.ryantinklepaugh.freightaudit.

Product purpose

FreightAudit is a document-first freight-payment reconciliation tool that links rate-confirmation terms, settlement lines, rule arithmetic, findings, evidence, and dispute status in one audit case.

Current data and permission boundary

camera or imported document images processed on the device
ML Kit OCR text, source excerpts and bounding boxes
audit cases, calculations, findings, evidence checklists, dispute lifecycle, and notes
locally generated evidence reports and user-directed exports
purchase entitlement and legal-choice evidence

Camera access is optional and used only when you choose to capture a document. Document images, OCR output, excerpts, audit cases, findings, and notes remain app-private and local and are not uploaded to Uncommon Weather, Supabase, or an artificial-intelligence service. Public EIA data requests contain no case or document content.

Required safety boundary

FreightAudit is a recordkeeping and arithmetic aid, not legal, accounting, tax, collection, brokerage, or carrier advice. OCR, contract interpretation, rules, and calculations can be incomplete or wrong. Verify every source line, governing agreement, deadline, and amount before sending a dispute or making a financial decision.

Limited mode

After a decline or withdrawal, the following remain available:

read-only cases, documents, findings, and calculations
local export and deletion controls
legal, support, subscription-management, and purchase-restoration controls

The following remain unavailable until the current documents are affirmatively accepted:

new or edited cases and document scans
new audits or dispute-generation actions
new purchases

Legal choices and verification

A decline or withdrawal takes effect locally at once and remains limited without recurring prompts. A current affirmative choice unlocks ordinary app access after it is durably stored on the device; signed-receipt delivery may retry in the background. Android proof is recorded separately from iOS proof. A service outage does not silently convert a decline into acceptance or relabel an iOS receipt as Android.

Release state