Legal

Privacy policy

This describes what the Settle prototype actually does with information at this version. It is written from the code, not from a plan.
Last updated 30 October 2026
In short
No accounts, no analytics, no cookies set by the app, no ads, and no uploads of your bill files. Settle is a testnet prototype with sample data.

What stays on your device

  • Bill photos and PDFs. When you pick one, the app previews it on your device. The app has no code that uploads it.
  • What you type while posting a bill, such as the amount, provider and story. It is held in memory while the page is open and is gone when you reload or close it. It is not sent anywhere.
  • One stored value. After the intro screens, the app saves a single key, settle:onboarding-complete, set to true, so it does not show them again. It uses AsyncStorage, which is your browser's local storage on web and app storage on iOS and Android. Clear site data or app data to remove it.
The app code stores nothing else. Your browser may keep its normal cache of the site's files.

Network requests the app makes

  • Loading the app. Your browser requests the site's own files from whichever host serves it: pages, scripts, fonts, animations and images. Fonts and animations are bundled with the app and are not fetched from a third-party font service.
  • Your wallet, on web only. The app talks to the Freighter browser extension on your device to see whether it is available. If you press connect, the extension asks you, and the app then reads your public address and which Stellar network the wallet is on. A public address is not a secret. In the public demo, no payment is signed; in a build connected to the testnet settlement API, you can sign a testnet payment.
  • The settlement API, only if a build is configured with one. The default build is not. When one is configured, a funding request sends the bill id, the amount in minor units, the currency, your wallet's public address and a random idempotency key, and later the signed transaction. It never sends your bill file. The request goes to the address that build was configured with.
The app contains settings for Stellar testnet endpoints (Horizon and RPC) and a link format for a public block explorer, but it does not call those endpoints today. Links you press, such as GitHub or Freighter, take you to other sites with their own policies.

Hosting

When the web build is deployed on Vercel, Vercel serves the files and, like any web host, handles connection data such as your IP address and browser details in its logs. Settle adds no tracking on top of that. See Vercel's privacy policy for how it treats that data.

What Settle does not do

  • No analytics, advertising, session recording or tracking scripts.
  • No cookies set by the app.
  • No accounts, so there is no profile data to delete on a server.
  • No selling or sharing of personal data. The app does not collect any.
  • No use of your files to train models. Files are not uploaded.

The planned evidence design

If Settle ever accepts bill evidence, it is designed to collect the least that proves a bill, redact before anything else sees it, show supporters only redacted fields, and delete on a schedule. That design, including proposed retention periods that still need legal review, is in docs/privacy-evidence.md. It is partly implemented in the separate settle-api repository. The app does not upload bills, so it does not apply to this app today. This policy will be updated before that changes.

Contact and changes

For privacy questions, open an issue on GitHub, and do not post personal documents or real account numbers there. To report a vulnerability or a document-privacy flaw privately, follow the security policy. Settle does not publish a contact email for this prototype.
Changes to this policy appear in the changelog. The date above is the last update.