Using Daybreak today
By using the website or an invited pilot build, you agree to these terms and the Privacy notice. If you do not agree, do not use the pilot build. Website previews are demonstrations: they do not schedule, change, or deliver an operating-system alarm.
During the private pilot, do not rely on Daybreak as your only alarm for medication, caregiving, travel, work, emergencies, or another time-critical obligation. Keep an independent backup alarm until the launch reliability program is complete.
Alarm and Night Arc expectations
Daybreak is designed so the operating system—not a network camera or browser view—owns wake delivery. Even so, pilot behavior can be affected by device power, speaker or Bluetooth routing, volume and notification settings, operating-system permissions, device-vendor restrictions, software defects, or unsupported configurations.
Gentle Night and Committed Night are deliberate wind-down tools. They do not make a phone impossible for its owner to leave. Do not use them to confine another person or interfere with emergency access. The in-app emergency exit and the device's own safety controls must remain available.
Camera and media honesty
Current browser horizons and Director v1 camera candidates are simulations driven by real solar geometry. They are not public live cameras. If the invited camera pilot later supplies a still frame, its provenance and eligibility must be labeled according to the product's live/replay contract.
Reviewed-media contribution is deferred for v1. Public upload, review, and catalog routes are unavailable. If a future program opens, recordings would remain private unless Daybreak created, technically verified, human reviewed, and approved a separate derivative. AI-generated media would have to identify its provider, model, version, workflow record, and prompt record and could not claim a real place.
Optional QwenCloud Director choice
An invited native build may offer an optional QwenCloud candidate selector after a separate permission screen. You may decline or withdraw that permission. Daybreak sends only the bounded simulated candidate context described in the Privacy notice, uses only neutral per-request aliases, accepts only one supplied alias or no selection, maps it to a trusted catalog entry on the server, and constructs every displayed field itself. Provider text is never shown as a camera fact or provenance claim.
This optional selector is advisory and may be unavailable, limited, delayed, or wrong. Every failure returns the deterministic Director, and the operating-system alarm does not wait for or depend on either result. Do not attempt to bypass the native-only marker, daily limits, shutdown control, or output validation.
Contributing a horizon
Email may be used only to ask about a possible future program. An inquiry is not a submission, does not grant Daybreak a media license, and does not promise acceptance, publication, or a response. Do not email media or attachments.
If Daybreak later opens an intake program, separate contribution terms will specify eligibility, prohibited content, truthful synthetic-media disclosures, the license needed to process and publish approved media, review and rejection rights, and withdrawal and deletion procedures before a file is accepted. Questions can be sent to support@daybreakhorizons.com.
Acceptable use
You may not:
- interfere with, overload, probe, or bypass service security;
- misrepresent a simulation, replay, or pilot frame as live;
- use Daybreak to monitor people or property without authority;
- copy, resell, or redistribute media without the required rights; or
- use the service in violation of law or another person's rights.
Ownership and open-source plans
Daybreak's name, visual identity, website, application, and original media remain protected by applicable intellectual-property laws. The repository is private during the first native build. A component is open source only when Daybreak publishes it with a specific license; planned public protocols are not themselves a license today.
Pilot availability and responsibility
Pilot access can be limited, changed, suspended, or ended while we investigate safety, reliability, security, rights, or operational issues. Pre-release software and previews are provided on an “as available” basis to the extent permitted by law, without a promise that every device, alarm, camera, or network response will be uninterrupted or error-free.
To the extent permitted by law, Daybreak is not responsible for indirect or consequential losses arising from a preview or pilot failure. Nothing here limits rights or responsibilities that applicable law does not allow us to exclude.
Changes and contact
We may update these terms as the pilot and launch service change. A revised version will show a new date. Questions can be sent to support@daybreakhorizons.com. Email support is not an emergency service and does not carry a guaranteed response time.