OurTab.US ← Back to app

Privacy Policy

Last updated: September 19, 2026 · Document version: 2026-09-19

This Privacy Policy describes how information is collected, used, stored, and shared when you use OurTab.US (the “Service”). OurTab.US is a trade name of Uber Website Solutions LLC (“we,” “us,” or “our”).

1. Consent

We obtain consent through sign-in flows that reference these terms and, where shown, an explicit confirmation step before you use the Service. By signing in and using the Service, you acknowledge the collection, processing, and storage of your information as described here and in our Terms of Service, subject to applicable law.

2. Information we collect

Account information. When you sign in with a supported provider (such as Google, Apple, or Facebook), we receive identifiers and profile information that the provider shares with the app (for example, account ID, email address, and name or profile photo if made available by the provider). If you sign in with email and password, we store the account you create through Firebase Authentication. If you sign in with, add, or enroll a mobile phone number—including required SMS two-step verification for Pro households—we process that number and SMS verification codes through Firebase Authentication and Identity Platform (Google) as described in Google’s documentation for Firebase Authentication and related abuse-prevention tools.

Expense and household data. You may enter expense amounts, descriptions, categories, dates, recurring items, split allocations, household identifiers, member labels, and related settings. This content is stored so the Service can function and sync between household members.

House info. You may optionally store household reference records (for example company name, type, phone, and notes) and, if you choose, account, username, and password fields encrypted with a household passphrase. Those optional credentials are visible to household members who unlock House info with the passphrase. Do not store secrets you are not authorized to share with the household.

Bank linking and transactions (Plaid). If you connect a financial institution, you interact with Plaid, which provides the bank-linking interface and retrieves account and transaction information according to your authorization. Our systems store Plaid connection credentials (such as access tokens) in encrypted form on our backend; they are not exposed to other household members and are not readable from the client app. We store account and transaction details needed to show balances, transactions, and categories in the app (for example, amounts, dates, merchant or description fields, account nicknames, and masked account identifiers). We do not store full debit or credit card numbers or card verification values for bank-linking flows. Only transaction or account lines you explicitly add to the shared household ledger are visible to other members of that household, as described in our product. Plaid’s use of information is also described in Plaid’s legal and privacy materials.

Apple Card (FinanceKit). On a supported iPhone, if you connect Apple Card, the app requests iOS financial-data permission and reads Apple Card transactions on the device through Apple FinanceKit. We upload those transactions to your personal ledger in the same encrypted form we use for Plaid-sourced rows (for example amounts, dates, and merchant or description fields), tagged as Apple Card. Other household members see a line only if you share it to the House Ledger. Apple processes on-device access according to Apple’s terms and the permission you grant in iOS Settings.

Payments and subscriptions. Paid plans may be processed by Stripe, the Apple App Store, or Google Play, depending on platform. When you subscribe or manage billing, the processor collects payment method and billing details on its own checkout, store, or portal pages. We receive and store identifiers needed to tie your subscription to your account and household (for example customer, product, or subscription identifiers, plan or price references, and subscription or entitlement status). We do not store complete payment card numbers on OurTab servers. Stripe card data is handled according to Stripe’s privacy policy. Apple and Google handle App Store and Play purchases according to their policies. You cancel or update a store-billed subscription in your Apple ID or Google Play account, not only by deleting OurTab.

Receipt images (optional). If you use receipt scan, you provide a photo from the camera or photo library. We send that image to Google Gemini / Vertex AI to extract draft fields such as amount, merchant, date, and a suggested category. We use the model output to pre-fill an expense form. We store a daily scan-quota counter on your account. We do not keep a permanent archive of receipt images for the scan feature after the request completes. Google processes the image as our AI subprocessors according to Google’s terms for those APIs.

Push notifications (optional). If you enable notifications, we store device tokens (Firebase Cloud Messaging) and your notification preferences. We may send alerts when another household member adds an expense, on a scheduled settle-up reminder, or when someone is invited and already has an account. Notification content can include household activity such as that an expense was added or that a balance reminder is due.

Support tickets. If you contact support, we collect the subject, message, ticket metadata, and any images you attach (for example screenshots). Attachments are stored in our cloud storage so our team can review them. We may email ticket notices through our email provider.

Technical data. Like most web and mobile applications, the Service may process technical information such as device type, browser or OS type, app version, general location derived from IP (if collected by our vendors), crash and diagnostic logs, and usage events. On the mobile apps this includes Firebase Analytics and Firebase Crashlytics. On the web, analytics and advertising technologies are described in section 4.

3. How we use information

We use the information above to:

4. Advertising, cookies, and similar technologies

We group optional technologies on the website into categories so you can choose what we may use:

When you first visit our public web pages, you can Accept All, Reject Non-Essential, or Manage Preferences for optional categories. You can change your choices at any time using Cookie Preferences in the site footer.

On the web application, we may display advertising through Google AdSense when you have consented to marketing cookies. Third-party vendors, including Google and Meta, may use cookies or similar technologies according to their own policies.

The iOS and Android apps do not show the web cookie banner. They may use Firebase Analytics and Crashlytics for product improvement, reliability, and crash diagnosis, as declared in each store’s privacy or data-safety form. Those mobile SDKs are not used for cross-app or cross-website advertising tracking in OurTab.

You can learn more about how Google uses information from sites and apps at How Google uses information from sites or apps that use its services. You can manage personalized ad settings in your Google account at Google Ad Settings.

5. Where data is processed

The Service uses cloud infrastructure to host authentication, databases, application logic, file storage, messaging, and related services. Your information may be processed in data centers operated by our vendors and their subprocessors according to those vendors’ terms and privacy policies.

Bank connections rely on Plaid’s infrastructure. Apple Card ingest starts on your iPhone (FinanceKit) and is then stored in our backend. Payment processing relies on Stripe, Apple, or Google, depending on how you subscribed. Receipt images you submit for scanning are processed by Google Gemini / Vertex AI. Invite and support emails are sent through SendGrid. Push delivery uses Firebase Cloud Messaging (and Apple Push Notification service on iOS). Those providers process data according to their own terms and policies, in addition to how we use data as described in this policy.

6. Sharing

We do not sell your personal information. Data you add to a household is visible to other members of that household as designed by the product. We may share information with service providers who assist in operating the Service—including cloud hosting and infrastructure (Google Firebase / Google Cloud), bank connectivity (Plaid), on-device financial-data access (Apple FinanceKit), payment processing (Stripe, Apple, Google), email delivery (SendGrid), AI receipt extraction (Google Gemini / Vertex AI), push delivery (Firebase Cloud Messaging), and analytics or crash reporting (Firebase Analytics and Crashlytics)—when required by law, or to protect rights and safety. Those providers are permitted to use data only to provide their services to us or as described in their own policies.

7. Retention

We retain information for as long as your account is active and as needed to provide the Service. You may request deletion of your account or data where applicable; see our Data Deletion page. Some information may be retained where required for legal, security, fraud-prevention, or backup reasons. Support tickets and attached images may be retained for audit after an account is closed. Subscriptions billed by Apple or Google remain with those stores until you cancel them there.

8. Security

We implement reasonable technical and organizational measures appropriate to the nature of the Service, including encrypting Plaid credentials and personal transaction details at rest on our backend, encrypting optional House info secrets with a household passphrase, and restricting access to server-side functions. No method of transmission or storage is completely secure. Household members who know the House info passphrase can read those optional credentials.

9. Your choices

You may disconnect from the Service by signing out and ceasing to use it. You may manage certain data through in-app settings, including notification preferences, linked bank or Apple Card connections (where offered), and theme or profile fields. You can disable push notifications in the app and in your device settings. For OAuth sign-in, you may also review permissions in your Google, Apple, or Facebook account, as applicable. You can withdraw iOS financial-data permission for Apple Card in iOS Settings. To request deletion of your account, use our Data Deletion page.

10. Children

The Service is not directed at children under 13, and we do not knowingly collect personal information from children under 13. Paid plans, bank linking, Apple Card ingest, and SMS two-step verification are intended for users who are at least 18 (or the age of majority where they live, if higher). If you believe we have collected information from a child, contact us so we can delete it.

11. Changes to this policy

We may update this Privacy Policy from time to time. We will post the revised policy on this page and update the “Last updated” and document version. If we require new consent for material changes, we will describe how to agree in the product or by notice.

12. Contact

For privacy questions, contact Uber Website Solutions LLC.