E-TransportOpen workspace ↗

E-TRANSPORT / DOCUMENTS

Privacy policy.

A clear view of the information used to run your account and keep your purchase records.

Draft for company review · Prepared

Who is responsible

This draft describes the current E-Transport application. The company has not yet confirmed the legal data controller, its address or the public privacy contact. The issuer named in an offering is not automatically the platform’s data controller.

A public support and privacy contact has not yet been appointed. Contact details will be published here once confirmed by the company.

Information used by the platform

Account and sign-in
Account ID, name, Google email and profile image when provided, linked provider identifiers, wallet address and proof-of-control records. Authentication also uses session records and provider tokens.
Security
Session and request information, including IP address and browser information, sign-in challenges and rate-limit records. Administrators also have authenticator, recovery and access records.
Shares and orders
When applicable: shareholder identity and verification references supplied for company approval, the approved token wallet, quotes and accepted terms, orders, payment references and statuses, share-register entries, statements and token-delivery evidence.

These records support sign-in, access control, purchase recovery, payment checking, company registration and reconciliation. E-Transport does not need your Google password, wallet seed phrase or private key.

Cookies and browser storage

Session cookies keep you signed in and support authentication. The platform’s sign-in session is configured for up to seven days and can be renewed through activity. This session duration is not a deletion period for account or transaction records.

Browser session storage holds request and quote references so a reload can recover the same purchase request without creating a duplicate. WalletConnect also uses browser storage for wallet connection state. Clearing storage or using another browser can remove local recovery information; existing server orders remain in Orders.

Signing out ends the application session and attempts to disconnect WalletConnect. If disconnect cannot be confirmed, follow the instruction to disconnect E-Transport in your wallet. Signing out or unlinking a wallet does not delete ownership or transaction records.

Services involved

Authorized company staff use the relevant shareholder, purchase and registration records according to their roles. Hosting, application operation and backup services process the data needed to deliver and protect the platform.

  • Google: if you choose Google sign-in, basic identity information is shared with the application. Google’s own processing is described in its privacy policy.
  • WalletConnect / Reown: if you use the mobile-wallet connection, its infrastructure handles connection and protocol data. See the Reown privacy policy.
  • ExPay: for a payment, the invoice service processes order and payment information. Read the provider’s notice on its payment service before paying.
  • Blockchain infrastructure: network providers process wallet and transaction queries when the platform checks token delivery. Public chain records can be viewed independently.

The final company policy must identify the applicable service providers, processing countries and international-transfer arrangements. This draft does not claim that processing is confined to Switzerland or any other single country.

Public blockchain records

On-chain token operations expose addresses, quantities, transaction references and events. Blockchain records are public and cannot be erased by deleting an application account. A wallet address may be linkable to its holder.

The platform separately keeps the shareholder and payment records needed to relate a registration to its token representation. Do not put personal identity documents, passwords or private wallet information into a public transaction or a public support message.

Retention and your requests

Account, purchase and registration data are stored in the application database; backups preserve recoverable copies. Ownership and financial audit records are designed to preserve history. There is currently no self-service account-deletion feature or automatic deletion schedule for these records.

The company must approve retention periods or criteria, the applicable processing grounds, and a procedure for requests to access, correct, export or delete data where applicable. This draft does not promise immediate deletion of records, backups or public blockchain history.

You can review connected sign-in methods in Account and your available purchase records in Orders. For a privacy request, keep your account reference and use the confirmed private contact once published. Never send passwords, authenticator recovery codes or seed phrases.

A public support and privacy contact has not yet been appointed. Contact details will be published here once confirmed by the company.