Useful tools.
Clear principles.

Your file is uploaded when you process it

Choosing a file does not upload it automatically. It is sent to our server when you click “Remove duplicates”. The published site uses HTTPS. The example contains fictional data only.

We use it to complete your task

We read the CSV to remove repeated rows and return the result. An upload may use a temporary file during the request, which is closed after reading. We do not create a permanent CSV copy, a file archive, or a record of its contents.

The cleaned file stays temporarily in the response memory and in your browser so you can download it. Loading another file or closing the page makes that result unavailable in the tool.

A limited record of operations

To measure usage and identify errors, we store a random job reference, timestamp, tool identifier, size, duration, row counts, processing status, and your account reference. This record does not contain the filename, file contents, or an IP address.

Job history has a 30-day retention period, with periodic automatic cleanup. A record-count limit may remove older entries sooner. Your account shows only your own recent jobs. Usage queries are private to server administration.

Your account and essential cookies

We store your sign-in email, display name, password hash when you use a password, account creation date, and email verification status. Accounts connected to Google also keep Google's account identifier. We do not store your plain-text password or Google access, refresh, or ID tokens. Account records are kept separately from temporary job history and do not expire after 30 days.

An essential cookie keeps your session active. Sessions expire after seven days, or after one day without activity. Signing out revokes the current session. Changing your password revokes all previous sessions. Anonymous form-protection sessions last up to 30 minutes. We keep only a hash of each session credential on the server.

Short-lived counters based on hashed email or network identifiers help limit automated sign-in attempts. Counter windows last up to one hour; expired counters and sessions are removed periodically.

Email verification and Google sign-in

If you create an account with email and password, our email provider receives your address and a verification message. Pending sign-ups keep an email and password hash for a 10-minute verification window. We store only a session-bound digest of the verification code. Expired pending records are removed automatically.

If you choose Google sign-in, Google authenticates you and shares your account identifier, name, email, and verification information with us. We request only basic sign-in profile information. Your CSV is not shared with Google or the email provider. Temporary Google sign-in attempts expire after 10 minutes; callback parameters are excluded from application and proxy access logs.

Technical service logs

Separately, the server may log technical request information, such as the IP address, timestamp, requested path, and response code, to operate the service and diagnose errors. These logs do not include your CSV contents.

No advertising trackers

We use essential account cookies, with no advertising cookies or third-party analytics services. Interface fonts and resources are served from our own site.

You stay in control

Choose which file to process and download only the results you need. You can cancel a request from the interface. If the server has already received it, processing may finish even after your browser stops waiting for the response.