Privacy Policy

Contri is operated by Contri Money Labs. This Privacy Policy applies to the Contri mobile app, backend APIs, public website, waitlist pages, and legal pages available at contri.money.

Our support, privacy, and grievance contact for India-facing users is help@contri.money.

Contri helps people coordinate group expenses. The current MVP includes group expenses, equal split calculations, balances, settlement records, personal logs, guests, CSV import, and Share-to-Contri review flows.

Contri is not a bank, wallet, NBFC, payment processor, payment gateway, escrow service, service that proves payments happened, or dispute resolution service. Payments happen outside Contri through the payment method or app chosen by the people involved.

Contri does not process, verify, reverse, refund, guarantee, or confirm payment success. A settled status or saved record in Contri is a user-managed coordination record, not confirmation from a bank, UPI system, or payment app.

• Account and profile data: name or display name, email address, authentication identifiers, user ID, and basic Google profile information if you use Google Sign-In.
• Authentication and security data: email OTP, sign-up, sign-in, password reset, session, device, security, rate-limit, and abuse-prevention metadata.
• Groups, participants, and guests: group names, member records, participant records, guest names, optional guest emails, invite metadata, claim metadata, and related activity.
• Expenses, splits, balances, and settlements: amounts, descriptions, notes, dates, payer and participant records, split rows, settlement rows, settlement status, and balance history.
• Personal logs: amount, direction, counterparty, date, optional note, source, confidence, and related details. Personal logs are private to your account while your account is active.
• CSV import data: CSV files you select for import are parsed for review, and confirmed normalized rows can be saved as group expenses.
• Share-to-Contri data: trusted Android source metadata, on-device OCR-derived review details, and confirmed derived fields if you choose to save them.
• UPI demand tap metadata: taps on Pay with UPI may record sanitized demand or interest metadata. We do not collect payment credentials through this flow.
• Notifications: Firebase Cloud Messaging token, notification preferences, notification rows, unread state, and delivery-related metadata.
• Analytics and diagnostics: Firebase Analytics events, Firebase Crashlytics crash diagnostics, Firebase identifiers, app version, device and OS details, and reliability logs.
• Website and waitlist data: email addresses and related submission metadata if you join the waitlist or contact us through the public site. Waitlist and marketing email operations may use MailerLite.

• No Advertising ID.
• No Android AdServices permissions.
• No device contacts or phonebook data.
• No location data.
• No camera permission.
• No media or read-storage permission.
• No UPI PIN, card credentials, bank credentials, or payment passwords.
• No raw receipt screenshot upload or storage by Contri.
• No evidence of completed payment or bank/payment-app confirmation.

Share-to-Contri is designed to make receipt and transaction review faster without turning Contri into a payment verifier. When you share a supported receipt or image to Contri, the app can use trusted Android source metadata and on-device OCR to prepare review details.

Raw receipt screenshots are not uploaded to or stored by Contri. Nothing from Share-to-Contri is saved until you review and confirm it. If you confirm, derived fields can be saved as personal logs, group expenses, or settlement records, depending on what you choose.

Share-to-Contri does not confirm that a payment happened. You remain responsible for checking the details before saving or marking anything settled.

CSV import is user-selected. Contri parses the selected CSV so you can review normalized rows before saving them as group expenses. Unsupported or incomplete rows may be skipped or require review.

Confirmed rows become group expense records visible to the relevant group participants. You are responsible for confirming that imported data is accurate and that you have the right to use it in Contri.

UPI payment launch is not active. The Pay with UPI experience is Coming Soon and is used for demand capture only.

Tapping Pay with UPI should not be treated as a payment attempt, payment success, UPI app launch, or confirmation that a payment happened. Contri may record sanitized tap metadata to understand interest in the feature.

If you allow notifications, Contri uses Firebase Cloud Messaging to deliver service notifications. We store FCM tokens, notification preferences, notification rows, and unread state so the app can send and show relevant updates.

We aim to keep push notification content generic where privacy-sensitive details are involved. You can manage notification permissions in your device settings and available app settings.

Contri uses Firebase Analytics to understand app usage and Firebase Crashlytics to diagnose crashes and reliability issues. These tools may process Firebase identifiers, device details, app version, crash traces, and event metadata.

Contri does not show ads, does not use the Advertising ID, and does not request Android AdServices permissions.

• Create, authenticate, secure, and support your account.
• Operate groups, guests, expenses, splits, balances, settlements, personal logs, imports, and Share-to-Contri review flows.
• Send service notifications and important account messages.
• Send transactional account emails such as OTP, password reset, and service messages.
• Send waitlist or marketing emails only where you joined the waitlist or otherwise opted in.
• Improve reliability, diagnose crashes, and prevent abuse.
• Respond to support, privacy, deletion, security, or legal requests.

We do not sell your personal data.

App account sign-up, sign-in, OTP, password reset, security, and service emails are transactional emails. Contri uses Resend for these transactional messages.

Waitlist and marketing emails are separate from app account emails. Joining or using the Contri app does not automatically subscribe you to marketing emails.

If you join the waitlist or otherwise opt in to marketing emails, Contri may use MailerLite for waitlist or marketing email operations. You can unsubscribe from marketing emails using the unsubscribe link in those emails, including MailerLite unsubscribe links.

Group data is shared with the members, guests, or claimed participants who need it for that group, expense, split, balance, or settlement record. Personal logs are private to your account while your account is active.

We use service providers and processors to run Contri, including Google and Firebase for authentication, analytics, crash diagnostics, notifications, and platform services; Supabase for database and backend services; Google Cloud Run and GCP for backend hosting and infrastructure; Resend for transactional email delivery; MailerLite for waitlist and marketing email operations; Vercel for the public website; and Cloudflare for DNS, CDN, security, and proxy services for Contri web and join surfaces.

Payment apps and payment providers you use outside Contri are not controlled by Contri and have their own terms and privacy policies.

We use HTTPS and encryption in transit, authentication, access controls, rate limits, abuse-prevention checks, and operational logging to protect Contri. Android app backup is disabled for the Contri app.

We design sensitive paths to avoid or redact unnecessary raw fields where practical, especially around receipt-derived data, diagnostics, logs, and support workflows.

Account and profile data are kept while your account is active and as needed for service, security, support, abuse prevention, legal, and operational reasons.

Shared group ledger records, including expenses, splits, settlements, balances, and participant history, may remain for other participants after an account is deleted or anonymized so their records continue to make sense.

Personal logs are private and user-controlled while your account is active. Account deletion does not promise automatic deletion of every personal log in this policy. If you want account deletion to include personal-log handling, contact support.

Security, diagnostic, email, analytics, and abuse-prevention records may be retained as needed for legitimate operational, safety, or legal purposes.

You can delete your account in the Contri app from the delete account flow. You can also read the current steps on the delete account page or contact support at help@contri.money.

After successful in-app deletion, your account profile is deactivated and anonymized. Shared group ledger and history may remain for other participants, as described above.

Contri is not intended for children. If you are under 18, use Contri only with appropriate parent or guardian permission where required. If you believe a minor has provided personal data without appropriate permission, contact us.

• Use account settings to review or update available profile details.
• Use notification settings in Contri or on your device to manage notifications.
• Use in-product controls where available to edit or delete user-controlled records.
• Contact us for access, correction, deletion, or privacy requests.

Email help@contri.money for support, privacy, grievance, access, correction, or deletion questions or requests.

We may update this Privacy Policy as Contri changes. When we do, we will update the Last updated date on this page.