Privacy & Cookie Policy

We run no user accounts on top of your wallet and keep no centralized store of your operational data. What little we collect is minimized by design.

Minimal billing details: To invoice the software subscription, we collect three fields at pay time: legal name, country of incorporation, and tax ID. That is the entire list — no passports, ID scans, selfies, or biometric data.

Account & subscription data: Basic data needed to operate your subscription, such as your wallet address and its on-chain subscription state.

Technical logs: Standard server logs (for example, request metadata and error diagnostics) kept for security and reliability.

Roster & payout history — stays on your device: Every CSV file, wallet address, payee name, and payout amount is parsed and held strictly inside your own browser (IndexedDB). Your roster is never uploaded to us and never leaves your device in readable form.

Your three billing fields are stored server-side, encrypted at rest with AES-256 (via pgcrypto) at the database layer, and keyed to a one-way hash of your wallet. They are dissociated by design from any payout data, so your identity is never tied to who you pay.

We want to be precise, because honesty here protects you: this is dissociation, not zero-knowledge. The encryption key is held server-side, which means PurserPay can technically decrypt your billing details when it must — for instance, to issue an invoice. We do not claim we are unable to read them. What we do not do is link them to your payout activity.

Your roster and payment history: These live only in your browser. We never receive them, so we cannot see who you pay, how much, or how often.

Your keys and funds: We never collect, store, or access your private keys, seed phrases, or funds. All on-chain actions are signed directly by your own TRON wallet.

We use native browser storage rather than tracking cookies. We deploy no marketing, analytics, or third-party profiling cookies.

Functional storage: Your roster and active distribution tables live in your browser’s IndexedDB. Small technical values — wallet-connection state and interface preferences — may use localStorage or a strictly functional session cookie. None of it is transmitted to us.

Your control: This data is entirely user-controlled. Clearing your browser’s site data, cache, or cookies permanently destroys all local records.

Sanctions screening: Before a batch can be signed, destination addresses are screened server-side against OFAC and international sanctions lists. Each address is salted-hashed and checked transiently; addresses are not stored in the clear or tied to your identity, and a match blocks the batch.

Public ledger: Once you sign, the transaction is routed to public TRON nodes. On-chain data (recipient addresses, amounts, block timestamps) is inherently public and immutable by the nature of distributed ledgers — this is outside our control.

We do not sell your data. We share it only with the infrastructure providers strictly needed to run the service, under their standard data-processing terms.

Processors we use: Cloud hosting and application infrastructure (Vercel) and managed database infrastructure (Supabase). These process data on our behalf to operate the platform; they do not receive your device-local roster.

You hold control over your data. Where applicable data-protection law grants you rights of access, rectification, and erasure, we honor them as follows:

Your roster: Device-local and under your sole control — erase it any time by clearing your browser’s site data.

Your billing details: You may request erasure at any time; on request we permanently wipe your encrypted billing record from our database.

For privacy requests or data-protection questions, contact us at dorian@sailorlabs.xyz. For how the product is built and the non-custodial guarantee, see our Legal & compliance page.