Mulixo

Privacy Notice

Version 1.6 · Last updated: 15 October 2026

1. Controller and scope

Fındık: Para Yönetimi is developed and published by Mustafa Özen; Mulixo is the brand name used for the service. This notice explains processing in the mobile app, support service and optional connections. Contact us through the Fındık support center.

2. Data required to provide the app

Account and profile details and the financial records you choose to enter are processed to provide the requested features, protect the account, synchronize records, provide support and secure the service. Data is isolated by account. If notifications are enabled, a Firebase Cloud Messaging token is used to deliver them to the correct app installation; it is not used to build an advertising profile.

If you cancel your subscription, your subscription status is read through our store provider RevenueCat so the app can show a one-time in-app return offer; the offer dates and a one-way digest (hash) of your purchase are stored with your account. Your optional cancellation survey answer (reason, optional note, plan type, store and day) is stored anonymously, without a link to your account. No e-mail or notification is sent for this purpose.

When your subscription ends, a one-time service e-mail with no promotional content or offer is sent to the e-mail address of your account.

3. Optional product analytics

Analytics remains off until the user makes an affirmative choice. If allowed, Firebase Analytics can process fixed screen and feature codes, impressions and interactions, flow steps and outcomes, technical foreground duration and app/device version. Firebase may also generate installation identifiers, device details and approximate country or region.

We do not add financial amounts, balances, debts, bank or card details, transaction descriptions, search text, OCR/document content, email, name, Directus user ID or precise location to product analytics. Advertising ID collection, ad-personalization signals, Google Ads/AdMob data linking and BigQuery export are not enabled for this purpose.

4. Optional diagnostics and performance

Diagnostics requires a separate choice. If allowed, Firebase Crashlytics may process a limited error category, sanitized app-only stack, crash information and app/device version. Firebase Performance Monitoring may process manual timing measurements limited to fixed technical codes without personal data. Raw error messages, financial content, user text and account identity are not intentionally attached.

Google states that Crashlytics retains crash reports and related identifiers for 90 days before deletion begins. Performance Monitoring retains IP-associated events for 30 days and installation-associated and de-identified performance data for 60 days before deletion begins.

5. Choice, withdrawal and legal basis

Analytics and diagnostics are independent and optional. Refusal does not affect core features, the account or a subscription. Choices can be changed at any time under Settings → Analytics and diagnostics. You can also review or withdraw under Menu → Privacy and security. Not now leaves collection off and is not asked again. The choice is stored on your Fındık account and applies on all devices. Withdrawal stops new collection but may not instantly erase data already lawfully processed and placed in a provider retention cycle. The basis for optional measurement is the user’s specific, informed and freely given consent. Consent does not remove the controller’s statutory obligations.

6. Providers and international processing

Fındık may use PostgreSQL/Directus for app infrastructure; Google Firebase for messaging, analytics, crashes and performance; OpenAI for the optional ChatGPT connection; and Apple App Store or Google Play for subscriptions. Providers may process necessary data in other countries under their applicable terms and data-processing safeguards. Only data needed for the enabled service is transferred.

6a. Advertising and Apple tracking choices

Free usage may include ads provided by Google AdMob. The Google Mobile Ads SDK may process IP addresses to estimate coarse location, device and advertising identifiers, ads viewed and ad interactions, and SDK diagnostics and performance data. Your financial records are not sent to the advertising provider.

On iOS, permission to link the advertising identifier with data from other companies’ apps and websites is requested separately through Apple’s AppTrackingTransparency system dialog. This decision is separate from Google UMP advertising data-processing choices and Fındık product analytics/diagnostics consent. If tracking is denied or restricted, non-personalized ads are requested. Tracking choices can be changed under iOS Settings → Privacy & Security → Tracking. Refusal does not block core finance features or your subscription.

Google UMP presents advertising data-processing choices where required. Where its privacy options form is required, you can manage these choices again through the app’s advertising privacy options. Product analytics and diagnostics consent does not authorize advertising tracking; Firebase advertising storage, advertising user data and advertising personalization consent remain disabled.

Google privacy policy · AdMob data disclosure · Apple tracking permission

7. ChatGPT connection

The connection is optional. findik.read covers viewing and calculations; findik.write covers creation, updates, deletion and status changes. Write and deletion actions require separate confirmation. Your Fındık password is not shared with ChatGPT.

8. Retention, deletion and rights

Financial records are retained while the account is open to provide app functions. Users can request access, correction, deletion, restriction or withdrawal through the support center. ChatGPT statement/import previews expire after 15 minutes and are cleaned within 24 hours. MCP security/audit records and finalized reservations are kept for 30 days; monthly counters for 18 months. Expired OAuth operations are cleaned after one day, and revoked/expired tokens and connections when their 30-day conditions are met. Deleted production database copies expire from scheduled backups within 12 days; provider retention follows the separate periods above.

Anonymous cancellation survey answers are kept for 24 months and then deleted automatically. If you delete your account, the return-offer record is unlinked from it; only the purchase digest (hash) remains so the same purchase never receives a second offer.

The delivery record of the subscription-ended notice (account identifier, a one-way digest of the purchase and the delivery status; no e-mail address or content is stored) is deleted automatically 30 days after sending, and immediately if you delete your account.

9. Official references

EDPB consent guidance · Firebase privacy and security · Firebase Analytics collection controls · Crashlytics opt-in reporting