ONIRIKALAB APP
Privacy & Ethics
We build products that respect people. Privacy-first is not a slogan—it is a set of defaults.
THE PROMISE
A clear standard, not fine print.
Our goal is simple: minimize data, maximize clarity, and avoid manipulative design. If we ever collect data, we do it for a specific reason, explain it, and keep it limited.
We minimize data
We aim to keep personal data out of the product whenever possible. Features should work without building profiles or tracking behavior.
We keep it transparent
No hidden flows. No ambiguous buttons. No surprise permissions. Users should always understand what the app is doing.
We respect attention
We avoid addictive loops and dark patterns. Premium means calm, not noisy. You should feel in control, not “kept inside.”
ETHICS
Principles we design by.
These are the rules we follow across every product—apps, websites, and experiences.
No dark patterns
No forced urgency, no confusing opt-outs, no disguised ads, no “trick” buttons.
Default-safe choices
Defaults are conservative: minimal permissions, minimal collection, and clear user control.
Explainable UX
Every important action is understandable. If a feature affects privacy, we explain it in plain language.
Respect attention
Notifications should be useful, not addictive. We avoid spammy prompts and aggressive retention tactics.
DATA
What we may use—and why.
Different apps may require different inputs (e.g., reminders, local preferences). The rule stays the same: collect only what is necessary to deliver the feature.
Usually not needed
- Advertising identifiers
- Cross-app tracking
- Unnecessary location collection
- Building behavioral profiles
Sometimes needed
- Local settings (language, theme)
- Notifications (for reminders you enable)
- Basic diagnostics (to fix crashes)
- Optional analytics (strictly limited)
If analytics are enabled, they are kept minimal and used to improve stability and UX—not for advertising.
SECURITY
Secure defaults.
Security is part of design. We prefer simple architectures, reduce attack surface, and keep dependencies under control.
Least privilege
We request permissions only when a feature truly needs them—and only at the moment it matters.
Safe storage
Sensitive data should remain local when possible. If stored, it is protected with secure platform practices.
Maintenance
We keep codebases lean, dependencies reasonable, and update critical components when needed.
Questions about privacy?
Contact us for clarifications, collaborations, or support. We reply with clarity—no templates.