Privacy

It asks. It does not assume.

Your files stay on your machine. When something has to go out, you can see which app sends it and where it goes.

Describes the design and the code in the repository. The guest side is not independently audited.

How a request works.

The same four steps for every app and service.

  1. An app asks

    It names a permission word, such as one folder or one site.

  2. The host checks

    Grants live on your Mac, not in the guest. Default is no.

  3. The desktop asks you

    A sheet shows who is asking and what for. Decisions are tied to that app, version and package.

  4. One use, then gone

    The answer is a one-use token. More permissions in an update are asked again.

App by app.

What can leave, and where it goes.

AppWhat can leave your machineWhere to
FilesNothing. Browses local drives.-
NotesNothing. Saved to the guest RAM drive, which is lost on restart.-
BrowserThe pages you ask for, fetched by the host engine.The sites you visit
WeatherThe coordinates of a preset city. Nothing else.The Norwegian Meteorological Institute, with an identifying request header
MusicNothing. Reads the host music library.-
CalendarNothing. A local store.-
SheetNothing. Opens and saves local files.-
WallpapersA one-time fetch tool, run by you with your own key.Pexels
KamikinNothing. Avatars and chat are local.-

AI features are planned, not built. When they arrive, keys stay in the Mac keychain and every action waits for your approval. See AI in the OS.

This website.

No trackers

This website loads no external scripts, fonts or analytics.

No cookies

It stores your theme choice, and the notes in the Try it desktop, in your own browser only.

No accounts

There is nothing to sign in to.

Go deeper.

Security

The layers, the install checks and what is not promised. Read it →

Installer note

The threat table and trust states. Read it →

See what is private for yourself.

Run it in a VM and watch the permission sheets.