CTDMM · Legal

Privacy Policy

Last updated: 2026-07-30

This page is maintained by CTDMM (Sauoaiga Benjamin Malatai, Owner & Founder, ABN 87 935 788 011) to describe how MioS handles your data.

Data we hold

• Account: email, authentication identifiers, sign-in provider (e.g. Google).
• Profile & Mika Memory: what you choose to save (name, preferences, notes).
• Artifacts & Signals: content you upload or generate inside the Vault, Signals, and Circle workspaces.
• Vault sensitive fields: encrypted client-side with a passphrase only you hold; ciphertext is all we store.
• Operational logs: minimal request logs for security and reliability.

How we use it

• To operate MioS for you (auth, storage, AI routing, team workspaces).
• To secure the service and investigate abuse.
• We do not sell your data. We do not train third-party foundation models on your content.

Subprocessors

• Lovable Cloud (Supabase-backed) — database, authentication, storage, edge functions.
• Lovable AI Gateway — model routing (Google Gemini, OpenAI) for chat, images, embeddings.
• Google OAuth — optional sign-in provider.

Data location & retention

Data is stored on managed infrastructure operated by our platform providers. You can delete artifacts, signals, memory, and your account at any time; deletions are permanent.

Your rights

Under the Australian Privacy Act (and equivalent laws where applicable), you can request access, correction, or deletion of your personal information. Email admin@ctdmm.com.

Security

Transport is TLS-encrypted. Database access is gated by row-level security so each Architect (and each Circle) can only reach their own rows. Vault sensitive fields are AES-GCM encrypted in the browser before upload.

Children

MioS is not directed to children under 16.

Contact

Owner: owner@ctdmm.com · Support: admin@ctdmm.com · www.ctdmm.com