Verification Method

59m.club is a public standard for daily screen time. This page defines how measurement and verification are calculated so the system remains transparent and consistent across all profiles. The purpose is not motivation or coaching, but clear, stable qualification under a single rule.

Standard Definition

Metric

Daily outcome (pass / fail / missed)

Threshold

Pass means you met the “under 59” standard. Minutes stay on-device.

Qualification Window

Rolling 7-day window (7 tracked days)

Qualified State

7/7 passes in the current window

Pending State

Fewer than 7 tracked days

Measurement Source

Clients may use platform APIs on-device to determine pass/fail.
59m.club does not ingest or publish usage minutes.
Daily public records are stored as date + outcome.

Verification reflects measurement conditions available from the platform APIs.

Record Logic

Each calendar day has at most one canonical outcome.
Same-day updates may update today’s outcome while it is live.
Verification is derived from the rolling window of outcomes.
A missing day is not automatically interpreted as a pass.

Timezone and Day Boundary

Day boundaries are resolved by server date for canonical storage. Client local date may differ near midnight. The canonical record date is the stored date.

Today is always visible on profile surfaces, even when 0m.
Historical calculations operate on stored YYYY-MM-DD records.

Integrity Assumptions

Device ownership is represented by private device key per account.
Writes require valid X-Device-Key.
No third-party ad/analytics SDK participation in measurement path.

Limitations

Platform API behavior can vary across OS versions and permission states.
If device permissions are revoked, data continuity can break.
A missing day is not automatically interpreted as qualified.

Change Policy

Any future changes to threshold, averaging window, or classification rules will increment this spec version and be published here before enforcement.