Private alpha
It will break. Please tell us how.
ChronoZero is early software run by one person. Bug reports from alpha testers are the main thing that makes it better, and every one of them is read by hand.
What to expect during the alpha
Better to say this now than to let you find it out on a bad day. While ChronoZero is in private alpha:
- There will be bugs. Screens that fail to load, recommendations that arrive late, timelines that render oddly, and occasional errors you have to back out of.
- The service can go down. There is no availability guarantee and no on-call rotation. Deployments happen during the day.
- Recommendations can be wrong. They are model-generated estimates, not measurements. Override them whenever they do not match reality, because that correction is exactly what the system learns from.
- Data may move or reset. Migrations during the alpha can change or clear parts of your history. Backups exist and are restore-tested, but do not treat ChronoZero as your only record of anything important.
- Features will change. Things you rely on may be reworked or removed while the product finds its shape.
None of this is a reason to be gentle in your feedback. Blunt reports are the useful kind.
Reporting a bug
The fastest route is inside the application: open the account menu and choose Report a bug. That form attaches the technical context the report needs: which screen you were on, the application version, and the identifier of the request that failed. You do not have to describe any of it.
The in-app form sends nothing beyond what you write plus that technical context. It never attaches your task titles, calendar contents, or activity history.
What makes a report useful
- What you did, in the order you did it.
- What you expected, and what happened instead.
- Roughly when it happened, and in which timezone.
- Web or iOS, and which screen.
- Whether it happens every time or only sometimes.
A one-line report is still worth sending. “The timeline was empty this morning” is a real signal.
What happens next
Reports land in a queue the operator reviews personally. There is no ticketing system and no service-level agreement, because this is a student project rather than a support desk. You will not always get a reply, but reports do get read, and the ones that reproduce get fixed.
Security reports
If you find a vulnerability, please report it privately to security@chronozero.app before disclosing it anywhere else. Give us a reasonable window to fix it. Please do not test against other people's accounts, run automated scanning or load testing, or access data that is not yours. The alpha terms set out what is and is not permitted.
Privacy, export, and deletion
Export and deletion can be requested from Settings inside the application. For anything else about your data, whether access, correction, restriction or objection, write to privacy@chronozero.app. The privacy notice describes what is processed and why.
Not a medical or emergency service
ChronoZero does not diagnose, treat, or measure any medical or psychological condition, and it is not a medical device. If you are unwell or in crisis, contact a qualified professional or your local emergency number. Do not wait for a recommendation from a planning app.
Access and accounts
Anyone can join the waitlist. Requests are reviewed by hand and approved one at a time, so there may be a wait. If your access has already been approved you can sign in with Google or with a password set on the approved address.