Tabulys
Compare Monthly replay Security Log in

Legal

Privacy policy

Tabulys compares your files in your browser: their content never reaches us. This policy describes the little data the site does handle, why, for how long, and who helps us run it.

Who is responsible

The controller of the data described here is the publisher of Tabulys: Sebastien Bourreau EI, trade name Logalysm, 8 bis rue Abel, 75012 Paris, France. Write to contact@tabulys.com for any question about this policy or to exercise your rights. The full identification of the publisher and of the host is in the legal notice.

This policy is written under the General Data Protection Regulation (GDPR): the publisher is established in France, and its supervisory authority is the CNIL. It also covers visitors protected by the UK GDPR and by the Canadian PIPEDA.

Your files stay in your browser

Your files are read and compared locally, in your browser, and are never sent: not to our server, not to anyone else. This is a commitment of the publisher, also written in the terms of use.

The names of your columns are never sent, and cannot be found again from what is sent. The audience measurement below carries only an HMAC-SHA-256 of the column names of each file, computed with a random key that is drawn in your browser, kept there, and never sent.

The security page lists every request the site sends and explains how to check this yourself.

Audience measurement

Its only purpose is the audience measurement of the publisher: counting how the comparison is used, to decide what to build next. Its data is never cross-referenced with other data and never transmitted to anyone.

The site sends one of these five events when it happens, each with these fields and no other; the server refuses any event that does not match them:

  • comparison_done, once per comparison that reaches a result: event_name, browser_id, schema_hash_a, schema_hash_b, entry_page, referrer_category, browser_family, row_band, duration_in_milliseconds, engine_version.
  • export_done, once per export of a result: event_name, browser_id, export_format.
  • save_clicked, once per click on “Save for next month”: event_name, browser_id, schema_hash_a, schema_hash_b, entry_page, browser_family.
  • waitlist_joined, once per accepted sign-up to the waiting list, without any identifier: event_name.
  • import_failed, when a file cannot be read or a comparison cannot complete, without any identifier: event_name, file_type, failure_cause.

browser_id is a random identifier drawn by your browser at your first comparison; schema_hash_a and schema_hash_b are the keyed hashes of the column names described above; entry_page is the path of the first page you visited, without its query string; referrer_category says only whether that visit came from a search engine, an AI assistant, another site or nowhere. The security page describes every field and its allowed values.

The local storage of your browser keeps one record for this measurement: the date of your first visit, the path of that first page, the category of its referrer until it is sent, and, from your first comparison, the identifier and the key. The record is used 13 months at most from that date, never extended by a later visit; past them it is no longer used, and the site erases it the next time it reads it. A new record starts at your next visit.

The server stores each event with its day of arrival and no time, client address or other request data. An event is deleted 25 months at most after that day; a deleted event can remain in the backups of the database for as long as they are kept, as described below.

The site shows no consent banner, and this is why: this measurement is exempt from consent, as the CNIL allows for audience measurement used by the publisher alone, for this purpose alone, never cross-referenced nor transmitted, with an identifier of limited lifetime and the right to object. The legal basis of this processing is the legitimate interest of the publisher in measuring the use of its site.

Opting out

At the bottom of every page, the “Opt out of audience measurement” button stops every event. It erases the identifier and the key from your browser and leaves a mark there that the site reads before sending anything. This mark belongs to your browser: clearing the data of the site, or using another browser, removes it.

The waiting list

When you join the waiting list of the monthly replay, your email address is relayed to Brevo, which sends you a confirmation email: you are on the list only once you confirm (double opt-in). Tabulys does not store your address, and associates no identifier nor hash with it: the waitlist_joined event carries none.

The legal basis is your consent, given by the box you tick in the form. You can withdraw it at any time, by the unsubscribe link of the emails sent to the list or by writing to contact@tabulys.com. The address stays on the list, kept by Brevo for the publisher, until you withdraw it.

The logs of the server

The server keeps logs to run the site and protect it, on the basis of the legitimate interest of the publisher:

  • The web server log of the other requests, the page that confirms your place on the waiting list included, the icons of the site and the probes of the monitoring aside: your IP address, the date, the method and the path without query string, the status and the size of the answer, its duration, the referring page without query string and the browser identification cut to 120 characters. Its error log also holds the IP address. Both are kept 14 days.
  • The requests of the audience measurement (POST /telemetry) and of the waiting list (POST /waitlist) are logged without IP address, referring page, browser identification nor query string: only the date, the method, the path and the status. Their errors below the most severe level, which would carry the client address, are not written.
  • The application log holds the warnings and the errors of the application, kept 365 days. A line of this log can carry the fields of the form that was being submitted, passwords and tokens masked: for instance the email address typed into the log-in form. The waiting list form is not one of them, its address is never written there.
  • A copy of the errors is also written to the log of each container of the server, capped at 50 MB per service, the oldest lines removed first.

What the site stores in your browser

  • In the local storage, the record of the audience measurement described above (tabulys.visitor), and the mark of your opt-out (tabulys.opt_out). This measurement is exempt from consent.
  • In the session storage of the tab, during a comparison, a marker (tabulys.interrupted_comparison) that holds the role, the type and the size band of each file, never its name nor its content: if the page stops during the comparison, it can explain why when reopened in the same tab. The browser erases it with the tab.
  • One cookie, PHPSESSID, set only by the log-in page: it protects the form and keeps you logged in. No other page sets a cookie for a visitor who has not logged in.

The marker and the cookie are strictly necessary to the service you ask for, and need no consent.

Backups

The database, which holds the audience measurement events, is backed up every day. The server keeps its own copy of each backup, not encrypted, 7 days. Each backup is encrypted on the server before it is sent to Koofr, which never receives the key, and is kept there 15 days.

Who helps us run the site

Four processors act on behalf of the publisher, all established in the European Union:

  • OVH SAS, Roubaix, France: hosts the server of the site, in its data centre of Beauharnois, Canada, and the mailboxes of the publisher.
  • Brevo (Sendinblue SAS), Paris, France: sends the confirmation email of the waiting list and keeps the list, in the Tabulys account of the publisher.
  • Koofr d.o.o., Slovenia: stores the encrypted daily backups of the database, without ever receiving their key.
  • Better Stack s.r.o., Czech Republic: monitors that the site answers; it receives no data about visitors and holds only the account of the publisher.

The server of the site is in Canada, in the data centre of OVH SAS in Beauharnois: the data it holds, described above, is transferred there. The European Commission has decided that Canada ensures an adequate level of protection of personal data (decision 2002/2/EC), which allows this transfer without other safeguards.

Your rights

You can ask for access to your data, its rectification or its erasure, the restriction of its processing or its portability, and object to its processing, by writing to contact@tabulys.com. You will get an answer within one month. The identifier of the audience measurement is drawn by your browser and never tied to your name: we can find its events only if you send it to us.

If you think your rights are not respected, you can lodge a complaint with the CNIL, 3 place de Fontenoy, TSA 80715, 75334 Paris Cedex 07, France, www.cnil.fr.

On this page

Who is responsible Your files stay in your browser Audience measurement The waiting list The logs of the server What the site stores in your browser Backups Who helps us run the site Your rights
Tabulys

Start

Compare two files Monthly replay Log in

Your files

Verify what leaves your browser

Legal

Legal notice Terms of use Privacy policy
A service by Logalysm