How SpendWise handles your data.

Developer: Jhake Ryan Aragon
Contact: spendwise.support.ph@gmail.com

Last updated: 22 October 2026. This policy describes the current SpendWise app and support practices. SpendWise is currently undergoing testing before public release.

Information and purposes

Information	How it is used and stored
Email, account identifier, display name and authentication credentials	Firebase Authentication manages sign-in and password recovery. SpendWise uses your identifier to associate records with your account. Never send passwords to support.
Expense amounts, categories, payment methods, notes and dates	Stored on the device and synchronized to Cloud Firestore to provide expense history and budgeting features. Payment-method labels do not connect to a bank account.
Monthly limits and receipt images	Stored locally for budgeting and receipt viewing. Receipt images are not uploaded to Firebase. The camera or image picker accesses images you choose.
Added-money entries and savings challenges	Firestore stores amounts, notes, dates, challenge baselines, spending totals and visibility choices to provide those features.
Community messages and leaderboard information	Messages and sender names are shared with signed-in users. Visible leaderboard entries share a display name and savings score with signed-in users. Do not post confidential information.
Deletion requests and support emails	Used to verify ownership, process requests, prevent unauthorized deletion and respond to support questions.
Technical and security information	Google/Firebase services process information needed to deliver and protect the service, such as network information and authentication tokens. The Android release uses Firebase App Check with Google Play Integrity to help verify app and device integrity when accessing protected services.

Community moderation and saved choices

Community participation requires acceptance of our Community rules. Firestore stores your account identifier, the accepted rules version and acceptance time. A posting timestamp and message identifier enforce a ten-second posting interval. Your private block list stores the blocked account identifiers, display names and block dates. Blocking hides posts for you; it does not prevent others from seeing your shared posts.

When you report a message or user, Firestore stores your identifier, the reported account and message identifiers, the report type and reason, a copy of the reported post and display name, and submission time. Only authorized moderators can read reports. Reports are reviewed manually; a report does not automatically prove a violation. Moderators can remove posts, suspend Community posting, dismiss reports and restore access. Review outcomes and dates are stored. Suspension records store the affected account identifier and date. Moderator account identifiers are stored to enforce review access.

Open reports are retained while awaiting review. Closed reports are scheduled for manual removal after 30 days; this depends on administrator maintenance and is not an automatic timer. Deleting a post alone does not erase its report copy. Account cleanup removes reports involving the deleted account, its Community settings and block references involving it. Posting suspensions remain until restored or the account is deleted. For review of a moderation decision, email SpendWise Support. Community is not continuously monitored or an emergency service.

The app remembers an adult self-declaration separately for each account on this device. This is not identity or age verification. Account cleanup removes that account’s saved declaration. SpendWise is configured to exclude its private app data from Android backup and device transfer. After uninstalling the app, clearing its storage or changing phones, locally stored receipts, budget settings and expenses that have not synced may be lost. Expenses already synced to Firestore can load again after you sign in. This setting does not delete older backups.

Optional AI Budget Coach

When you send a message to the AI Budget Coach, its text and conversation context are sent to Google through Firebase AI Logic and the Gemini Developer API. The app does not automatically attach your expense database or receipts. Information you type yourself is included.

Within an open AI Coach screen, previous messages and replies provide conversation context. Leaving that screen, signing out, or changing accounts ends the app’s conversation session. The app does not intentionally save AI chat history to its expense database. Clearing the app session does not erase requests already sent to Google or provider-side records.

With the current no-cost Spark configuration, Gemini’s unpaid-service terms apply. Google may use prompts and responses to improve its services, and human reviewers may process them. Do not enter personal, sensitive or confidential information. AI answers are general budgeting education, not professional financial advice.

Firebase AI monitoring was switched off on 12 October 2026. Earlier monitoring stored AI content in project logs; switching monitoring off does not erase those existing records. Project log retention is described below. This setting does not change Google’s separate handling of Gemini requests under its provider terms. Account cleanup does not automatically erase those provider records.

Reporting an AI response

You can report an AI response inside the app. If you choose to report, SpendWise saves a copy of that response (very long responses may be shortened), your selected reason, account identifier, submission time and review outcome in Firestore. Your prompt and the rest of the conversation are not attached to the report. A per-account timestamp and report identifier enforce a ten-second interval between reports. Reports are available to authorized moderators; the submitting account can read its own report acknowledgement. Other users cannot read them.

Moderators review reports manually and use them to investigate and improve AI safety. Open reports remain while awaiting review; closed reports are scheduled for manual removal after 30 days through administrator maintenance. Account cleanup removes your AI reports and reporting timestamp. Reporting is not an emergency service and does not erase Google-held AI records.

Service providers and sharing

SpendWise uses Google/Firebase for authentication, cloud records, abuse prevention and optional AI features, and Gmail for support email. These providers may process data on servers outside your country. Shared community and visible leaderboard content is available to other signed-in users. Files you choose to export or share are handled by the destination you select.

The current app does not include advertising, Firebase Analytics or Firebase Crashlytics SDKs. Google/Firebase may still process technical and operational information to provide their services.

Retention and deletion

Cloud account data is kept while your account is active unless deleted through supported app features or an account-deletion request. Request deletion through the app or our account-deletion page. Verified requests are completed within seven days.

A minimal completion record is kept for 30 days after completion to block old sessions, then removed through administrator maintenance. Local receipt files, caches, exported files, gallery originals and other devices require the local-removal steps on the deletion page. Support and deletion-request email conversations are permanently deleted from the support mailbox 30 days after the case is completed, including copies in Sent and Trash. This does not remove copies in your own mailbox. Firestore scheduled backups and point-in-time recovery were disabled when checked on 12 October 2026, with no backups or recent managed export operations shown. Known development records include developer-created test accounts with made-up expenses. Deleting cloud records does not automatically remove separately saved screenshots or exports. If your request concerns a separate copy held by SpendWise Support, identify that copy in your request so it can be checked as part of the deletion process; do not send additional sensitive records unnecessarily. The seven-day account-cleanup commitment does not describe provider-controlled retention.

Project logs and provider records

The project’s default log bucket is configured to retain entries for 30 days. Required administrative and system audit logs are retained for 400 days. Earlier AI logs remain subject to the retention of the bucket where they are stored. These periods do not describe all Google-held data or promise that every AI record is removed after 30 days. Google’s separate AI data handling is governed by the provider information linked below.

Security and your choices

Account-based Firestore rules restrict private records, and administrator credentials are kept outside the app. The Android release uses Play Integrity for App Check. As checked on 17 October 2026, App Check enforcement is enabled for Cloud Firestore and Firebase AI Logic, while Authentication remains in monitoring mode. Firestore account-ownership rules provide a separate access-control layer. No method of storage or transmission is perfectly secure. You can choose not to use community, leaderboard visibility or the AI Coach, and can contact support to ask about access, correction or deletion.

Website

These static pages contain no analytics scripts, advertising scripts, forms or tracking cookies added by SpendWise. The hosting provider processes network requests to serve the site. Email links open your chosen email application; opening a link does not send the email.

Audience and changes

SpendWise is intended for college students and young adults aged 18 or older, with initial availability limited to the Philippines. It is not intended for people under 18. If you believe someone under 18 has provided personal information through SpendWise, contact support so we can investigate and handle deletion as appropriate. We will update this policy when data practices change and show the revised date.