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 way it gets better, and every one of them is read by hand.

What to expect during the alpha

You should know this before you rely on it. While ChronoZero is in private alpha:

  • There will be bugs. Screens may fail to load, recommendations may arrive late, and timelines can render oddly. Now and then you'll hit an error you have to back out of.
  • The service can go down. There's no availability guarantee and nobody on call, and deployments happen during the day.
  • Recommendations can be wrong. They are model estimates, not measurements. When one doesn't match your day, override it. The system learns from that correction.
  • Data may move or reset. Migrations during the alpha can change or clear parts of your history. Backups exist and restores are tested, but don't use ChronoZero as your only record of anything important.
  • Features will change. Things you rely on may be reworked or removed while the product settles.

None of this is a reason to go easy on your feedback. Blunt reports are the useful ones.

Reporting a bug

The fastest route is inside the app: open the account menu and choose Report a bug. The form attaches the technical context a report needs, including the screen you were on, the app version and the ID of the request that failed, so you don't have to describe any of it.

The in-app form sends what you write plus that technical context. It never attaches your task titles, calendar contents or activity history.

What makes a report useful

  1. What you did, in the order you did it.
  2. What you expected, and what happened instead.
  3. Roughly when it happened, and in which timezone.
  4. Web or iOS, and which screen.
  5. 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 go into a queue the operator reviews personally. There's no ticketing system and no service-level agreement, because this is a student project and not a support desk. You won't always get a reply, but reports are read, and the ones that reproduce get fixed.

Security reports

If you find a vulnerability, please report it privately to [email protected] before disclosing it anywhere else, and give us a reasonable window to fix it. Please don't test against other people's accounts, run automated scanning or load tests, or access data that isn't yours. The alpha terms set out what is and isn't permitted.

Privacy, export, and deletion

You can request an export or deletion from Settings inside the app. For anything else about your data (access, correction, restriction or objection), write to [email protected]. 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 instead of waiting 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 is already approved, you can sign in with Google or with a password set on the approved address.