# Data & Legal

{% tabs %}
{% tab title="Data Management" %}

## Everything is anonymous by default <a href="#id-1-everything-is-anonym-by-default" id="id-1-everything-is-anonym-by-default"></a>

We do not collect data (IP, location, browser, etc.). In fact, by default, your users will all be anonymous when interacting with in-app experiences (views, votes, etc.) or on your changelog portal.\
\
However, some features may require specific data.\
\
**For example**, if you want to use our segmentation feature, you must send data to us. You don't need to send personal data for segmentation to work. Let’s say you want to push experiences only to your paying users, then you simply send the data "paying user" which is not considered personal data in this case.

***

## But personal data can be pushed <a href="#id-1-but-personal-data-can-be-pushed" id="id-1-but-personal-data-can-be-pushed"></a>

Personal data becomes a subject when it comes to identifying users.\
\
For example, if you want to know who responded to a survey, viewed an experience, or even created a segment based on personal information, you must send personal data to see it in your Jimo dashboard. Identification is not implemented by default. To implement it, you must ask your developers to add code in your app to send identification data (username, email, etc.) to Jimo. As long as your tech team doesn’t add this mechanism to your website, no personal data is present on Jimo.

***

## About our database infrastructure <a href="#id-1-about-our-database-infrastructure" id="id-1-about-our-database-infrastructure"></a>

Our databases are encrypted and only accessible by the systems inside our infrastructure. Firewalls make sure that only authorized systems have network access to our database.\
\
We perform daily database backups to recover if any issues put our service down. Those backups are stored for a maximum of 14 days and are encrypted.<br>

{% hint style="info" %}
Get more info on our **service terms** and **privacy (RGPD)** on our landing page:

* <https://www.usejimo.com/terms-services>
* <https://www.usejimo.com/privacy>
  {% endhint %}
  {% endtab %}

{% tab title="Mgmt of payment information" %}
Storage of payment information such as card number, CVC, or expiration date is made by [Stripe](https://stripe.com/en-fr), our payment infrastructure partner.\
\
Stripe is a popular payment infrastructure, a leader in online payment processing, which provides a fully secure way to handle payment and store payment information.\
\
Having that said, Jimo still stores those three pieces of information :\
\
\- Last four numbers of the card number\
\- Brand of the card number (Visa, MasterCard, etc.)\
\- Name of the cardholder\
\
We store that information so we can easily display it as you may need it during your navigation.\
\
Feel free to [contact us](mailto:sam@usejimo.com) if you have any questions about payment!
{% endtab %}

{% tab title="Cookies created" %}
After Jimo is installed on your platform, you might see some cookies being created. All our cookies are **functional** cookies only. They are part of the core system and do not serve some third-party logic.

You will find a list of the cookies in [our Cookie Policy](https://www.usejimo.com/cookie-policy#5).
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.usejimo.com/docs/data-and-legal/data-and-legal.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.