Cookie Policy
In optimizing product experience, we utilize cookies for specific functionalities.
Cookie Policy Updates
We may update this policy by posting the new version here. Personal notifications are not provided, so please check this page periodically. The effective date is at the top.
Cookies
Cookies are compact text files stored on user devices.
Two cookie definitions follow next to learn more.
From Google:
Cookies are small pieces of text sent to your browser by a website you visit. They help that website remember information about your visit, which can both make it easier to visit the site again and make the site more useful to you.
Source: How Google Uses Cookies | Google
From the GDPR (General Data Protection Regulation):
Cookies are an important tool that can give businesses a great deal of insight into their users’ online activity.
Cookies are small text files that websites place on your device as you are browsing. They are processed and stored by your web browser.
Source: Cookies, the GDPR, and the ePrivacy Directive | GDPR.eu
You can read the GDPR cookies page to learn more about cookies and their types.
Cookie Types
A brief framework of cookie types related to this notice is given to understand their purpose.
Cookies by Domain
First-Party Cookies: These are set by the domain you are visiting and are often used for essential functionality, such as secure log-in and preference settings.
Third-Party Cookies: These are set by domains other than the one you are visiting and are often used for analytical purposes.
Cookies by Purpose
Cookies are used for various purposes or categories.
Essential Cookies: These are necessary for the website or web app to function properly and do not require user consent. They typically store session information or user preferences. The website cannot be used properly without these strictly necessary cookies.
Functional Cookies: These enhance the website or web app performance as certain functions may not be available without them. They allow users to remember their preferences and settings, provide a personalized user experience, are anonymous, be first-party or set by third-party service providers, and do not track browsing activity across other websites. For example, cookies that remember user location, chosen language, or other settings, a live web chat platform, and optional security parameters like a single sign-on (SSO).
Analytical Cookies: These cookies collect data on how users interact with the website or web app, including metrics like page views, bounce rates, and traffic sources. They cannot be used to directly identify a certain visitor. They help website owners understand and improve site performance.
Targeting Cookies: These are used to identify visitors between different websites and may be used by companies to build a profile of visitor interests or show relevant ads on other websites, and are usually third-party. They are used on a limited basis, and we do not use them to serve third-party ads on our websites or web apps. For example, cookies installed by YouTube in videos embedded into our site to track their views and user preferences.
Updating your Cookie Preference
You can always set your consent via the Cookie Banner or Customization Pane.
You can update your preferences by clicking the "Cookie Preference" button at the page footer. It will show the Cookie Banner, and if you want to open the Customization Pane, you can do it from the Banner.
You can quickly set your choices with the Cookie Banner, while its Customization Pane shows you granular information and options.
Cookies Used
The specific cookies used across MathSwe websites or web apps are listed.
MathSwe Domains
MathSwe domains with their respective subdomains follow.| Domain | Subdomains |
|---|---|
| mathswe.com | |
| math.software | tsd, rsm, ops |
| mathsoftware.engineer | blog, dev, me |
For example, rsm.math.software is a subdomain of math.software.
When a domain and all its subdomains use a cookie, then a *. wildcard will denote them. For example, *.math.software defines math.software and all its subdomains.
The given domains, subdomains, and wildcard ("*.") allow denoting the websites or web apps using a particular cookie.
First-Party Cookies
| Cookie | Description | Provider | Retention | Purpose | When Visiting |
|---|---|---|---|---|---|
| cookie-consent | Stores the visitor's cookie consent with their preferences and consent ID. The cookie banner and customization pane needs it to work. | 1 year | essential | *.mathswe.com, *.math.software, *.mathsoftware.engineer |
Cookies set by Third-Parties
The following cookies are stored as first-party but set and managed by third-party providers.
Cookies set by Google
| Cookie | Description | Provider | Retention | Purpose | When Visiting |
|---|---|---|---|---|---|
| _ga | Used to distinguish users. It is the main cookie used by Google Analytics, which enables the service to distinguish one visitor from another. Each ‘_ga’ cookie is unique to the specific property, so it cannot be used to track a given user or browser across unrelated websites. | 2 years | analytical | *.mathswe.com, *.math.software, *.mathsoftware.engineer | |
| _ga_<container-id> | Used to persist session state. | 2 years | analytical | *.mathswe.com, *.math.software, *.mathsoftware.engineer |
Cookie Consent Record
When you set your cookie preference, the system processes your request and gives an ID representing your consent. You can check your consent ID from the Cookie Banner and find more information from the Customization Pane.
The purpose of consent records is not to collect personal data but to store the record when you give consent, so we comply with data regulations, like the GDPR. Consent records minimize the data stored as much as possible to avoid collecting personal data.
- ID: Universal unique ID the system assigns to each cookie consent record.
- Domain: The MathSwe website/web app that requests your cookie consent.
- Preference: Cookies you choose in the banner per purpose (functional, analytical, and targeting).
- Creation Date: When the server made the consent effective (i.e., when you set your preference). Further, it is crucial when deducing the information, like the effective cookie policy at that time, that the site presents to you when giving consent.
- Geolocation: Includes the time zone, country, city, and region/region code to know the cookie laws that apply to your place.
- Anonymous IP: Your IPv4 address with the last digit anonymized. For example, the IP
x.y.z.wbecomesx.y.z.0to minimize the data collected. Handling the full IP is avoided in the process as much as possible. - User Agent: Your browser user agent.
The consent proof shows there is a process where you give consent transparently.
The website/web app stores the server response after making your consent effective in the cookie-consent cookie to remember it, as described above in the first-party cookies.
The information stored in your browser (cookie-consent) is the consent ID, preference, creation date, and geolocation.
Storing consent proofs allows websites that use cookies to comply with data privacy laws, such as the GDPR.