Privacy Policy

Batwaara is designed to minimize personal data collection. When you create an account or split expenses:

• Account Credentials: Authenticated via Clerk OAuth (Email, Google, or GitHub). We store only your primary user ID, display name, and avatar URL.
• Group & Expense Data: Group names, member rosters, expense descriptions, split values, and timestamps stored in Supabase PostgreSQL.
• Receipt Scans: Images uploaded for AI OCR parsing are processed transiently to extract line items and auto-fill amounts.

We never store your credit card numbers, bank account numbers, UPI PINs, or raw banking passwords.

When triggering debt settlements via UPI or payment gateways, Batwaara generates direct upi://pay intent links that launch your native mobile banking app (Google Pay, PhonePe, Paytm). All payment authorizations take place inside your bank’s encrypted environment.

All database communications enforce TLS 1.3 encryption in transit. Row-Level Security (RLS) policies inside PostgreSQL strictly isolate group data so only authorized group members can read or modify expense ledgers.

We utilize trusted developer infrastructure providers:

• Clerk Inc. — Identity & OAuth management.
• Supabase Inc. — Managed PostgreSQL database with RLS.
• Formspree Inc. — Contact form message forwarding.
• Vercel Inc. — Frontend hosting & privacy-friendly analytics.

5. Contact & Data Deletion

You may request full deletion of your user account and associated group logs at any time by contacting us at abhinavm16104@gmail.com.