Privacy Policy

1. Tenant Database Isolation Architecture

To provide maximum privacy and isolation, Telocargo is built on a **database-per-tenant** design.

• Zero-Sharing: Your item specifications, pallet patterns, stacking configurations, and orders are stored in a dedicated, isolated SQLite database file.
• No Co-mingled Data: Your business records are never stored in the same database tables as other customers. A directory database maps accounts, but execution data is entirely separated at the file level.

2. Information We Collect

We collect only the minimum data required to deliver precise mechanical calculations and authentication:

• Identity Data: Username, email, password hashes, and user roles (managed in the master directory).
• Physical Specs (Cargo Data): Item dimensions (mm), weights (g), stacking limits, and shipping constraints (stored in your tenant-isolated database).
• Access Logs: System metrics, errors, and access timestamps to ensure the security and uptime of the terminal endpoints.

3. Use of Cookies and Session Storage

We use secure cookies to support our **Dual Authentication Strategy**:

• Session Cookies: HTTP-only cookies are utilized to parse JWT tokens for Server-Side Rendering (SSR) in SvelteKit. These cookies are locked with `SameSite=Lax` or `Strict` and `Secure` attributes.
• Client-Side Storage: Bearer tokens are kept in temporary client memory or state stores for web app API routing.
• No Tracking Cookies: We do not deploy third-party advertising cookies or trackers.

4. Data Deletion and Portability

Because your tenant data is contained within a single SQLite database file, it is highly portable. You may request a complete export of your tenant SQLite database, or request permanent deletion of your tenant database at any time. Upon deletion request, the file is securely deleted from our storage volumes.