Information can be useful only when people can handle it with confidence. Security at Quiix is therefore treated as part of the product design, not as an optional layer added at the end.
Protection at several levels
A secure application needs more than a password screen. Account controls, session handling, permission checks, safe uploads, database access and responsible deployment practices must work together. Each layer reduces a different kind of risk.
Access and ownership
Quiix checks who is signed in and whether that person is allowed to reach the requested dataset, record or administrative function. Ownership and membership rules help prevent information from crossing boundaries simply because someone knows an address or identifier.
Encryption for files and selected text
Supported uploaded files are encrypted before storage when the server encryption key is configured. Selected record text can also be encrypted at the user's choice. Encrypted text is deliberately excluded from search because the server does not keep a searchable plain-text copy.
The encryption key must be stored outside the public web directory and backed up securely. Losing it can make encrypted material impossible to recover; exposing it weakens the protection it provides.
Safer uploads and deletion
File handling validates permitted types, controls size and uses generated storage names. When a record is permanently removed from the recycle bin, its associated stored files should also be removed so that deleted information is not silently left behind.
Security is an ongoing practice
No system becomes secure once and stays that way automatically. Updates, reviews, backups, server configuration and careful administration remain essential. Quiix provides technical safeguards, while operators retain responsibility for protecting credentials, encryption keys and infrastructure.
Our aim is straightforward: sensible protection, clear limitations and fewer hidden assumptions about the safety of important information.