Arkevia is based on a digital safe designed to receive dematerialized pay slips and HR documents transmitted by the employer. The service, published under the MyArkevia brand, is aimed at employees whose company has chosen this solution to archive pay slips, employment contracts, amendments, or certificates. Accessing the Arkevia my account space requires understanding both the initial activation process and the security mechanisms that govern the storage of these sensitive documents.
AES-256 Encryption and Archiving Standards on Arkevia
Most connection guides to MyArkevia simply explain where to click. They overlook the technical infrastructure that underpins the reliability of the service. The documents stored in the safe are encrypted with the AES-256 algorithm, a level deemed banking-grade. This encryption standard is used by financial institutions and administrations to protect classified data.
The archiving architecture is certified NF Z42-013, the French reference standard for electronic archiving with probative value. The data centers also comply with the ISO/IEC 27001 standard for information security management. The servers are located in France, placing the entire system under GDPR jurisdiction without transferring data outside the European Union.
These three pillars (encryption, archiving certification, national hosting) distinguish MyArkevia from simple public cloud storage. An employee who accepts the dematerialization of their pay slips entrusts their documents to an infrastructure whose regulatory framework guarantees their integrity for the legal retention period.
To better understand the daily operation and connection steps, the access to the Arkevia my account space details the complete journey from activation to document retrieval.
Activation of the MyArkevia Account: What the Employer Really Triggers
The employee does not create their MyArkevia account on their own initiative. It is the employer who initiates the process by sending an invitation via email. This email contains an activation link and a temporary code. Without this invitation, access to the service is impossible.
The legal framework precisely governs this step. Since the Labor Law of 2016 (Article L3243-2 of the Labor Code), the employer can dematerialize pay slips by default, unless there is explicit opposition from the employee. The employee has a thirty-day period to refuse dematerialization after notification. After this period without opposition, the electronic pay slip replaces the paper format.
Several points deserve attention during activation:
- The invitation email often ends up in spam, especially on corporate email accounts with strict filters. Checking the spam folder before contacting HR avoids unnecessary back-and-forth.
- The activation link has a limited validity period. If the deadline is exceeded, a resend must be requested from the employer or HR, as the user cannot generate a new invitation themselves.
- The password chosen during activation must meet complexity criteria (uppercase, lowercase, numbers, special characters). This password is specific to the safe and should not be the same as the professional email password.
Connecting to MyArkevia and Managing Dematerialized Pay Slips
Two addresses coexist: myarkevia.com for employees (professional access) and arkevia.com for individuals using the safe for personal purposes. Confusion between the two portals is common and leads to identifier errors.
The standard connection requires the email address provided during activation and the associated password. In case of forgetfulness, the reset procedure sends a link to this same email address. If the employee has changed their email address since activation (leaving the company, changing providers), recovery becomes more complex and requires direct contact with Arkevia support.
Document Retention After Leaving the Company
A point often misunderstood: the MyArkevia safe remains accessible to the employee even after the end of the employment contract. Archived pay slips are retained for fifty years or until the holder turns seventy-five, in accordance with legal obligations. The former employer cannot delete or modify documents already deposited.
The employee retains their personal identifiers. They can continue to view, download, or share their documents from their space. However, no new documents will be deposited by the former employer after the contract ends.
Limitations and Gray Areas of the Arkevia Digital Safe
The technical robustness of the service should not overshadow certain practical limitations. The MyArkevia interface remains plain, if not austere. The classification of documents relies on categories predefined by the employer, and the employee has limited leeway to reorganize their files according to their own logic.
Depositing personal documents (diplomas, rent receipts, identity documents) is possible, but the allocated storage space varies depending on the contracts subscribed to by the employer. Field feedback varies on this point: some users report ample space, while others encounter limitations that force them to choose between documents.
The mobile application exists, but its ergonomics lag behind current standards. Navigation requires several steps to reach a specific document, whereas competitors like Digiposte or PeopleDoc offer more direct paths.
The question of data portability in the event of a change of provider by the employer also deserves to be raised. If a company decides to migrate to another digital safe, the transfer of documents already archived in MyArkevia is not automatic. The employee should regularly download their pay slips to have a local copy independent of the provider chosen by their employer.
MyArkevia fulfills its role of secure archiving with a solid regulatory framework. The real fragility of the system lies not in the technology, but in the dependence on the employer’s choice: the employee has no control over activation, migration, or the allocated storage space. Keeping a local copy of each document remains the most concrete precaution.