Local-first clinical workspace
Histories, notes, preferences, and write-pad drafts are stored in your browser first. They remain available on that device when the network is unavailable. Anyone with access to the device or an exported backup may be able to read that data, so use anonymous patient identifiers and secure the device.
Accounts and cloud sync
Signing in is optional for local clerking. When you sign in, your email identifies the account and eligible workspace data is synchronized through our cloud database so you can recover or resume it. Queued local edits are sent when connectivity returns.
AI processing
When you choose an AI feature, the relevant note text and clinical context are sent to configured AI providers to generate the requested output. Do not enter real patient names or unnecessary identifying information. AI features require a connection and do not remove the local note if a request fails.
Billing and diagnostics
Payment processors handle checkout and return transaction status needed to grant credits or subscriptions. ClerkKit records credit and entitlement events but does not store full card or mobile-money credentials. Error monitoring is configured without default personal-data collection; diagnostic events may include technical error details and route names, not note bodies by design.
Your controls
You can export or reset local data from Settings. Signed-in users can sign out or permanently delete their cloud account and cloud-synced data from Account & Sync. Deleting a cloud account does not silently erase data already stored on the device; use Reset all data separately when that is your intention.
Clinical responsibility
ClerkKit is intended as an assistive documentation and educational tool. It is not an emergency service and is not intended to replace professional clinical judgment, diagnosis, or treatment decisions. Verify every AI-generated suggestion before relying on it.