Privacy
Privacy for file comparison and review in ClearKit.
Learn how ClearKit handles file uploads, browser-based comparison, storage, and Stripe payments in plain English.
Keep the flow small
ClearKit avoids collecting more data than it needs for the current workflow.
Be clear about payment
Payments go through Stripe Checkout instead of a larger account system.
Say what is true today
This page explains how ClearKit works today in plain English.
ClearKit is built to help you review structured work without creating a heavy data footprint around it.
For Compare, files are read and parsed in your browser so you can review results locally. The app may also use limited local state needed to keep the experience working, such as remembering whether premium is unlocked on that device.
When you use Compare, you choose the old file and the new file directly in the browser. ClearKit reads those files so it can validate them, parse them, and build the results you see on screen.
ClearKit currently supports CSV and JSON in this workflow. If you are working with highly sensitive material, it is still a good idea to follow your own internal review rules before uploading anything anywhere.
ClearKit does not rely on a full account system or long-term file library for Compare. The goal is to avoid storing uploaded files as a normal part of using the tool.
Some limited data may still exist around product operation, such as service logs or billing confirmation state on your device. That is different from keeping a long-term copy of the files you compare.
If you choose to unlock premium, payment is handled through Stripe Checkout. ClearKit does not collect or store your full card details directly.
After a successful payment, ClearKit confirms access so premium results and exports can be used on that device.
You can decide whether to upload files at all, and you can clear local browser data if you want to remove browser-stored state such as the premium unlock cookie.
If a hosted ClearKit deployment holds billing-related or operational data connected to you, you can ask the operator of that deployment about access, correction, or deletion. Exact rights can depend on where you are located and how that deployment is run.
If you have a privacy question, use the contact method provided with the ClearKit deployment you are using. That is the right place to ask how a specific hosted version is configured.
If you need a privacy contact before using the product with sensitive material, ask for that detail before uploading files.
Practical Summary
The goal is simple: help you review files without turning ClearKit into a large data collection system.
ClearKit keeps the workflow light, uses Stripe for payments, and avoids a full account setup. If you need stricter guarantees for sensitive data, confirm the deployment details before using it.