Your data is yours. Period.
At BillSplitter, we build utilities that respect your digital boundaries. Read below to understand how our local-first architecture guarantees your data security.
1. Zero Server Processing
When you use BillSplitter, you are running a complete standalone application inside your browser. Unlike traditional online tools that transmit inputs, receipts, or email lists to a backend server, we perform 100% of our calculation, OCR parsing, and state updates locally.
Because we do not have a backend database or web server capturing inputs, we literally cannot see, store, or sell your information.
2. Local Browser Persistence
To offer a convenient experience, we persist your active splitting session inside your browser's local sandbox using the localStorage API. This saves details like:
- Names of group members
- Calculated upfront payments and currency selection
- Itemized descriptions and individual prices
- Selected theme and language preferences
This data never leaves your device. You can clear this session state at any time by clicking the "Start Fresh (Reset)" button in the calculation outcome card or clearing your browser cookies/cache.
3. Optical Character Recognition (OCR) Privacy
Our receipt scanning feature is powered by Tesseract.js, a fully compiled WebAssembly port of the Tesseract OCR engine.
When you capture a photo of a receipt or upload an image file, the image is loaded into a local canvas element where the script analyzes characters. No image file or parsed receipt text is uploaded to any cloud service. It is fully sandboxed on your device, ensuring maximum confidentiality.
4. Web Analytics and Tracking Cookies
BillSplitter does not implement tracking pixels, advertisement networks, or external analytics trackers. We do not place cookies on your browser. Our hosting platforms (such as Vercel or GitHub Pages) may log basic access metadata (such as IP addresses and browser headers) for security and service availability, but no application-specific data is accessible to them.
5. Contact and Changes
Since the source code of this tool is fully open-source, you are welcome to inspect it directly to verify these privacy mechanisms. If you have any inquiries regarding our security practices, feel free to open a ticket or contact us via our developer details page.
Last Updated: June 19, 2026