The short version
- Daybreak does not sell personal information or use it for ads.
- We have not added product analytics, advertising pixels, or cross-site tracking to this website.
- The Bedtime preview synthesizes audio in your browser. Scene, sound, volume, and timer preferences stay in local browser storage.
- Current invited app builds are designed to keep alarm schedules, Night Arc preferences, and locally generated sound on the device.
- Optional QwenCloud Director selection is off until a person gives separate permission. Declining or withdrawing permission keeps the deterministic Director and does not affect alarm delivery.
- Reviewed-media contribution is deferred for v1. Public upload, review, and catalog routes are unavailable.
Information the website handles
Ordinary web requests
When you visit, the hosting and security providers that deliver the site may process standard request information such as an IP address, browser and device details, requested path, and request time. Those providers may keep security or access logs under their own settings. Daybreak does not use those logs to build advertising profiles.
Local Bedtime preferences
The Bedtime preview uses your browser's local storage to remember the scene, sound, volume, and exact timer duration on that browser. It does not use a Daybreak account, and the preview does not send those choices to a Daybreak application server. Clear the site's browser data to remove them.
Director Studio
Director Studio sends the selected time, dawn-or-dusk intent, mood, and result limit to the Daybreak Director API. Version 1 returns a simulated camera decision built from real solar geometry. Standard request metadata may still appear in hosting or security logs. The public browser Studio uses the deterministic Director and does not invoke the paid QwenCloud route.
Horizon contributions and review
The planned contribution studio, reviewer console, upload endpoint, and public media catalog are not available in v1. An email asking to hear about a future program records only the address, message, and other information the sender chooses to include. It is not a media submission or an acceptance, and people should not attach media.
If Daybreak later opens a contribution program, its notice will explain the account, intake, quarantine, processing, human review, catalog, retention, withdrawal, and deletion practices before files are accepted. The intended design keeps originals private, removes metadata and audio from separate derivatives, and requires rights, privacy, safety, scene, and provenance review before publication; none of those future controls is a currently available service.
Fonts and linked services
The site currently requests web fonts from Google. Google can receive standard request information when your browser loads those fonts. Following an external link or opening your email application places you under that provider's privacy terms.
Private-pilot app builds
Invited pilot builds use device permissions only for features the person chooses, including operating-system alarm delivery, optional local solar-time suggestions, notifications, audio, and approved distraction controls. Approximate location is intended to calculate local sunset and sunrise suggestions on device, not to create a movement history.
If a pilot build connects to a Director or camera service, the service can receive the requested wake context and standard network metadata needed to answer and protect the request. Alarm delivery is designed not to depend on that network response. Daybreak does not currently provide accounts, cloud sleep histories, or advertising profiles.
Optional QwenCloud camera selection
An invited native build may offer a separate, optional QwenCloud Director choice. It is off by default and starts only after an affirmative permission screen. When enabled, the Daybreak server sends Alibaba Cloud's international Qwen Chat Completions service the scheduled UTC time, dawn-or-dusk intent, selected mood, and up to four already-eligible simulated candidates labeled only with neutral per-request aliases such as c1 through c4, plus Daybreak-computed scores for timing, framing, health, weather, image, and mood. The server maps an accepted alias back to its trusted catalog entry. It does not send the phone's IP address, result limit, catalog camera IDs, camera names, places, coordinates, account or device identifiers, alarm identifier, or location to QwenCloud.
QwenCloud processes that small JSON request with the qwen3.8-max model. Daybreak fixes the call to non-thinking mode to keep this bounded selector within its latency and cost limits. Its pay-as-you-go console currently retains call metadata for 14 days, including the call time, status, model, API-key identifier, token usage, latency, request identifier, Daybreak server network IP, and workspace or account identifiers. Current console log detail does not expose the prompt or output content, although QwenCloud must process both to answer the request. Alibaba Cloud's current international product terms state that customer input and output are processed on the customer's behalf and are not used to improve its models without separate consent. Daybreak does not log the prompt or model output.
To limit cost and abuse, the Daybreak server observes the requesting IP only long enough to create a one-way, daily rotating quota key. It stores that key with a count for one UTC-day bucket, not the raw IP. The previous bucket is replaced on the next provider reservation after the day changes, or during operational cleanup. Hostinger separately receives the caller IP to deliver and protect the request and may retain it in infrastructure or access logs under its own settings. Missing configuration, a daily limit, timeout, refusal, malformed output, or any other provider failure uses the same deterministic Director result. Permission can be declined or withdrawn in the app at any time without changing the alarm.
Media retention and choices
Daybreak is not accepting media in v1 and therefore does not operate public submission-retention or deletion workflows. If a future program opens, its notice will describe how long submission metadata, private originals, review copies, processing receipts, decisions, and approved derivatives are retained, as well as withdrawal and deletion choices.
When you contact us
If you email us, we receive the address, message, and attachments you choose to send. We use them to answer the request, operate the pilot, investigate a problem, and maintain necessary records. Please do not send medical information, passwords, alarm PINs, or more personal detail than the issue requires.
We keep support and pilot correspondence only as long as reasonably needed for those purposes, security, and legal obligations. You can ask us to delete your correspondence unless we must retain it.
Choices, safety, and changes
You can clear local browser preferences, decline optional permissions, withdraw optional QwenCloud permission, stop using a pilot build, or ask about information you sent us. The service is not directed to children under 13. We will revise this notice before introducing materially different practices such as an account or cloud history, and we will update the date above.
Privacy and security questions can be sent to support@daybreakhorizons.com.