Skip to content

Last updated 13 November 2026

Privacy

Signed in to workspaces? Read the account privacy notice

This notice covers the free tools used without sign-in. Starting sign-in or using an account is covered by the separate account privacy notice. The exceptions are the anonymous sign-in counts listed below. Free tools remain free and need no account.

The short version: your files stay on your device. We never see them. We count page views and tool use anonymously, without cookies, and we only have your email address if you give it to us.

Who is responsible: megarows.com (MegaRows) collects the personal data described on this page and is responsible for it. Contact: hello@megarows.com.

Files are processed locally in your browser and never uploaded. When you open a file in MegaRows, it is read by your own browser on your own device. Its contents, its name and its column names are never sent to us or to anyone else. At most, an anonymous usage count notes the kind of file and a rough size range, such as “CSV, 10–100 MB” (see below).

Your files

MegaRows is a website that runs entirely in your browser. Counting, viewing, charting, calculating and converting all happen on your device. We do not run servers that receive or store your files, so there is nothing for us to keep, share or lose. You can confirm this in your browser’s developer tools: the Network tab shows no upload when you open a file.

Anonymous usage counts

To learn which tools people use and whether they work, the site counts a few things anonymously and sends the counts to our own server at megarows.com. Nothing goes to any other company’s tracking service.

  • A page was viewed (the page’s address, such as /csv-row-counter). On the first page of a visit, also which site sent you here, by name only (for example “reddit.com”, “google.com”, an AI assistant such as “perplexity.ai”, or “direct” if none), the campaign tag of a MegaRows link you followed (such as “launch1”), and how the page was opened (a link or a typed address, a reload, Back or Forward, or loaded ahead by the browser). On a later page of the visit, only that it was reached from another MegaRows page, and how it was opened. Never the address of the page you came from.
  • The plotter opened a file or could not open it: the kind of file (for example CSV, Excel, MATLAB, HDF5 or TDMS, and whether it came compressed in a .gz file or a ZIP archive), rough ranges for its size, row count and opening time, which of our pages it was opened on, how many files were open together (1, 2, 3–4, 5–8 or 9–16), or the kind of problem (for example “password-protected”).
  • For an opened file, also the kind of data in it (for example a MATLAB timeseries log or a spreadsheet of records), as a category, never its contents or names, and for a MATLAB file whether it holds objects the plotter could not read.
  • For a file that could not be opened, also the type of file that couldn’t be opened, from its extension and a fixed list (for example TDMS, Parquet or MATLAB), never its name, and for a MATLAB file what stopped it, as a category (for example a kind of MATLAB object it could not read yet, a damaged file, or a MATLAB script rather than data).
  • The plotter drew its first chart, at most once per page visit: whether it showed one of our samples or your own file, which of our pages your visit started on (for example “/plotter”), and the kind of device: phone, tablet or computer, worked out from the screen size and whether it has a touch screen, never from the device’s name or model.
  • Which plotter features were used, such as saving a chart as an image, switching a chart to bars or to box plots, summarising rows by month, comparing several files or calculating across two files, splitting a file that stores its signals in one column into channels, downloading a wide CSV, zooming a chart with the scroll wheel or a pinch, opening the statistics, switching on the measurement cursors, copying their values, or adding an event line, a limit line or a pinned value, sorting, filtering or searching the data table, downloading it as shown, opening a plot in its own window, opening the list of a MATLAB file’s variables (also when it opened by itself) or copying a path or a value from it, opening a menu of actions (a right-click, or More on a phone’s action bar) or the action bar itself, switching the time axis to relative or back, stacking a chart’s series in lanes (and whether with the lanes button in the plot’s header), using or dismissing a suggested X axis, a file opening with the X axis you chose for files with the same columns, pressing “Log scale, X” while it is greyed, or opening, copying or downloading a spectrum’s table of peaks (for the Math dialog, also which button opened it). Also when everything was reset to the defaults, when a file opened with the default layout because its saved layout didn’t finish opening last time, when the plotter asked before opening files that may not fit in your device’s memory and whether you opened them anyway, when the plotter showed “Something went wrong” (what went wrong is only ever sent as the error report described below), and when it said that MegaRows was updated since the page was opened and whether its Reload was pressed. Never where a cursor, a line or a window was, its value or its label, never what you sorted, filtered or searched for, never what a menu was about or which action you chose, never a path or a value you copied, and never a peak’s frequency or value. Each feature is counted at most once per page visit, not every click. Never the names of your signals or columns.
  • On a page with the plotter, when an unexpected error happens (the plotter shows “Something went wrong”, an error nothing in the page caught, or the plotter’s background file reader stops), a report of it: the type of error from a fixed list (such as “TypeError”, otherwise “other”), what the plotter was last doing (for example opening a file, drawing a chart or running a calculation), which part caught it, up to five places in our own program code where it happened (the name of one of our code files with a line and column number), the version of our code (the same for everyone who loaded that version), the last three plotter features used on that page (from the list above), the type and rough size of the last of your files opened on it (for example “MATLAB, 1–10 MB”) and the kind of problem, from a fixed list (for example “out of memory”, “part of the page could not be loaded” or “the page’s text changed while it loaded”, otherwise “other”). Like every count, it also records the page’s address, the browser family and the country, and it is stored and deleted like the other counts. It never includes your file’s name or contents, column, signal or variable names, the error’s message, any other address or anything you typed. At most three reports per page visit, the same error only once, and no identifier is added to follow you between pages. None is sent with Do Not Track, Global Privacy Control or the switch below. Some errors cannot be reported, for example when the browser itself stops the page.
  • Which calculation was run in the Math dialog (for example “Butterworth filter” or “PSD”), the kind of result, whether it worked, failed or was cancelled (for a failed one, the kind of problem, for example “too few samples” or “out of memory”), and rough ranges for the file’s row count and how long it took. Never your formula, your column or channel names, any value or the error’s message.
  • For the merge tool: opening a set records total-size and file-count ranges; finishing records how files were combined and file-count, total-size and row-count ranges; failing records the kind of problem. File-count ranges include 3–5.
  • CSV splitting: opening records a file-size range; completion records the method (rows, size or column) and ranges for output files (such as 6–20), file size and time taken; failure records the problem type. Never column names, values or file names.
  • A converter (for example MAT to CSV or CSV to MAT) handed a CSV or MAT file to your browser to download: the kind of file converted, whether it was one of our samples or your own file, a rough range for its size, and which converter page it was on. It does not tell us whether the file was saved.
  • A Support link was clicked (a choice on the Support page, “Support MegaRows” in the footer, the Support link in the top bar or the phone menu, or a link on the support card shown after a download): only which of these links it was, never an amount or payment details.
  • The support card shown after a download came into view, or its “Not now” was pressed: only which of the two, never an amount, payment details or whether a payment was made. “Not now” and the thank-you page each save a mark in this browser so the card stays hidden (for the rest of the day, or for good). The marks are not sent with the counts.
  • An option in “Do more with this file” was chosen, or, while the “I want this” buttons were on the site, one of them was clicked (which upcoming tool, such as “Sort, filter and search”), even if no message was sent.
  • For the row counter, opening records the file-size range (such as 10–100 MB); finishing records ranges for file size, line count and time taken; failure records the error type and file-size range.
  • The sample of the row counter, the merge tool or the CSV splitter was tried (which of the tools). A sample is never counted as a counted, merged or split file.
  • A feedback message was sent (its type, such as “Bug”), or, while the waitlist was open, someone joined it (the interest they chose).
  • Our server set aside a feedback message or a waitlist signup that looked automated (which of the two forms, and which check it failed), never what was in it.
  • The plotter invitation card was shown or dismissed. Do Not Track, Global Privacy Control and the switch below stop these browser counts.
  • Dismissing the plotter invitation saves a preference in this browser so the card stays hidden. The preference is not sent with the counts.
  • The sign-in window opened or sign-in finished in this tab: where sign-in started (the homepage, plans page, header, account settings, the plotter, the plotter invitation card, Keep layout in the plotter's Do more menu, or directly), and email code, Google or Microsoft when known, with browser family and country; never an email address or account ID. Do Not Track, Global Privacy Control and the switch below stop these browser counts.
  • A sign-in, or linking Google or Microsoft to an account, did not succeed: whether it was by email code, Google or Microsoft, the step it stopped at (sending or checking the code, or going to or coming back from Google or Microsoft) and the reason, from a fixed list (for example “wrong or expired code” or “too many tries”, otherwise “other”), never the email address, the code, an account ID or the ID from Google or Microsoft. Our server makes this count, so the switch below cannot stop it; Do Not Track and Global Privacy Control do.

Each count also records the browser family (for example “Firefox”, without version) and the country, which Cloudflare derives from the connection. We never collect file names, file contents, column names, exact file sizes or row counts, email addresses, full browser details, the address of the page you came from or any ID, and we never store IP addresses: our server only uses yours for a moment to limit how often counts can be sent (see Hosting below). The counts use no cookies or local storage. The only thing kept in your browser for them is which of our pages your visit started on, in session storage, which your browser clears when you close the tab; it is the same for everyone who starts on that page, so the counts still cannot be linked to each other or to you. The counts are stored in Cloudflare Workers Analytics Engine and deleted after three months. We look at them as daily totals (for example, how many CSV files were opened yesterday), which we keep in our private back office.

Do Not Track and Global Privacy Control are honoured: if your browser sends either signal, the site sends no counts at all. We may also use Cloudflare Web Analytics, which is cookie-less as well, to measure page views and loading speed.

You can switch off the counts this browser sends by visiting megarows.com/?notrack=1. The switch cannot stop the two counts our server makes itself: a feedback message or a waitlist signup set aside as automated, and a sign-in, or linking Google or Microsoft to an account, that did not succeed. Do Not Track and Global Privacy Control stop those two as well.

Cookies and local storage

The free tools set no cookies. Signing in uses the necessary session and security cookies, which the account privacy notice explains. Your browser’s local storage remembers your light or dark theme choice, whether you switched off the anonymous counts, whether you have seen the plotter’s first tips, your chart settings (what the scroll wheel does and where the values at the cursor show) and, for the files you open in the plotter, your plot layout (with its event lines, limit lines and pinned values, whether values show on the measurement cursors, the data table’s sort and filters, including the values you filter by, which plots you opened in their own windows, with those windows' size and place on the screen, and whether the time axis is relative or the file’s own, with the clock the charts show date-times on) and math channels (including their formulas) and whether a file’s signals are split into channels (and, when you chose it, which column it is split by), so they come back when you open the same file, or the same files together, again, the widths you dragged the plotter’s side panels to, the height you dragged its data table to, whether its column list is open, with several files open the height you dragged their file list to, whether the channel list shows a channel that several files share once or once per file, and whether the plot legends show the file names, which MATLAB files you closed the list of variables for (so it does not open by itself for them again), whether CSV downloads write every digit of each number (“Full precision”), and the X axis you chose (or a suggested X you dismissed) for files with the same columns, kept as a code made from the column names and the column’s place among them, never a name or a value, for the last 50 sets of columns. While a saved layout opens, local and session storage also keep a short note of it (a code made from the file, never its name), so that a layout that stops the page from responding is skipped the next time; the note goes as soon as the layout has opened. Session storage holds the first page of your visit (see above) until you close the tab, and nothing of it while the anonymous counts are off. None of this ever leaves your device. You can clear all of it at any time on the Reset page.

Hosting

The website is served by Cloudflare. Like any web host, Cloudflare processes basic technical data (such as your IP address and browser type) to deliver the pages and protect them from abuse. To stop abuse, our server code briefly uses your connection’s address to limit how often forms and counts can be sent; the address is never stored or logged (the limit only counts a scrambled form of it, for a minute at a time). Your files are never part of this.

Waitlist

For signups made while the waitlist was open, the retained record contains the email address, the interest you chose (such as “Pro plan” or “Engineering formats”), the page you signed up on, the country Cloudflare derives from your connection, the time you signed up, and a record of your consent: that you ticked the box, with the exact wording and its version. The consent box was not preselected and read: “Email me about MegaRows launches and the Pro plan. Unsubscribe anytime by emailing hello@megarows.com.”

The signup was sent to megarows.com and is stored in our private back office, which only we can access. We use your email only to tell you about MegaRows launches and the Pro plan, as you agreed. We never sell or share it and never use it for advertising.

To unsubscribe, email hello@megarows.com at any time and we will take you off the list. You can also ask us to delete your signup completely.

Feedback

If you use the feedback form, we receive what you type, your email address if you choose to give one, the page you sent it from, the MegaRows version and a coarse browser and operating system label (for example “Chrome 140 on macOS”). It is sent to our own server at megarows.com and stored in our private back office. The form never adds your file names or file contents by itself. We use your email only to reply to you.

The message is free text, so we receive whatever you write in it, including any personal details you put there, such as your name, your company or something about your work. Please leave out anything you would rather we didn’t have, and don’t paste data from your files. If a MATLAB file holds objects the plotter can’t read yet, “Ask for these classes to be read” fills in the names of MATLAB’s own classes it found (such as containers.Map), never your own class or variable names; you see the text and can change it before sending.

Support payments

The choices on the Support page open a checkout page run by Stripe (Stripe Payments Europe, Limited, with Stripe Payments UK Ltd for regulated payment services), which takes your card or wallet details under the Stripe privacy policy. We never receive full card numbers.

From Stripe, we receive the email address and the name on the card entered at checkout, the billing country, the amount and date, whether the support is monthly, the payment reference, the card brand, last four digits, expiry date and issuing country (or the wallet used, such as Apple Pay), and the result of Stripe’s fraud checks, which can include an approximate location. We use these details to keep accounting records, answer questions about a payment and stop monthly support on request. The basis is the payment itself (contract) and the duty to keep accounting records (legal obligation). Kept for 5 years after the 31 January Self Assessment deadline for the tax year of the payment, as HMRC requires for business records.

Your personal data and your rights (UK GDPR)

The personal data we keep comes only from the two forms and from support payments, and only if you choose to send it:

  • Waitlist: your email address, the interest you chose, the page you signed up on, your country (which Cloudflare derives from your connection: the country only, never the address), the wording and version of the consent you agreed to, and the time you signed up.
  • Feedback: the type of message (such as “Bug”), what you write, your email address only if you add one, the page you sent it from, the MegaRows version, a coarse browser and operating system label (for example “Chrome 140 on macOS”), and the time you sent it.
  • Support payments: from Stripe, the email address and the name on the card entered at checkout, the billing country, the amount and date, whether the support is monthly, the payment reference, the card brand, last four digits, expiry date and issuing country (or the wallet used, such as Apple Pay), and the result of Stripe’s fraud checks, which can include an approximate location (see Support payments).

Using the tools needs no email, no account and no cookies. Like any web host, Cloudflare also processes basic technical data to deliver the site (see Hosting).

Why, and on what basis: for the waitlist, to email you about launches and the Pro plan, based on your consent, which you can withdraw at any time; for feedback, to reply to your message, based on our legitimate interest in answering you; for support payments, as set out under Support payments.

How long we keep it: waitlist emails until you unsubscribe or ask us to delete them; feedback emails only as long as needed to follow up, and no longer than 12 months; support payment records as set out under Support payments.

Who handles it: our hosting provider (Cloudflare) and the private back-office tool we use to manage requests store it on our behalf, and Stripe handles support payments (see Support payments). We never sell it or share it for anyone else’s marketing.

Your rights: you can ask to see, correct or delete your data, withdraw your consent, or object, by emailing hello@megarows.com. We reply within one month. You can also complain to the Information Commissioner’s Office (ico.org.uk).

The anonymous usage counts described above contain no personal data.

Contact

The personal data described here is collected by megarows.com (MegaRows), which is responsible for it. Questions about privacy? Email hello@megarows.com or . If this statement changes, we will update the date at the top of this page.

How you may use MegaRows is set out in our Terms of Use.