Security
Security starts with fewer unnecessary moving parts.
For launch, the public website is static-first and intentionally avoids accounts, dashboards, payment forms and unneeded client-side tracking.
Static public site
The marketing website is built as static HTML, CSS and assets, reducing server-side attack surface.
No public account area
The launch website does not include login, account management or stored user profiles.
No payment flow yet
Pricing and payment can be added only after the product and legal pages are ready.
Security headers
Cloudflare Pages headers are included for baseline browser hardening.
Careful product claims
The site avoids unverified words like zero-knowledge, compliant or military-grade.
Local-first direction
MemoryVault is positioned around storage the user controls, not forced cloud dependency.
Security language policy
Cenuzo should only publish security claims that can be supported by implementation details, documentation and review. Until then, the website should use accurate product-direction language: local-first, privacy by design, no mandatory cloud and minimal collection.
Safe today
Designed for local-first backup. No mandatory cloud. Website has no account area.
Avoid until proven
Zero-knowledge, end-to-end encrypted, compliant, military-grade or guaranteed recovery.
Questions about Cenuzo security?
Use the contact page or email security directly for security, product and launch questions.