ModunOS

Privacy Policy

Privacy on ModunOS is an architectural property: the platform should not need to possess your private life merely because it can connect you. This page explains what that means in practice today — and what we still keep precise for legal clarity.

Last updated: September 2026. Soft release — practices evolve as features harden; we will update this page when they do.

This page is the human-readable explanation of our privacy practices, plus the operative policy summary for soft release. It is not legal advice. As ModunOS grows (messaging, mail, encrypted vaults, stronger rights tools), sections below will expand — without pretending unfinished work is already shipped.

Who operates ModunOS

ModunOS is operated by Modun Systems (founder Charles Arden, United Kingdom). ModunOS / Modunos are product and website brands — not separate companies. Contact: [email protected] (general: [email protected]). Companies House / registered address details will be published when incorporation or sole-trader registration outcomes are finalised.

Where does your data live?

ModunOS distinguishes your private workspace, ModunOS Core (what the platform needs to run accounts, security, and services you use), and public content you deliberately publish.

Private

Your files, app saves, settings, and local AI threads when they stay on your device — or, if you sign in and save to the cloud, on ModunOS storage under your account.

ModunOS Core

Account identity, authentication, subscription/tier state, security and delivery metadata needed to operate the service.

Public

Profiles, spaces, and assets you choose to publish. Existing on ModunOS does not make something public by itself.

Guest mode lets you try many surfaces without a cloud personal ledger. Connected (signed-in) mode syncs saved data to ModunOS so it follows your account. Download / desktop shells use the same modes: privacy follows whether you are connected, not the window chrome alone.

What ModunOS Core knows

Identity — account identifiers, username, email, authentication state, and public handle where applicable.
Eligibility — date of birth and country/region used to enforce age rules (including COPPA- and GDPR-oriented minimums).
Service — subscription or tier status and entitlements required to provide paid features.
Security & operations — authentication and abuse-related signals, connection metadata needed to deliver the service, and limited error/presence telemetry.
What you sync or send — citizen cloud files, social messages, and AI requests you choose to use (see below).

We design ModunOS to minimise information permanently retained by ModunOS beyond what is needed for the functions above. We do not claim that infrastructure never sees requests: edge networks and servers necessarily process connection data while you use the service.

Categories of information

Category	Examples	Typical home
Account	Username, email, password hash, date of birth, country	ModunOS Core (servers)
Personal workspace	Saved Garage / Health preferences, uploaded files, layouts	Your device cache and/or ModunOS cloud storage when signed in
Messages & social	Friend links, direct messages, delivery state	ModunOS servers (so we can deliver and show history)
AI conversations	Prompts and replies via Lucen / Modun Void	Processed by the selected AI path; browser may keep recent turns locally; we aim not to keep a permanent ModunOS prompt archive
Billing	Payment method and invoices	Stripe (payment processor); ModunOS keeps tier/entitlement state
Security & telemetry	Auth events, abuse signals, client error reports, live presence	ModunOS operations (often short-lived); edge providers may log access metadata
Public content	Published spaces, public profiles, assets marked public	Visible according to product rules you opted into

How we use information

To create and maintain your Modun identity and provide cloud sync, messaging, and other connected features you use
To verify eligibility and comply with applicable age and privacy rules (including COPPA and GDPR-oriented requirements)
To process payments and entitlements through our payment provider
To route AI requests you initiate to the configured model provider
To protect security, investigate abuse, and keep the platform reliable
To improve performance and user experience using limited operational signals — not by selling your personal data as an advertising product

AI services

When you use ModunOS AI features (including Lucen in the OS and Modun Void on ai.modunos.com), your request is processed so a model can respond. Cloud models (such as Google Gemini, when configured) necessarily receive the prompt content for that request. Optional local model paths may keep processing on a machine you control.

Processing a request is not the same as ModunOS permanently storing it. We aim to avoid building a durable ModunOS archive of prompt bodies. Model providers have their own terms; we do not control every vendor retention practice and will refine disclosures as contracts and product options mature.

Messages

Social direct messages are stored on ModunOS infrastructure so recipients can receive them and so signed-in users can see history. End-to-end encryption for a dedicated Messenger experience is a product direction we may grow into; it is not what the current social message store claims. Peer “privacy” controls (for example limiting who can message you) affect other users — they do not make the server unable to store delivery data.

Payments

Card and checkout data are handled by Stripe. ModunOS receives the information needed to recognise your subscription or tier so features unlock correctly.

Infrastructure and third parties

Depending on how you use ModunOS, processing may involve:

Cloudflare — edge delivery, access control, and security (connection metadata such as IP addresses)
Our hosting origin — application servers, databases, and file storage
AI model providers — when you use cloud AI
Stripe — payments
Government or partner APIs you explicitly trigger (for example vehicle MOT lookup in Garage, when enabled)

Browser cookies and similar technologies (including localStorage used for sessions) are described in our Cookie Policy.

Data retention

We retain account and synced workspace data while your account is active and as needed to provide the service, secure the platform, and meet legal obligations. Soft-release automation for fixed purge schedules and self-serve deletion is still maturing; contact us if you need help with access or deletion requests.

Children

ModunOS does not knowingly collect personal information from anyone under the applicable minimum age. Registration asks for date of birth and country to enforce eligibility. If we learn we have collected information from an underage user, we will delete that account information as quickly as our processes allow. See also our Terms of Service.

Legal summary

1. Overview

This Privacy Policy describes how ModunOS (“we”, “us”) collects, uses, stores, and shares information when you use modunos.com, related subdomains (including ai.modunos.com), downloadable clients that connect to our services, and associated APIs.

2. Information we collect

Depending on your use of the Services, we may collect:

Account registration data (username, email, password, date of birth, country of residence)
Service and usage data necessary to operate features you use (including synced files, messages, presence, and settings)
Payment-related entitlement data from our payment processor
AI request content you submit to AI features
Technical and security data (such as IP addresses, device/browser characteristics, timestamps, and error reports) generated when you communicate with our infrastructure

3. How we use your information

To provide and maintain your Modun identity and connected services
To verify eligibility and comply with COPPA, GDPR, and other applicable regulations
To improve security, performance, and user experience
To process transactions and prevent fraud or abuse

4. Sharing

We share information with processors who help us run the Services (hosting, edge security, payments, AI inference, and APIs you invoke). We do not sell personal information as an advertising commodity. If we introduce partner placements inside the ecosystem, we will describe them clearly and separately from this baseline.

5. Your choices and rights

You may use guest features without creating an account. You may choose not to save personal ledgers to the cloud. Depending on your location, you may have rights to access, correct, or delete personal data. Soft-release self-serve tooling is expanding; contact us to exercise rights we support today.

6. International processing

Our infrastructure and processors may process data in the United Kingdom, European Economic Area, United States, or other regions where our providers operate. We will refine transfer disclosures as our legal entity and contracts mature.

7. Changes

We may update this Policy as ModunOS evolves. The “Last updated” date at the top will change when we do. Material changes will be reflected on this page; continued use after an update constitutes notice of the revised Policy for soft-release purposes.

8. Contact

For privacy-related questions or requests, contact us via official channels on modunos.com or email [email protected] (general contact: [email protected]).