ß
DailyByte
Something not working, or a question the app doesn't answer? Write to me directly — DailyByte is made by one person, and that person reads every message.
Get in touch
Expect a reply within a couple of days. Including your problem and what you were doing when something went wrong makes it much faster to sort out.
First check that notifications are allowed: iOS Settings → DailyByte → Notifications. If permission was declined when you first set up, iOS won't ask again, so it has to be switched on there.
Your bytes are still being generated either way — open the app and they'll be waiting on the Home and History tabs.
Open Settings in the app. You can change your topic, how many bytes you get each day, and the time each one arrives. Changes take effect from your next delivery, and your existing history stays where it is.
No — three is the deliberate maximum. The app is built around a small daily amount rather than a feed, and raising the ceiling would undo the thing that makes it work.
Bytes are generated by AI and aren't reviewed by a person before they reach you, so mistakes are possible. Every byte carries a link to read further and check it yourself. If you spot something clearly wrong, send it over — it helps improve how bytes are written.
Bytes are for curiosity, not for medical, legal or financial decisions.
In the app: Settings → Delete account. It's immediate and permanent, and removes:
Nothing is kept afterwards, so there's no way to restore it. You're welcome to sign up again, but you'd be starting from scratch.
If you signed up with an email address, use Forgot password on the sign-in screen to reset it. If you used Sign in with Apple or Google, use that same button — an account created that way has no password of its own.
Still stuck? Email me with the address you signed up with and I'll look into it.
Check your spam folder first. Codes can take a minute or two. If nothing arrives, tap Resend code, and get in touch if it still doesn't show up.
They stay in your History. Switching topic only changes what gets generated from that point on.
Bug reports are genuinely welcome. The most useful ones say what you expected, what happened instead, and roughly when — that's usually enough to track it down.