Plain privacy
for early testing.

In brief

Your timers live on your devices first. If you create a test account and enable sync, Ora uses the information needed to identify your account, connect devices, and exchange timer operations.

What the test service uses

The account flow uses your email address. Connected apps provide a generated device identifier, a display name, and a platform label. Timer sync carries timer records and small operation events needed to rebuild state on another signed-in device.

What Ora does not need

The baseline product does not require GPS, microphone recordings, raw Bluetooth identifiers, raw app or window names, or continuous sensor streams for timer sync or smart alarm routing.

Browser registration

After verification, this website keeps only a non-secret account summary in browser storage so it can show that the address is ready. Authentication tokens are not intentionally persisted by the website.

Early-test limitation

These are practical privacy notes for an active test service, not final commercial terms. Retention and self-service deletion controls are still being prepared for a wider release.