Time
Where your time went and what it produced, per role, from your calendars and the mail you send. Only you see it.
Last verified 2026-10-12
In the web app
Off until you turn it on
Under Settings, Time you turn on Track my time; until then zonask builds nothing.
Only you see this. zonask never reports your time to anyone, and no screen or tool shows anyone else's time.
Per role you choose whether it is tracked and its Kind of work, which decides what counts most for that role.
What zonask reads
Each morning, for the previous workday (Monday to Friday), zonask reads the busy events of every calendar you use as My calendar and when you sent mail from each account.
Of an event it reads the time, the title, whether you organised it, your answer and who else was invited; the description is never requested.
Of the mail you send it reads only when each message was sent: no subject, no text and no recipient.
Events you declined, all-day events, free time and the busy copies zonask writes for calendar mirroring are left out.
The session estimate
Mail you send becomes sessions: messages less than 15 minutes apart are one session, and each message counts 5 minutes before you sent it, or the Minutes per sent email you set.
When a meeting and a mail session overlap, or the same meeting is in two calendars, each minute counts once.
Value classes
The AI gives each activity one of six classes from counts only (its length, whether you organised it, how many people from how many outside companies, new contacts, messages sent and the role), never its title or anyone's address.
Create: something was produced and shipped. Decide: a decision or an approval was made. Relate: relationship or sales value without a closed deal.
Deliver: client work. Coordinate: internal alignment where you own a follow-up. Overhead: presence without contribution.
The value score from 0 to 100 comes from the class, how much you contributed and the role's kind of work; minutes, email counts and attendance never raise it.
Every activity shows one evidence line, for example "You organised; 4 people from 2 outside companies".
Review and approve
Time shows a day by role with minutes, class and evidence; Approve, Edit (role, minutes, class), Exclude and Approve all confirm it.
Build again reads a day once more, from the last 30 days; what you approved or excluded stays as it is.
When a calendar or a mailbox could not be read, the day says so, for example "Incomplete: calendar of info@capptoo.ch could not be read".
Titles are encrypted and kept 30 days; after that an approved activity keeps its time, role, class and score, and anything you did not approve is deleted.
The weekly report
Value report shows per role last week's hours by class, the value score of the last four weeks, your top 5 contributions with their evidence, the overhead share and one sentence of what changed. Only approved time counts.
The morning summary links "Review yesterday" with the day's hours, and on Monday adds Last week's value.
Self-tracking only, and what comes later
zonask tracks your own time only: it never shows, ranks or scores another person, and employers or teams get no view of it.
GitHub and Drive activity and travel from receipts come in a later version.
Log an activity in Productive
When Productive is connected and a project is mapped to an activity's role, an approved activity shows Log in Productive. You choose the project, the service, optionally a task, the minutes and a note, then answer Yes on the desk; nothing is written before that.
Afterwards the activity says Waiting for your Yes, Logged in Productive or Result not confirmed. Check Productive. One activity is logged at most once. The Productive page explains each step.
Turning tracking off offers Delete my time data, and Delete all my data removes it too.
In Claude or ChatGPT
list_activities lists a day's activities, as a card with Approve all and Edit where the host supports it; both only put a message in the chat.
get_value_report gives the weekly report, and confirm_activities approves, edits or excludes, after your confirm.
time_settings reads whether tracking is on, the minutes per sent email and each role's choices; set_time_tracking changes them and build_day builds a past day again, both after your confirm.
Each activity also says whether it is in Productive, and log_productive_time proposes one time entry for one approved activity.