DayBright Privacy Policy

Last updated: 18 October 2026. This policy applies to DayBright version 2.0 and later for iPhone and iPad.

DayBright is made by Sergey Dikarev, an independent developer (wilder.dev). If anything in this policy is unclear, write to me@wilder.dev.

The short version

• DayBright has no account, no server and no analytics. Nothing you do in the app is sent to me or to anyone else.
• Your areas, sparks, check-ins and reviews are stored only on your device.
• Sparks are written on your device by Apple Intelligence. Where it is not available, DayBright uses its built-in library.
• The optional context sources (Calendar, Reminders, Contacts, Health, Weather) are off until you turn them on. Each one needs your permission in iOS, is read on the device and is summarised into one line.
• The one thing that leaves your device: with Weather on, your approximate location is sent to Apple's weather service to fetch the forecast. DayBright does not keep it.
• The App Store privacy label for DayBright is "Data Not Collected".

Who is responsible

DayBright is published by Sergey Dikarev (wilder.dev), contact me@wilder.dev. Because DayBright does not send me any data, I do not become the controller or processor of your personal data under the GDPR, the UK GDPR, the CCPA or similar laws by your use of the app. The only personal data I may hold is what you send me yourself, for example by email (see "When you write to me").

What DayBright stores on your device

Everything DayBright creates lives in its own private database on your device:

• Your areas: the areas you chose, whether each is on or off, their order, and any custom areas you created with their name, description and art.
• Daily briefs and sparks: the text of each brief and spark, how many minutes it takes, whether you did or skipped it and when, whether you marked it as liked or not, and a one-line summary of the context that shaped it (for example how busy the day was, the weather, or that a birthday was near).
• Check-ins: your brightness rating for the day (1 to 5), the optional line you wrote, whether you did the spark, and the reflection written for that day.
• Weekly reviews: the headline, pattern, highlight and suggestion written for each week.
• Your day's pulse: the energy, minutes and place you tapped, and how many times you asked for a swap or an easier spark.
• Settings: your morning and evening times, which context sources are on, your share-card style, your language choice, and whether you have DayBright+.

From this history DayBright works out patterns on the device, such as the time of day that suits you, whether you prefer short sparks, and which areas work for you. These patterns are computed when a spark is written and are not sent anywhere.

The database is kept in the app's container, which is shared only with the DayBright widgets, Control Center buttons and Live Activity on the same device. It is protected by iOS data protection. DayBright 2.0 does not sync it to iCloud or to any server. If you back up your device to iCloud or to a computer, the database is part of that backup, which is handled by Apple and by you.

To delete all of it, delete the app. The only exceptions are the entries DayBright wrote into the Health app with your permission, which stay in Health until you delete them there (see "Health data").

How sparks are written

Briefs, sparks, reflections and weekly reviews are written by Apple Intelligence (Apple's on-device Foundation Models) running on your iPhone or iPad. The prompt contains the area, a few recent spark titles, yesterday's check-in, today's pulse, the patterns described above and, if you turned them on, the one-line context signals described below. The text is generated on the device. DayBright does not use Private Cloud Compute, OpenAI or any other cloud model, and the prompt and its result are not sent to Apple, to me or to anyone else.

If Apple Intelligence is not available on your device, is turned off, is still downloading, or does not support your language, DayBright uses its built-in library of sparks. The library is part of the app and needs no network.

Optional personal context (DayBright+)

With DayBright+ you can let a few sources of your own data shape the spark. Each source is a separate switch in DayBright's Settings, is off until you turn it on, and asks for the matching iOS permission. Each source is read on the device, reduced to one short line, used inside the on-device prompt, and not kept apart from the one-line summary saved with that day's spark. You can turn any of them off at any time in DayBright's Settings or in iOS Settings, Privacy & Security.

• Calendar: DayBright counts your busy blocks for the day and finds your longest free window. It looks at times only, never at event titles, locations, notes or attendees. With Calendar on, DayBright may also schedule a local notification ("Your spark fits now") for the start of that free window.
• Reminders: DayBright counts how many reminders are overdue or due today. It never uses what they say.
• Birthdays (Contacts): DayBright looks for contacts whose birthday falls in the next seven days and uses their first name or nickname so a spark can suggest reaching out. Nothing else is read from your contacts, and no contact data is kept beyond the spark text itself.
• Sleep and steps (Health): see "Health data".
• Weather: see "Weather and location".

Health data

With "Sleep and steps" on, DayBright reads from the Health app last night's sleep, today's step count and the State of Mind entries you logged, and summarises them into one line (for example "slept 6 hours, 3,000 steps, mood low") that shapes that day's brief and spark.

With "Write to Health" on, which is a separate switch and off by default, DayBright saves your evening check-in as a State of Mind entry and a finished calm spark (mindfulness or meditation) as mindful minutes in the Health app.

Health data is used only for the features described here. It is never stored by DayBright outside the Health app, except for the one-line summary saved with the day's spark. It is never sent anywhere, never used for advertising or marketing, never shared with or sold to third parties, and never used for data mining or any other purpose. You can withdraw DayBright's access at any time in the Health app (your profile, Apps and Services) or in iOS Settings, and you can delete anything DayBright wrote in the Health app.

Weather and location

With Weather on, DayBright asks for your location while using the app, takes one location fix, and asks Apple's weather service (WeatherKit) for the current conditions, the forecast and today's sunset. To answer, Apple receives your approximate location for that request. Apple's handling of it is described in Apple's privacy policy at https://www.apple.com/legal/privacy/. DayBright keeps neither your location nor the forecast beyond the one-line summary used for the day. Weather data is provided by Apple Weather; see https://weatherkit.apple.com/legal-attribution.html.

Photos and moments

Photo sparks (DayBright+): when you choose a photo, DayBright uses the system photo picker, so it never sees your photo library, only the one photo you pick. The photo is reduced in size on the device and shown to Apple Intelligence on the device to write a spark. DayBright does not save the photo, and the photo never leaves the device. The only thing kept is the spark.

Moments: on devices where Apple's Journaling Suggestions are available, "Add a moment from today" in the check-in opens Apple's picker. DayBright receives only the moment you pick, turns it into a line of text for your note, and keeps only the note you save.

Notifications

DayBright's reminders are local notifications, scheduled on your device for the morning and evening times you set, plus "Your spark fits now" when Calendar is on. DayBright does not use push notifications and has no notification server.

Widgets, Live Activity, Control Center, Siri and Shortcuts

The DayBright widgets, Control Center buttons and the spark timer Live Activity read the same database on your device. Siri and Shortcuts phrases such as "What's my spark in DayBright" are handled by Siri on your device and answered by DayBright from that database. How Siri processes your request is described in Apple's Siri privacy information in iOS Settings.

Purchases

DayBright+ is sold as an in-app subscription through Apple's App Store. Apple handles the payment. I never see your name, address, payment details or Apple Account. DayBright checks on the device whether your Apple Account has an active subscription, using Apple's StoreKit, and stores a simple yes or no so that the widgets know. Apple provides me with sales reports that do not identify you. Subscriptions are managed in your Apple Account settings; Apple's privacy policy applies to the App Store.

Sharing

When you share today's spark as a card, DayBright creates an image on the device and hands it to the iOS share sheet. Where it goes from there, and who sees it, is your choice and is governed by the app or service you share it with.

No analytics, tracking, ads or third-party SDKs

DayBright 2.0 contains no analytics, no crash-reporting SDK, no advertising and no tracking of any kind, and includes no third-party code that talks to a server. DayBright does not track you across apps or websites and will never ask for permission to do so.

If you have turned on "Share With App Developers" in iOS Settings, Privacy & Security, Analytics & Improvements, Apple may send me anonymised crash reports for DayBright. They come from Apple, contain no content from the app, and I use them only to fix crashes.

When you write to me

If you email me@wilder.dev, I receive your email address and what you write. I use them only to answer you and to fix the problem you report, keep them as long as needed for that, and do not share them with anyone. Write to the same address if you want your messages deleted.

Earlier versions of DayBright

DayBright versions 1.x (2023 to 2026) worked differently: the daily advice was written by OpenAI's service, so the names of the topics you chose and the prompt built from them were sent to OpenAI, and anonymous usage statistics were collected with Google Firebase Analytics. DayBright 2.0 does neither. Nothing is sent to OpenAI or Google by version 2.0 or later, the statistics are no longer collected, and the Firebase project that received them is being closed. If you used 1.x, your topics and advice history were moved into the on-device database when 2.0 first launched and remain only on your device.

Your choices and rights

• Permissions: every data source is optional. Turn it off in DayBright's Settings or in iOS Settings, Privacy & Security.
• Deleting your data: delete the app. Entries that DayBright wrote in the Health app are deleted in the Health app.
• Your rights under the GDPR, the UK GDPR, the CCPA and similar laws: because I hold no data about you, there is nothing for me to access, correct, delete or hand over; your data is on your device, in your hands. I do not sell or share personal information. If you believe I hold data about you, or you have a complaint, write to me@wilder.dev. You can also complain to the data protection authority in your country.

Children

DayBright is not directed at children under 13, or under the minimum age for consent to data processing in your country. DayBright collects no data from anyone, including children.

Security

Your data stays in DayBright's private container on your device, protected by iOS data protection and your device passcode, and is not transmitted. No security is perfect, so keep your device updated and protected.

Changes to this policy

When this policy changes, the new version is posted at the same link with a new date, and a material change is mentioned in the app's release notes. Continuing to use DayBright after a change means you accept the new version.

Contact

Sergey Dikarev (wilder.dev)
me@wilder.dev

See also the terms of use.