Straight answers on data, AI and what we will never do.
Short version: your data is stored in Australia, AI analysis runs through OpenAI under a no-training arrangement, your tender documents are private to your account, and Helm never submits anything on your behalf. The detail, with nothing rounded up:
Where your data lives
Your account, business profile, watchlist and pipeline live in Supabase's Sydney region (AWS ap-southeast-2). The application itself runs on a server in Sydney. Two categories of data leave Australia in transit to processors: payment details go to Stripe, and text being scored or drafted is processed by OpenAI in the United States. Neither is stored by us offshore. This is the same statement our legal page makes, because there is only one version of the truth.
What the AI sees, and what it never does
- What is sent: your capability statement and profile facts, and the text of tenders being scored or drafted, are sent to OpenAI for analysis. That is the whole list.
- No training: our API usage is not used to train OpenAI's models, per their API data-usage terms.
- No invention: drafted text must trace to your profile, the tender's own documents, or stay behind a visible [CONFIRM: ...] marker. Compliance matrices quote your documents verbatim with file and page. An automated audit runs against every release.
- Itemised scores: every match score is a sum of labelled parts you can read on the tender page. A relevance score is never a win probability and we never call it one.
Your tender documents
Documents you upload live in a private bucket, are served only through your authenticated session, are never shared across accounts, never enter anyone else's matching, and are deleted 90 days after the tender closes. You bring your own copies under your own portal registration; Helm never fetches portal documents for you.
What Helm will never do
- No automated submissions. Helm prepares; you submit. A tool that lodges government tenders on your behalf is a liability you should not accept from anyone.
- No bid/no-bid verdicts. Helm states evidence and gaps; the pursue decision is yours.
- No republishing of procurement officers' personal contact details. Whatever the SEO upside.
- No data from restricted portals. Helm indexes sources whose terms permit it, shows the licence line on every record, and asks first everywhere else.
Provenance on every record
Every tender in Helm carries a source line: which portal, under what licence, read when, with a link back to the original. Counts are labelled: "indexed" and "on live feeds" are different numbers and we show both. Sample data is labelled as sample data.
Certifications
None yet claimed. Helm is an early-stage product and we will not decorate this page with a roadmap dressed as an achievement. When a certification is audited and held, it will appear here with its scope and date. Ask us anything specific through the contact form.
Questions a careful buyer should ask any provider
- Which portals permit your provider's data model, and can they show you the terms?
- Are the counts on the homepage live records or an archive?
- Are the dashboard numbers real data or a labelled sample, and if unlabelled, why?
- Where does AI processing run, and does the marketing claim match the privacy policy?
We are happy to answer all four about Helm, in writing, any time.