Why Every Tool on Deecliq Has a Usage Tracker — And Why That's Not Surveillance
I track how tools are used. Here's exactly what I collect, what I don't, and why I think transparency matters more than a privacy policy no one reads.
Let me be upfront about something: Deecliq tracks usage. If you use the PDF merger, I know a PDF was merged. If you use the XML validator, I know a file was validated.
Here's what I do collect:
- Which tool was used
- When it was used (date and time)
- How many files were processed
- Session duration
Here's what I don't collect:
- The content of your files
- Your IP address (beyond what the server log naturally captures)
- Any data that identifies your company or the nature of your work
Why track at all? Because I want to build tools people actually use. Usage data tells me which tools are valuable and which ones I built based on false assumptions. It tells me when a tool breaks (sudden drop in usage after an update is a red flag). It helps me prioritize what to build next.
I built this platform alone. Usage data is my product research, my QA, and my roadmap — all at once. I think being honest about that is more respectful than hiding it in a 40-page privacy policy.