Privacy Policy

This Policy explains how ShareSlice ("we", "us", or "our") collects, uses, stores, and shares information when you use the ShareSlice app and related services.

1. Information we process

• Account: Firebase user ID, email, nickname, avatar, sign-in provider, language, and settings.
• Expense and ledger content: groups, members, roles, invitations, expenses, income, settlements, shared wallets, ledgers, transfers, adjustments, currencies, exchange rates, categories, dates, notes, recurring rules, receipts, saved line items, and optional payment plans you create, including plan names, types, funding-source labels, reward rates, spending caps, and valid periods.
• Payment-receiving information: optional bank or wallet provider, recipient, account or wallet identifier, branch, payment link, instructions, and QR image. ShareSlice does not execute payments. Do not enter passwords, card security codes, or banking credentials.
• Receipt recognition: receipt image and detected merchant, date, amount, currency, tax, tip, category, text, and line items.
• Subscriptions: product, store, entitlement status, purchase or restoration result, and related transaction identifiers. Apple, Google, and RevenueCat process payment credentials; we do not receive complete card details.
• Support, device, and reliability: messages, attachments, app version, platform, language, device type, push token, notification preferences, App Check information, error category, sync result, and performance data.
• Analytics and advertising: screens, feature actions, results, app experience, account origin, language, subscription state, coarse usage buckets, and data processed by Google Mobile Ads such as device or advertising identifiers, IP address, ad interactions, and consent choices. Analytics events exclude names, notes, invitation codes, receipt text, payment details, raw amounts, image URLs, email addresses, and stack traces.

2. Uses

We use information to manage accounts; provide splitting, bookkeeping, offline sync, receipts, payment information, subscriptions, notifications, migration, and support; display data to authorized users; prevent abuse; diagnose failures; improve the service; and meet legal and security obligations.

3. Receipt scanning and AI

Quick Recognition runs on-device when supported. AI Recognition requires internet access. Recognized text may be sent to Google Vertex AI Gemini to create structured fields; Gemini does not receive the source image. If on-device recognition is unavailable or fails, the image may be sent temporarily to Google Cloud Vision.

The OCR backend does not retain source images or complete OCR text. Structured results may be cached for up to 24 hours. Limited request and quota metadata may be kept for up to 40 days for abuse prevention, accounting, and monitoring. Images are stored in Firebase Storage only when you keep the receipt and save the record. Review results before applying them.

4. Payment information and sharing

Payment-receiving information is optional and may be shown to authorized members of linked groups. Editors manage information for unlinked members. Information copied from a saved member into a group is stored independently and copies already shared cannot be recalled automatically. Recent payment text and QR images may be encrypted in secure device storage for offline use and are separated by account and cleared on sign-out or account switching.

5. Providers

We use Google Firebase and Google Cloud for authentication, databases, Functions, Storage, App Check, messaging, analytics, OCR, and AI; RevenueCat, Apple App Store, and Google Play for subscriptions; Google Mobile Ads for advertising; Branch for invitations and deep links; and Google and Apple for sign-in. Providers may process data internationally under their own terms. We do not sell group, ledger, receipt, or payment-instruction content.

Meta advertising measurement

We use Meta App Events to measure installs and app sessions associated with our Facebook and Instagram advertising. Meta may receive install and session events, event times and session duration, an SDK-generated app-instance identifier, app and device information (version, operating system, model, language and time zone), and network information such as your IP address. These identifiers do not guarantee anonymity. Our current integration disables automatic event logging and advertising-ID collection. It does not send Meta registration, group creation, expense or subscription events, account IDs, group content, receipts or payment details. The SDK may still contact Meta for configuration and measurement. See the Meta Privacy Policy for its processing, retention and privacy controls. Contact us below with privacy requests. This policy does not replace consent or platform permission where required.

6. Security and retention

We use authentication, authorization, transport encryption, short-lived media links, and access-controlled cloud storage. Account and feature data is generally retained while your account is active or as needed to provide the service. Backups, security logs, subscription records, and legally required records may remain for a limited period. No system is completely secure.

7. Choices and rights

You may edit or delete supported records, manage camera, photo, notification, and available advertising choices, choose whether to use cloud AI, and request account deletion in the app. Shared copies, backups, security, transaction, and legally required records may remain as applicable. Contact us to request access, correction, or deletion.

8. Children, international processing, and changes

ShareSlice is not directed to children under 13 or the applicable local minimum age. Data may be processed outside your country. We may update this Policy when features, providers, or legal requirements change and will update the date above and provide additional notice when required.

9. Contact

Email: bad.tech.service@gmail.com