Controls verifiable on the public website
The site is served over HTTPS. SMTP credentials used by the contact form are read server-side from environment variables and are not embedded in the client bundle. The form applies email validation, a bot-trap field, simple rate limiting and consent validation for enrolment.
- ✓ Server-side SMTP secrets
- ✓ Form validation and anti-abuse controls
- ✓ No personal form fields in NovaMind custom Analytics events
NovaMind governance
The stated design principle is to define scope before connecting tools: required access, allowed actions, forbidden actions, human owners and stop conditions. Sensitive decisions remain subject to an authorised person in the published scenarios and pilots.
What this page does not claim
We currently claim no public security certification. We do not present EU residency by default, automatic secret rotation, customer backup policy, disaster recovery or continuous log monitoring as verified until they are documented for the relevant configuration.
Before a production deployment
Scoping should document what is relevant to the project: hosting and region, data categories, retention, subprocessors, access rights, read/write separation, logging, backup and restore where applicable, deletion/export, incident handling and human responsibilities.
Report a security concern
Use contact@novalinkos.com with the subject “Security”. Do not include passwords, secrets or sensitive data in the first message.
NovaLinkOS Technologies SAS · NovaMind™ ·
contact@novalinkos.com