What Aumos keeps on your machine, and the little that ever leaves it.
Last updated
Aumos has no account and no server holding your portfolio. Your mandates, positions, manager runs, judgements and orders live in a file on your own computer and are never uploaded. We could not read them if we wanted to.
This website measures its own visitors with Google Analytics, and the application does not. Nothing that measurement sees comes from the application or from your store; section 5 says exactly what it is.
Nearly all of it. A manager run is the one exception and section 3 says what leaves. What stays, specifically:
Aumos makes requests to our release host to check for updates, to list the catalogue of managers and data sources, and to download one you chose to install. Those requests carry what any web request carries — an IP address, a timestamp, the version asking — and our host keeps ordinary access logs of them. They do not carry anything about your portfolio.
It also makes the requests a manager run needs, directly to the vendors you supplied credentials for. Those go to that vendor, not to us.
A manager run drives a command-line coding assistant you are already signed in to — Claude Code or Codex — on your own computer. So that it can judge, the run puts what it needs into that assistant's session: a snapshot of the portfolio it is judging, the mandate governing it, whatever the managers have written down about it, and whatever a data source answered. That session reaches the servers of whoever provides that assistant, in the United States. It goes there under your own subscription and their terms and privacy policy apply to it. It does not come to us, and we hold no key to it.
A portfolio can be set to anchor its judgements. When it is, Aumos sends the hash of a sealed judgement and nothing else — not the judgement, not the mandate, not the positions, and not a hash of them. The hash is a fixed-length value that cannot be turned back into what it was made from.
It is off until you turn it on, per portfolio, and turning it on covers judgements sealed from that moment onwards rather than the ones before it. Turning it off stops new ones; it does not withdraw what is already logged, because an append-only log that could be edited would prove nothing.
aumos.app sets one cookie of its own, and only when you use the language switch: it stores which language you chose, so the site can keep drawing itself in it.
Every page of aumos.app also loads Google Analytics, which tells us how many people reach the site and by which route. It sets its own cookies, and it sends Google the ordinary things a web request carries — your IP address, your browser and operating system, which page you are on, and the site you followed a link from. We use it for nothing but counting visits to this website.
You can refuse it. Blocking cookies for this site in your browser, or installing Google's own opt-out add-on, stops the measurement; nothing on this site needs it to work, and the one cookie that is ours — the language you chose — is set only when you use the switch.
It runs on aumos.app and nowhere else. The application you download does not load it, and no measurement here can see anything from your store, because nothing from your store is ever on this website. There is no advertising and no other third-party tracker on any page.
If you ask to be told when the download opens, we keep the email address you typed and which language you were reading the site in. Nothing else: not your IP address, not your browser, nothing about your computer. It is held in a key-value store operated by Upstash, outside the country you are in, until that notice is sent — and then the whole list is deleted. Write to the address in section 10 at any time and we erase yours before that.
Three things named above leave the country you are in. Google Analytics receives what section 5 lists, from this website only, and it goes to the United States. The session a manager run drives reaches the provider of the assistant you are signed in to, carrying what section 3 lists, under your own subscription, and that goes to the United States too. And if you joined the waitlist, the address you typed is held in the store section 5 names, which Upstash operates outside the country you are in.
The first two do not pass through us and are not something we can read. The third one is ours: we hold that list, we are the ones who will send the notice, and section 5 says how long it is kept and how to be taken off. If you would rather the first two did not happen: the analytics is refused as section 5 describes, and a manager run only happens when you start one.
Your store is a file on your own computer, so reading it, correcting it and deleting it are things you do directly rather than things you ask us to do — we have no copy to act on. What we hold is the ordinary access logs of section 3, the analytics of section 5, and — if you joined the waitlist — the email address section 5 describes. The first two are not tied to a name or an account. The third one is a way of reaching you, and asking us to erase it is the one request on this page we can actually act on.
For those, and for anything else about this policy, write to us at the address in section 10.
The date at the top of this page is when it last changed. A change that alters what leaves your machine will say so on the page rather than only moving the date, and takes effect when it is published here.
Deleting the application and its store directory removes everything Aumos keeps about you on your own computer, because there is no copy of it anywhere else. Two things are not in that directory and are covered above: anchored hashes, and — if you joined the waitlist — the email address you gave. Write to the address in section 10 and we erase that address; the whole list is deleted once the notice it exists for has been sent.
untilled (언틸드) — https://untilled.team.
Data protection officer under the Personal Information Protection Act: Sangmin Lee (이상민), Proprietor — min@untilled.team.