जानें कि क्या सार्वजनिक होता है।

Who we are

The Daystreak community is run by Thinksview, Level 6, Menara Genesis, No. 33, Jalan Sultan Ismail, Bukit Bintang, Kuala Lumpur, Malaysia. Thinksview is the controller of the personal data described here. For privacy questions and requests, appeals and takedown notices, email [email protected].

This notice covers the optional community in Daystreak and Daystreak Countdown and on daystreak.net. Everything else the apps do is covered by their own privacy policies: Daystreak and Daystreak Countdown. A Bahasa Melayu version is available: Notis Privasi (BM).

What the community is

The community is optional. Your records stay on your device and never need an account, and our community server never receives a record you have not chosen to share.

You can share a record as a public card, share selected Memoryline stories, keep a public profile and send encouragement. Taking part is for adults aged 18 and over. Anyone can read reviewed public content without an account.

The community is not available in mainland China and, for now, in the European Economic Area, Switzerland, the United Kingdom and the nearby territories that follow their data protection rules. We decide this from the country of the network each request comes from and, in the apps, from your App Store or Google Play country. To learn where the community is offered, the app asks our server once after it is installed and, where the community is not offered for your App Store or Google Play country, at most once a day after that; this request carries no account or device identifier, only what every internet request carries, such as your IP address. Making items private, exporting and deleting work everywhere.

Taking part is voluntary. If you don’t sign in, every private feature keeps working; you just can’t share or encourage.

What we collect

• (a) Sign-in. You sign in with Google or Apple through Google Firebase Authentication. Firebase stores your email address (including an Apple “Hide My Email” relay address), name and profile photo URL, in the United States. Daystreak and Daystreak Countdown each use their own Firebase project; daystreak.net uses the Daystreak one.
• (b) Account. Our server stores a keyed hash of your Google or Apple account ID (not your email address or name); your Firebase user IDs, kept only so we can delete them; the country of your network when you joined, the date you joined and the version of the terms you accepted; and records of your consents.
• (c) Devices. For each signed-in device: its platform, a label, and when it was added and last seen. Labels are coarse: “iPhone · Daystreak” on iOS, the model such as “Pixel 9a” on Android, and the browser and system such as “Chrome · macOS” on the web.
• (d) What you share. For each shared card: its title and description, the number and its dates, the last check-in date, paused state, colours and icon, an optional background photo, your time zone and the day it last changed. Shared Memoryline stories contain the notes, dates and photos you selected. Photos are reviewed, resized to at most 1600 px and stripped of metadata such as location.
• (e) Public profile. A random public author ID and either an anonymous name and avatar or, after review, a custom name and avatar. If you choose your Google photo, we copy it once (256×256, no metadata).
• (f) Encouragement and follows. Who encouraged which card or story, with which phrase and on which day; whether you have read or hidden it; the authors you block; which public cards you follow and since which day; who follows your cards (shown only to you); and the check-in alerts and evening reminders we send to followers.
• (g) Notifications (apps only, if you turn them on). Your device’s notification token, app language and time zone. The lock-screen title is hidden by default.
• (h) Safety and technical data. Reports and their details; moderation decisions; your network (IP) address, which we use to check your region, and a keyed hash of it for rate limits and to de-duplicate anonymous reports; and service logs.

This data comes from you, from your device and from Google or Apple when you sign in.

What is public, and how it links

A shared card shows its title and description; the number and its dates, the last check-in date and whether it is paused; its colours and icon; the background photo if you chose one; your time zone as a UTC offset only, such as GMT+8 (we store the full zone to count days correctly); the day it last changed; and your public profile.

It is a live card: numbers, dates, pauses, colour and icon update automatically from your record. Title, description and photo changes are reviewed first, and the approved version stays visible meanwhile. A new number, check-in or pause reaches others at the next half hour, so they cannot see the exact time you checked in. If you share a card’s link, chat apps may show a preview (title, number, check-in status and photo) and keep it after you make the card private.

One pseudonymous public author ID links all your cards, stories and encouragement across both apps and the website, so others can tell they come from the same person.

Encouragement is public, including who sent it and the day it was sent.

Others can follow your public card. Followers get one notification when your check-in appears publicly (at the next half hour, never the exact time). Only you see who follows your cards: you can remove a follower, block them, or turn check-in alerts off for a card. Followers who turn on evening reminders may also get one notification in your evening (8 to 11 pm in your time zone, which we read from the time zone your app reports) when your streak would break that day; turning check-in alerts off for a card stops these too. Making a card private ends its follows.

Anyone can see public content and save copies of it. Community pages are not offered to search engines.

Why we use it (legal bases)

• To provide the community you ask for (contract): your account and sign-in, sessions on your devices, delivering notifications you turned on, and exporting or deleting your data.
• Your consent: publishing each card or story, its background photo, a custom name, your Google photo and notifications. You can withdraw consent at any time by making an item private, changing your profile or turning notifications off. This does not affect what happened before.
• Our legitimate interests: keeping the service secure, rate limits, reviewing content and keeping moderation records, region checks, and keeping consent and deletion records to show what you agreed to and that we honoured deletions.
• Legal obligations: answering lawful requests and keeping records the law requires.

We do not sell your data, use it for advertising or profiling, or use it to train AI models.

Sensitive topics

The community does not accept records about health, treatment, addiction, sex life, religion or other sensitive personal topics (see the community guidelines). Please don’t share them; reviewers reject them. A neutral title can still reveal sensitive details.

Who receives it

• Cloudflare runs the community server (Workers), its database (D1) and media storage (R2), processes images and keeps service logs.
• Google provides Firebase Authentication and, for notifications, Firebase Cloud Messaging.
• Apple provides Sign in with Apple and, on iOS, the Apple Push Notification service.
• Other people see what you make public.
• Authorities, when the law requires us to disclose data in response to a valid request.

Our service providers process data only on our instructions.

Where it is stored

The community database and media are stored in the European Union; images are processed transiently. Cloudflare runs the service at the location nearest to you, and its service logs are global; logs are kept for up to 7 days. Firebase Authentication stores sign-in data in the United States. Notifications pass through Google and, on iOS, Apple.

Where data leaves the EU, the UK or your country, we rely on the EU-US Data Privacy Framework (where the provider is certified) and on Standard Contractual Clauses. Transfers out of Malaysia follow the cross-border transfer rules of Malaysia’s Personal Data Protection Act 2010.

How long we keep it

Public cards and stories stay until you make them private or delete them. Other data is kept as follows:

Your rights

Depending on where you live, you can ask to access, correct or delete your data, restrict or object to its use, receive it in a portable format (export), and withdraw your consent (make an item private).

• In the apps: Settings → My sharing lets you export, make items private, delete items or your whole identity, edit your profile, block people, change notifications and sign devices out.
• On the web: My sharing has the same controls, and Delete community data explains deletion.
• By email: [email protected]. If you lost access to your Google or Apple account, we can hide or delete your content, but we cannot move your identity to another account.

We reply within one month. We may ask you to confirm a request by signing in; we cannot verify who you are from a familiar title or photo.

You can complain to the data protection authority where you live. In Malaysia, this is the Personal Data Protection Commissioner.

Review, automatic pause and appeals

Cards, stories, text and photo changes, custom names and photos are reviewed before they become public. If we reject or remove something, we tell you why.

If 3 different people report someone’s encouragement within 7 days, that person’s sending is paused automatically and a moderator reviews it. You can appeal any decision by email to [email protected].

Children

The apps are for ages 13 and over. Taking part in the community — signing up, publishing, encouragement and a custom profile — is for adults aged 18 and over, by self-declaration. If we learn that an identity belongs to someone under 18, we delete it.

This website

Community pages run no analytics. The only third-party scripts are Google’s sign-in scripts, on the sign-in and account pages. These pages keep the following in your browser (our keys start with daystreak.community.):

• Local storage: your community sign-in (session.v1); privacy actions still waiting for the server (withdrawals.v1, story-withdrawals.v1, deletions.v1); a copy of your public name and avatar with your unread count (profile-cache.v1); a flag that the next sign-in must be interactive (interactive-sign-in.v1); whether you closed the Discover banner (mission-dismissed.v1); and Firebase Authentication’s own sign-in state (firebase: keys).
• Session storage, this tab only: encouragement you started before signing in (up to 10 minutes; pending-interaction.v1), a sign-in redirect in progress (up to 10 minutes; sign-in-redirect.v1) and a one-time “signed in” notice (signed-in-toast.v1).

Signing out removes the sign-in, the profile copy and the Firebase state. Our other pages use Cloudflare Web Analytics, which counts visits without cookies; it does not run on community pages.

Changes

We update this notice when the community changes, and show the date above. If a change affects what you agreed to, the apps and this website ask you to review it before you share or encourage again.