Input is processed only in the active browser tab's memory and is not sent to a ByteQuant server.
Tool Pipeline: CSV → Masking → JSON
Parses CSV in the active browser tab, masks email, phone, IBAN, Turkish ID, and payment-card candidates with explainable rules, then exports JSON or CSV. Algorithmic detection is neither legal compliance nor identity verification; human review is required.
Turkish ID and card candidates are masked only when their checksum passes. This does not prove that a number belongs to a real person or account.
Input and output are not stored. The optional usage counter keeps only tool identity and count, never content.
Output comes from disclosed rules or browser APIs and needs independent review before high-impact use.
A result in three steps
- 01
Choose a CSV file or paste text and verify the column preview.
- 02
Select masking types and manually review detected candidates and changed cells.
- 03
Download the cleaned result as JSON or CSV and protect the source separately.
When is this tool useful?
- ✓ Preparing sample data for GDPR/KVKK
- ✓ Turning CSV into a safer JSON draft
- ✓ Pre-cleaning support and test records
Automated output is a preliminary assessment. Do not use it alone for legal, financial, medical, or security-critical decisions.
Frequently asked questions
Does this tool send input to a server?+
No. Processing runs in this browser tab. Data leaves the page only when you choose to copy or download the result.
Is the result definitive?+
The tool produces consistent output from disclosed rules and browser APIs, but context, data quality, and method limitations can affect it. Verify high-impact decisions.
Is input saved?+
No. Tool input is not persisted to localStorage or another durable store. Only with your consent may tool slug, count, and last-used time be kept on this device for personal shortcuts; that record can be deleted through privacy choices.