Privacy

The short version

GridRinse cleans your files inside your web browser. The files you open, their contents, their names and the cleaned results are never sent to us or to anyone else, whether or not you have an account. We do not use advertising trackers or third-party analytics scripts; our own first-party usage counting sets no cookies; it keeps a random anonymous ID in your browser's local storage, which you can clear at any time.

How your files are handled

• When you choose or drop a file, your browser reads it from your disk into the page’s memory.
• Parsing and cleaning run in a background thread of the page (a Web Worker) on your computer.
• Downloads, including ZIP files for batches, are created in your browser and saved straight to your computer.
• When you close or reload the tab, the file and results are gone from memory. We keep no copy because we never receive one.

This is also enforced technically: the site sends a Content-Security-Policy header with connect-src 'self', which tells your browser to block the page from sending data to any other server. Our own server has no endpoint that accepts files. You can check this in your browser’s developer tools (Network tab): opening and cleaning a file makes no request containing its data.

Accounts (optional)

If you create an account, we store:

• your name, email address and a hash of your password (never the password itself);
• active sign-in sessions, with the IP address and browser description of each, so you can review and sign out devices;
• your workspace, its members and invitations;
• saved workflows: the list of cleaning steps. Steps contain the settings you typed, such as column names and find & replace text, stored as typed. Find & replace values are limited to 1 KB so that workflows cannot be used to store cell data;
• billing status (plan, Stripe customer and subscription ids). Card details are handled by Stripe and never reach us.

Deleting your account (Account → Delete account) immediately removes your login, sessions and profile, the workspaces you own alone and every workflow saved in them, and cancels their subscriptions.

Usage statistics

We count page views and feature use with our own first-party counter (no cookies, no third parties). An event records the page path (without query string) and a few fixed values such as “batch mode, 3 files, ZIP download”. It never includes file names, column names or cell contents, and we do not store your IP address with it. Events are kept for 13 months; deleting your account unlinks them from you.

What is stored on your device

Workflows you save “in this browser” live in your browser’s local storage, together with a random identifier for the usage counter. If you sign in, a session cookie keeps you signed in. You can clear all of it from your browser’s site data settings.

What our servers see

Like any website, the server that delivers the pages receives standard request information (IP address, browser user agent, the page requested) and may keep it in short-lived logs for security and reliability. Fonts are served from our own domain.

Contact

Contact details will be added before publication.

Service providers

• Cloudflare (hosting, security filtering, transactional email delivery): processes the technical data of each request, such as IP address and browser type, and may record anonymous page-load timings (no cookies, no file data).
• Neon (database hosting): stores account, billing-status and support data.
• Stripe (payments): processes card and billing details for paid plans under its own privacy policy.

None of them receive the files you clean.

Who is responsible

GridRinse is operated by [legal entity — to be added before publication] [business address — to be added before publication]. Contact: support@gridrinse.com. Abuse reports: abuse@gridrinse.com.