# Telemetry

MeiliSearch collects anonymized data from users in order to improve our product. This can be deactivated at any time, and any data that has already been collected can be deleted on request.

# What tools do we use to collect and visualize data?

We use Segment (opens new window), a platform for data collection and management, to collect usage data. We then feed that data into Amplitude (opens new window), a tool for graphing and highlighting data, so that we can build visualizations according to our needs.

# What kind of data do we collect?

Our data collection is focused on the following categories:

  • System metrics, such as the technical specs of the device running MeiliSearch, the software version, and the OS
  • Performance metrics, such as the success rate of search requests and the average latency
  • Usage metrics, aimed at evaluating our newest features. These change with each new version

See below for the complete list of metrics we currently collect.

We will never:

  • Identify or track users
  • Collect personal information such as IP addresses, email addresses, or website URLs
  • Store data from documents added to a MeiliSearch instance

# Why collect telemetry data?

We collect telemetry data for only two reasons: so that we can improve our product, and so that we can continue working on this project full-time.

In order to create a better product, we need reliable quantitative information. The data we collect helps us fix bugs, evaluate the success of features, and better understand our users' needs.

We also need to prove that people are actually using MeiliSearch. Usage metrics help us justify our existence to investors so that we can keep this project alive.

# Why should you trust us?

Don't trust usโ€”hold us accountable. We feel that it is understandable, and in fact wise, to be distrustful of tech companies when it comes to your private data. That is why we attempt to maintain complete transparency about our data collection, provide an opt-out, and enable users to request the deletion of all their collected data at any time. In the absence of global data protection laws, we believe that this is the only ethical way to approach data collection.

No company is perfect. If you ever feel that we are being anything less than 100% transparent or collecting data that is infringing on your personal privacy, please let us know by emailing our dedicated account: privacy@meilisearch.com. Similarly, if you discover a data rights initiative or data protection tool that you think is relevant to us, please share it. We are passionate about this subject and take it very seriously.

# How to disable data collection

Data collection can be disabled at any time by setting a command-line option or environment variable, then restarting the MeiliSearch instance.

For more information about configuring MeiliSearch, read our configuration reference.

# How to delete all collected data

We, the MeiliSearch team, provide an email address so that users can request the complete removal of their data from all of our tools.

To do so, send an email to privacy@meilisearch.com containing the unique identifier generated for your MeiliSearch installation (Instance UID when launching MeiliSearch). Any questions regarding the management of the data we collect can also be sent to this email address.

# Exhaustive list of all collected data

Whenever an event is triggered that collects some piece of data, MeiliSearch does not send it immediately. Instead, it bundles it with other data in a batch of up to 500kb. Batches are sent either every hour, or after reaching 500kbโ€”whichever occurs first. This is done in order to improve performance and reduce network traffic.

Be advised!

This list is liable to change with every new version of MeiliSearch. It's not because we're trying to be sneaky! It's because when we add new features we need to collect additional datapoints to see how they perform.

Metric name Description Example
context.app.version MeiliSearch version number 0.23.0
infos.env MeiliSearch env production
infos.has_snapshot true if snapshots are activated, otherwise false true
system.distribution Distribution on which MeiliSearch is launched Arch Linux
system.kernel_version Kernel version on which MeiliSearch is launched 5.14.10
system.cores Number of cores 24
system.ram_size Total RAM capacity. Expressed in KB 16777216
system.disk_size Total capacity of the largest disk. Expressed in Bytes 1048576000
system.server_prodiver Users can tell us on which provider MeiliSearch is hosted by filling the MEILI_SERVER_PROVIDER env var. This is also filled by our cloud deploy scripts, e.g. GCP cloud-config.yaml (opens new window) gcp
stats.database_size Database size. Expressed in Bytes 2621440
stats.indexes_number Number of indexes 2
start_since_days Number of days since instance was launched 365
user_agent User-agent header encountered during API calls ["MeiliSearch Ruby (2.1)", "Ruby (3.0)"]
requests.99th_response_time Highest latency from among the fastest 99% of successful search requests 57ms
requests.total_succeeded Total number of successful search requests 3456
requests.total_failed Total number of failed search requests 24
requests.total_received Total number of received search requests 3480
sort.with_geoPoint true if the sort rule _geoPoint was used, otherwise false true
sort.avg_criteria_number Average number of sort criteria among all search requests containing the sort parameter 2
filter.with_geoRadius true if the filter rule _geoRadius was used, otherwise false false
filter.most_used_syntax Most used filter syntax among all search requests containing the filter parameter string
q.max_terms_number Highest number of terms given for the q parameter 5
pagination.max_limit Highest value given for the limit parameter 60
pagination.max_offset Highest value given for the offset parameter 1000
primary_key Name of primary key when explicitly set as part of document addition, document update, index creation, or index update. Otherwise null id
payload_type All values encountered in the Content-Type header, including invalid ones ["application/json", "text/plain", "application/x-ndjson"]
index_creation true if a document addition or update request triggered index creation, otherwise false true
ranking_rules.sort_position Position of the sort ranking rule 5
sortable_attributes.total Number of sortable attributes 3
sortable_attributes.has_geo true if _geo is set as a sortable attribute, otherwise false true
filterable_attributes.total Number of filterable attributes 3
filterable_attributes.has_geo true if _geo is set as a filterable attribute, otherwise false false
searchable_attributes.total Number of searchable attributes 4
per_task_uid true if a uid is used to fetch a particular task resource, otherwise false true