Cloud login and PIN lock
The cloud account verifies access, then the app protects daily entry with a local PIN before users reach store data.
Security and control
Designed so store access stays controlled from the cloud portal.
Hisaab Kitab separates sensitive service settings from the mobile app, keeps AI usage controlled, and lets owners manage approval, expiry, and business access centrally.
Control model
Practical safeguards for real deployments.
The goal is simple: a shop can work quickly, but paid access, cloud sync, and AI service remain under owner control.
Role-based permissions
Owners, admins, staff, accountants, and sales roles can be aligned with clear portal permissions.
Owner approval
Payment, approval, suspension, expiry, and renewal controls are managed from the portal instead of hidden in the app.
AI key isolation
The OpenRouter key stays on the server. The mobile app receives only allowed settings and uses authenticated API calls.
Sync-aware access
Business profile data, branch identity, and active subscription status are refreshed from cloud records after login.
Audit and recovery tools
Local backup, cloud full backup, sync queue, conflict records, and audit logs help diagnose operational problems.
AI usage safety
Balanced Cost mode keeps AI useful without open-ended spend.
Voice commands use balanced cloud settings and local device speech where possible, keeping the assistant practical without unnecessary spend.
Server-only keyNo API secret is shipped inside the mobile app
Authenticated AI routesOnly logged-in stores can request config or plans
Monthly limitsBusiness-level usage can be capped
Usage logsModel, tokens, estimate, and business id are logged