Privacy Policy

Who this covers

This policy applies to the Actium Desktop app for macOS and the Actium app for iPhone and iPad, both published by Matthew De George. It describes how the apps handle information. It does not cover this website beyond the pages that host it, or any third-party service you choose to connect Actium to.

What Actium stores, and where it is stored

Actium is built around folders you already have. It does not import your files into a proprietary database or upload them anywhere.

• Your documents stay in the folders you registered — in iCloud Drive, on local storage, or wherever you keep them. Actium reads and indexes them in place.
• Metadata Actium creates — custom fields, annotations, tags, item identifiers, previews, and extracted context — is written as human-readable JSON and text files in an _actium folder beside the documents it describes, so it travels with your files and remains readable without the app.
• An on-device index (a local database in the app's container) speeds up search and browsing. It is derived from your files and stays on the device, unless you turn on the optional cross-device check described under iCloud below.
• App settings and preferences are stored using standard system storage (UserDefaults) on the device.

Deleting the app removes its container, index, and settings. The sidecar metadata files remain next to your documents until you delete them yourself.

Information the developer collects

None. The apps contain no analytics, no crash-reporting SDK, no advertising, and no third-party code that phones home. There is no Actium account and no developer backend. Nothing about you, your device, or your files is sent to Matthew De George or to any service he operates.

iCloud

If your registered folders live in iCloud Drive, Apple syncs those files and their sidecar metadata between your own devices under your own Apple ID. That sync is handled entirely by Apple and is governed by Apple's Privacy Policy and iCloud terms. The developer has no access to your iCloud data and operates no cloud storage of his own. There is deliberately no Actium sync service; the sync explainer covers why.

Actium also keeps a small amount of data in its own private iCloud container, which lives in your iCloud account and is visible only to Actium on your own devices:

• Standalone links — links you make to items outside your registered folders — are stored there, each as the item's name, location and identifier and the name of the device that made it, so they open on your other Macs, iPhone and iPad.
• The optional cross-device check (off by default) shares a summary of each device's index there, so your devices can confirm they agree about your items: the paths of items within your registered folders, their identifiers, a summary of the app's Health and recent activity, and the device's name and app version. Turning it off on a device removes that device's copy.

Neither contains the contents of your documents, and the developer has no access to either.

On-device and local-network AI

Actium's optional AI features — semantic classification, related-item suggestions, and similar analysis — run against a local Ollama model on your Mac. Text from your files is sent only to that local model.

• iPhone and iPad do not run the model themselves. They can queue an analysis request for one of your own Macs, on your own network or via iCloud, for that Mac to fulfil and return the result. The request and result stay within your own devices.
• No file content is sent to a hosted AI service, to the developer, or to any other third party as part of these features.

The local MCP server (macOS)

On macOS, Actium Desktop can optionally run a small server so an AI client on the same Mac can search, browse, and read your library. This server:

• listens only on the loopback address (127.0.0.1) and accepts no connections from other machines;
• is read-only with respect to your documents;
• is off unless you enable it, and whatever local AI client you point at it is your choice and subject to that client's own privacy terms.

Optional connection to a Client Experience Platform

Actium can optionally connect to a Client Experience Platform (CEP) server that you supply, using a standard sign-in (OAuth) flow. This is entirely opt-in. If you never configure a server, no such connection is made. When you do configure one, the data exchanged is governed by the terms of that server, which you or your organisation control.

System capabilities the apps declare

For transparency, and to match Apple's required-reason API disclosures, the apps use these system capabilities purely on-device:

• User defaults — to store your settings and preferences.
• File timestamps — to detect when files you selected have changed, so the index stays current.
• Available disk space — to check capacity before creating a catalogue or copying files from one.

None of this information is transmitted off the device.

Children

Actium is a general-purpose productivity tool. It is not directed at children and does not knowingly collect information from anyone, including children.

Changes to this policy

If this policy changes, the updated version will be posted on this page with a new effective date. Because the apps collect nothing, changes are expected to be rare and clarifying rather than substantive.

Contact

Questions about this policy or about privacy in Actium can be directed to Matthew De George via matthewdegeorge.com.