Kimie
Draft — pending legal review. This page describes how Kimie actually handles data today, in plain language, but it has not yet been signed off by a lawyer and is not final legal advice. Treat it as a good-faith description, not a binding legal document, until this notice is removed.

Privacy Policy

Last updated 27 August 2026

1. Who we are

Kimie is operated by Nagare Business Flow Lab (ABN 32 542 463 012), trading as Kimie (“Kimie”, “we”, “us”). We are governed by the law of Australia. For anything in this policy, including a request to access, correct, or delete your personal information, contact us at hello@kimie.com.au.

2. What this policy covers

This policy covers personal information handled by the whole Kimie service: this website (kimie.com.au) and the Kimie product app (app.kimie.com.au), which recruiting teams use to screen candidates. Where handling differs between the two, we say so explicitly below.

3. Information we collect

On this website

If you request early access, we collect the email address you provide and which form on the page you submitted it from. That’s sent directly to a private Slack channel our team monitors — it isn’t stored in a database on this website. We don’t otherwise collect personal information on this site beyond standard hosting and analytics data described in the sections below.

In the Kimie product app

Recruiting teams that use Kimie provide us with:

  • Recruiter account information (name, email, and login details for the people at a recruiting team who use Kimie).
  • Job description text pasted in to define a role’s screening criteria.
  • Candidate data: resume files, the text extracted from them, candidate names and emails, and any call notes a recruiter records against a candidate.

Candidates don’t sign up for or interact with Kimie themselves — their data reaches us because a recruiter using Kimie submitted it. See Section 13 for how a candidate can exercise their rights over that data.

4. How we use your information

We use the information above to operate the service you or your recruiting team requested: to respond to early-access signups, to run candidate screening and scoring against the criteria a recruiter sets, to operate recruiter accounts, and to send transactional emails related to the product. We don’t sell personal information, and we don’t use it for advertising.

5. AI processing — and no training on your data

Candidate scoring is powered by Anthropic’s API. Each scoring call is a single, stateless request for one candidate against one job description — nothing about a previous candidate or a previous customer’s data is fed into scoring another. Candidate and job description data is never used to train or fine-tune any AI model, ours or Anthropic’s. The one exception is a non-production evaluation harness we use internally to grade scoring quality before launch, which never uses real recruiter or candidate data.

6. Automated decision-making

Kimie uses a computer program — an AI model — to help recruiters screen candidates, and this section discloses that use in the specific terms the Australian Privacy Principles require for automated decision-making.

Personal information the program uses

For each scoring request, the program uses the job description and screening criteria text a recruiter has entered for a role, together with that candidate’s resume data: the resume text and the name, work history, skills, and qualifications extracted from it.

The kind of decision it makes

The program produces a Score and a Verdict — a recommendation of how well a candidate matches a role’s criteria. It doesn’t decide whether a candidate is shortlisted, interviewed, or rejected; the recruiter using Kimie makes that call, and may accept or override the program’s recommendation (see Section 5). We disclose it here because a Score or Verdict can materially affect whether a candidate is shortlisted for a job, and that’s the kind of outcome this disclosure requirement is about, regardless of who makes the final call.

If you’re a candidate and want to know more about how a specific Score or Verdict was produced, or want a recruiting team to review it, contact us at hello@kimie.com.au or see Section 13.

7. How long we keep candidate data, and how to delete it

In the product app, a candidate’s data is kept until 12 months after the job they applied to is closed, or 24 months after the candidate’s record was created if the job is never closed — whichever comes first. A recruiter can also purge a candidate’s data on demand, at any time, for any reason.

A purge permanently deletes personally identifying information — the resume file, name, email, resume text, filename, call notes, job title, and any quoted resume evidence — while keeping a de-identified record that a candidate existed, was scored, and was purged. This lets a recruiting team keep an honest audit trail without retaining the personal information itself.

8. Who we share information with

We use the following service providers to run Kimie. Each is named here, along with what it sees:

ProviderRoleWhat it sees
AnthropicAI scoringJob description text and candidate resume data, sent per request to score a candidate. Nothing is used to train or improve Anthropic’s models.
SupabaseDatabase and file storageAll data persisted by the product app: recruiter accounts, candidate records, and resume files.
VercelHostingInfrastructure and request logs for this website and the product app.
ResendTransactional emailRecipient email addresses and message content for account and product emails.
SentryError monitoringError reports from both apps, which may incidentally include request data present at the point of failure.
SlackEarly-access signupsThe email address and source of an early-access signup on this website. Not used by the product app.

We don’t share personal information with anyone outside this list except where required by law.

If we add a new subprocessor that will process your data, we’ll update this table and the “last updated” date above, and make a reasonable effort to email the primary contact on your account with advance notice before the change takes effect where the change is material. See our Security page for more on how we protect the data these providers handle.

9. Analytics

We use PostHog for analytics on this website — pageviews, on-site events, and how visitors interact with individual pages, including heatmaps and session recordings. Text typed into form fields (like the early-access email field) is masked by default in recordings, so we see that a field was used, not what was typed into it. PostHog derives an approximate location from your IP address.

10. Overseas disclosure

Several of the providers listed in Section 8 — Anthropic, Vercel, Resend, Sentry, Slack, and (once live) PostHog — process data outside Australia. This is a disclosure of overseas recipients for the purposes of Australian Privacy Principle 8 (APP 8). We choose providers with strong security and privacy commitments, but we don’t control the law of the countries they operate in, and APP 8’s usual safeguards may not apply to information they hold in the same way as if it stayed onshore.

11. Data breach notification

If we experience a data breach involving personal information we hold — including one originating at a provider listed in Section 8, such as Supabase or Resend — we assess it against the Notifiable Data Breaches (NDB) scheme in Part IIIC of the Privacy Act 1988 (Cth). Where we determine the breach is likely to result in serious harm to any individual affected (an “eligible data breach”), we will notify the Office of the Australian Information Commissioner (OAIC) and affected individuals as soon as practicable, consistent with the NDB scheme’s requirements — including what happened, what information was involved, and what we recommend affected individuals do in response.

Responsibility for running this process sits with us — Nagare Business Flow Lab, trading as Kimie — even when an incident originates at a service provider we use rather than in our own systems. If you’re a recruiting team or a candidate and believe your data may have been affected by a breach, contact us at hello@kimie.com.au.

12. Serious invasions of privacy

Since June 2025, Australian law has let a person sue directly over a serious invasion of their privacy — for example, if their personal information were misused. This is separate from, and in addition to, the Privacy Act rules described elsewhere in this policy: it doesn’t require the OAIC or any regulator to be involved, and it doesn’t require proof of financial loss.

It applies to how we handle candidate and recruiter data across Kimie, and it’s one more reason we only collect and use personal information for the purposes described in this policy.

13. Your rights

You can ask us to access, correct, or delete the personal information we hold about you by emailing hello@kimie.com.au. We’ll respond within a reasonable time and confirm what we’ve done.

If you’re a candidate whose resume or details were submitted to Kimie by a recruiting team, you didn’t sign up for Kimie yourself and may not know which team used it. You can still exercise your rights — either by asking the recruiting team you applied to (who can purge your record directly), or by emailing us at hello@kimie.com.au and we’ll help track it down and action your request.

14. Changes to this policy

We’ll update this page as our data handling changes, particularly as we move from Early Access toward general availability and complete legal review. We’ll update the “last updated” date above whenever we do.

15. Contact

Questions about this policy, or anything covered by it, can go to hello@kimie.com.au.