Privacy Policy

Hosia · Konquer Media Pty Ltd · ABN 15 685 811 492 · Australia
Last updated: 9 October 2026

The short version

There is no telemetry, no analytics, and no crash reporting. The application does not automatically report what you do with it. Chats reach our service when you use a Hosia-hosted model or choose to share feedback, including the optional automatic-sharing switch described below.

The Hosia app checks for updates when it opens and every 6 hours, so it can tell you when a new version is out. That request carries no account or device identifier (see "Update check" below).

Otherwise it contacts a server we operate only when you ask it to: when you sign in to a Hosia account (your chats then go through our hosted service, described under "If you sign in" below); for the model catalogue, only if you have switched it on and only when you open the model picker; and when you connect a Hosia Plus key in the command line version; and when you share chat feedback with our team. None of these happens at startup or on a schedule unless you have signed in.

Free online may train AI models. If you sign in and use the free plan, your chats go to free AI models whose providers may use them to train and improve their models. Do not enter private customer or personal information there. For private work, use your own key or a local model (your chats then never pass through us unless you choose to share them as feedback), or Hosia Plus when it opens. Finding and installing skills does not contact us.

Setting Hosia up the first time, reading replies aloud, and keeping its list of models current contact other companies' servers, not ours. They are described under "Setup, voice and model list" below.

If you ask for help with hosia debug share, it uploads a support report to a public paste service, described under "Support reports" below.

Hosia Plus, our paid subscription, is not on sale yet. We take no payments today.

If you use your own API key, your prompts go directly from your machine to the provider you chose. We see chat text only if you separately choose to share feedback with our team.

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:

On Windows, that folder is %LOCALAPPDATA%\hosia instead of ~/.hosia. The Hosia app keeps your sign-in and window settings separately, in ~/Library/Application Support/Hosia on a Mac or %APPDATA%\Hosia on Windows.

Deleting those folders deletes everything Hosia holds about you locally. The program itself can be removed separately without touching them.

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 report usage or errors to us. The update check described below asks only for the latest version number.

The requests that can reach us

Apart from signing in (see "If you sign in" below), these are the only requests the application sends to us. The other places our address appears are links it prints for you to open.

Update check. The Hosia app asks https://api.hosia.com.au/downloads/latest.json for the latest version number when it opens and every 6 hours after that, and tells you if a newer version is out. The request carries no account or device identifier, no API key and no prompt. Like any web server, ours keeps normal short-lived request logs (your IP address, the time and the address requested). We do not use them to track you.

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. That file is not published yet, so if you switch the option on today the request fails and the picker keeps its built-in list. When it is on, the file is requested 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.

Connecting a Plus key. The command line version can connect a Hosia Plus key. Plus is not on sale yet. When you connect a Plus key (they begin hos_), it sends one request to https://api.hosia.com.au/v1/models carrying that key, to check it before saving it. Nothing else is sent with it. Anything that does not begin hos_ is refused before any request is made.

Skills. Hosia can install skills, optional add-ons. Browsing, searching for, inspecting or installing one (hosia skills …, or /skills … in a chat) sends nothing to us: we publish no skills index, and Hosia's index source is switched off. Skills bundled with Hosia are read from your disk; everything else goes only to third parties, such as the registries listed under "Skill registries" below.

The model catalogue and Plus key requests 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 an automated check in the Hosia source fails if a fresh launch of the command line version makes any request to hosia.com.au. The Hosia app's update check is described above.

The model catalogue 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>). 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 do not sign in, leave the model catalogue off and never connect a Plus key, the only request the application sends us is the update check.

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.

If you sign in: the hosted service

Signing in is optional. It lets Hosia work with no keys to copy: your chats go through our hosted service at api.hosia.com.au, which forwards them to an AI model through OpenRouter and streams the answer back.

What we hold when you sign in. Sign-in is handled by Supabase, which holds your email address and a user id on Amazon Web Services in Sydney, Australia. Our service stores, in a database on a server we rent from DigitalOcean in Sydney, Australia:

• your account: email address, plan, and limits;
• a one-way hash of the session token the app uses (not the token itself);
• one record per request: time, model name, number of tokens, and cost;
• an encrypted key our service uses to reach OpenRouter on your behalf.

We do not store your chats. Chats from the Hosia app pass through our service on their way to and from the model, and are not written to our database or logs. Our web server keeps short-lived operational logs of each request (time, IP address, address requested, and result), with sign-in tokens removed. Your conversations stay on your computer, as described above. When a request asks for it, a copy of the reply can be held for up to 24 hours so a dropped connection can be retried, and is then deleted.

Free online may train AI models. The free plan uses free models offered through OpenRouter. The providers of those models may keep your chats and use them to train and improve their models, under their own policies. Do not enter private customer information, personal information about other people, or anything confidential on the free plan. For that, use your own key or a local model, or Hosia Plus when it opens: paid plans only use providers that agree not to collect your data and not to retain it.

Where it goes. OpenRouter and the model providers it routes to may process your chats outside Australia, including in the United States. Your account data, with Supabase and on our server, is held in Sydney.

Signing out removes the session from your computer and revokes it on our service. To delete your account and the records above, email support@hosia.com.au.

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, your prompts, files and the model's replies stay on your machine, unless you have a reply read aloud (see "Setup, voice and model list" below). Hosia still downloads a public list of models from models.dev after it starts, at most once an hour (see "Setup, voice and model list" below).

Setup, voice and model list

These requests go to other companies' servers, never to us. None of them carries your keys or an account identifier. Only reading aloud sends any text: the words being read. Each is handled under that company's own policies.

• First-run setup. The first time the Hosia app opens, and again after an update, it downloads a private copy of Python using the uv installer, which fetches a standard Python build from GitHub. It then downloads the parts Hosia needs from the Python Package Index (pypi.org). On Windows it also downloads Git for Windows (PortableGit) from github.com, which Hosia uses to run commands.
• Reading replies aloud. The default voice is on-device Kokoro. Once its model is installed, it generates speech on your computer without sending the text to a speech service. Other voices follow the provider selected in voice settings. Microsoft Edge speech sends the words to Microsoft; a configured cloud speech provider sends them to that provider. If a local voice is unavailable, Hosia can use a stand-in and returns a note with the audio identifying that change. Check the selected voice and any stand-in note before reading confidential text aloud.
• Model list. Hosia downloads a public list of AI models and their prices from models.dev after it starts and when the model picker needs it, at most once an hour. This is not our model catalogue described above: it comes from models.dev, not from us.

Skill registries

Searching for or installing a skill may send requests to public skill registries and code hosts (GitHub, skills.sh, ClawHub, LobeHub, browse.sh), never to us: a search can be forwarded to them, and installing downloads the skill's files from wherever it is hosted. These are ordinary requests to third parties under their own policies; none of them carries your keys or your prompts.

Support reports - only if you share one

hosia debug share, the /debug command in a chat and the dashboard's debug-share button upload a support report to a public paste service, paste.rs, or dpaste.com if paste.rs fails, and show you the links. The report holds a summary of your setup (operating system, Python and Hosia versions, model, provider, which API keys are set but not the keys themselves, and settings you changed from the defaults) and recent lines from Hosia's logs. Unless you send /debug from a messaging app, it also includes the full logs, up to 512 KB each. Logs can contain parts of your conversations, tool output and file paths. Before upload, text shaped like a credential and email addresses are masked, unless you pass --no-redact.

Anyone who has a link can read that paste. Hosia asks paste.rs to delete its pastes once six hours have passed, the next time you run hosia debug or while the gateway is running. dpaste.com pastes expire after seven days (--expire changes that). hosia debug delete <url> deletes a paste.rs paste straight away. Nothing is uploaded unless you run one of these, and hosia debug share --local prints the report on your screen instead. What you upload is held by those services under their own policies, not by us.

Chat feedback you choose to share

The desktop app offers Send to Hosia team and reply feedback. Manual sharing shows a preview and lets you add a note before sending. It sends user and assistant text, your note and rating, the selected model, app version and operating-system platform to our authenticated feedback service. The Hosia team can read this text to investigate problems and improve Hosia. Feedback is separate from ordinary model inference and numeric usage records.

Before sharing, the app removes tool results and tool-call arguments and masks recognized email addresses, keys and other credential patterns in chat text. This is not a guarantee that every private detail is removed. Names, addresses, facts repeated in a reply and private information in your note may remain. Check the preview and note; do not share confidential information you do not want our team to read. Attached image pixels and file bytes are not included in this text feedback payload.

Share my chats with the Hosia team while testing is off by default. If you enable it, a finished turn may share the redacted chat automatically, at most once per chat per day, without a separate preview for every send. Turning it off stops future automatic sharing; it does not delete feedback already sent. To request access, correction or deletion of shared feedback, email support@hosia.com.au. Feedback retention and access controls must be assessed separately from the usage-record retention described below.

Our gateway - only if you subscribe

Hosia Plus is not on sale yet, so nothing in this section applies today. We will update this page before it opens.

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 same hosted service the free plan uses, described under "If you sign in" above.

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

Ordinary inference usage records contain numbers, not the content of your prompts or the model's replies. Chat feedback you choose to share is a separate text submission, described above.

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

We take no payments today. Once Hosia Plus opens, 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.

This website

hosia.com.au is hosted by Vercel, which keeps short-lived server logs (your IP address, the page you asked for and the time) and may handle your request on servers outside Australia. The site runs no analytics and sets no tracking cookies. When you sign in to the Hosia app, it opens a sign-in page on this site, which creates or opens your Hosia account (see "If you sign in" above). You can also use the app with no account, with your own key or a local model. Once Plus opens, your plan and subscription status are stored with your account at Supabase, which hosts our account database in Sydney.

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. If you have not signed in, we hold nothing about you beyond the short-lived request logs described under "Update check", unless you email us. If you have, we hold the account records described under "If you sign in" and any chat feedback you have chosen to share.

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, Supabase, OpenRouter and the model providers it routes to, DigitalOcean, Vercel, and, once Hosia Plus opens, 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, we will update this page and the date at the top. Subscribers will be told by email before a change that affects them takes effect.

Contact

support@hosia.com.au · Konquer Media Pty Ltd, ABN 15 685 811 492, Victoria, Australia.