Legal

Privacy Policy

Plain and short: your sheets are yours, we don’t sell your data, and there are no ads in Muetual.

Last updated: 26 October 2026

Muetual (“Muetual”, “we”, “us”), operated by evensys, provides a shared expense-tracking service on the web and mobile. This policy explains what we collect, why, and the choices you have.

Information we collect

  • Account information. Sign-in is handled by our authentication provider, Clerk. We receive your name, email address, and (if you choose social sign-in) your profile image. We never see or store your password.
  • Content you create. The data you enter to use the service: Expenses Sheets, expenses, categories, budgets, recurring rules, and the members you invite.
  • Preferences. Settings such as language, appearance, currency, and notification choices.
  • Subscription details. If you subscribe, we store which plan you are on and when it renews. Payments are handled by the App Store, Google Play or Stripe; we never see or store your card details. RevenueCat manages the subscription on our behalf and receives an identifier for your account.
  • Notification tokens. If you turn on push notifications, your device issues a token so we can deliver them. It identifies the app on that device rather than you, and it is removed when you turn notifications off.
  • Messages you send us. If you write to us through the contact form, we store your name, email address and message so we can reply. The form is protected by Cloudflare Turnstile, which checks that a person rather than a bot is submitting it.
  • Ad-measurement data. Which of our campaigns brought you to Muetual, and a few events that followed, such as a sign-up, a trial or a subscription. On the web and in the mobile apps this is collected only if you agree; on iOS, Apple also tells us whether an install came from an Apple Ads campaign. See “Advertising measurement & your consent” below.
  • Limited technical data. Basic, short-lived logs needed to operate and secure the service. Our website, muetual.com, sets no tracking cookies; the web app sets Google Analytics cookies only if you accept them.

How we use your information

  • To provide and maintain the service and sync your sheets across your devices.
  • To send transactional email you’d expect: invitations, member and budget alerts, and the optional weekly summary.
  • To reply to messages you send us.
  • To give you the features of your plan, and to manage your subscription and its renewals.
  • To keep the service secure, prevent abuse, and diagnose problems.
  • To learn which of our ad campaigns bring people to Muetual, as described in the next section.

We do not sell your personal data, and we show no ads in Muetual. Measuring our own ad campaigns is the only advertising use we make of personal data, and what you record in your sheets is never part of it.

Advertising measurement & your consent

We advertise Muetual on Google and in Apple’s App Store, and we want to know which of those ads actually bring people in. That is all the measurement below is for, and it never includes what you record in your sheets: expenses, amounts, notes, categories and budgets stay out of it.

  • Our website (muetual.com). The website itself sets no tracking cookies. If you arrive from one of our campaigns, it only passes the campaign parameters along in its links to the web app.
  • The web app (muetual.app). A banner lets you accept or decline optional measurement, or choose in its settings. Nothing optional loads until you choose: we use Google Consent Mode v2 in its basic mode, so Google’s tag is not loaded at all before you agree. Until then, the campaign parameters of the link you arrived with (utm_source, utm_medium, utm_campaign, utm_term, utm_content, and Google’s click identifiers gclid, gbraid and wbraid) are held only in that browser tab’s session storage, and they are discarded if you decline.
  • If you accept on the web. Google Analytics (Google’s gtag.js and its cookies) records your visit, with the page address cut down to its path and the campaign parameters, and the same product events as the apps (sign-up, sheet created, member invited, invite accepted, trial started and subscription started). We link Google Analytics to Google Ads to see which of our ads led to them; Google signals and ad personalization stay off. The campaign parameters are saved with your account, so we know which campaign brought you. And RevenueCat’s own purchase-flow analytics is switched on.
  • The mobile apps. The apps offer the same choice, switched off until you turn it on. If you accept, Google Analytics for Firebase records a few product events (sign-up, sheet created, member invited, invite accepted, trial started and subscription started) with an app instance identifier, and we use them to measure our Google Ads campaigns. On Android this may include the Android advertising ID. On iOS you make this choice in Apple’s App Tracking Transparency prompt, because Apple counts advertising measurement as tracking. Even if you allow it, we do not use the advertising identifier (IDFA).
  • Apple Ads on iOS. Through Apple’s AdServices framework, collected via RevenueCat, Apple tells us whether an install came from one of our Apple Ads campaigns. It uses no advertising identifier and needs no tracking permission.
  • Changing your mind. You can change your choice at any time: in the web app’s account settings, or in Settings in the mobile apps.

When information is shared

  • With people you invite. Members of a sheet can see that sheet’s expenses, categories, budgets, and the other members. You control who you invite and their role (view or edit).
  • With service providers that run the product on our behalf: Clerk (authentication), Cloudflare (hosting, database and bot protection), Mailjet (email delivery), Expo (push notification delivery), RevenueCat with Stripe (subscriptions and payment; on the web, RevenueCat’s purchase-flow analytics runs only if you accept it), and Google (Google Ireland Limited for users in the EEA and the UK, Google LLC elsewhere) for Google Analytics (on the web, and through Firebase in the apps) and the Google Ads campaign measurement built on it, only if you accept them. On iOS, Apple tells us through its AdServices framework whether an install came from an Apple Ads campaign. Purchases made inside the mobile apps are processed by Apple or Google under their own terms. Each processes data only to provide its service to us.
  • For legal reasons if required by law, or to protect rights and safety.

Storage & security

Your data is stored in Cloudflare’s infrastructure and transmitted over encrypted connections (HTTPS/TLS). We limit access to the data needed to run the service. No system is perfectly secure, but we take reasonable measures to protect your information.

Your choices & rights

  • Access or correct your data from within the app, or by contacting us.
  • Manage which emails you receive in Settings, or via the unsubscribe link in any email.
  • Accept or decline ad measurement, and change your mind at any time, in the web app’s account settings or in Settings in the mobile apps.
  • Request deletion of your account and associated data (see below).

Retention & deletion

We keep your data while your account is active. Delete a sheet you own and its expenses are removed; leave a shared sheet and you lose access to it. You can delete your account yourself at any time, from Settings in the app or on the web. It erases your account, your sheets and their expenses immediately and cannot be undone: sheets you own are deleted for everyone in them, while expenses you added to someone else’s sheet stay in that sheet with your name removed. If you would rather we did it, send us a message.

Children

Muetual isn’t directed to children under 16, and we don’t knowingly collect their data.

International transfers

We use global infrastructure, so your data may be processed in countries other than your own. Where required, we rely on appropriate safeguards for such transfers.

Changes to this policy

We may update this policy as the product evolves. Material changes will be reflected by the “last updated” date above, and where appropriate we’ll notify you in the app or by email.

Contact

Questions about this document? Send us a message.