Data & privacy
This page explains how your modeling is stored and lets you manage its recovery settings. There is no account or server-side library of modelings.
How your modeling is stored
In your browser.
An opaque session identifier—not your modeling—is kept in the browser for up to
14 days. A small workspace index and preferences are kept in the
server-side django_session record for that session. Clearing the cookie makes stored recovery
copies unreachable from that browser, even before their server expiry.
For fast access. The latest saved modeling and available calculations stay in the fast Redis cache for up to 1 hour after the latest save. Reads do not extend that time, and eviction or infrastructure failure can remove this copy sooner.
For recovery. A smaller, inputs-only recovery copy is kept in live PostgreSQL for 12 hours after the latest save or retention change. If Redis has expired, the first recovery load can be slower while calculations are rebuilt. Expired recovery rows and server-side sessions are physically purged within 1 hour during normal service operation.
Workspace storage
0 B of 50 MB across the modelings in this browser session.
This is the latest successfully saved size, read from existing storage metadata. The 50 MB limit is a capacity policy for this shared public deployment; it is not an e-footprint modeling or file-format limit. A self-hosted installation can raise the limit to match its infrastructure.
Recovery retention
This choice applies to every modeling in this browser session. Expiry is measured from the latest save or retention change. Changing it updates the expiry of recovery copies that are still available; it does not extend the Redis hot cache.
Security
Operation and hosting. Operated by Boavizta. Clever Cloud is the data processor and hosting provider for the application containers, PostgreSQL, and Redis, hosted in Paris.
Transport. HTTPS protects data in transit between your browser and the application. TLS protection for the connection between the application and Redis is being set up. Until it is completed and verified, no encrypted-transport assurance is made for that connection.
Storage. Live PostgreSQL storage and the Redis hot cache are encrypted at rest.
Redis backups. Redis backups are being disabled. Until that change is completed and verified, no claim is made that provider backup or persistence is disabled.
PostgreSQL backups. Daily PostgreSQL backups are retained for seven days. They are separate from live recovery storage and are not encrypted at rest. Backup encryption is being set up. Until activation is completed and verified, treat the backups as unencrypted.
Backups are observed to run overnight, but their timing can vary. A short recovery period such as six hours normally expires before that window and reduces the chance of capture; it does not guarantee exclusion. Any modeling still stored when a backup runs can remain in that backup for up to seven days.
Contact. Security contact: vincent.villet@publicissapient.com.