Signed JSON
The internal document keeps an HMAC-SHA-256 signature that verifies integrity before the plan is loaded.
Work and financial planning
Security designed for sensitive personal information
Backup confidentiality, password derivation and JSON integrity are verified through separate controls.
SchedulesFinancesAlarmsFinancial AIAES-256-GCM
7 daysVisible week
HMAC + AESSecure backup
Password → Argon2id
The password is not used directly as an AES key. Argon2id derives a 256-bit key using a cryptographic salt.
AES-256-GCM
When protection is active, the complete signed JSON is stored inside an authenticated AES-GCM container.
Import verification
The system authenticates and decrypts AES-GCM, recovers the JSON and then requires a valid HMAC before replacing current data.
AI and privacy
Financial analysis shares only a reduced summary
When the user requests an analysis, WorkFlow Planner Pro calculates and selects the indicators required to build a compact financial payload. The full backup, HMAC signature, encryption keys, passwords and session data are not part of that request.
Explicit request
Analysis starts only when the user requests it from the Dashboard.
Application-calculated data
The application calculates the figures and AI is limited to interpreting the indicators it receives.
Data minimization
A compact financial contract is sent instead of the complete operational JSON.
Principles
Optional protection without backdoors
User password
There is no master recovery password for opening an AES backup if the password is lost.
Temporary session
The password can be kept temporarily during the session for future exports and is removed when the session ends.
Compatibility
Unencrypted backups remain valid when they meet the required structure and signature rules.