Data handling

A practical overview of how ClerkOps handles saved and temporary work.

Hosting and storage

Saved records use a private server database and uploaded files use private object storage. The deployment and storage arrangements are confirmed for each release.

Account access

You can continue with Google or use a ClerkOps username and password. Google sign-in stores only the name and verified email needed for account access; it does not request Gmail, Drive, contacts or your Google password. Username accounts still use approval and a private activation code.

Approved processing

Clerky’s cloud services reviews and malware checks use connected services. They are paused in Confidential Mode. Ask support for the current data processing register before uploading records subject to special contractual requirements.

Communications

Customer support stays in the private account inbox. The ClerkOps Team receives a notification and reference rather than customer message content.

Beta review

Final commercial data terms and the saved account retention schedule remain under review.