How was today?

Privacy Policy

Effective 19 September 2026 · Last updated 26 September 2026

The English version, and the fallback for every region without its own. The app is not offered in the EU or EEA, so this is not a GDPR document. Also available in 한국어 and 日本語 and 繁體中文.

How was today? collects nothing. There is no server, there is no account, and the developer cannot read what you write.

1. Who is responsible

How was today? is made and operated by Daehyeon Kim, an individual developer.

For anything about privacy, write to kdhmonkeyd@gmail.com. You will get an answer as soon as it is read.

2. What we collect

We collect nothing. There is no account, no login, and no server operated by the developer. None of the following is ever received, stored or transmitted to us:

No analytics SDK (Google Analytics, Firebase or similar), no advertising SDK and no crash reporter is bundled with the app. Not one third-party SDK is included.

What you create — your one-line answers, an optional mood and weather, and the date — is yours. It lives on your device and, if you turn it on, in your own iCloud. The developer has no copy and no way to get one.

3. Where your data lives

WhatWhereWho can read it
Answers, mood, weather, datesYour device, and your own iCloud if enabledOnly you
App settings (notification time, lock)Your deviceOnly you
Diagnostic logYour device onlyOnly you (Settings → Recent logs)
Device or advertising identifiersNot collected—

iCloud sync uses Apple's CloudKit private database, which belongs to your Apple Account. The developer has no access to it. Turn iCloud off and the app still works; your entries then stay on the device alone.

4. When the app uses the internet

The app makes no network requests of its own. There is no networking code in it and no developer server to talk to.

Two things use the network, and Apple handles both:

Tapping the Terms of Use link on the purchase screen opens Apple's page in Safari. That is the same as typing the address into a browser; the app sends nothing.

5. Artificial intelligence

This app has no artificial intelligence features. Nothing you write is sent to a language model, on-device or otherwise.

6. Device permissions

PermissionWhyWhen asked
NotificationsTo send the daily question. These are local notifications scheduled on your device, not push messages from a serverLast screen of onboarding
Face ID / passcode (optional)To confirm it is you when App Lock is onWhen you turn App Lock on

Face ID returns only success or failure to the app. The biometric data itself stays with iOS and never reaches the app.

Declining a permission leaves the rest of the app working, and you can withdraw it at any time in iOS Settings. Location, contacts, photos, calendar, microphone and camera are never requested.

7. Payments

Purchases are handled by Apple's App Store. The developer never receives, sees or stores card numbers or payment details. All Apple reports back is whether this device has an active subscription.

Cancellations and refunds follow Apple's policy. You can cancel in Settings → Apple Account → Subscriptions.

8. Who else receives data

Nobody. We hold no personal data to pass on, and nothing is ever sold or shared.

The app does rely on Apple services, and those are a relationship between you and Apple:

ServiceUsed forTheir policy
iCloud (CloudKit)Sync between your devices, in your Apple AccountApple Privacy Policy
App StoreSubscription billingApple Privacy Policy

If law enforcement asked, there would be nothing to hand over. Your entries are on your device and in your Apple Account.

9. How long data is kept

The developer keeps nothing, so no retention period applies on our side.

What you create stays on your device and in your iCloud until you delete it:

You do not need to ask the developer to delete anything; there is no copy to delete.

10. Security

11. Children

How was today? is not directed to children under 13, and the developer knowingly collects no personal information from anyone, of any age. Because nothing is transmitted to or stored by the developer, there is no parental consent mechanism to operate under the US Children's Online Privacy Protection Act (COPPA).

If you believe a child has somehow provided personal information, write to kdhmonkeyd@gmail.com and it will be looked into.

12. California privacy rights

Under the California Consumer Privacy Act as amended by the CPRA, California residents may know, delete, correct, and opt out of the sale or sharing of their personal information.

The developer collects no personal information, sells none, and shares none — including for cross-context behavioural advertising. No category of personal information was collected in the preceding twelve months, so there is nothing to disclose, delete, or opt out of. No sensitive personal information is collected either.

You will never be treated differently for exercising these rights, and no financial incentive is offered in exchange for personal information. To ask anything, write to kdhmonkeyd@gmail.com.

13. For users in Japan

Under Japan's Act on the Protection of Personal Information (APPI), a business must disclose the purpose of use of personal information it handles, obtain consent before providing it to third parties, and respond to requests about retained personal data.

The developer handles no personal information. Nothing you write leaves your device for the developer, so there is no purpose of use to disclose, no third-party provision to consent to, and no retained personal data to disclose, correct, or delete. Requests can still be sent to kdhmonkeyd@gmail.com.

14. For users in the United Kingdom

Under the UK GDPR and the Data Protection Act 2018, you have the rights of access, rectification, erasure, restriction, portability, and objection, and the right to complain to the Information Commissioner's Office.

The developer is neither a controller nor a processor of your entries. What you write stays on your device and, if you leave iCloud on, in your own iCloud account, where Apple acts for you under your own agreement with Apple. There is no transfer of your entries to the developer and no international transfer by the developer, so there is nothing here for us to access, rectify, erase, restrict, port, or object to. You can read, export, and delete everything yourself inside the app. Questions are welcome at kdhmonkeyd@gmail.com.

15. For users elsewhere

Similar rights exist under Canada's PIPEDA, Brazil's LGPD, Australia's Privacy Act, India's DPDP Act, and comparable laws. The answer is the same in every case, because it follows from how the app is built rather than from where you live: the developer holds none of your data. There is no server, no analytics, and no account with us.

The two rights that matter in practice — getting your data out, and deleting it — are in the app itself, and they work without asking anyone. Settings → Export entries writes everything to a plain text file. Deleting an entry, or deleting the app and turning off iCloud for it, removes it.

16. Where this app is available

The app is not offered in the European Union or the European Economic Area, in Switzerland, or on the China mainland App Store. If you are in one of those places, it should not appear on your App Store.

The United Kingdom is served. The UK is in neither the EU nor the EEA; section 14 sets out what UK GDPR means here, which in practice is that we hold nothing of yours.

17. Changes to this policy

If this policy changes, the effective date at the top changes with it and the change is noted in the app's release notes.

If an analytics tool, a crash reporter, or any server feature is ever added, this policy is updated first and states plainly what goes where.

18. Contact

DeveloperDaehyeon Kim
AppHow was today?
Emailkdhmonkeyd@gmail.com