This is a list of the categories of cookies used in our website and why we use them.
These cookies are required for the website
| check_expiration | All simulations are available for 3 months by default. The user can extend this period at will on its profile page. This cookie check if the period is comming to its end and warn the user to extend the storage period if they do not want their simulation to be deleted. |
|---|---|
| sessionid | A session ID cookie is a small piece of data stored on a user's device by a web application to uniquely identify and track a user's session during their interaction with the website or web application. It is used to maintain continuity and statefulness between different pages and actions within a session. When a user visits a website, the web server generates a unique session ID and sends it to the user's device as a cookie. This session ID is often a random string of characters. As the user navigates through the website, their browser includes the session ID in every request sent to the server. The server uses this session ID to associate the user's actions and data with their specific session on the server side. Session ID cookies are temporary and usually expire when the user closes their browser or after a certain period of inactivity. They play a crucial role in maintaining user authentication, preserving user preferences, and enabling a seamless and personalized browsing experience within a single session on a website or web application. |
| csrftoken | A CSRF cookie, also known as a Cross-Site Request Forgery cookie, is a security measure implemented in web applications to prevent Cross-Site Request Forgery attacks. These attacks involve malicious websites tricking users into unknowingly making unintended and potentially harmful actions on other websites where they are authenticated. The CSRF cookie typically contains a token that is unique to a user's session. When a user interacts with the web application, this token is included in requests to the server. The server then compares the token from the cookie with the token from the request to ensure that the action is legitimate and originates from the same user's session. If the tokens do not match or are missing, the server can reject the request, preventing unauthorized actions. In essence, a CSRF cookie helps safeguard against unauthorized actions being executed on a user's behalf without their knowledge or consent. |