Local first
Processing and storage stay on the user's own device whenever the function can reasonably operate without a central service.
Our privacy principles
Less data. More control.
Mistirix products are designed around a simple engineering principle: if something can work locally, it should work locally. Data should only leave your device when there is a clear reason for it to do so.
Mistirix Engineering
Privacy starts with architecture
We do not treat privacy as a setting added after development. It influences how our products are designed from the beginning.
Data minimisation
We aim to request only the information required for a specific function. Information that is not needed should not be collected by default.
Minimal cloud dependence
Cloud infrastructure is used where it provides a necessary function, not simply because central storage is convenient.
User control
Wherever possible, users should remain in control of their own information, settings and devices instead of depending on Mistirix to hold everything centrally.
Data we do not need
Not every feature needs your identity
Many digital services begin by asking for an account, name, email address and other personal information. Mistirix takes the opposite approach: first determine what is technically necessary, then ask only for what the function actually requires.
Avoid collection before protecting collection
Security and encryption are important, but the safest unnecessary personal information is information that was never requested or centrally stored in the first place.
Product architecture
Different products. The same engineering principles.
TUSAVO and OVALIA serve very different purposes, but both follow the wider Mistirix approach to data minimisation and local-first engineering.
TUSAVO
Family configuration and safety settings are designed to remain local whenever possible. Central services should contain only the minimum information needed for functions that genuinely require them.
About TUSAVOOVALIA
The active personal record is designed to live primarily on the user's own device. Normal use should not depend on a central Ovalia account or remote copy of the complete record.
About OVALIAWhen cloud services are needed
Remote does not mean unlimited
Some functions cannot exist entirely on one device. Subscriptions, recovery, remote communication or other connected features may require external services. When that happens, the same minimisation principle still applies.
Purpose-specific
Server-side information should have a defined reason to exist and should support a specific product function.
Limited by design
A connected feature should not automatically turn the entire product into a cloud-first service.
Protected in transit
Where information must move between devices or services, the system is designed to use appropriate secure communication and encryption.
No secondary collection by default
Data collected for one necessary function should not silently become a general-purpose profile of the user.
Children and families
Extra care where children are involved
Products intended for families require particular restraint. Mistirix aims to keep children's information, family relationships and household settings out of central infrastructure unless a function genuinely cannot work without it.
Family data is not business data
Information about children and family life should not become a resource to collect simply because software makes that possible. Product requirements come first; collection follows only where necessary.
Security
Protect what must exist
Data minimisation reduces exposure, but information that does need to exist still requires appropriate protection. Security is therefore part of the same engineering approach rather than a separate concern.
Secure local storage
Sensitive local information is designed to use platform-appropriate protection instead of relying on plain application storage.
Encrypted communication
Connected functionality is designed so sensitive information can be protected while moving between trusted devices and services.
Recovery without central ownership
Where recovery is offered, the goal is to preserve user continuity without turning Mistirix into the permanent owner of the user's complete personal record.
Continuous review
Privacy and security assumptions should be reviewed as products and platform capabilities evolve.
Legal information
Product-specific policies will remain explicit
This page explains the engineering principles behind Mistirix products. Before public release, each product will also provide the formal privacy, data-processing and usage information required for the services it actually offers.
No hidden expansion of purpose
If a future Mistirix feature requires additional information or a different form of processing, that requirement should be made clear rather than being silently absorbed into a broad permission or generic privacy statement.
Mistirix
Collect less. Protect what remains.
Mistirix products are engineered to avoid unnecessary personal data in the first place.
Where a function does not need your name, email address or other identifying information, we prefer not to ask for it. Data that never needs to be collected does not need to be stored, transferred, secured or recovered later.
For the information that does need to exist, we design around appropriate protection: secure local storage, encrypted communication and carefully limited external processing.
This approach is better for privacy, simpler for us to secure and more efficient for the infrastructure behind our products.
Less central data means less storage, less unnecessary traffic and fewer systems running just to hold information nobody truly needed.
Because the greenest database is sometimes the one you never had to build.