Privacy Policy

The short version

Most of my apps keep everything on your device and never ask who you are. Some need an account, or have to send something out to be processed, and this page says exactly what each of those involves. Wherever data does leave your device, it goes for one stated job and is used for that job only. I don't build profiles of anyone, I don't sell what you create, and no app of mine follows you into another one.

What stays on your device

Whatever you make in an app — documents, entries, calculations, settings, history — is written to your device's own storage and protected by the same passcode, encryption and biometrics that protect everything else on it. That copy is the one that counts, I cannot read it, and nothing about it travels anywhere on its own.

Deleting the app removes that data with it. The one exception is a backup you turned on yourself: if iCloud or Google backup includes the app, a copy sits in your own Apple or Google account, under their terms rather than mine.

What the apps fetch

Some apps reach the network to pull something down — reference data, templates, exchange rates, content updates, or an ad. Those requests only ask for something; they carry what the request itself needs and nothing more, and never your account details.

When something has to be sent out to be processed

A few features cannot run on the phone alone: the work takes more than the device can do, or it needs a service that only exists online. Where that is the case, the app sends what that particular job needs, and it is clear that this is what the feature does before you use it.

What happens on the other end is narrow, and it is meant to be the whole of what happens. Your data is used to produce the result you asked for, the result comes back, and the copy is discarded once it has served that purpose. The contents are not read or used for anything besides the job you asked for, and they are not sold or handed to anyone to use for their own ends. It travels over an encrypted connection.

Some of that work runs on infrastructure I rent rather than own. A provider used this way acts on my instructions and is held to the limits above: it may use what passes through only to perform the job, may not keep it afterwards, and may not use it to train anything. It may sit in another country, which is what makes an online feature possible at all.

Where a feature has to keep something for longer — because holding it is the point of the feature — three things follow. What is kept stays yours. The app names what it keeps and why at the point it asks you for it, rather than leaving you to find out here. And for as long as it is held, it sits behind access controls and security measures appropriate to it, and you can have it deleted.

Apps with an account

Where an app offers a sign-in, the account exists for one reason: to carry your data with you from one device to the next. Only what that requires is stored — the email or sign-in identifier the account is keyed to, the content you chose to sync, and the timestamps that decide which copy is the newer one. The synced content is kept while the account exists; when you delete the account the live copy goes with it, and whatever remains in routine backups ages out as those backups rotate.

An account does not carry your contacts, your location history or your address book, it is not used to build an advertising profile, and it is not shared with anyone else.

An app that lets you create an account also lets you delete it from inside the app. If you can't find the option, or you no longer have the app installed, write to admin@tuanem.com from the address the account uses — or naming it — and I'll delete the account and its synced data and confirm when it is done.

Advertising

Free apps may show ads, which is what pays for them. The ads are served by third-party ad networks that operate independently of me and under their own privacy policies. What such a network receives is the device's advertising identifier and coarse technical context — device model, operating system, language, country, and which app is showing the ad — and it uses that to choose an ad, count it, and detect fraud.

You control that identifier from system settings rather than from the app. On iOS, the app must ask before it can use the identifier for tracking, and Privacy & Security holds the switch that turns the request off for every app at once. On Android, the ad ID can be reset or deleted outright under Settings, in the ads section of privacy.

Nothing you create, and no account detail, is passed to an advertiser. Beyond these networks and the platform's own reporting described below, my apps carry no library whose job is to follow you from one app or website to another.

Some privacy laws, California's among them, treat serving a personalised ad as sharing data even where no money changes hands for it. Turning off the identifier as described above is what stops it, and an app that shows ads keeps working with it off — the ads it shows are simply untargeted.

Crash reports

Apple and Google pass developers crash reports and install statistics for apps on their stores, and you appear in those only if you agreed to share diagnostics with developers in your system settings. What arrives is a crash trace or an aggregate count, not a name, a message or a file. Where an app carries a crash reporter of its own as well, it is there for the same narrow purpose — to show me what broke, so it can be fixed.

Permissions

An app asks for a permission at the moment a feature needs it and explains what it is for. Declining leaves the rest of the app working. Anything you grant is used for the feature that asked and nothing else — the camera for a scan, photos for the image you picked, notifications for the reminder you set — and you can withdraw any of it at any time in system settings.

Children

My apps are built for a general audience rather than for children, and I don't knowingly collect anything from a child under 13, or under the higher age your country sets. If you believe a child created an account in one of my apps, write to me and I'll delete it.

Who is responsible for this

Every app here is mine — the work of one independent developer in Vietnam. I decide what these apps do with your data and I answer for it, which in the language of data protection law makes me the controller for everything described on this page. You can reach me at admin@tuanem.com, and that address is the way to reach me about any of it.

A store listing can show a different developer name from one store to the next, so a name is not what decides whether this policy applies. What decides it is whether the app is mine — the ones this site links to are, and if you are unsure about an app that claims to be, ask me at the address above.

What entitles me to handle your data at all is narrow. An app processes what it must in order to deliver the feature you asked it for; anything beyond that — a permission, an account, a personalised ad — is asked for first and works only while you allow it. Withdrawing permission is always available and never retroactive: it stops what comes next rather than undoing what you already asked for.

Your rights

You can ask for a copy of what an app holds about you, ask for it to be corrected, ask for it to be deleted, withdraw a permission you gave earlier, or object to a particular use. Write to admin@tuanem.com, say which app you mean, and include the address any account uses so I can find it. I answer as fast as I can and within a month at the outside, and I don't charge for it.

If you think I have handled your data badly, tell me first — it is usually a misunderstanding I can fix the same day. You are also entitled to complain to the data-protection authority for the country you live in, without going through me at all.

Changes

When this policy changes, I update this page and the date below. If a change alters what an app does with your data rather than how the policy is worded, the app says so before the change takes effect.