This Privacy Policy explains how Miao YU ("we," "us," or "our") handles information in connection with the LoanGauge mobile application (the "App"). This English-language version is the master, globally applicable version of our Privacy Policy. Where we provide translations, the English version governs in the event of any conflict.
LoanGauge is an educational tool. It helps users understand how car-title lending works and generates illustrative estimates. We are not a lender, broker, credit-services organization, or financial advisor, and we do not process loan applications.
The App is supported by advertising. It uses Google AdMob to display ads and, where required by law, asks for your consent before any ad is requested. Sections 8 and 12 explain what that means for your data and how you can change or withdraw your choices at any time.
The App also uses Google Firebase Analytics and Google Firebase Crashlytics to record how the App is used and to collect crash reports. That processing starts when you open the App. It is separate from advertising and is described in Section 9.
By downloading or using the App, you acknowledge that you have read and understood this Privacy Policy.
1. Summary (plain-language overview)
- The App's own features run on your device. The vehicle details, preferences (including your selected country), checklists, points balance, and estimates you create are stored locally on your device, not on our servers.
- We do not operate servers that receive the estimates, vehicle records, checklists, or other content you create in the App. We cannot read that content. Separately, the App uses Google Firebase Analytics and Google Firebase Crashlytics to record how the App is used and to collect crash reports. See Section 9.
- We do not require an account, and we do not ask you to provide your name, email, address, or government identifiers to use the App.
- The App is ad-supported. It integrates the Google Mobile Ads (AdMob) SDK and shows banner, in-content native, interstitial, app-open, and opt-in rewarded-video ads. AdMob and its advertising partners process device data and identifiers to deliver, cap, and measure those ads. See Section 8.
- Where a consent choice is required in your region (for example the EEA and the UK), the App shows a Google User Messaging Platform (UMP) consent message before any ad request, with an explicit “Do not consent” option. If you refuse consent as a whole, the ads SDK is not started and no ad at all is shown — not even a non-personalized one. If you decline only personalization, non-personalized ads are shown instead. Either way, the rest of the App works normally.
- In those regions the App shows an "Ad Privacy Options" entry under Profile → About that reopens the consent form so you can change or withdraw your consent at any time.
- On iOS we present Apple's App Tracking Transparency (ATT) prompt. If you decline, ads are limited to non-personalized advertising.
- Usage analytics and crash reports start when you open the App, including during onboarding. They are not controlled by the advertising consent message, by Apple's tracking prompt, or by the ad-free unlock, and there is no in-app control to turn them off. Deleting the App stops further collection from that installation.
- We do not ask for location permission, do not read your GPS position, and never receive GPS or other precise location ourselves. Google (advertising partners and Firebase Analytics) may derive an approximate location from your IP address. The consent message also lists precise geolocation as an optional feature: it is off unless you actively turn it on, and you can refuse or withdraw it at any time (see Section 8d).
- Payments for optional in-app purchases are handled by Apple. We never receive your payment-card details. Buying "Unlock Everything" removes all ads. It does not stop Firebase Analytics or Crashlytics.
- We do not sell your personal information for money. Personalized advertising may nevertheless qualify as a "sale" or "share" (cross-context behavioral advertising) under some U.S. state privacy laws; Section 12 explains how to opt out.
This summary is for convenience only; please read the full policy below.
2. Scope
This policy applies to the LoanGauge mobile application and any related services that link to it. It does not apply to third-party services, websites, or products that we do not control, including Apple's App Store, Google's services, or any lender you may contact.
3. Information we collect
We practice data minimization and collect as little information as possible.
a. Information you provide and create in the App.
When you use the App you may choose a country, which sets the currency, distance unit, vehicle catalogue, and the states or equivalent regions offered when you create an estimate; enter vehicle information (such as category, make, model, year, mileage, condition, title status, outstanding balance, and a desired amount); select a state or equivalent region; and use checklists. This information, along with the estimates it generates, your points balance and check-in history, your notification preferences, and your other preferences (such as appearance mode, the selected country, and any unlocked content), is stored locally on your device using the operating system's standard app-storage mechanisms. We do not transmit this content to our servers, and we cannot access it. A limited set of coarse facts about an estimate (not the make, model, year, mileage, amounts you type, or the estimate itself) may be sent to Google Firebase, as described in Sections 3(g) and 9. If you export a report as a PDF, the file is generated on your device; it leaves your device only if and where you choose to share it (for example, through the iOS share sheet).
The App infers a default country from your device's region setting; it does not use location permission to do so. Language is separate: the App follows the per-app language you set in iOS Settings, and that choice need not match the selected country. Language is processed on-device as described in Section 3c.
Notifications. If you turn on reminders, they are local notifications scheduled on your device. There is no push server and no device token; nothing about your reminders is sent to us or to any third party.
b. Purchase information.
If you make an optional in-app purchase, the transaction is processed by Apple through the App Store using your Apple ID. Apple may share with us limited, non–payment-card information such as a transaction identifier and confirmation of purchase or restoration, so we can unlock the content you bought. We do not receive your credit- or debit-card number.
c. Device and technical information.
The App may process basic technical information on your device (such as device model, operating-system version, language, region/time-zone settings, and app version) to operate correctly, format currency and content, and infer a default region. This processing occurs on-device. The same kinds of technical data may also be sent to Google when Firebase Analytics or Crashlytics runs, as described in Sections 3(g) and 9.
d. Diagnostics you choose to share via Apple.
Independently of Firebase Crashlytics (Section 9), if you have enabled sharing of diagnostics and usage data in your iOS settings, Apple may provide us with aggregated, anonymized crash and usage reports through App Analytics. This data is controlled by Apple and does not identify you to us. You can change this in iOS Settings → Privacy & Security → Analytics & Improvements.
e. App ratings.
If you choose to rate the App, the rating prompt is presented by Apple. Your review and rating are handled by Apple under Apple's terms; we do not receive personal information from this feature.
f. Advertising data. AdMob
The App integrates the Google Mobile Ads (AdMob) SDK. Subject to your consent choices and your ATT selection, Google and its advertising partners may collect and process:
- the advertising identifier (IDFA) — only if you allow tracking through the ATT prompt — and the vendor identifier (IDFV);
- IP address and the approximate location derived from it; and, only if you actively opt in to the corresponding optional feature in the consent message, precise geolocation data (see Section 8d);
- device and technical data such as device model, OS version, language, screen size, network type, and app version;
- ad-interaction data such as ad requests, impressions, viewability, clicks, and rewarded-video completions, used for delivery, frequency capping, fraud prevention, billing, and aggregated reporting.
The App itself also keeps on-device counters (ads shown this session and today, timestamps of the last full-screen ad) purely to enforce our own frequency limits. These counters stay on your device and are never transmitted.
No ad object is created and no ad request is made until the consent flow described in Section 8 has completed and allows it. If you purchase "Unlock Everything", the ad SDK is not used at all. Firebase Analytics and Crashlytics still run, as described in Section 9.
g. Usage analytics and crash reports processed by Google Firebase. Firebase
The App integrates Google Firebase Analytics and Google Firebase Crashlytics. We are the controller of this processing. Google processes the information on our behalf as a processor. Details of what is sent, what is not sent, when collection starts, and how it relates to advertising are in Section 9.
In short, Firebase may process:
- automatic usage events (such as first open, session start, and, where the SDK records them, screen views and a completed App Store purchase) and events we record for key in-app actions (such as completing onboarding, completing or leaving an estimate, opening a paywall, starting checkout, a failed purchase or a restore, watching a rewarded video, earning or spending points, and sharing a report);
- coarse facts attached to some of those events, such as the selected country and region (state or equivalent), vehicle category, condition, and title status, and whether you entered a desired amount or an outstanding balance;
- coarse user properties, such as selected country, whether onboarding is complete, whether you have purchased the ad-free unlock, whether ads have been removed, a bucketed points range, a bucketed vehicle-count range, whether any reports have been unlocked, and the App Tracking Transparency status;
- crash reports if the App fails, including technical logs and the state of the App at the time of the failure; and
- technical identifiers used to operate those services, including the iOS Identifier for Vendor (IDFV) and a Firebase App Instance ID. We do not attach Apple's Identifier for Advertisers (IDFA) to the events or user properties we record. The Firebase Analytics SDK we use may still read the IDFA if you have allowed tracking. We do not use Firebase to personalize advertising.
This does not include the make, model, year, mileage, or amounts you type, and it does not send a copy of the estimates stored on your device. Collection starts when you open the App, including during onboarding. It is independent of advertising consent. There is no in-app control to turn it off.
4. What we do not collect
- We do not collect your name, email address, phone number, mailing address, or government-issued identifiers as a condition of using the App. If you email us, we receive whatever you include in that message.
- The App does not request the device's location permission and never reads your GPS position; it does not access your contacts, photos, microphone, health data, or camera. (For approximate location derived from IP address by Google, see Sections 3(f), 3(g), 8 and 9.)
- We do not create user accounts or profiles on our servers, and we receive none of the vehicle records, estimates, checklists, or reports you create in the App, except the coarse facts described in Sections 3(g) and 9.
- We do not operate our own analytics backend. We do integrate Google Firebase Analytics and Crashlytics, which process a Firebase App Instance ID and related technical identifiers as described in Section 9. We still do not receive an identifier that lets us recognize you across other companies' apps.
5. How we use information
We use the limited information described above to:
- provide and operate the App's educational features and generate on-device estimates;
- localize content, currency, and default region;
- process and restore your optional in-app purchases (via Apple);
- deliver, cap, and measure advertising, and — where you consent — personalize it (Section 8);
- schedule the local reminders you turn on, and operate the points and rewarded-video features;
- maintain the security, integrity, and proper functioning of the App, including preventing invalid ad traffic;
- diagnose problems and improve the App, including through Firebase Analytics and through aggregated, anonymized information;
- operate Firebase Crashlytics so we can diagnose crashes and keep the App stable; and
- comply with legal obligations.
We do not use your information for automated decisions that produce legal or similarly significant effects about you. Estimates are illustrative and are not lending decisions.
6. Legal bases for processing (EEA/UK users)
Where the EU/UK General Data Protection Regulation applies, we rely on the following legal bases:
- Consent (Art. 6(1)(a) GDPR, and Art. 5(3) of the ePrivacy Directive for storing or accessing information on your device) — for advertising, advertising identifiers, ad personalization and measurement, and for any optional feature you actively turn on in the consent message, such as the use of precise geolocation data. Consent is collected through the Google UMP consent message described in Section 8, and you may withdraw it at any time via the "Ad Privacy Options" entry in the App. Withdrawal does not affect the lawfulness of processing carried out before withdrawal. This consent mechanism applies to advertising. It does not apply to Firebase Analytics or Crashlytics, which are described in Section 9.
- Performance of a contract (Art. 6(1)(b)) — to provide the App and process and restore the purchases you request.
- Legitimate interests (Art. 6(1)(f)) — to keep the App secure and functional, to enforce our own on-device ad frequency limits, to prevent invalid ad traffic and fraud, to operate Firebase Crashlytics so we can diagnose crashes and keep the App stable, and to operate Firebase Analytics so we can understand how the App is used and improve it, balanced against your rights.
- Legal obligation (Art. 6(1)(c)) — to comply with applicable law.
For processing carried out through the App we act as the controller. For the advertising described in Section 8, Google acts as an independent controller (and, for certain measurement activities, as a joint or separate controller) under its own terms; the vendors you see listed in the consent message act as controllers for their own processing. For Firebase Analytics and Crashlytics, we are the controller and Google acts as our processor, as described in Section 9.
7. How your information is stored and retained
- Local storage. Content you create in the App, your preferences, your points balance, and our on-device ad frequency counters are stored on your device using the operating system's standard app-storage mechanisms. They remain until you delete them (for example, using the App's "Reset All Data" function or by uninstalling the App).
- Consent record. Your consent choices are stored on your device by the Google UMP SDK, in the format defined by the IAB Transparency & Consent Framework, and are made available to the advertising vendors you have chosen. Uninstalling the App removes this record.
- Retention by us. Because we do not store your App content on our servers, we do not retain it. We hold only what you send us directly (for example, an email you write to us), for as long as needed to handle your request.
- Retention by others. Purchase records maintained by Apple, advertising data processed by Google and its partners, and Firebase Analytics and Crashlytics data processed by Google on our behalf, are retained according to their own policies. See Google's data-retention information and the Firebase privacy documentation.
- Firebase identifiers. The Firebase App Instance ID and related technical identifiers described in Section 9 are sent to Google when you use the App. “Reset All Data” in Profile does not stop this processing. Deleting the App stops further collection from that installation; it does not erase information already sent.
Please read Apple's App Store privacy labels and the privacy manifests shipped with the App, the Google Mobile Ads SDK, User Messaging Platform, and Firebase together with this policy. This policy is the fuller, controlling description. Each privacy manifest describes only the code that ships it. Advertising through AdMob may involve tracking as Apple defines that term, which is why we present the App Tracking Transparency prompt. The App's own privacy manifest does not itself mark the App as used for tracking; the Google Mobile Ads SDK ships a separate privacy manifest for advertising. The App's own privacy manifest lists data this App's code sends through Google Firebase Analytics (that analytics SDK does not ship its own collected-data manifest): device identifiers used for analytics, product-interaction events, purchase history recorded by analytics, and coarse location inferred from IP address (not GPS). Crash reports and other diagnostic data are declared in the Firebase Crashlytics privacy manifest. Please keep the App Store privacy labels aligned with the combined picture; this policy remains the fuller description.
8. Advertising and consent AdMob
a. What we show.
The App is ad-supported and uses the Google Mobile Ads (AdMob) SDK, provided by Google Ireland Limited (for users in the EEA, the UK and Switzerland) or Google LLC. The App may display:
- Banner ads anchored at the bottom of browsing screens. Some of these banners may be collapsible: they can arrive expanded over the content above, and you can collapse them back to the standard banner height. A collapsible banner is still a banner ad from the same SDK and partners; expanding or collapsing it does not collect additional categories of data.
- Native ad cards placed in content, always marked with an "Ad" badge and the AdChoices icon;
- Interstitial (full-screen) ads at natural transition points;
- App-open ads when you open the App from a cold start after onboarding, or when you return to the App after a genuine period in the background;
- Rewarded video ads, which are always opt-in: they play only when you deliberately choose to watch one in exchange for points.
The App applies its own frequency limits (cooldowns, per-session and per-day caps) and does not show full-screen ads on certain screens, including onboarding, the paywall, the store, and legal pages, or during the step-by-step estimate input flow. These limits are enforced with counters stored only on your device.
b. Consent, and how to change it.
Where a consent choice is required by law in your region — including the European Economic Area, the United Kingdom, and certain other regulated jurisdictions — the App presents a consent message from Google's User Messaging Platform (UMP) the first time it is shown after onboarding, and before any ad is requested. The message identifies the purposes of processing and the advertising vendors involved, and lets you consent, refuse, or manage each option individually. Your choices are recorded on your device under the IAB Transparency & Consent Framework (TCF) and communicated to those vendors.
- Refusing is as easy as agreeing: the message shows an explicit “Do not consent” option alongside the consent option, in addition to the option to manage each purpose and vendor individually.
- If you refuse consent as a whole (for example by choosing “Do not consent”), the Google Mobile Ads SDK is not initialized and no ad of any format is requested — not even a non-personalized one, and not the opt-in rewarded video, which means rewarded points cannot be earned by watching videos in that state. The daily check-in and the one-time welcome bonus still work. This is a consequence of the framework itself: without your permission to store and access information on your device, no ad can lawfully be requested.
- If you instead allow the basic storage and access purpose but decline personalization (through “Manage options”), the App continues to show non-personalized ads, which are based on the content and general context rather than on a profile of you.
- Whichever choice you make, every other feature of the App continues to work normally. Access to the App is not conditioned on your consent to advertising.
- In regions where a consent choice is required, the App displays an “Ad Privacy Options” entry on the Profile screen, in the “About” section next to the Privacy Policy and Terms of Use links. It stays available there for as long as the requirement applies. Selecting it reopens the same consent management form, where you can review the purposes and vendors and change or withdraw your consent at any time. Withdrawing consent does not affect the lawfulness of processing carried out before withdrawal.
- As a convenience, the same option is also offered in the rewarded-video area when videos are unavailable because consent was declined, so you can reconsider without leaving the screen. This is an additional shortcut only; the entry on the Profile screen is the permanent one.
- Where applicable law does not require a consent choice for your region, Google's UMP does not classify privacy options as required and this entry is not shown. You can still control ad personalization through your device settings, as described below.
- Some vendors may rely on legitimate interests for certain purposes. Where that is the case, the consent form lets you object to it; the same form remains available through the "Ad Privacy Options" entry.
c. App Tracking Transparency (iOS).
Once the consent flow has completed, and only if you have not already made this choice on your device, the App presents Apple's App Tracking Transparency (ATT) prompt. The two prompts are never shown at the same time, and neither is shown during onboarding.
- If you allow tracking, the advertising identifier (IDFA) may be used to personalize and measure ads.
- If you decline, the IDFA is not available and ads are limited to non-personalized advertising. Non-personalized ads still involve limited processing of device data (such as IP address and general ad-interaction signals) for ad delivery, frequency capping, fraud prevention, and aggregated reporting; they are contextual rather than based on a profile of you.
- You can change this choice at any time in iOS Settings → Privacy & Security → Tracking, and adjust Apple's own ad personalization under → Apple Advertising.
d. Location data used for advertising.
The App does not request the device's location permission, does not read your GPS position, and contains no location SDK. We do not receive GPS or other precise location from the device. Approximate country or region may still be derived from an IP address by Google, as described below and in Sections 3(c), 3(g) and 9.
- Approximate location. As with any internet connection, advertising partners can derive an approximate location (typically country or city level) from your IP address. This is used for ad delivery, legal compliance, and fraud prevention.
- Precise geolocation. The consent message presents "use precise geolocation data" as a special feature under the IAB Transparency & Consent Framework. It is an opt-in feature: it cannot be relied on under legitimate interests, and it applies only if you actively enable it yourself in the consent message. If you do, participating vendors may process precise location data for the advertising purposes you agreed to. You can decline it at the outset, or turn it off later at any time through the "Ad Privacy Options" entry described in Section 8b. Declining has no effect on your ability to use the App.
e. Children and ad content.
The App is not directed to children, is not in Apple's Kids Category, and is not tagged for users under the age of consent. Requested ads are restricted to Google's "G" (general audiences) maximum content rating.
f. Google's role and further information.
Google's processing of data in this context is governed by Google's own terms. See policies.google.com/privacy, policies.google.com/technologies/ads, Google Ads Controller-Controller Data Protection Terms, and the list of advertising partners that may serve ads in this App. The full vendor list applicable to you is also available inside the consent message itself.
g. Removing ads.
The optional "Unlock Everything" in-app purchase removes all advertising. Once it is active, no further ad is requested or displayed, and on subsequent launches the ad SDK is not started at all. It does not stop Firebase Analytics or Crashlytics, which are described in Section 9.
9. Analytics
a. Google Firebase Analytics and Crashlytics. Firebase
The App integrates Google Firebase Analytics and Google Firebase Crashlytics, provided by Google LLC (and, where applicable, Google Ireland Limited). We are the controller of this processing. Google processes the information on our behalf as a processor under the Firebase Data Processing and Security Terms and related Firebase privacy documentation. See also Google's Privacy Policy.
This processing is separate from advertising (Section 8). It is not controlled by the Google UMP consent message, by “Ad Privacy Options”, by Apple's App Tracking Transparency prompt, or by purchasing the ad-free unlock. Collection starts when you open the App, including during onboarding. There is no in-app control to turn it off. Collection is disabled in automated tests and SwiftUI previews so that those environments do not send data to production Analytics or Crashlytics.
For users in the EEA/UK, we rely on legitimate interests (GDPR Article 6(1)(f)) for this processing, as described in Section 6: to understand how the App is used so we can improve it, and to diagnose crashes so we can keep the App stable. We have considered that this processing starts without an in-app opt-out. If you object, you can stop further collection from that installation by deleting the App, as described below. Where ePrivacy Directive Article 5(3) may also apply to storing or accessing information on your device for this purpose, we disclose that we do not currently present a separate consent prompt for Firebase; the UMP message described in Section 8 covers advertising only.
b. What is sent, and what is not.
Subject to the minimization described here, Firebase may process:
- Automatic events provided by the SDK, such as first open and session start. The SDK may also record screen views. For a completed App Store purchase, an in-app purchase event may also be recorded automatically. If AdMob is linked to the same Firebase project, impression-level ad revenue may appear as an ad_impression event. We do not log that advertising event ourselves.
- Events we record for key in-app actions, including: starting and completing onboarding, and which onboarding page is shown; starting, stepping through, completing, or leaving an estimate unfinished; viewing an estimate result; tapping to view or unlock a report; opening, selecting, or dismissing a paywall; starting checkout; a failed purchase attempt; attempting to restore purchases; watching a rewarded video; earning points (from videos, daily check-in, the welcome bonus, or a purchase); spending points to unlock a report; viewing a report; and sharing a PDF.
- Coarse facts on some events, such as the selected country and the selected region (state or equivalent), vehicle category, condition, and title status, whether you entered a desired amount or an outstanding balance, which estimate step you were on, which in-app item you selected, and a count of points or of videos watched that day. These facts do not include make, model, year, mileage, or the amounts you type into an estimate, and they do not include a copy of estimate text stored on the device.
- Coarse user properties, such as selected country, whether onboarding is complete, whether you have purchased the ad-free unlock, whether ads are currently removed, a bucketed points range, a bucketed count of saved vehicles, whether any reports have been unlocked, and the App Tracking Transparency authorization status.
- Crash reports if the App fails, including stack traces, device and OS version, and the state of the App at the time of the failure. A stack trace is technical, but it may include text that was on screen.
- Technical identifiers used to operate those services, including the iOS Identifier for Vendor (IDFV) and a Firebase App Instance ID. We do not attach the IDFA to the events or user properties we record. The Firebase Analytics SDK we use may still read the IDFA if you have allowed tracking through Apple's App Tracking Transparency prompt. If you decline that prompt, the IDFA is not available. We do not use Firebase to personalize advertising.
Firebase events may also include the kinds of technical data described in Section 3(c) (such as device model, OS version, language, country derived from IP, and coarse time zone), because the Firebase SDK runs on the same device and communicates with Google's servers.
c. Apple App Analytics, and advertising measurement.
Independently of Firebase Crashlytics, Apple may collect crash and usage data if you have enabled Share With App Developers in iOS Settings. That data is governed by Apple's policies and your iOS settings; we receive it only in aggregated form, if at all, through App Store Connect.
Advertising measurement by Google AdMob and advertising partners (impressions, clicks, viewability, and rewarded-video completions) is described in Section 8. That processing is controlled by the advertising consent and ATT choices in Section 8, not by this Section 9.
d. How to stop further collection.
“Reset All Data” in Profile deletes the App's local content on your device. It does not stop Firebase Analytics or Crashlytics, and it does not erase information already sent to Google.
Deleting the App stops further collection from that installation. It does not erase information already sent. Google retains Firebase Analytics and Crashlytics data according to Google's Firebase retention practices. You may also contact us at yumiao.dev@gmail.com if you wish to make a request about information Google processes on our behalf.
10. How we share information
We do not sell your personal information for money, and we do not transfer your App content to anyone. Note that personalized advertising may nevertheless be characterized as a “sale” or “share” under certain U.S. state privacy laws — see Section 12. We share information only as follows:
- Apple — for App Store distribution, in-app purchases, ratings, and optional diagnostics, under Apple's privacy terms.
- Google (AdMob) and its advertising partners — device data, identifiers, and ad-interaction data, in accordance with your consent and ATT choices, as described in Section 8. The applicable vendor list is shown in the consent message.
- Google (Firebase) — usage events, coarse facts, user properties, crash reports, and technical identifiers described in Section 9, processed by Google on our behalf as a processor.
- Service providers — parties that help us operate the App (for example, hosting for this policy page), bound by confidentiality and data-protection obligations.
- Legal and safety — where required by law, regulation, legal process, or to protect rights, safety, or the integrity of the App.
- Business transfers — in connection with a merger, acquisition, financing, or sale of assets, subject to this policy.
11. International data transfers
We provide this App globally. Apple, Google (including AdMob and Firebase), and Google's advertising partners may process information in countries other than your own, including the United States, whose data-protection laws may differ from those in your jurisdiction. Where required, such transfers rely on appropriate safeguards — for example, the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, and, where applicable, the EU–U.S. Data Privacy Framework and its UK Extension. Details of Google's transfer mechanisms are set out in Google's privacy documentation linked in Sections 8 and 9.
12. Your privacy rights
Depending on where you live, you may have some or all of the following rights regarding personal information about you: to access, correct, delete, port, restrict, or object to processing, and to withdraw consent.
- Because your App content is stored only on your device, you can delete that local content at any time using "Reset All Data" in the App. That function does not stop Firebase Analytics or Crashlytics. Uninstalling the App stops further collection from that installation; it does not erase information already sent to Google.
- Advertising choices: use "Ad Privacy Options" in the App where it is shown (Section 8b), the ATT setting in iOS Settings → Privacy & Security → Tracking, and Google's own ad controls. Where the entry is not shown because no consent choice is required in your region, the device settings remain available.
- Analytics and crash reports: there is no in-app control to turn off Firebase Analytics or Crashlytics. To stop further collection from that installation, delete the App. For information Google processes on our behalf, you may also contact us at the email below.
- EEA/UK (GDPR): you may withdraw advertising consent at any time, and you have the right to lodge a complaint with your local supervisory authority. You may also object to processing based on legitimate interests, including Firebase Analytics and Crashlytics. Because much of your App content stays only on the device, we may be unable to identify you from that content (Art. 11 GDPR). Requests concerning advertising data, and concerning Firebase data Google processes on our behalf, should also be directed to Google or made through us at the email below.
-
California (CCPA/CPRA) and other U.S. state privacy laws: you have rights to know, access, delete, and correct, and the right to opt out of the "sale" or "sharing" of personal information and of targeted advertising and profiling.
- We do not sell your personal information for money, and we do not knowingly sell or share the personal information of consumers under 16.
- However, personalized advertising delivered through AdMob may qualify as a "sale" or a "share" (cross-context behavioral advertising) or as "targeted advertising" under CPRA and similar state laws.
- You can opt out by declining Apple's App Tracking Transparency prompt (or turning off "Allow Apps to Request to Track" / the per-app toggle in iOS Settings), by using the in-app "Ad Privacy Options" entry where it is shown, or by purchasing the ad-free unlock. The App is not a website and does not process browser-based opt-out preference signals such as Global Privacy Control; the controls just described are the means of opting out.
- The categories involved are identifiers (advertising/device identifiers, IP address), internet or other electronic network activity (ad interactions), and geolocation data (approximate location inferred from IP address; precise location only if you have actively opted in through the consent message, where one is shown); they are disclosed to advertising partners for advertising purposes.
- We do not collect or process sensitive personal information for purposes that would trigger a right to limit its use.
- We do not discriminate against you for exercising your rights.
- Mexico: you may have rights under applicable Mexican personal-data protection law, including the rights of access, rectification, cancellation, and opposition (ARCO), and any other rights that law provides. Because your App content is stored only on your device, you can cancel or delete it at any time using "Reset All Data" in the App or by uninstalling it. Because we do not hold your App content on our servers, we may be unable to locate a local record that relates to you. Requests concerning advertising data, and concerning Firebase data Google processes on our behalf, should also be directed to Google or made through us. To exercise a right that involves information we control, contact us at the email below.
- Thailand: you may have rights under the Thai Personal Data Protection Act, including to be informed, access, rectify, erase, object, withdraw consent, and data portability, as that law provides. Because your App content is stored only on your device, you can delete it at any time using "Reset All Data" or by uninstalling. Requests concerning advertising data, and concerning Firebase data Google processes on our behalf, should also be directed to Google or made through us. To exercise a right that involves information we control, contact us at the email below.
- Indonesia: you may have rights under Indonesia's personal-data protection law, including to access, rectify, end processing, delete, and withdraw consent, as that law provides. Because your App content is stored only on your device, you can delete it at any time using "Reset All Data" or by uninstalling. Requests concerning advertising data, and concerning Firebase data Google processes on our behalf, should also be directed to Google or made through us. To exercise a right that involves information we control, contact us at the email below.
- Vietnam: you may have rights under Vietnam's personal-data protection rules, including to be informed, consent, access, correct, delete, and object, as those rules provide. Because your App content is stored only on your device, you can delete it at any time using "Reset All Data" or by uninstalling. Requests concerning advertising data, and concerning Firebase data Google processes on our behalf, should also be directed to Google or made through us. To exercise a right that involves information we control, contact us at the email below.
- Other jurisdictions: you may have comparable rights under applicable local law.
To make a request that involves information we control, contact us at yumiao.dev@gmail.com. We may need to verify your request, and we may be unable to fulfil it if we cannot link any data to you. For information held by Apple or Google, please use their respective privacy controls.
13. Children's privacy
The App is intended for adults and is not directed to children under 18. We do not knowingly collect personal information from children. Content entered in the App is stored only on the device and is not transmitted to us. Separately, usage and crash information described in Section 9 is sent to Google Firebase when the App is opened. A parent or guardian can remove local content directly at any time using “Reset All Data” in the App or by uninstalling it. If a child has provided personal information to us directly through a channel we control (for example, by emailing us), contact us at yumiao.dev@gmail.com and we will delete the information we hold. Advertising in the App is not directed to children: the App is not tagged for users under the age of consent, and ad requests are limited to the "G" (general audiences) content rating. We comply with applicable children's-privacy laws, including COPPA (U.S.) and the GDPR's provisions on children where relevant.
14. Security
We use reasonable technical and organizational measures appropriate to the limited data involved. Because your App content stays on your device, its security also depends on your device's own protections (passcode, biometrics, and OS updates). Traffic between the App and third-party services is encrypted in transit. No method of storage or transmission is completely secure.
15. Third-party services and links
The App and this policy may reference third-party services (such as Apple, Google, or external educational resources). We are not responsible for the privacy practices of third parties. Please review their privacy policies. Any lender or financial provider you choose to contact is independent of us and governed by its own policies.
16. Changes to this Privacy Policy
We may update this Privacy Policy from time to time — for example, when we change our advertising partners or introduce new features. When we do, we will revise the “Last updated” and “Effective date” shown at the top of this page, and the current version will always be available at this address and through the link in the App.
We do not send push notifications about policy changes, and we have no way to contact you individually, because we do not collect contact details as a condition of using the App. Please review this page from time to time. Where we consider a change to be material, we may in addition surface a notice inside the App, but you should not rely on receiving one.
Except where a change requires your consent, your continued use of the App after the new effective date means the revised policy applies to you. Consent-based processing is different: we do not treat continued use as consent. Where advertising requires your consent, that consent is obtained only through the consent message described in Section 8, and where a change materially affects what you agreed to, you will be asked again through that same mechanism. Until then, your existing advertising choices remain in effect and can be changed at any time as described in Sections 8b and 12. The UMP message covers advertising only; it does not control Firebase Analytics or Crashlytics.
17. Contact us
If you have questions or requests regarding this Privacy Policy or your information, contact:
LoanGauge is an educational tool only and does not provide financial, legal, or lending advice. Estimates are illustrative and are not offers, approvals, or lending decisions.