Analytics, Privacy, and Transparency

Several people asked about analytics in HandsOnMoney, which is important topic especially for a finance app.

With the latest release, HandsOnMoney includes an Analytics Opt-Out setting and the ability to request data deletion. I also wanted to clearly explain:

• why analytics exists
• what is collected
• what is not collected
• whether data is sold
• how to disable analytics completely

Short version

HandsOnMoney uses lightweight analytics to improve the product.

It does not send your transactions, balances, account names, receipts, imported files, or other financial records to analytics.

I do not sell user data.

You can now disable analytics anytime in:

Settings → Privacy

Why analytics exists

I use analytics for two practical reasons:

1. To understand where users get stuck

For example:

• onboarding drop-offs
• confusing screens
• buttons people tap but abandon
• sync flows that fail too often

This helps me improve the product based on real usage instead of guessing.

2. To measure whether HandsOnMoney is becoming useful

I look at retention metrics such as whether users continue using the app after days or weeks.

That helps answer an important question:

Is HandsOnMoney creating enough value for people to come back?

My principles

Collect as little as possible

I only want enough data to improve the app.

Never collect financial content for analytics

Your books and financial records should stay your business.

Give users control

If you do not want analytics enabled, you can turn it off.

Build trust long term

Trust matters more than short-term metrics.

What is collected

Typical analytics events are things like:

• screen opened
• button tapped
• sync completed
• sync failed
• app error occurred

This helps me understand what works and what needs fixing.

What is NOT collected

HandsOnMoney analytics does not include:

• transaction amounts
• payees
• memos
• balances
• budgets
• account names

That information is not useful for improving flows or onboarding, so it is intentionally not included.

Do I sell data?

No.

HandsOnMoney is not an advertising business, and I do not sell user data.

I also intentionally limit what analytics contains.

That means I do not collect the kinds of rich personal or financial datasets that are commonly valuable to advertisers, brokers, or data resellers.

In simple terms:

I cannot sell what I chose not to collect.

What about technical metadata?

Like many analytics systems, some technical device information may be included automatically to help diagnose compatibility issues, such as:

• app version
• iOS version
• device type
• general region / country
• language / locale

I actively minimize or disable fields that feel excessive or unnecessary.

My litmus test

Before adding any analytics event, I ask:

If this data were exposed tomorrow, could it reveal someone's finances or meaningfully compromise their privacy?

If the answer is yes, it should not be logged.

Analytics Opt-Out

If you prefer no analytics at all, you can disable it anytime:

Settings → Privacy

That setting is there because reasonable people can disagree about analytics, and users should have control.

Technical appendix

For users who want deeper transparency, I will also publish technical blogs covering:

• analytics events currently sent
• SDK configuration choices
• fields intentionally disabled
• examples of tracked events
• privacy safeguards in error logging

Final note

HandsOnMoney is a small independent project.

My goal is to build a sustainable product people trust. Not to extract value from their personal data.

I'm trying to find the right balance between understanding what works, what doesn't, and respecting your privacy.

If any part feels excessive, or if you think something could be used against users, please let me know.

Thank you to everyone who raised these questions. They directly shaped this release.