Privacy Policy

1. Overview & Philosophy

SettleRoute is architected as a zero-knowledge, zero-backend application for payroll data. We believe your contractor payment data is private by default. This Privacy Policy explains what minimal data we do and do not collect, how we use it, and your rights.

2. Data We Do NOT Collect

SettleRoute does not collect, transmit, or store the following on any server:

• CSV payroll data — all CSV parsing happens in your browser memory via PapaParse;
• Recipient wallet addresses — never transmitted to SettleRoute infrastructure;
• Payment amounts or disbursement details — processed client-side only;
• Private keys or seed phrases — SettleRoute has zero access to wallet credentials;
• Personal identification information — no KYC, no email required to use the Service.

3. Local Data Storage (IndexedDB)

SettleRoute uses your browser’s built-in IndexedDB storage (under the database name settleroute_db) to store:

• Draft sessions — active batch payout data saved for crash recovery;
• Transaction receipts — historical audit trail of completed batches (on-chain hashes);
• Contractor directory entries — wallet addresses you manually save for recurring payroll;
• Payout templates — recurring payroll configurations.

This data is stored only on your local device. It is never synchronized to cloud servers. You can clear all local data at any time through your browser’s storage settings. Clearing your browser data will permanently remove all locally stored SettleRoute data.

4. Blockchain Transparency

By the nature of public blockchain technology, all on-chain transactions executed through SettleRoute are publicly visible on the relevant blockchain explorer (Basescan, Arbiscan, PolygonScan). This includes:

• The initiating wallet address (your treasury wallet);
• All recipient wallet addresses in the batch;
• Token amounts transferred to each recipient;
• Protocol fees collected.

This is inherent to public blockchains and is not specific to SettleRoute. SettleRoute does not enhance or reduce the public visibility of on-chain transactions beyond what the underlying blockchain provides.

5. Webhook Integrations (Optional)

If you configure the optional webhook dispatcher feature (for n8n, Zapier, or ERP integrations), transaction receipt data is transmitted to the webhook endpoint URL you configure. SettleRoute does not operate or have access to these endpoints — you are responsible for the security and privacy practices of any third-party services you connect via webhooks.

6. On-Chain Subscriptions

The Accounting Pro Pass subscription is managed entirely on-chain. When you subscribe, the smart contract records your wallet address and expiry timestamp on-chain — this is publicly visible on the blockchain. No email address, name, or personal information is collected as part of the subscription process.

7. Third-Party Services

SettleRoute may utilize the following third-party services which have their own privacy policies:

• RainbowKit / WalletConnect — for wallet connection. Review WalletConnect’s privacy policy at walletconnect.com;
• Blockchain RPC Providers — to read on-chain data (gas prices, token balances);
• Google Fonts — for typography (Inter, JetBrains Mono).

8. Cookies

SettleRoute does not use advertising cookies or third-party tracking cookies. Essential session data is stored in your browser’s local storage and IndexedDB as described above. You may disable cookies in your browser settings, though this may affect Service functionality.

9. Your Rights

Because SettleRoute does not collect personal data on its servers, traditional data subject rights (access, deletion, portability) are satisfied by the fact that all your data remains on your own device. You can exercise full control by:

• Clearing your browser’s IndexedDB storage to remove all local SettleRoute data;
• Disconnecting your wallet from the application at any time;
• Not configuring webhook integrations if you prefer complete data isolation.

10. Changes to This Policy

We may update this Privacy Policy from time to time. The “Last Updated” date at the top of this page reflects the most recent revision. Continued use of the Service after any changes constitutes acceptance of the updated policy.