Privacy Policy

Effective date: October 13, 2026. This policy covers the DayBloq app for Android (“the app”), the Sloth Club community board at daybloq.com/sloth-club, and the website daybloq.com. “DayBloq”, “we” and “us” mean Nguyen Chau Han, an individual developer based in Vietnam who operates DayBloq. We decide how the data described here is used (we are the “data controller”). Privacy contact: contact@daybloq.com, or the contact form.

What changed on October 13, 2026

What changed on September 29, 2026

The short version

1. Your journal stays on your phone

Your journals, pages, day colors, notes, stickers, templates you have applied, sleep log, dream log, reminders and settings are saved in the app’s own storage on your device. The journal works offline. We do not upload it, we do not keep a copy of it, and we have no way to read it. Nothing from your journal is sent to our servers, to analytics, or to any other company, except the look of a journal you choose to share (section 5).

Because the only copy is on your phone, deleting the app or clearing its storage deletes your journal. If you want to keep it, use Backup first.

2. Backups go to your own Google Drive

Backup is optional and off until you turn it on. When you do, you sign in with Google and allow DayBloq to create files in your Google Drive. DayBloq asks only for the narrowest Drive permission (drive.file), which lets the app see and change only the files it created itself, and nothing else in your Drive.

Google’s handling of your Drive is covered by the Google Privacy Policy. DayBloq’s use of information received from Google APIs follows the Google API Services User Data Policy, including its Limited Use requirements: we use Drive access only to save and restore your backup, and for nothing else.

3. What the app sends, and to whom

The app uses a small number of services to understand how it is used, to know which of our ads brought people in, to run subscriptions, and to download stickers and templates. None of them receive your journal. The data below is tied to random identifiers, not to your name.

ServiceWhat it receivesWhy
Google Analytics for Firebase (Google)Which screens open and which buttons are tapped, including the template name of every page, app version, device model, OS version, language, approximate country or region (from your IP address), an app instance ID, the advertising ID where Android provides it, and each goal you pick when you start, by name, with every event. Never the words, colors or pictures in your journal.To see which features are used and where people get stuck, so we can improve the app.
Firebase Remote Config and Cloud Storage (Google)A Firebase installation ID, app version and IP address when the app fetches settings and downloads stickers, templates and fonts.To deliver app content and settings.
AppsFlyerThe advertising ID, IP address, device model, OS version and install source, plus three events, each sent once per install and never with anything you wrote or colored: finishing the first-run tutorial, coloring on a third page within a day of installing, and journaling on the calendar day after installing. It also receives, through RevenueCat, when you buy, start a trial or subscribe, and the amount.To measure which ad campaigns lead to installs. AppsFlyer passes campaign results to the ad networks we advertise with (currently TikTok) so they can measure and improve those campaigns (section 9).
Google Play BillingYour purchase. Google handles payment; we never see your card or bank details.To sell and renew subscriptions.
RevenueCatAn anonymous app user ID, your purchase and subscription history, the advertising ID, the AppsFlyer ID and the Firebase app instance ID.To check whether you have VIP, restore purchases, and connect purchases to our analytics.

Reminders are scheduled by your phone itself, and nothing is sent from a server to deliver them. DayBloq shows no ads and contains no advertising SDK that shows ads.

Your choices. You can delete or reset your advertising ID in Android settings (Settings > Google > Ads, or Settings > Privacy > Ads on some phones); once it is deleted, the services above cannot use it. You can also write to us to have analytics data about your install deleted.

4. The Sloth Club

The Sloth Club is an optional community board on daybloq.com where people ask for features, show pages and swap tips. Only people signed in with a code from the app can read it. The app shows a sign-in code and a button that opens the board in your browser; nothing on the board is shown inside the app except a count of posts with new comments: your own posts, posts you have commented on, and replies to your comments.

What we store if you use it: a record created the first time you open the Sloth Club screen in the app, holding a random identifier the app generated for your install (we keep only a scrambled form of it and of its secret), a display name picked at random that you can change, whether your subscription is active, your app version and platform, the RevenueCat and Firebase identifiers for your install (so that when you ask for help we can find your install without asking you to prove who you are), which posts you have commented on, when you last opened the board and each post you wrote or commented on, and when someone last replied to your comments (so the app can tell you about new comments, only while that notice is on in the app’s Settings), which posts you voted for, and any reports you send. It holds no email address and no real name unless you type one yourself.

Who can see what you post: posts, comments, pictures you add and your display name are visible to everyone signed in to the Sloth Club, and anyone with the app can sign in. A picture’s address is long and random, so it is hard to guess, but anyone who has it can open that picture. When a post is hidden, its pictures move to a private place and their old addresses stop working. Please do not post personal details.

Pictures are shrunk in your browser before upload, which removes the hidden data inside them, including location. They are stored in Google Cloud Storage and checked by Google Cloud Vision for adult or violent content. Every picture stays private until a person on the DayBloq team has looked at it; only then can other members see it.

Moderation: new posts, comments and reports are emailed to the DayBloq team (sent through our mail provider, Resend) so we can read everything that goes up. The board records your IP address in scrambled form, for a short time, to limit sign-in attempts and spam. Signing in sets one cookie in your browser that keeps you signed in for up to 7 days; it is not used for tracking or advertising.

Reasons and reports: when the team hides or removes a post, or stops an install from signing in, we record which part of the community guidelines it broke, whether we believe it is illegal, and whether an automatic check was involved. The author can read that reason on the post. For a removed post we keep a small note of whose it was, why and when, never what it said, so its address can still tell its author why. The note is kept for at most 12 months, and the button on the delete your data page erases it sooner. Anyone, signed in or not, can report illegal content through the contact form, which asks for the address of the post, the kind of content, and your name and email (you may leave those out when the report is about a child), and sends it to us through Web3Forms. If you give an email address, we confirm by email within a day that we received the report, and later tell you what we decided and how to challenge it.

Keeping and deleting: sign-in codes expire after 12 hours, one-time links after 5 minutes, and spam counters within about two days. Everything else stays until you delete it or we remove it. You can edit or delete any post or comment of yours from its page, and erase everything at once on the delete your data page. If we are keeping a post as evidence of illegal content, we keep it hidden until the authorities no longer need it, even after you delete your data. Deleted pictures can take up to a day to disappear from caches along the way. Reports about a post are deleted with the post. Uninstalling the app throws away its identifier, so a reinstall arrives as a new person; to have an old record removed, write to us.

You must be at least 17 to post, comment or vote on the Sloth Club.

5. Journal links you share

From a journal’s menu in the app you can make a link and a six-character code that let someone else copy the journal’s look into their own DayBloq. Nothing is sent until you tap Create link. The share rules say what a link may carry and what happens when one is reported.

What we store for each link: the code; the journal’s look, made only of things DayBloq itself ships - the cover, which page templates in which order, the color of each label, DayBloq’s own stickers with their position, size, angle and transparency, the number of pages, and a journal name picked from our list; for a gift, a note and the wrapping’s colors, both picked from our lists; the anonymous record of your install described in section 4, with the same details (if you have never opened the Sloth Club, making or opening a link creates it), so that sharing the same journal twice gives the same link and the daily limit on new links works; the app version and when the link was made; and counts, in total and for each month, of how often the link’s page was opened, how often its Google Play button was tapped (on a gift’s page, also its button that opens DayBloq or Google Play), and how many installs came through it, copied the journal and used it in their first day.

What never goes: anything you wrote or typed, including page titles and labels you renamed, your notes, the days you colored in, pictures, and your name. The person who opens the link sees the templates’ own titles and labels, in their language, and nothing that says who made it.

If you open someone else’s link: the app asks our server for that journal’s look. It then tells our server, once each, that it arrived through that link (and whether by the link, by Google Play’s install referrer or by a typed code), that it copied the journal, and that the new journal was used in its first day. These are stored with your install’s anonymous record under that link, so each person counts once.

Who can see a link: anyone who has the link or the code. There is no search and no list of links, and a link’s page is kept out of search engines. The page counts a visit with a small script, without cookies.

Reports: anyone can report a link, from its page or in the app. We store the reason, the time, and either your install’s anonymous record or, on the web, a scrambled form of your IP address, so that one person counts once and the button cannot be abused. A report is kept as long as the link it is about. Reports are emailed to the DayBloq team through Resend. When three different people report the same link, it stops working until we have looked.

Keeping and deleting: a link, a gift included, has no end date: it and its counts stay until you delete your data, we take the link down, or you ask us to remove it. The button on the delete your data page removes every link your install made, which stop working at once, along with the records of links you opened or reported. A journal someone already copied stays on their phone. Uninstalling the app throws away its identifier and leaves your links working; to have them removed, write to us with their codes.

Guess links: from a page’s “…” menu you can make a link that asks your friends to guess the color of your day. For it we store the code; the page’s template and the color of each label, and for each label whether it still has the template’s own name (a label you renamed shows as a color only); and the same install record, app version, time and counts as for a journal link. Each guess stores the color that was picked, a nickname picked from our list, and the time. Nothing about who guessed: we never ask, and the IP address only feeds the scrambled spam counters, which go within about two days. Which color you really colored in never leaves your phone: the app fetches the guesses and compares them there. A guess older than 8 days is deleted the next time the sender’s app checks for new guesses. Turning a link off in the app stops it and deletes its guesses at once, and the button on the delete your data page removes your guess links with everything under them.

Creator pages: when someone who makes videos about DayBloq agrees with us to have a page of their own, we copy one of their journal links under a new code and show it at daybloq.com/c/ with a name, a short line about them, a link to their own page and, when we paid them or sent them something, a “Paid partnership” mark, all of which they agreed to and we typed in; nothing on it comes from the app. It stores the same things and counts as any journal link, so we can tell them each month how many people their page brought; the counts say nothing about who. The page and its link come down when they ask, when they delete their data as above, or when we take it down.

6. This website

Please do not put journal contents into the contact form if you want them to stay only on your phone.

7. How long we keep data

8. Why we may use this data (legal bases)

Where laws such as the GDPR apply, we rely on:

9. Selling and sharing

We do not sell personal data. The app does share some data for advertising: it gives AppsFlyer the advertising ID and the three install events described in section 3, and AppsFlyer passes campaign results to the ad networks we advertise with (currently TikTok), so they can measure and improve our campaigns. Those results include purchases, trial starts and subscriptions, with their value. Some laws, such as California’s, call this “sharing” for advertising. You can stop it by deleting your advertising ID (section 3).

Apart from that, we share data only with the service providers listed above, who process it for us, and with authorities when the law requires it.

10. Security

Everything the app and the website send travels encrypted (HTTPS). Data we hold for the Sloth Club and for journal links is stored with Google Cloud, encrypted at rest, and only the DayBloq team can reach it. Your journal is protected by your phone’s own lock, and your backup by your Google account.

11. Where data is processed

Our service providers may process data in the United States and other countries. Where the law requires it, transfers are covered by safeguards such as the European Commission’s Standard Contractual Clauses, which these providers offer.

12. Your rights

Wherever you live, you can ask us to tell you what data we hold about you, correct it, delete it, give you a copy, or stop using it. Most of it you can handle yourself: your journal and backups are already in your hands, and the delete your data page covers the rest. For anything else, write to contact@daybloq.com; we answer within 30 days. You may also complain to your local data protection authority.

13. Children

DayBloq is for people 13 and over. People under 18, or under the age of majority where they live, need the permission of a parent or legal guardian, as the Terms say, and some features may be switched off for them. Posting, commenting and voting on the Sloth Club are for people 17 and over. DayBloq is not directed at children under 13, and we do not knowingly collect personal data from anyone under 13. If you believe a child under 13 has given us personal data, write to us and we will delete it.

14. Changes to this policy

If what the app or the website collects changes, this page changes with it, and the effective date at the top moves. For significant changes we will also say so in the app or on this site before they take effect.

15. Contact

contact@daybloq.com, or the contact form. See also the Terms of Service and the Sloth Club community guidelines, and the share rules for journal links.