Privacy Policy

What data the BetterMingle app processes, why it needs it, and what rights you have.

Last updated:


1. Data controller

The data controller is CodeWhiskers, operator of the BetterMingle app. For privacy matters contact us at info@bettermingle.app.

2. What we process

CategorySpecific dataPurpose
IdentityName or nickname, e-mail, phone number (optional), account IDApp functionality, account management, communication, abuse prevention
Content you createEvents, expenses, polls, tasks, schedule, lists, wishlist, chat messagesApp functionality
PhotosProfile avatar and images uploaded to an eventApp functionality, personalization
Approximate locationEvent and carpool locations entered via place searchApp functionality
PurchasesIn-app purchase history and subscription statusUnlocking paid features, account management
Technical dataDevice identifier, performance diagnostics, crash logsAnalytics, stability, security, advertising
Usage dataInteractions with the app and which features you useAnalytics and product improvement

The app does not request access to precise location (GPS), contacts, calendar or microphone. We do not process card or bank account numbers — payments go exclusively through Google Play.

The app is not intended for children under 16 and we do not knowingly process their data.

3. Legal basis

4. Who we share data with

We do not sell your data. We share it only with processors that let us run the app:

ProcessorPurpose
Google Firebase (Authentication, Firestore, Storage, Cloud Functions, Crashlytics)Sign-in, data storage, files, server logic, crash reporting
Google Play BillingProcessing payments and subscriptions
RevenueCatSubscription management and purchase validation
Google AdMobServing ads in the free version
Google Places APISearching and autocompleting event locations
PostHog (EU)Anonymized product analytics

Some processors may handle data outside the European Economic Area. Where that happens, the transfer is covered by the European Commission’s Standard Contractual Clauses or another adequate mechanism. PostHog data is hosted in the EU.

We may disclose data to public authorities where required by law.

5. Sharing inside an event

This matters: content you add to an event is visible to the other participants of that event. That includes your name and avatar, expenses and their splits, poll votes (unless the poll is anonymous), assigned tasks, room occupancy, offered carpool seats and chat messages. Do not put anything in an event that you would not show to everyone invited.

6. How long we keep data

If you took part in an event created by somebody else, content you added to it (a chat message or an expense record, for example) may be retained to keep the event consistent for the remaining participants.

7. Security

All traffic between the app and our servers is encrypted (HTTPS/TLS). Access is enforced by database-level rules so that only participants of an event can reach its content. The app also lets you protect an event with a PIN.

8. Your rights

Under the GDPR you have the right to:

Exercise your rights by e-mailing info@bettermingle.app. We respond within 30 days. You also have the right to lodge a complaint with the Czech Data Protection Authority (uoou.cz).

9. Advertising and analytics

The free version shows ads via Google AdMob, which may use your device advertising identifier for measurement and personalization. You can limit ad personalization in your device settings (Settings → Google → Ads). Paid plans are ad-free.

We use analytics to understand which features are used and where the app fails. The data is not used to profile individuals.

10. This website

bettermingle.app is a static site with no sign-up. It uses no analytics or advertising cookies and builds no user profiles. Our hosting provider (Vercel) processes technical access logs, such as IP addresses, for as long as needed to operate and secure the site.

11. Changes to this policy

We may update this policy. We will announce material changes in the app or by e-mail. The current version is always available on this page.