Frequently asked questions

You upload a document — an Aadhaar, a PAN, a purchase receipt. Klok reads it, fills the fields it can, and shows you the document beside the draft with anything uncertain highlighted. You correct and confirm. The record is written only on your confirmation — the AI has no path to save anything on its own, and that guarantee is covered by automated tests.

Then you see it immediately, because the original document is on the screen next to the draft, and low-confidence fields are flagged and must be touched before you can commit. A wrong read costs you two seconds of correction — never a wrong record.

Indian identity documents (Aadhaar, PAN, passport, driving licence) into the employee record, and purchase receipts into expense claims. Resumes and more document types are on the roadmap — each new type is a small addition, not a new product.

No. Documents are sent to the AI provider only to be read, under API terms that exclude training. The raw extraction is stored in your tenant for audit and nowhere else.

An afternoon for a serious start: add your entities and branches, invite your team, and send onboarding links to employees. Because employees enter their own details and documents, the usual weeks of HR data entry simply do not happen.

No. It runs in the browser and installs on phones like an app in two taps — no app store, no IT involvement.

Yes — CSV import with a preview step for the employee master and opening leave balances. Or skip the spreadsheet: send everyone an onboarding invite and let their records build themselves.

The employee flow is: tap Punch in the morning, apply leave from a phone, snap a receipt. Each screen carries a plain-language "how this works" panel. A new joiner manages on day one.

Free for 14 days — all core modules, no card. It exists so you can prove the validation workflow on your own people before paying.

By employee count bands, not per user login — per-user pricing makes companies restrict logins, which kills adoption. Add every manager and every employee.

UPI, cards, netbanking and bank transfer; monthly or annual (annual = 10 months). GST invoice provided.

Reminders, then a 7-day grace banner, then the workspace turns read-only — never deleted, never suspended. Your data stays exportable throughout; it is never held hostage.

You do, unambiguously. Settings → Download all data exports every record as CSVs, one click, anytime.

Encrypted at rest, never rendered where they are not needed, and documents live in a private vault reachable only through signed, tenant-checked URLs — never a public link.

Yes — tenant isolation is enforced at the database layer and verified by automated tests on every release.

Only where the employee has personally switched on consent, and only during their working hours — both rules are enforced in code, not policy documents. Attendance geofencing uses the punch moment only; field tracking requires explicit opt-in that the employee can revoke anytime.

The audit trail is immutable — who approved what, when, with remarks — and exports to CSV. Every AI-validated record also keeps the original document and the raw extraction as evidence.

English, हिन्दी, العربية (RTL), Deutsch, Français, Español, 日本語, 中文 and more — each user picks their own from the header; the company sets the default.

Connect your own gateway (Meta Cloud API, UltraMsg, AiSensy, Twilio or Interakt) in Settings. Leave decisions, claim updates and approvals can then ring bell + email + WhatsApp, with editable templates.

Yes — every approval flow carries an SLA. A request sitting past its deadline escalates to the next level automatically, and the escalation itself is logged.

Yes — a checkout after midnight closes the previous day's attendance row correctly. Cross-midnight pairing was built and test-pinned from day one.

Attendance, leave and expense data is payroll-ready today (present/half/LOP/overtime per day, approved reimbursements). The full Indian statutory payroll pack — PF, ESI, PT, TDS, payslips — is in active development.