Security & privacy
Uploaded files are somebody's customers
Names, phone numbers, addresses and email addresses deserve careful handling. These are the principles Informatt is built around.
Per-user data isolation
Every project, file and processing artefact belongs to exactly one account. Access is enforced at the data layer, not only in the interface.
Immutable source files
An uploaded file is never edited in place. Processing writes new derived versions, so you can always return to what you gave us.
Retention and deletion
Projects carry a retention window. When it elapses, uploaded files and derived data are removed on a schedule you control.
Encryption in transit and at rest
Files are transferred over TLS and stored encrypted. Access to storage is scoped to the owning account.
Minimal exposure
Previews are sampled, logs exclude record contents, and processing output is only rendered to the account that owns it.
Background processing boundaries
Large datasets are processed server-side in batches, so full customer datasets are never held in browser memory.
Current stage: prototype
Informatt is in an early interface-first stage. Authentication, storage and the processing engine are not yet connected, and the workspace runs on sample data. Please do not upload real customer records until we announce that production data handling is live.