Ambuity
Sign in Apply

Privacy policy

What is kept, where it goes, and how long it stays.

This policy covers Ambuity at ambuity.app and the apps that open it. It says what the service does today. Effective 13 November 2026.

Who we are

Ambuity is the product of Mitchell Craig Roemling trading as ASPIRE 2: X (ABN 21 658 558 016), a sole trader in Brisbane, Queensland, Australia. "We" on this page means that business. Write to mitch@mitchellroemling.com about anything here.

We follow the Australian Privacy Principles and the Notifiable Data Breaches scheme even though a business of our size may not need to.

What is kept, and where

With the desktop app, the files in the folders you join stay on your computer, and a file is copied into your vault only when you import it. Your store keeps each computer's name and when it was last online, the names of the folders you join, and an index of the files in them: each file's path, title, tags, the links it makes, its size and its date, never the file itself. When an agent reads one of those files, your computer sends its text for that answer, and it stays in that conversation like anything else an agent reads.

One measurement runs on these pages: Cloudflare Web Analytics, a small script Cloudflare adds to each page as it is served. It counts page views and load times and records the page, the referrer, the browser and operating system type, the device type and the country, without a cookie, an identifier or a fingerprint, under Cloudflare's own privacy policy; we see totals, never a person. No advertising trackers, no third-party cookies, no contacts, and no location beyond the country Cloudflare reads from your connection.

Every company your words can reach, and why

Whatever an agent reads to answer you (a note, a file, a search result, a calendar event, a mail or a plugin's answer) is sent with your words to the model that agent runs on, and stays in that conversation. Which company that reaches depends on the model you choose for each agent. What each company says it does with what it is sent is taken from its own page, with the day we read it.

We do not sell your data, show you advertising, or share your data with anyone beyond the companies above and the plugins you add yourself, except where the law requires it.

The gateway's log

Some model requests pass through Cloudflare's AI Gateway. For those requests, the gateway counts requests and cost and keeps a log with what was sent, the model's answer, the tokens and the cost, so that a failure can be found and a bill checked. The log is bounded by the gateway's storage limit, which we set to hold about a month of use, and older entries roll off as new ones arrive. Only our own Cloudflare account can open it, and nothing in it is used to train a model. Deleting your account does not reach into it: what it holds of you rolls off within about a month.

Your calendar, by its address

Only if you connect it, under Customize, Integrations, by pasting its private address: the secret address your calendar gives for subscribing to it. What is kept is that address, sealed in your own store like a password: it is never shown on a page again, never given to a model and never written to a log. Beside it we keep the calendar's own name, if it gives one, and when it was last read, to show you on its card.

When an agent you have let read your calendar looks at your day, or your Dashboard shows the week ahead, the service fetches the calendar on your behalf from the calendar's own provider, the company that serves the address, and reads each event's time, title and place. Before each fetch it looks up the name of the provider's site, never the secret part of the address, through Cloudflare's public resolver (1.1.1.1), to check that the address leads to the public internet and not to a private network. It holds what it fetched for a few minutes, so it is not fetched twice, and it writes nothing to your calendar. The provider sees the service's request, not you: it comes from Cloudflare's network and carries no cookie or sign-in of yours. Events an agent reads go to the model it runs on, stay in that conversation and pass through the gateway's log, as anything else it reads does.

Disconnect, in the same place, removes the address here. Anyone who holds the address can read the calendar, so to stop it working everywhere, reset it in your calendar too.

Plugins

A plugin is a server you add yourself, under Customize, Plugins, by its address and, where it asks, a key. Adding it lets no agent use it; you let each agent use it on that agent's setup. When an agent calls one of its tools, the server receives what the agent sends it, and its answer goes to the agent's model as untrusted text. A call that would act waits for your approval first, unless you chose Always for that tool, which you can take back on the agent's setup, or marked the plugin read-only when you added it. Each server is run by whoever made it, under their own terms and privacy policy, not ours.

Apps you connect through Composio. In the same place you can connect an app you use, such as GitHub, Notion or Slack, with one press. You sign in on that app's own page, and the sign-in it gives is held for you by Composio, in the United States, a company that connects apps to products like this one, under an id that stands for your account and carries nothing else about you. When an agent you have let use the app calls it, what the agent sends and what the app answers pass through Composio to the app and back, and the answer reaches the agent's model as untrusted text; a call that would act waits for your approval first, as with any plugin. No file of yours goes to Composio unless an agent sends it in a call you approved. Composio keeps the sign-in until you disconnect the app here, which ends it; what Composio keeps of each call is under its own terms and privacy policy, and what the app does with the call is under the app's.

App cards on your Dashboard. When you put a card from a connected app on your Dashboard, Ambuity reads that app through Composio when you open the Dashboard, when you ask it to, with no agent and no model involved. It keeps only what the card shows (a count, a total, a few short lines such as a sender and a subject, never the body of a mail) in your own space, and deletes it when you remove the card or disconnect the app. Your agents may read what a card shows, as they read any outside text: it grants them nothing. Adding the card is your word that this one app may be read for that one card; a card only ever reads.

Mail to your agents, when it is on

Where the service takes mail, each agent has an address of its own, shown in Settings, Account. Mail sent there comes in through Cloudflare's email routing and is kept in your own store: from a sender the agent takes mail from, as a Work item on its conversation; from anyone else, held until you allow the sender or bin it, and a binned mail's words are gone. Nothing in a mail is taken as an instruction, and nothing is ever sent from the address. What an agent reads of a mail goes to its model like anything else it reads.

Cookies

The service sets two cookies, both necessary to work: aspire2_session, which keeps you signed in for up to thirty days and is sealed so that only the service can read it, and aspire2_auth, which lives for ten minutes while you sign in. These pages set none. Because nothing beyond what is necessary is set, there is no cookie banner and nothing to choose. Stripe's and WorkOS's own pages set their own cookies under their own policies.

When you collapse or expand the sidebar, the app remembers that choice in this browser's local storage. The choice stays on this device and is not sent to us. Clearing the site's browser storage removes it.

What we never do

How long it stays, and how to export or delete it

How it is kept safe

Every request is signed in before it does anything; your store is yours alone and every shared row carries your identifier; the keys the service uses are held by the platform and never reach a model, a log or a page. Your agents read your notes and files and never delete or rewrite them; what they remember is written only through fixed operations, with a version behind each. An agent acts outside the service only through a plugin you added, as the section on plugins says. If a data breach likely to cause you serious harm ever occurred, we would tell you and the Office of the Australian Information Commissioner, as the Notifiable Data Breaches scheme requires.

Your choices

Changes to this policy

When this policy changes, the new version is published here with its date, and a change that matters to you is emailed to the address on your account before it applies.

Who to ask

Mitchell Craig Roemling trading as ASPIRE 2: X (ABN 21 658 558 016), Brisbane, Queensland, Australia. Support and privacy: mitch@mitchellroemling.com.

Apply for the beta