Data handling
Know what is processed and when it is deleted.
This page describes what Kauro does today, and it says plainly what Kauro does not claim.
- Connection to your CRM
- None. Kauro works on exported files only.
- Files of a free check not followed by a purchase
- Removed 7 days after the check is ready, and no later than 14 days after the files were sealed.
- Files and package of a purchased project
- Removed 7 days after the first package is ready, and no later than 14 days after payment is confirmed. A project in stages has its own deadlines, below.
- Sign-in
- Each person signs in with their own identity and a verified email address, with a password or, where Kauro offers it, with Google. Two-step verification is recommended, and a recent re-authentication protects high-impact actions.
- Security certification
- None claimed.
What happens to a file
Uploaded and sealed
Your team uploads the exported files and seals the set. A sealed set never changes.
Measured
The free data health check measures the whole set and changes nothing.
Prepared only as approved
Only the changes your team approved are applied, and the result is checked before release.
Deleted on schedule
Files, results and the package are removed on the schedule below, whether or not anyone asks.
What Kauro processes
The files your team uploads, the settings and decisions it enters, and the account and billing details needed to run the service.
Do not upload credentials or secrets, full payment card data, or health data. A field called notes can hold sensitive information. The checks Kauro runs on uploaded content reduce that risk but cannot promise to find every case.
How customers are kept apart
Each customer's data is separated from every other customer's, by the application and by rules that the database itself enforces. A request for another customer's project is answered exactly like a request for a project that does not exist.
What a model may see
When a model helps to interpret data, it receives only a limited context that Kauro selects, never your files as a whole. It cannot approve a change and it cannot write to your CRM. The limited context is deleted together with the project data it came from.
Verify who we are
Check these yourself before you trust a message that claims to come from us.
- Legal name
- KAURO DATA S.A.S.
- Colombian tax ID (NIT)
- 902120412-8
- Contact
- In writing only: contact@kaurodata.com
- Named providers
- Amazon Web Services, Resend, Google Workspace and Cloudflare, as the data processing terms describe.
Search the NIT yourself in Colombia's public company register, RUES, at https://www.rues.org.co/.
We never change bank details by e-mail. If a message says otherwise, do not pay; ask us in writing from your account.
How long each kind of data stays
Each kind of data has its own period, and a hard limit it never passes.
| What is kept | For how long |
|---|---|
| An upload that is not completed | It is removed when its inspection ends or 24 hours after the upload started, whichever comes first. |
| The files and results of a free data health check that is not followed by a purchase | They stay available for 7 days after the check is ready or has failed, and are removed no later than 14 days after the files were sealed. |
| The files and the delivery package of a purchased project | They stay available for 7 days after the first package is ready, and are removed no later than 14 days after payment is confirmed. |
| A project delivered in stages | Its workflow ends 21 days after the first stage is released and no later than 30 days after payment is confirmed; the final delivery then stays available for at most 7 days. Each stage shows its own deadline and the date of deletion. |
| Import receipt data | It is removed 7 days after its verification reaches a final state, or with the project when a staged project still needs it. |
| Target settings your team confirmed | A saved setting is used to prepare a new delivery for 30 days at most, and stops being used at once when the target changes in a material way. It stays in the project's record, and a repeat project can start from it only after your team confirms it again. |
| The project's record | Its column names and counts, decisions and destination details stay after the files are deleted, while the account is active and up to six months after it closes. A repeat project can reuse them. |
| The limited context sent to a model provider | It is deleted together with the project data it came from. |
| Application logs | They are kept for 30 days and contain no CRM content and no secrets. |
| Minimised security records | They are kept for 180 days, and longer only under an explicit legal basis. |
| Financial and legal records | They are kept for the period the applicable rules require and are stored apart from CRM contents. |
- A download link works for 15 minutes.
- A defect in Kauro's work can be reported for 30 days after the package is prepared, and Kauro aims to repair a verified material defect within 5 business days.
- Because files are removed on this schedule, a claim made after they are removed may need the exact source files to be uploaded again.
What deletion does not cover
Deleted means removed from Kauro's storage, staging and derived files, including temporary support copies, on the schedule above. A copy you downloaded stays with you, and financial and legal records are kept apart from CRM content for as long as the rules require.
What this page does not claim
Kauro has not been through an independent security certification and does not claim one. It does not promise anonymity or zero retention, it does not look for vulnerabilities in your systems, and it does not guarantee that you meet any regulation.
Read the terms or ask a question
Security questions are answered in writing. Describe the question and leave customer data out of the message.