Money Visualiser app privacy policy

Who is responsible

The Money Visualiser app for iPhone and Android (com.moneyvisualiser.app) is published by Rising Throne, the studio behind therisingthrone.com. Rising Throne decides why and how the data described here is used. Write to contact@therisingthrone.com with any question about your data, including a request to see, correct or delete it.

This policy covers the app. The Money Visualiser website and therisingthrone.com have their own notices; ours is the Rising Throne privacy notice.

In short

You do not need an account, and the app does not ask for your name or location. An e-mail address is optional, and only if you send a problem report.
Anonymous usage counts and crash reports are on by default. One switch in Settings turns them off.
The app shows ads from Google AdMob. Where Google’s consent form applies, it asks you first, and on iPhone Apple’s tracking prompt decides whether ads are personalised.
The amount you type and the scenes you build stay on your device. Usage counts carry only a size band, for example 1,000 to 10,000 US dollars.

What the app collects

Usage counts and crash reports

While the switch described below is on, the app sends usage counts and crash reports to Google’s Firebase Analytics and Firebase Crashlytics. A usage count says that something happened, not what you typed:

when the app opens, and which screen you are on, named after the app’s own screens such as home or settings;
when you finish setup (the currency and units you picked) and when you finish or skip the tutorial;
when a scene is built or fails to load: the kind of asset (fiat, crypto or metal), the amount as a size band in US dollars, the environment and display surface, single or compare mode, and how many milliseconds the scene took to appear;
when you compare two assets (which kinds), share or save an image, copy a link, or open a link into the app;
when rates fail to load, when the app asks you to review it in the store, and when an ad has been shown;
when you switch sharing back on.

A crash report holds the error, the state of the app and basic device details at the moment it failed. We keep amounts out of it.

Firebase also records some technical details by itself: the app version, device model, operating system and its version, language, a random Firebase installation identifier, and an approximate region that Google works out from your connection. Google states that Google Analytics 4 does not log or store IP addresses.

The app can also send the same usage counts to Money Visualiser’s own server, api.moneyvisualiser.com, with a second random install ID, the app version and the platform, so that we can count usage ourselves.

Advertising

The app shows banner, native and full-screen ads served by Google AdMob. To show an ad, AdMob receives your device’s advertising identifier (the IDFA on iPhone, the Advertising ID on Android), your IP address and details about the request and the ad.

Where Google’s consent form applies, for example in the European Economic Area, the United Kingdom and Switzerland, it appears when you first open the app. You can open it again under Settings, Privacy, Manage ad choices. Without your consent, the app asks for non-personalised ads only.
On iPhone, the app also shows Apple’s tracking prompt with this text: “Money Visualiser uses this permission to show more relevant ads and help keep the app free.” If you decline, the app asks for non-personalised ads only.
On Android outside those regions, ads can be personalised. You can reset or delete your advertising ID, or opt out of ad personalisation, in your phone’s privacy settings.

The usage switch does not control ads. Google handles advertising data under its own privacy policy, linked below.

Reports you send us

Settings, Help, Report a problem sends the category you pick, your description, your e-mail address if you add one, the app version and platform, and the app’s random install ID. A screenshot goes along only if you switch on Attach a screenshot, which the app warns may show your amounts. This does not depend on the usage switch, because you press Send. If our server cannot be reached, the app opens your e-mail app with the report instead.

When you write to us by e-mail, we receive your address and message, and we keep them to answer you.

Connections the app makes

To work, the app asks our servers for exchange rates and prices (api.valuethen.com and api.moneyvisualiser.com) and for 3D scene files (assets.moneyvisualiser.com). Some cryptocurrency logos come from cdn.jsdelivr.net, a public content delivery network. These requests carry no account or advertising identifier of yours, but like any internet request they reach the server together with your IP address. Our servers are hosted by Cloudflare, which processes IP addresses to deliver the response and to protect the service from abuse.

What stays on your device

Your settings, saved scenes, cached rates and downloaded scene files are stored on your device. When you tap Save to Photos, the app adds the picture to your photo library; it asks for permission to add only, not to read your photos. When you share, the app you choose receives the image. The app does not use your contacts, camera, microphone or location.

The switch in the app

Open Settings, then Privacy. The row reads:

Share anonymous usage analytics

Helps improve the app. No personal data.

In Turkish the app shows:

Anonim kullanım analizlerini paylaş

Uygulamayı geliştirmeye yardımcı olur. Kişisel veri toplanmaz.

The switch is on by default. Turning it off:

stops Firebase Analytics and Crashlytics collection on your device, so no more usage counts or crash reports are sent;
stops sending to our own server and deletes the events still waiting on your device;
deletes the app’s install ID and resets the Firebase identifier on your device.

Turning it on again starts with new identifiers, so nothing ties the new data to the old.

“No personal data” is the app’s short wording: we collect no name, e-mail address, account or precise location. Under data protection law the random identifiers above can still count as personal data, so we treat them that way and honour the rights described below.

Why we may use your data

Usage counts and crash reports: our legitimate interest in keeping the app working and improving it (Article 6(1)(f) of the GDPR; Article 5(2)(f) of Turkish Law No. 6698, KVKK). This is why the switch starts on, and why you can object at any time by turning it off.
Advertising identifiers and personalised ads: your consent, given in Google’s consent form or in Apple’s tracking prompt. You can withdraw it in the app’s Settings or in your phone’s settings.
Reports and e-mails you send us: our legitimate interest in answering you and fixing the problem you describe.

Google as our processor

Firebase Analytics and Crashlytics are Google services. For them, Google processes data on our behalf under the Firebase Data Processing and Security Terms. Advertising through AdMob is handled by Google under its own privacy policy. Google’s documents:

How long data is kept

Crash reports: Google’s Firebase documentation says Crashlytics keeps crash stack traces and the identifiers that go with them for 90 days.
Usage counts in Google Analytics: event-level data is kept for 14 months, the longest period Google Analytics allows, and is then deleted. Standard aggregated reports are not affected by that setting.
Reports and e-mails you send us: until we no longer need them to answer you and fix the problem, and then we delete them.
Data on your device: until you clear it or remove the app.

Children

The app does not ask for your age and has no accounts. It is not set up differently for younger users: the collection described here applies to everyone who uses it. If a parent or guardian wants data deleted, use the steps on the delete data page or write to us.

Transfers outside your country

Google processes data in several countries, including the United States. Its Firebase privacy page states that Google complies with the EU-U.S. and Swiss-U.S. Data Privacy Frameworks and the UK Extension. Our own servers run on Cloudflare’s global network. If you live in Türkiye, article 9 of KVKK governs transfers abroad; write to us if you want to know how it applies here.

Your rights

Depending on where you live, you can ask us for access to the data we hold about you, for its correction or deletion, to restrict how we use it, or to object to it. You can withdraw consent you gave for ads at any time. Under the GDPR you can also ask for the data you provided in a usable format. In Türkiye, article 11 of KVKK gives you the matching rights, including learning whether your data is processed, why, and who receives it.

We can only find data we can tie to you. Usage and crash data is linked to a random identifier on your device, not to your name, so we cannot look it up from your name or e-mail address. Turning the switch off, which resets the identifiers, is the most reliable way to cut the link. Messages and problem reports you sent us we can find from the e-mail address you used and roughly when you wrote.

Write to contact@therisingthrone.com and tell us which app and phone you use. We answer within 30 days. You can also complain to the data protection authority where you live; in Türkiye that is the Personal Data Protection Authority (Kişisel Verileri Koruma Kurumu, kvkk.gov.tr).

Contact

contact@therisingthrone.com. The support page lists the other ways to reach us, and the delete data page has the steps for removing data.

Changes

When this policy changes, the date above changes with it.