Skip to main content
AXIA Solutions

Personal data

Privacy policy

What we collect, why, for how long, and how to exercise your rights.

Last updated: 24 September 2026

Data controller

AXIA Solutions — Route de Sousse-M’saken 4070, Tunisia — contact@axiasolution.com

Data protection officer contact details: [À VALIDER PAR AXIA]

Data collected

The website only collects data through its forms.

Contact form: full name, company (optional), email address, phone, subject, related product (optional), message.

Partnership form: partnership type, company, full name, email address, phone, country, message.

Internship application: chosen topic, last name, first name, email address, phone, school or university, field of study, preferred topic, message and attached CV.

Purposes and legal basis

This data is used solely to handle your request: answering you, reviewing an application or a partnership proposal. The legal basis is your consent, collected through the checkbox on every form.

Retention periods

Contact messages and partnership requests: 24 months. Internship applications and CVs: 12 months.

These periods are website settings: the value shown here is the one applied.

Recipients

Your data is accessible only to the AXIA Solutions staff handling your request. CVs can only be downloaded by an administrator, and every download is logged. No data is sold or passed on for commercial purposes.

Cookies and audience measurement

The website sets no advertising cookie and no audience-measurement cookie.

Traffic is counted on the server, anonymously: only the day, the page and the language are recorded. No IP address, no visitor identifier, no cookie.

The Google Maps map on the contact page is only loaded after you explicitly click. Until you do, no request is sent to Google.

Your rights

You have the right to access, rectify, erase, restrict and object to the processing of your data, and to withdraw your consent at any time. To exercise these rights, write to contact@axiasolution.com.

Security

CVs are stored outside the public root of the website and renamed; they are only reachable through an authenticated request. Back-office passwords are hashed. Traffic to the website is encrypted over HTTPS.