Privacy & data use
Information in the application
The MVP stores account details, organization membership, trade terms, counterparties, shipment events, documents, disputes, and audit history. Authentication may record IP addresses and user-agent information.
Purpose and storage
These records support agreement acceptance, evidence review, and settlement eligibility. This service stores application records in Cloudflare D1 and private evidence files in Cloudflare R2. Public demo playback uses simulated events calibrated by historical World Bank statistics.
Developer preview and connected providers
The developer preview stores credit and usage records, encrypted provider credentials, connection metadata, and waitlist preferences in a separate D1 database. It sends eligible references to your selected provider only for requested lookups. Connected tracking payloads and references are not retained by the preview; compact success, latency and error metadata is retained. Public reference data may be cached for 24 hours. Disconnect deletes stored credentials.
First-party product analytics and interest
We store a random first-party browser identifier for up to 90 days and a per-tab session identifier that rotates after 30 minutes without a recorded action. We record selected actions, normalized page categories, referrer domains and bounded campaign labels in D1. Subsequent authenticated actions can associate that identifier with your account; we do not rewrite earlier anonymous records. Funnel records contain no raw IP addresses, credentials, shipment references, precise location, or fingerprint. Rate limiting uses a daily keyed hash held by Cloudflare rate controls. Optional browser analytics respect Do Not Track, Global Privacy Control, and the browser opt-out below. Server-side product outcomes remain recorded. An interest submission stores your email, optional company, role, systems and use case, with first and latest attribution when available. Repeat submissions update your interests and contact permission. Permission is unchecked by default and applies only to beta access or a possible pilot; no unrelated mailing list subscription is created. These records are restricted to allowlisted operators.
Policy work still outstanding
The operator has not published a verified legal identity, privacy contact, retention schedule, complete subprocessor list, or data-rights procedure. Complete account deletion is not implemented. These implementation notes are not a reviewed privacy policy; those operator-owned items remain unresolved.