Skip to content

Last updated 9 November 2026

Account privacy

Files stay on the device. Sign-in creates an account record.

Account details and counts of signed-in activity help run workspaces, protect accounts and review payment disputes. File contents, file names, column names and values are never included in those records. Saved workspace layouts stay in this browser.

Read the free-tools privacy notice

Who is responsible

megarows.com (MegaRows) is responsible for account personal data. Privacy contact: hello@megarows.com.

Information held about an account

  • Email address, an account identifier and the selected sign-in method: email code, Google or Microsoft. Provider identifiers connect the chosen sign-in method to the account.
  • Session identifiers and times, coarse browser and operating-system labels, security records and temporary code verifiers. Codes are single-use and expire after five minutes.
  • Sign-in times, method, device class and country; active UTC days; daily counts of charts drawn, files opened, workspace saves and exports. These are account-linked counts, not anonymous analytics.
  • The Terms version accepted, the account privacy notice version presented and the recorded time.

Counts come from the browser and may be incomplete. Counts alone do not prove what a file contained or justify refusing a refund. No automatic refund decision is made from these counts.

A failed sign-in, or a failed link to Google or Microsoft, is also counted anonymously, without the email address or the account, as one of the usage counts listed in the free-tools privacy notice.

Network addresses and basic browser information are processed to deliver the service and prevent abuse. Account rate-limit records use derived keys rather than storing the full network address in the activity record.

An email address and sign-in information are needed for an account. Without an account, the free tools remain available. Signing in does not subscribe an email address to marketing.

Files, workspaces and cookies

File processing happens on the device. Sign-in and workspace saving do not upload file contents, names, columns, values or paths. Workspaces are saved in this browser, not synchronised through an online account. Opening a saved workspace can require selecting the original files again.

Sign-in uses necessary session and security cookies. The session cookie normally lasts seven days and can renew during use, with a maximum session age of 30 days. The sign-in security cookie lasts up to one hour. Provider sign-in also uses short-lived security cookies. These cookies do not serve advertising.

The anonymous-counts switch described in the free-tools notice does not switch off the account activity record. Account activity is separate from anonymous site analytics. Deleting an account does not erase original files or locally saved workspaces; browser storage can be cleared separately.

Purposes and lawful bases

Contract: providing requested account access, sign-in messages and workspace-plan access. Legitimate interests: proportionate account security, fraud prevention and human review of payment disputes.

The privacy notice explains data use; it is not consent to unrelated processing. Any optional marketing needs a separate choice.

Service providers and international transfers

Cloudflare provides hosting and account database infrastructure. Brevo delivers sign-in and security emails. Selecting Google or Microsoft opens that provider’s sign-in process; provider handling is also explained in Google’s privacy notice and Microsoft’s privacy statement.

Stripe is the payment provider, under the Stripe privacy policy. Optional support payments already go through Stripe’s checkout (Support payments in the free-tools notice); plan payments are not available yet. Stripe handles card details. For plan payments, MegaRows will receive payment status and transaction references, not full card details; what support payments share is listed under Support payments.

Account records are kept in a Cloudflare database located in the European Union. A database location alone does not establish where every provider processes data: Cloudflare, Brevo, Google, Microsoft and Stripe may also process data in other countries, including the United States. For the safeguards that apply to these transfers, or a copy of them, email hello@megarows.com.

Retention and deletion

Account identity information remains while the account exists. Activity and agreement records are removed by daily maintenance 18 months after the last payment, or after signup if no payment has been made. Deleting an account removes ordinary activity sooner. Records needed for an active dispute are held until that hold is released, then the normal deletion rules apply.

Expired sessions and code records are removed by daily maintenance. Security audit entries become eligible for daily deletion after 30 days, and known-device entries after 90 days without use. Cloudflare keeps restore points of the account database for up to 30 days; after that, a deleted record can no longer be restored.

Access, correction and deletion

On the Account page, Export downloads account records as JSON, Change email corrects the account email after verification, and Delete account requests a fresh code before deletion. Sign out everywhere ends active sessions.

Access, correction, deletion, restriction and portability rights depend on the circumstances. For other requests or help with the controls, email hello@megarows.com. Identity verification may be needed. The usual response period for a rights request is one month, with any lawful extension explained.

The right to object

Object to processing based on legitimate interests by emailing hello@megarows.com. Explain the circumstances so the request can be reviewed. This right is separate from account deletion.

Complaints

Privacy complaints can be sent to hello@megarows.com. A complaint can also be raised with the Information Commissioner’s Office.

Related notices

Free-tools privacy notice · Terms of Use