Privacy Policy

ChatProof (chatproof.topple.kz, the “Service”) is built so that we handle as little of your data as technically possible. In short:

• Your chat files are processed entirely in your browser. They are never uploaded to our servers and never leave your device through the Service.
• No accounts. There is no registration, login, email capture or user database.
• No cookies. The Service does not set cookies of any kind — neither functional nor tracking.
• No analytics. No analytics, advertising or tracking scripts are embedded in the site.
• The only personal data that reaches our infrastructure is the standard technical information contained in web-server access logs (such as your IP address), described in section 4.

When you drop a WhatsApp _chat.txt or Telegram result.json export into ChatProof, everything happens locally in your browser: the file is read, parsed, numbered and hashed (SHA-256) by JavaScript running on your own device, and the PDF is produced through your browser’s print dialog. The application has no upload endpoint — there is nowhere to send your chat to.

While you work, the parsed transcript is kept in your browser’s sessionStorage — temporary storage that belongs to the current browser tab. It is not a cookie, it is not transmitted to any server, and it is deleted automatically when you close the tab. We never see, store or back up your chat content in any form.

The Service does not require or offer registration. We do not ask for your name, email address, phone number or payment details, and we do not maintain any database of users or of processed documents. If you email us (section 8), we receive whatever you choose to send and use it only to answer you.

The website itself is delivered by our hosting infrastructure, which uses the nginx web server. Like virtually every web server, nginx writes standard access logs that may include your IP address, the date and time of the request, the requested URL, the HTTP status code, and your browser’s user-agent string.

These logs record only the delivery of the website’s pages and static assets — they never contain your chat files or any content from them, because those files are never transmitted. We use the logs solely for security monitoring, debugging and abuse prevention (for example, blocking malicious traffic). They are kept for a limited period as part of routine log rotation and are then deleted, and they are not shared with third parties except where the law requires it.

The legal basis for this processing, where the GDPR or a similar law applies, is our legitimate interest in operating and securing the Service.

The Service does not set cookies — no consent banner is shown because there is nothing to consent to. The only browser storage used is the sessionStorage described in section 2, which exists purely so the preview and print pages can display the transcript you just parsed. It contains data only you put there, is never read by any server, and disappears when the tab closes.

The site includes no analytics or tracking scripts — no Google Analytics, no advertising pixels, no session recording, no third-party fonts or CDNs that would see your visit. All page assets are served from our own infrastructure.

When paid PDF exports launch, checkout will be handled by a third-party payment provider acting as merchant of record. That provider will process the personal data needed to complete the payment (such as your email and payment details) under its own privacy policy, and this policy will be updated to name the provider before payments go live. Your chat content will remain entirely client-side regardless.

Because we do not collect or store your chat content or any account data, there is essentially nothing for us to retain, export or erase: your transcript is gone from sessionStorage as soon as you close the tab. The only data we hold that may relate to you are short-lived server access logs (section 4) and any emails you have sent us.

Depending on where you live, you may have rights under data protection law — such as the GDPR — to access, correct, delete or restrict the processing of your personal data, and to lodge a complaint with a supervisory authority. To exercise any of these rights with respect to the data described above, contact us at the address in section 8.

For any privacy-related question or request, email ponimaiycm@gmail.com.

We may update this Privacy Policy from time to time — for example, when paid exports launch. The current version, with its “Last updated” date, is always available on this page. If a change meaningfully affects how personal data is handled, it will be published here before it takes effect.