Track your time.
Understand your record. Stay in control.
ZoikoTime gives workers a clear way to record time, review classifications, add context, request corrections, and see approval status — without screenshots, keystroke capture, URL history, application names, or clipboard data.
A time record should be clear, correctable, and respectful
Workers need a fast way to record time, understand what is stored, see status, correct mistakes, and get help — without trading privacy for a usable record.
Easy capture
Start, stop, pause, and switch context with minimal friction on any supported device.
Visible record
See your own time events, totals, and current state — no guessing what was captured.
Clear status
Needs input, pending review, corrected, approved — plain state names, never vague labels.
Correction and context
Add missing detail or request a correction through a visible, trackable workflow.
Privacy and human review
Work-time facts only — no screenshots, keystrokes, browsing history, or app names.
Accessible support
Clear help routes when something goes wrong — no dead ends, no silent penalties.
From a time event to an approved record
ZoikoTime records an approved time event, applies configured deterministic rules, surfaces missing or conflicting information, lets you add context or request correction, preserves human review, and keeps a history of every approval.
Record
Approved time event captured
Classify
Deterministic rules organize it
Notify
Missing or unusual info surfaces
Add context
You explain or request correction
Review
Human authority stays in control
Approve & use
Approved record, kept in history
A flag is not an accusation, a productivity score, or a disciplinary outcome — it means information is missing or unusual enough to need a look.
Everything you need to understand your own record
Production-faithful, with synthetic data shown here. You see only your own authorized record — never another worker's, and never a leaderboard, activity score, or app/website usage.
Today · Aug 5, 2026
Needs input| Event | Project | Status |
|---|---|---|
| 09:00 – 12:30 shift | Client Onboarding | Approved |
| 13:15 – present | Missing project code | Needs input |
| Aug 4 correction | Break duration | Pending review |
No screenshots, app names, URLs, keystrokes, or activity scores appear anywhere in this view.
Start, pause, resume, and switch work with clear feedback
Start; stop; pause; resume; break; switch project; add a note; review today; open support — on the supported surfaces your organization has enabled.
Desktop app
Full review and correction, project context, and history on your desktop or web experience.
Mobile app
Records, corrections, and notifications for shift, field, and mobile work — one-handed reach.
Web experience
Browser access where production-supported, with the same review and correction workflow.
Connectivity states you can see
Online, offline pending, syncing, synced, and failed — never a false "submitted" state, and no silent data loss.
No exact offline promise
Offline capability is confirmed per supported platform. Where it isn't approved, the app tells you a connection is required.
Mistakes and missing context should be easy to resolve
You can review your own record, explain missing context, and request a correction through a visible workflow where enabled. The record keeps its status and history so the resolution stays inspectable.
| Stage | You see | Authorized reviewer sees | Audit record |
|---|---|---|---|
| Needs input | Plain reason and action | Configured issue and assignment | Flag source, rule/version, timestamp |
| Submitted | Your context and submitted values | Context, evidence, allowed actions | Actor, timestamp, prior/new value |
| Pending review | Current status and support route | Queue, SLA, escalation | Assignment and state changes |
| Resolved / corrected | Outcome, approved value, explanation | Final action, downstream readiness | Decision actor, reason, version |
| Reopened | Why it reopened and next action | New or conflicting information | Complete version chain |
Example label: "Unverified Exit — Pending Review," never "Time Theft" or "Suspicious Exit." A correction creates a reviewable request — never a silent overwrite.
Know what ZoikoTime collects — and what it never collects
The negative capability set is a binding product commitment, not a feature toggle.
Information used
- Approved time events
- Approved work / project context
- Schedule context where used
- Comments, corrections, approvals
- Disclosed authentication & device-trust events
Never collected
- Screenshots
- Keystroke content
- URL / browsing history
- Application-name monitoring
- Clipboard data & individual productivity score
Built for the ways people actually work
ZoikoTime records approved time and work context — it never infers work quality, personal commitment, or productivity from digital activity.
Remote worker
Consistent records across locations, devices, and time zones — without screen or app monitoring assumptions.
Hybrid team member
Simple project attribution across office and home days, with clear timezone and location-policy context.
Field & mobile worker
Reliable mobile capture, low-bandwidth behavior, and clear offline states — no unexplained blank screens.
Contractor & project worker
Clear assignment and customer/project attribution, with disputes resolved through visible review history.
Project-based worker
Task and customer context stays attached to the record, so time is traceable back to the right work.
Global / multi-timezone worker
Local timezone and daylight-saving context are shown clearly, so effective record time is never ambiguous.
Consequential decisions stay with authorized people
ZoikoTime may organize records and flag missing or unusual information, but authorized people review consequential changes. The platform does not decide discipline, label a worker dishonest, or create a productivity verdict.
Classification is policy-bound and reviewable — never branded as AI. AI may assist with anomaly flagging and signal quality only; it does not approve, punish, or decide pay.
Review doctrine
Role, permission, reason, evidence, previous/new value, timestamp, and status are all preserved for every consequential change.
Escalation
Support, manager/HR routes, and protected escalation as configured — without promising a universal grievance procedure.
A worker experience designed for real-world conditions
Accessibility as a requirement
WCAG 2.2 AA is release-blocking: keyboard, screen reader, voice control, high contrast, zoom, and reduced motion are all tested, not assumed.
Language & time zones
Locale-aware dates, times, numbers, and language, with daylight-saving and effective record time shown clearly.
Connectivity
Online, offline, pending, synchronized, and failed states are always visible — never a silent loss of your record.
Device support
A maintained platform and version matrix — unsupported devices are stated plainly, never hidden.
Alternative routes
Approved help or alternative capture routes when access fails — no worker is silently penalized for a system issue.
First use & updates
Access and installation instructions come only from the governed registry — no invented store, badge, or requirement.
Availability & compatibility registry
Support is driven by a governed registry — unsupported or gated platforms are simply absent, never shown as disabled or coming soon.
| Experience | Platform family | Role | Feature scope | Status |
|---|---|---|---|---|
| Worker mobile | Mobile family | Worker | Records, corrections, notifications | Supported |
| Worker desktop | Desktop / web | Worker | Full review & correction | Supported |
| Offline capture | Mobile family | Worker | Limited, publication-gated | Supported w/ limitations |
| Reviewer mobile | Mobile family | Manager | Context-first review | Plan dependent |
Generic platform families are shown until exact OS, browser, store, and installer requirements are verified.
Help and protection when you need it
Account security
Sign-in help, session visibility, device removal, and suspicious-access reporting.
Privacy
Plain-language Privacy page, data categories, purposes, and current jurisdictional information.
Support routes
Getting Started, Help Center, Product Documentation, System Status, and accessible contact.
No dark patterns
No forced consent, confusing toggles, or disguised marketing opt-ins for unrelated purposes.
Approved records can support the systems your organization uses
Approved means your record is ready for supported downstream use — not that payment has been issued. Payroll, billing, and employment decisions stay with your organization and its systems.
Worker record
Your time event, captured
Review / approval
Configured, human-controlled
Approved record
Ready for supported use
Downstream destination
Payroll, billing, project, audit
Post-approval changes preserve history and may trigger a new downstream version or reconciliation — nothing is silently overwritten.
Designed to be understood and used
We validate adoption against real dimensions instead of vanity metrics — no invented testimonials, logos, or ratings.
| Measure | Definition | Evidence |
|---|---|---|
| Task completion | Workers start, stop, add context, review, and seek help independently | Observed testing with representative users |
| Correction turnaround | Time from submission to visible resolution | Defined SLA and measured distribution |
| Privacy comprehension | Workers correctly identify collected vs. never-collected data | Short knowledge check |
| Accessibility | Critical tasks pass assistive-technology testing | Documented findings and remediation |
| Adoption | Active use across eligible workers, devices, and teams | Organization-level trend, never a worker ranking |