Last updated: Draft — date to be confirmed.
1. Current codebase
The current Folentra public website code does not include analytics, advertising pixels or marketing-cookie tooling. If this changes, the notice and consent approach must be reviewed before deployment.
2. Authentication storage
The authenticated workspace uses Microsoft Entra and browser storage required by the Microsoft authentication library to maintain the signed-in session. Microsoft may also use its own necessary cookies on Microsoft-controlled domains during sign-in.
3. Workspace preferences
The workspace stores client-keyed navigation progress in local storage. The current Master File content page also stores section-status text locally. These values remain on the browser or device until cleared and are not used for advertising by the current codebase.
4. External demo scheduling
The Book a demo link may open an external scheduling provider. That provider’s own privacy and cookie notices apply when a visitor continues to its website.
5. Managing browser storage
Users can clear cookies and local storage through their browser settings. Doing so may sign the user out and can remove locally stored progress or working state.
6. Final review
This notice must be checked against the production deployment, configured authentication tenant and final scheduling provider before publication.