Security at Melorite
Clear controls.
Careful claims.
Security depends on product scope, deployment and the data involved. We explain the controls that apply to your setup and do not claim certifications that have not been independently verified.
Protected connections
The public Melorite website is served over HTTPS. Product deployment, hosting and domain requirements are confirmed for each implementation.
Role-aware access
User roles and permission boundaries can be configured around agreed responsibilities so people work with the records relevant to them.
Data separation
Organisational records are designed to remain separated. The exact access model, hosting and isolation requirements are reviewed during setup.
During discovery
Confirm the controls your workflow needs.
The final security position belongs in the written scope, not in a generic marketing promise. File storage, backups, audit history and infrastructure responsibilities are documented for the implementation rather than assumed.
Roles and permission boundaries
Organisation and record access rules
Audit history required by the workflow
File handling and storage requirements
Backup and recovery expectations
Hosting and infrastructure responsibilities
Data import and export process
Incident and support contacts
Certifications and technology
Verify before relying.
Melorite does not claim SOC 2, ISO, HIPAA, GDPR certification or any other compliance certification on this page. Database, file storage, backup, retention and infrastructure choices can vary by implementation and should be confirmed in writing for your scope.
Ask a security questionDiscuss security in context.
Tell us what data, users and workflow are involved. We’ll address the relevant controls during product discovery.
Book a demo