Privacy & your files
Clear about your data.
How your files, email and results are handled when you use Clorse.
Updated October 30, 2026
Choose when your files leave your browser.
Selecting a file does not upload it. Enter your email and select “Prepare workpaper” to send the selected files to Clorse for processing. Only upload records you are authorized to share.
Who processes an uploaded file.
Clorse runs on Google Cloud. Supabase stores private job records and the resulting workpaper. Anthropic receives your source files and processes them through Claude Managed Agents to prepare the requested workpaper. Google Cloud handles website and upload requests. The information needed for each provider’s role is shared with that provider. These providers operate under their own applicable service and data-processing terms.
Private access, with a short retention window.
Your run is protected by a random access token kept in this browser tab’s session storage. It is not added to the page URL. Anyone with that token can access the run, so use a trusted device. Closing the tab may remove your access. Clorse keeps the workpaper available for up to 24 hours, then removes it through scheduled cleanup. Download a copy if you need to retain it.
Delete a run whenever you need to.
Use “Cancel & delete run” while processing, or “Delete workpaper” after completion, to revoke access to the run and remove its stored result. Clorse requests deletion of source files and the Anthropic agent session when a run ends or you delete it. If the provider is temporarily unavailable, deletion is retried through scheduled cleanup. Source uploads also have a 24-hour expiry. Provider operational logs, backups, and any records they must retain are subject to their own retention terms. A download you save on your device is not deleted by Clorse.
AI prepares. You review.
The tools prepare structured transactions, suggested receipt matches, recurring-rule proposals, explanations, and questions from the files you supply. Results may contain errors or omissions and require professional review against the source records. Clorse does not connect to, post to, or change QuickBooks or Xero accounts through these tools.
Your email address.
Your email is stored privately with your tool run so Clorse can identify the request. It is removed from the job record when the run is deleted or expires. It is not sent to the AI model or included in your downloadable workpaper. Results are available in your browser; entering an email does not sign you up for marketing or promise an email delivery.
Enquiries and website requests.
When you select “Send message”, your name, email address, optional firm name, and message are sent to Clorse through Google Cloud, stored privately in Supabase, and included in an internal Slack alert so Clorse can respond to your enquiry. Contact messages are separate from tool runs and their 24-hour expiry. When you start a tool run, Clorse receives an internal Slack alert with the tool name, your email address, run identifier and time. Slack alerts are retained separately from the 24-hour tool run; deleting a run does not remove an alert already delivered to Slack. Your uploaded files, file names, workpaper contents, and private access token are not included in Slack alerts. We also store a daily, hashed network identifier to limit spam. Ordinary website and tool requests may produce technical service logs, such as timestamps and request information, needed to operate and protect the service. These logs are separate from the source documents you choose to upload.
A question about your information?
Email [email protected]. Include the tool name and approximate run time when asking about a run. Do not email your private access token.