Poolsy Privacy Policy

1. Who Runs Poolsy

For any privacy question or request, contact renvoyapp@gmail.com.

2. What Data We Collect

We handle the following data to provide, secure, measure, and monetize Poolsy:

• Account data: email address, authentication-provider identifiers, password hash, and display name for account creation, sign-in, recovery, security, and identification within shared groups
• Shared group content: group and member names, expenses, splits, settlements, balances, recurring templates, budget targets, currencies, and dates for the shared ledger and synchronization between group members
• Purchase history and subscription status for Google Play billing, purchase validation, restore, premium access, and subscription analytics through RevenueCat
• IP address, ad and app interactions, diagnostics, and device or account identifiers, including the Android advertising ID when available, for advertising, measurement, and fraud prevention through Google Mobile Ads/AdMob
• The requested currency pair when fetching an exchange rate from Frankfurter; group names, expense descriptions, and account identifiers are not included in that request

3. On-Device Features and Data We Do Not Collect

Receipt photos you select for text recognition are processed on your device and are not uploaded or retained by Poolsy.

Payment reminders and budget alerts are scheduled locally on your device.

Poolsy does not access contacts or precise device location and does not include a first-party analytics or crash-reporting SDK.

4. Service Providers and Sharing

We do not sell personal data. Providers process data only as needed to operate, secure, measure, and monetize Poolsy as described in this policy.

• Supabase stores and synchronizes account, profile, and group data and provides authentication and account deletion
• Google Sign-In provides optional native authentication; Poolsy never receives your Google password
• Google Play and RevenueCat process purchases, purchase history, and premium entitlement status
• Google Mobile Ads/AdMob and Google's User Messaging Platform provide consent handling, ads, measurement, and fraud prevention
• Frankfurter returns requested currency exchange rates
• Other members of your groups can see the shared group and expense information added to those groups

5. Security and Retention

Data is transmitted using HTTPS/TLS. Supabase Row Level Security restricts shared group records to group members.

Account identifiers are retained while an account is active. Shared expense history and the member name or label shown in that shared ledger may remain after account deletion, with the deleted user's sign-in and account link removed, so remaining members' balances and history remain understandable.

Service-provider records such as purchase history may be retained under the provider's fraud-prevention, tax, legal, or operational requirements.

6. Your Choices and Account Deletion

Where Google's consent flow is available, you can manage advertising consent in the App. Android settings also let you reset or delete the advertising ID.

You can manage or cancel subscriptions in Google Play. Deleting a Poolsy account does not cancel an app-store subscription.

You can delete your account in Poolsy from Settings → Account → Delete Account or use Poolsy's published Delete Account page if you cannot access the App.

7. Children's Privacy

Poolsy is not directed at children under 13, and we do not knowingly collect data from children under 13.

8. Changes and Contact

If this policy changes materially, we will update the effective date shown above.

For questions, data requests, or concerns, contact renvoyapp@gmail.com.