Centee - AI Expense Tracker Legal pages for GitHub Pages deployment
Privacy Policy

Your money log stays intentionally small.

Centee is designed as a lightweight, voice-first expense tracker. This Privacy Policy explains what information the iOS and Android versions handle, when data stays on your device, when limited data is sent to external services to power AI parsing and AI reports, and what platform-specific sync or purchase features are available.

Last updated September 6, 2026
Accounts No sign-up or in-app account is required.
Current app model Local-first storage; optional iCloud sync on iOS; platform-managed purchases only where enabled.

1. Information we handle

Centee handles information that is necessary to create, organize, and, on supported platforms, sync your expense records. Depending on the platform and features you use, this may include:

  • Expense and income records you create manually or confirm after AI parsing, including title, amount, category, date, notes, and source text.
  • Receipt photos or other attachments you choose to add to a record. On iOS, supported attachment files may sync through your private Apple iCloud account when iCloud Sync is enabled.
  • Text you speak or type when using voice input or manual input. On Android, Centee receives the speech-recognition result from the device's speech-recognition service; Centee does not itself upload raw microphone audio to its AI parsing service.
  • Text recognized from receipt images. On iOS, receipt OCR may be performed on-device using Apple frameworks before text is sent for AI parsing. On Android, the current receipt-scanning flow sends the compressed receipt image you choose directly to the AI parsing service after you allow AI data sharing; the Android app does not perform on-device OCR before that request.
  • When you request an AI spending report, selected expense and income records from the report period, including titles, amounts, dates, categories, currency, summary metrics, budget information, locale, and custom category names.
  • Recurring bill and reminder plans you create, including cadence, next due date, reminder time, lead time, completion or skipped status, custom categories, app preferences, notification preferences, profile display name and bio, widget snapshot data, and purchase entitlement state.
  • Payment source profiles you choose to create, such as a card nickname, card type, issuer, last four digits, statement closing day, payment due day, credit limit and currency, or digital-wallet labels. Centee does not request or store a full card number or security code.
  • Limited purchase and transaction status information provided by Apple or Google through the applicable app-store billing service when a Premium purchase flow is enabled for that platform and build.
Important detail about receipts

On iOS, Centee may perform optical character recognition on-device before AI parsing. On Android, the current receipt-scanning flow sends the compressed receipt, bill, or payment screenshot you choose to scan directly to the parsing service after you allow AI data sharing. In either case, do not scan a document unless you are comfortable with the information in it being processed for the requested feature.

2. How we use information

We use information handled by Centee to operate the app and deliver the features you request.

  • To create, store, edit, display, and delete your records on your device.
  • To generate summaries, widgets, charts, and insights from your saved records.
  • To request microphone, speech recognition, photo-library or media access, camera, notification, and, on iOS, iCloud access only when you use features that require them.
  • To process natural-language text, receipt text, and, on Android, receipt images you choose to scan through the AI parsing pipeline so the app can suggest structured entries.
  • To generate optional AI weekly or monthly spending reports from the records and summary metrics you choose to analyze.
  • To store and display payment source profiles and associate a selected card or wallet with an expense record.
  • To sync supported records, attachment files, recurring bill plans, custom categories, and selected profile and preference data through iCloud when you enable iCloud Sync on iOS. The current Android version does not offer cross-device cloud sync.
  • To confirm and restore paid Centee Premium access through the applicable Apple or Google app-store billing service when that service is enabled for your platform and build.

3. External services, AI processing, and sharing

Centee does not sell your personal data. The app does, however, rely on a small number of third-party services when specific features are used.

  • Apple services. On iOS, Apple may process microphone, speech recognition, iCloud, notification, and purchase-related data according to Apple's own terms and privacy policies.
  • Android and device services. On Android, Android system services and the speech-recognition, camera, photo-picker, notification, or app-store provider selected on your device may process data needed to provide those features, subject to their own terms and privacy policies.
  • Google Firebase Analytics. The Android build includes Firebase Analytics for product measurement. Depending on the build and device settings, Firebase may automatically process app-instance identifiers, device and app information, and usage or diagnostic events.
  • Google Firebase Crashlytics. The Android build includes Crashlytics to receive crash reports and related technical diagnostics, such as stack traces, app state, device information, and build information, to help improve stability.
  • RevenueCat. On iOS, when the purchase service is configured, RevenueCat may process an anonymous app user identifier and purchase or entitlement status to manage subscriptions and restore access. Apple remains the payment provider.
  • Cloudflare Workers. AI parsing requests are routed through a Centee-operated Cloudflare Worker endpoint.
  • Xiaomi MiMo. The current AI parsing backend forwards parsing requests to Xiaomi MiMo to transform text and, for receipt or bill scanning, compressed images into structured expense data.

Before Centee sends data to the AI processing pipeline, the app displays an AI Data Sharing Consent screen that explains what data may be sent, identifies the processing services, describes the purpose of processing, and lets you decline. You can withdraw AI data sharing consent later in Settings.

In the current implementation, the information shared externally for AI parsing may include the text you speak or type, compressed receipt or bill images you choose to scan, OCR text recognized from those images when available, merchant names, amounts, dates, categories, notes, currency, locale, custom category names, current time, and an anonymous install ID. For AI reports, Centee may send expense and income records from the selected report period, including titles, amounts, dates, categories, currency, summary metrics, budget information, locale, custom category names, payment-method or payment-source labels, card or wallet categories, and an anonymous install ID. When you use Ask Centee, the request may also include a small selection of relevant record details needed to answer your question. For Apple App Store or Google Play purchases, the applicable storefront handles payment-card details and Centee does not receive your full card number. Separately, payment-source metadata that you choose to enter in Centee is stored locally and is not a payment credential.

We expect the third-party services we use for AI processing and infrastructure to protect data under their applicable terms, privacy commitments, and security practices. We do not use third-party AI services to sell your personal data or serve behavioral advertising.

No advertising SDKs in the current version

Based on the current app implementation, Centee does not include third-party advertising SDKs and does not use the information described above to serve behavioral advertising. The Google Play Data safety form and this policy must be updated if analytics, crash reporting, advertising, or other SDK behavior changes.

4. Storage, sync, and retention

Centee is local-first. Most app data is stored on your device. Some features add optional syncing or external processing:

  • Local storage. Records, recurring bill plans, reminder settings, custom categories, widgets, avatars, attachments, and app preferences are stored on-device so the app can work locally. On Android, the current version stores this information locally and does not provide cross-device cloud sync.
  • Optional iCloud sync on iOS. If you enable iCloud Sync, supported expense record data, attachment files, recurring bill plans, custom categories, profile details, avatar image, currency selection, and budget settings may sync through your private Apple iCloud account using CloudKit.
  • Widget data. Widget snapshot data is stored locally so the relevant iOS or Android widget can render current summaries.
  • Notifications. If you enable reminders, the app stores your notification preferences and recurring bill reminder schedule on your device and uses them to schedule local notifications.
  • Security and transmission. When Android sends information to the AI backend or Google services, the current build uses HTTPS/TLS transport. Android records and payment-source profiles are stored in the app's private local storage. Centee does not collect full card numbers or security codes.

The Android app does not create a Centee account or keep a server-side copy of your ledger. AI requests and responses may be processed by the Centee backend and its configured providers only when you request an AI feature; the Android app does not keep those requests as a cloud history. Cloudflare, Xiaomi MiMo, Firebase, Apple, Google, and other service providers may retain limited request, technical, crash, or transaction records under their own policies for security, abuse prevention, service operation, debugging, or legal compliance. We intend to retain information under our control only for as long as needed for the purposes described here. You can delete local records from inside the app, disable notifications, disable iCloud Sync, or uninstall the app.

5. Your choices

  • You can use core parts of Centee without creating an account.
  • You can deny microphone, speech recognition, photo-library or media access, camera, notifications, or iCloud permissions, but related features may not work.
  • On iOS, you can disable iCloud Sync in Settings. In the current implementation, changes to the iCloud setting apply on next app launch.
  • You can decline AI data sharing before AI parsing or AI report generation, and you can withdraw AI data sharing consent later in Settings.
  • You can review AI-generated results before saving them.
  • You can delete records and clear stored data from within the app.
  • Because Centee does not create a user account, there is no server-side Centee account to close. To ask about deletion of information under our control, email sampson1993@zohomail.cn.

6. Children

Centee is not directed to children under 13. If you believe a child has provided personal information through the app, please contact sampson1993@zohomail.cn.

7. Policy updates

We may update this Privacy Policy from time to time as the app evolves. If we make material changes, we will update the date at the top of this page and, when appropriate, update links inside the app or the App Store listing.

8. Contact

Developer: rings3studio. For privacy questions, data requests, or support, contact sampson1993@zohomail.cn.