Privacy at Divvie.
Effective August 21, 2026 · Early access
Divvie is built to help groups split restaurant bills together. This page explains the information Divvie uses while the product is in early access and how that information supports the service.
Information you give Divvie
- Receipt photos and the receipt details extracted from them, including merchant, items, prices, tax, tip, fees, and totals.
- Bill-participant information such as names, payment handles, item claims, payment status, saved groups, and bill history.
- If you create an account, basic profile information provided through your sign-in provider plus the payment methods you choose to save.
- If you join the early-access list, your email address.
How Divvie uses it
We use this information to scan receipts, synchronize live bills, calculate each person’s share, remember account preferences, show bill history and social features, hand users off to payment services, maintain the product, prevent abuse, and understand whether the core bill-splitting flow is working.
Service providers
Divvie relies on service providers to operate. Receipt images may be sent to OpenAI for receipt parsing. Supabase is used for authentication and account-related data. Render is used to host the web service. Google may process information when you choose Google sign-in. If you open Venmo, Cash App, PayPal, Apple Cash, or another payment service, that service handles the payment under its own terms and privacy practices.
Payments
Divvie does not hold, custody, or transfer the group’s money. Payment buttons are handoffs to third-party payment services. Divvie may store a payment handle or phone number that you voluntarily add so friends can see the methods you support.
Product analytics
Divvie may record limited first-party product events such as starting a bill, successfully scanning a receipt, moving between steps, opening an invite, or settling a bill. The current analytics implementation is designed around product-flow events rather than advertising profiles, and it skips collection when the browser sends a Do Not Track signal.
Retention and control
Information may be retained while needed to provide and improve early-access Divvie. Account users can remove bills from their visible history and change saved profile/payment information. Early-access data practices may change as deletion controls and production infrastructure mature.
Security
Divvie uses third-party authentication rather than storing your Google password. No online service can promise absolute security, so avoid putting sensitive information into free-text fields that is not needed to split a bill.