Privacy Policy

Hosia · Arman Khan, sole trader · ABN 60 951 750 991 · Australia
Last updated: 3 September 2026

Draft for review. Every factual claim below was checked against this repository's code and is accurate as at the date above. It has not been reviewed by a lawyer. Read it before publishing, and have it reviewed before you take money.

The short version

There is no telemetry, no analytics, and no crash reporting. The application does not report what you do with it, and does not send us your prompts, your files or your keys.

It can contact a server we operate for exactly two things, both downloads of a public file: the skills catalogue, when you search for or install a skill, and the model catalogue, only if you have switched it on and only when you open the model picker. Neither happens at startup or on a schedule. Both are described below. Nothing else on your machine reaches us unless you buy a subscription and choose to route your model requests through our gateway.

If you use your own API key, your prompts go directly from your machine to the provider you chose. We never see them.

What runs where

Hosia is a program that runs on your computer. It reads and writes your files, runs commands you or the model ask for, and talks to whichever AI provider you configure. All of that happens on your machine.

What stays on your machine

Everything, by default:

Deleting that directory deletes everything Hosia holds about you locally. The program directory can be removed separately without touching it.

What we never collect

We do not operate any analytics, telemetry or crash-reporting service, and the application contains no client for one. It does not phone home to report usage, errors, or the fact that it is running.

The requests that can reach us

Two features download a public file from hosia.com.au. Nothing else in the application has our address.

The skills catalogue. Hosia can install skills - optional add-ons. To find them it downloads an index from https://hosia.com.au/docs and keeps a copy under ~/.hosia/skills/.hub/index-cache/ for six hours. The download happens only when you browse, search for, inspect or install a skill (hosia skills …, or /skills … in a chat) and the local copy is missing or older than that.

The model catalogue. The model picker can refresh its list of recommended models from https://hosia.com.au/api/model-catalog.json. This is off by default (model_catalog.enabled: false in ~/.hosia/config.yaml); the application ships with the list built in, so you lose nothing by leaving it off. If you switch it on, the file is fetched only when you open the model picker (/model in a chat, or hosia model) and the local copy at ~/.hosia/cache/model_catalog.json is missing or older than an hour.

Both happen only when you do the thing described - never at startup and never on a schedule. The picker warm-up that runs in the background after the welcome banner cannot fetch our catalogue - the code forbids it - and a test in the repository fails if a fresh interactive launch makes any request to hosia.com.au.

Each request is an ordinary web request for a public file. It carries no account identifier, no API key, no prompt, and no information about your machine beyond what any HTTP request unavoidably reveals: your IP address, the time, and the HTTP client's user agent (hosia-cli/<version> for the model catalogue). We do not link those to a person, and we do not use them for analytics. Like any website, the server keeps short-lived operational logs.

If you never use skills and leave the model catalogue off, the application never contacts us at all.

We never receive your API keys. They are sent only to the provider they belong to, by your machine, over TLS. Where a key sits on your disk depends on how you added it:

• hosia keys add stores it in ~/.hosia/keys.json, created with file mode 0600. It is read from that file when a request needs it and is never placed in the environment of a running process.
• hosia setup, the provider and model wizards (hosia model), and the dashboard's environment page store it in ~/.hosia/.env, created with mode 0600 (an existing file keeps the mode it already has). Every Hosia process loads that file into its own environment when it starts, so a key stored this way is visible to anything that can read the environment of a running Hosia process - on some systems that includes other programs run by the same user.

If that distinction matters to you, add keys with hosia keys add.

Where your data does go

Your AI provider

When you use Hosia, your prompts, and whatever file contents or command output the model needs to answer them, are sent to the AI provider you configured - OpenRouter, Anthropic, OpenAI, Groq, DeepSeek, or another. That transfer is between you and them, under their privacy policy, not ours. We are not a party to it and cannot see it.

If you run a local model through Ollama, nothing leaves your machine at all.

Skill registries and model metadata

Searching for or installing a skill may also send requests to public skill registries and code hosts (GitHub, skills.sh, ClawHub, LobeHub, browse.sh): a search can be forwarded to them, and installing downloads the skill's files from wherever it is hosted. The model picker, and the background warm-up that runs once after launch, download a public list of models and prices from models.dev. These are ordinary requests to third parties under their own policies; none of them carries your keys or your prompts.

Our gateway - only if you subscribe

If you buy a subscription, you receive a token and your requests are routed through a server we operate, which forwards them to an AI provider on your behalf. This is the only circumstance in which your prompts pass through our infrastructure.

What that server stores:

• Your account: name, email address, plan, status
• A cryptographic hash of your access token. The token itself is never stored in readable form: between payment and the moment the post-payment page shows it to you, it is held encrypted under a key kept outside the database, and that copy is deleted as soon as it has been shown, or after 24 hours if it never was
• Usage records: timestamp, which model, counts of input, cached and output tokens, and the resulting cost

What it does not store: the content of your prompts or the model's replies. Usage is recorded as numbers, not text. There is no column in which a message could be kept.

We keep usage records for as long as your account exists plus seven years, because Australian tax law requires us to retain records substantiating income.

Payments

Payments are processed by Stripe. Card details go directly to Stripe and never reach our servers. We receive a customer identifier, a subscription identifier, and the email address you gave at checkout. Stripe's handling of your payment data is governed by Stripe's privacy policy.

Your rights

Under the Privacy Act 1988 (Cth) you may ask us what personal information we hold about you, ask us to correct it, and ask us to delete it. Because we hold very little - an email address, a token hash, and usage counts - these requests are usually satisfied in full.

To delete your account and its data, or to ask any privacy question, email support@hosia.com.au. We will respond within 30 days.

We do not sell personal information. We do not share it with third parties except the processors named above (your chosen AI provider, and Stripe) as needed to provide the service.

Children

Hosia is not directed at children and we do not knowingly collect information from anyone under 16.

Changes

If this policy changes materially, the version in the application repository changes with it and the date at the top is updated. Subscribers will be told by email before a change that affects them takes effect.

Contact

support@hosia.com.au · Arman Khan, sole trader, ABN 60 951 750 991, Victoria, Australia.