You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
- A **Product Usage Event** may describe a schedule, preparation, notification, alarm, onboarding, or account action without storing the user's raw schedule names, notes, place names, credentials, tokens, or free text.
103
111
- First-release **Product Usage Events** are **Workflow Milestone Events**, not every tap or raw navigation step.
-**Provider Authentication Completed** precedes **OnTime Session Established** during Apple or Google sign-in.
114
+
-**Provider Authentication Completed** does not mean the user is signed in to OnTime.
115
+
- The signed-in app experience begins only after **OnTime Session Established**.
105
116
- A **Product Usage Event** may include **Analytics Event Parameters** such as workflow, result, stable error category, coarse count, coarse duration, platform, or app version.
106
117
- An **Analytics Event Parameter** must not contain user-authored text, direct identifiers, tokens, raw exception strings, request bodies, or response bodies.
107
118
- A **Product Usage Event** uses a stable snake_case name and includes a schema version.
- "Event payload" was too open-ended; resolved: events use allowlisted **Analytics Event Parameters** only.
167
+
- "Login completed" was ambiguous for Apple and Google sign-in; resolved: external account prompt completion is **Provider Authentication Completed**, while usable OnTime sign-in is **OnTime Session Established**.
156
168
- "Alarm permission" was ambiguous between **Exact Timing Permission** and notification permission; resolved: notification permission may enable a **Fallback Notification**, but does not mean **Exact Timing Permission** is granted.
157
169
- "Pending" was ambiguous for notification status; resolved: the canonical state is **No Scheduled Notification** when notifications are enabled but no upcoming Schedule Notification is armed.
158
170
- "Allowed" was ambiguous for permission requests; resolved: a request action is not the same as granted **Exact Timing Permission**.
0 commit comments