FinanceScanner

Ad and privacy choices

Google's regional consent messages control advertising choices; FinanceScanner never sends calculator values, identity fields or local search text to ad code.

Google advertising choices

On supported regional visits, Google's certified consent message provides accept, reject and manage choices. A US state privacy message is also active. Google may still use limited data for security, fraud prevention and limited advertising where permitted.

You can also review or change personalization at Google ad settings. Browser cookie controls can remove stored identifiers, but may also reset a previous choice.

FinanceScanner's educational content and local calculators remain available without consenting to personalized advertising. Never enter identity, account or payment information into a calculator or search field.

These settings control FinanceScanner learning suggestions. Google advertising choices use Google's separate consent controls. This setting does not authorize advertising personalization, partner transfer or notifications.

Withdrawal is immediate. Turning this purpose off stops new personalized learning suggestions while keeping essential education and calculators available.

Google ad and privacy choices

trust · human review pending

Local-first privacy

Calculator inputs remain in page memory unless the user explicitly exports or later chooses an enabled account save.

My saved work

Safe next action: Keep identity, account and payment details out of every input. Open related page

Audience, steps, example, risks and evidence

Understand the reasoning

Learning examples should use invented numbers and avoid names or account identifiers. Local calculations and optional account saves have different data paths; inspect the active save choice instead of assuming everything stays on-device.

Worked learning example

Reading an example requires no bank account number. Choosing an explicitly enabled cloud save is a separate action from changing a calculator input.

Check your understanding

Does local-first mean every optional feature is guaranteed to remain offline?

Show answer and explanation

No. Account saves can use a server when enabled and deliberately chosen; read the active data notice.

Common mistake: Do not put passwords, identity documents or raw bank statements into calculation labels or search text.

Examples are invented educational scenarios, not provider quotes, forecasts or tax rates.

Who this is for

People using the KR educational release who want to understand a money decision before contacting a provider.

Not for

This is not a personal recommendation, provider quote, eligibility decision, tax opinion or legal opinion.

Key concepts

  • Local-first privacy
  • assumptions
  • limits

Steps

  1. Write down the values you know.
  2. Run the matching local calculator.
  3. Read the assumptions, limits and next action before deciding.

Worked example

Reading an example requires no bank account number. Choosing an explicitly enabled cloud save is a separate action from changing a calculator input.

Risks and limits

  • Do not put passwords, identity documents or raw bank statements into calculation labels or search text.
  • Actual provider terms and future outcomes can differ.
  • A missing fee, tax or timing assumption can materially change the result.

Scope: Initial educational scope: Republic of Korea (KR), KRW and English interface. Provider, tax and legal rules are not inferred.

Author: FinanceScanner educational content
Review: Automated structure checks only. Human financial and language review not completed. Listed sources are background references, not claim-by-claim approval.
Next review: 2027-02-28

Background sources — not claim-by-claim verification

Report a stale source or content error

trust · human review pending

Export and deletion control

A user-directed export creates a copy controlled by the user; local held data can be forgotten without contacting a provider.

My saved work

Safe next action: Delete held scenarios and exported files from the device when no longer needed. Open related page

Audience, steps, example, risks and evidence

Understand the reasoning

Export creates another copy with its own lifetime. Forgetting an in-app scenario, deleting an account record and deleting a downloaded file are separate operations and should be verified separately.

Worked learning example

A fictional scenario is exported to JSON and then removed from the app. The downloaded JSON still exists until it is deleted from the device or its backup location.

Check your understanding

Does removing the in-app record erase the exported file?

Show answer and explanation

No. The user controls that separate file and any copies made from it.

Common mistake: A local delete action must not be described as erasing every cloud or downloaded copy.

Examples are invented educational scenarios, not provider quotes, forecasts or tax rates.

Who this is for

People using the KR educational release who want to understand a money decision before contacting a provider.

Not for

This is not a personal recommendation, provider quote, eligibility decision, tax opinion or legal opinion.

Key concepts

  • Export and deletion control
  • assumptions
  • limits

Steps

  1. Write down the values you know.
  2. Run the matching local calculator.
  3. Read the assumptions, limits and next action before deciding.

Worked example

A fictional scenario is exported to JSON and then removed from the app. The downloaded JSON still exists until it is deleted from the device or its backup location.

Risks and limits

  • A local delete action must not be described as erasing every cloud or downloaded copy.
  • Actual provider terms and future outcomes can differ.
  • A missing fee, tax or timing assumption can materially change the result.

Scope: Initial educational scope: Republic of Korea (KR), KRW and English interface. Provider, tax and legal rules are not inferred.

Author: FinanceScanner educational content
Review: Automated structure checks only. Human financial and language review not completed. Listed sources are background references, not claim-by-claim approval.
Next review: 2027-02-28

Background sources — not claim-by-claim verification

Report a stale source or content error

Search all 246 items