Platform
Streaks and engagement
How successful daily sign-ins produce current streaks, personal bests, rank, and operator insight.
Security
Review the authentication controls behind a successful sign-in.
Audit logs
Understand operational history boundaries.
Earning a streak
A successful authenticated sign-in creates the first day of a login streak. Another successful sign-in on the next calendar day increments it. Additional sign-ins on the same day update activity time without adding another day.
Timezone and reset behavior
Day boundaries use the community timezone. If the previous recorded day is neither today nor yesterday, the next successful sign-in starts the current streak again at one. The longest streak remains the all-time best.
Rank and leader
The leaderboard includes active community members with streak records. It sorts by current streak, then longest streak, then most recent login. Rank reflects that current ordering; the leader is the first row.
What members see
A member sees their current streak, best streak, whether today is active, rank, number of ranked users, and the current leader’s display name, avatar, and streak totals. It does not expose detailed login timestamps for every member.
What administrators see
Authorized operators can inspect active-today, at-risk, lost, and no-streak states; current and best values; last active day; rank; aggregate metrics; and recent created, incremented, reset, and best-update events. Suspended and pending memberships are excluded.
Engagement and privacy boundary
A streak measures successful sign-in days only. It does not measure message content, pages viewed, time spent, event attendance, task completion, or Feed activity. Treat it as a lightweight participation signal, not a productivity or security score.