Account management · Regulations
Scheduling widget
The different cookies served through our scheduling widget are described in the table below:
| Cookie name | Cookie domain | Purpose | Cookie provider | Validity period | Personal data |
|---|---|---|---|---|---|
| JSESSIONID | Agendize server | Technical cookie | Agendize | Session only | |
| _pk_ses.* | Agendize server | Analytics | Matomo | 30 minutes | |
| _pk_id.* | Agendize server | Analytics | Matomo | 13 months | |
| _pk_ref.* | Agendize server | Analytics | Matomo | 6 months |
Backoffice
The different cookies served through our backoffice are described in the table below:
| Cookie name | Cookie domain | Purpose | Cookie provider | Validity period | Personal data |
|---|---|---|---|---|---|
| JSESSIONID | Agendize server | Technical cookie | Agendize | Session only | |
| az_active_user | Agendize server | Maintains user session authentication in backoffice | Agendize | 3 hours | Connected account |
| az_key_log | Agendize server | Maintains user session authentication in backoffice | Agendize | 3 hours | |
| az-cnx | .Agendize server | Maintains user session authentication in backoffice | Agendize | 6 hours | |
| az-access_token-v4 | .Agendize server | Enables API queries from the | Maintains | 6 hours | |
| favoriteCompany | Agendize server | Defines user's favorite location in the backoffice | Agendize | 1 day | Adresse email associée au compte client connecté |
| reporting.end.day | Agendize server | Absolute end date's day for reports in backoffice | Agendize | 1 day | |
| reporting.end.month | Agendize server | Absolute end date's month for reports in backoffice | Agendize | 1 day | |
| reporting.end.year | Agendize server | Absolute end date's year for reports in backoffice | Agendize | 1 day | |
| reporting.start.day | Agendize server | Absolute start date's day for reports in backoffice | Agendize | 1 day | |
| reporting.start.month | Agendize server | Absolute start date's month for reports in backoffice | Agendize | 1 day | |
| reporting.start.year | Agendize server | Absolute start date's year for reports in backoffice | Agendize | 1 day | |
| reporting.rate | Agendize server | Relative time period for reports in backoffice | Agendize | 1 day | |
| _pk_ses.* | Agendize server | Analytics | Matomo | 30 minutes | |
| _pk_id.* | Agendize server | Analytics | Matomo | 13 months |
Scheduling widget version 2 (obsolete)
The different cookies served through our former scheduling widget are described in the table below:
| Cookie name | Cookie domain | Purpose | Cookie provider | Validity period | Personal data |
|---|---|---|---|---|---|
| JSESSIONID | Agendize server | Technical cookie | Agendize | Session only | |
| _pk_ses.* | Agendize server | Analytics | Matomo | 30 minutes | |
| _pk_id.* | Agendize server | Analytics | Matomo | 13 months | |
booking.email | Agendize server | Pre-fills client's email address for next booking in scheduling widget | Agendize | 1 year | Client's email address booking an appointment |
booking.firstname | Agendize server | Pre-fills client's firstname for next booking in scheduling widget | Agendize | 1 year | Client's firstname booking an appointment |
booking.lastname | Agendize server | Pre-fills client's lastname for next booking in scheduling widget | Agendize | 1 year | Client's lastname booking an appointment |
booking.phone | Agendize server | Pre-fills client's phone number for next booking in scheduling widget | Agendize | 1 year | Client's phone number booking an appointment |
booking.waiting.list.subscribe | Agendize server | Sets client's default choice for waiting list registration for next booking in scheduling widget | Agendize | 1 year |