Privacy policy.

Future Ready, an honest read on how AI is changing your work, is operated by Kanso Pty Ltd (“Kanso”, “we”, “us”, or “our”), an Australian company based in Victoria. This policy explains what personal information we collect when you use the Future Ready platform at getfutureready.app, what we do with it, and the choices you have. We've written it in plain English; please ask if anything is unclear.

Future Ready is committed to handling personal information in accordance with the Australian Privacy Principles (APPs) under the Privacy Act 1988 (Cth). If you're in the European Union or United Kingdom, we also recognise your rights under the GDPR and UK GDPR — see Your rights below.

Kanso Pty Ltd is the data controller for the personal information described in this policy. You can contact us about anything privacy-related via the Kanso contact form.

Account information

When you create a Future Ready account, our authentication provider (Clerk) collects your email address and (optionally) your name. If you sign up via a third-party provider like Google or Microsoft, Clerk receives the profile information that provider chooses to share — typically your name, email, and profile picture URL.

We separately store a Kanso user record linked to your Clerk identity. That record includes your email, display name, email-verification status, your referral code, your credit balance, your email preferences (see Emails we send), which version of our terms you accepted and when, and timestamps. If you signed up via a referral link, we also store which user referred you (so credit can be attributed). If your email domain is on an organisation's rollout allowlist (see Team and organisation rollouts), your account is associated with that rollout for the purpose of granting its credits.

Content you submit

When you run a check-up, the text you type into the intake (a description of your work, your team, or your organisation) is sent to our AI engine to generate a report. The text you submitted is stored with your report so you can see “what you told us” on the report. Follow-up questions you ask are stored alongside the report. Subject lines and message bodies for support requests sent via “Ask our team”, credit requests, and team-rollout quote requests (approximate headcount, preferred contact, and anything you add) are stored on our service-ticket system and visible to Kanso administrators.

Kanso administrators can also open an account's reports and follow-ups in our admin console. We do this to answer support requests, investigate problems, and improve the engine — not to read reports for their own sake, and never to pass them to anyone else.

Usage and technical data

We keep a ledger of credit transactions (signup bonus, referral, check-up, follow-up, refund, admin grant). Our hosting and authentication providers log standard technical metadata — IP address, browser user-agent, timestamps — for security and abuse-prevention purposes.

Cookies and similar technologies

We use a small number of cookies and browser storage values, all functional:

• Clerk session cookies — required to keep you signed in.
• fr_ref — set when you arrive via a referral link; cleared once we've attributed the referral. 30-day lifespan, samesite=lax.
• fr_terms and fr_mkt — set when you tick the terms box and (optionally) the insights-email box on the sign-up page, so we can record your choices against your new account. Both last 30 minutes and are cleared as soon as they've been read.
• fr_aid — a random, first-party identifier that lets us count how many people move from reading a sample report to running a check-up. It carries no personal information, is never combined with third-party data, and isn't used for advertising. One-year lifespan.
• localStorage values — used to remember preferences like your theme, whether the sidebar or Ask panel is open, whether you've dismissed the refer-a-friend card, and a brief you haven't sent yet. These never leave your browser.

We don't use third-party advertising cookies or cross-site tracking pixels.

• To provide the service — generate check-up reports, allocate credits, deliver follow-up answers, and surface your history on your Home page.
• To run the credit economy — grant signup and referral bonuses, debit credits when you run a check-up or ask a follow-up, process administrator grants (and, when payments ship, process purchases).
• To respond to your support requests — read the “Ask our team” tickets you submit and reply via the same interface.
• To keep the service secure — detect and block abuse, enforce rate limits, maintain an audit trail for credit movements, and investigate incidents.
• To improve the product — analyse aggregated, non-identifying usage patterns. We do not use the content of your reports, follow-ups, or tickets to train AI models, nor do we share that content with anyone other than the subprocessors listed below as needed to provide the service.
• To email you — about your own reports and account, and, only if you've asked for it, with occasional insights from Kanso. Details in the next section.

There are three kinds, and you control two of them.

• Your reports. When a check-up finishes we email the report to you. This is part of the service.
• Reminders about your account. A note when your monthly credits top back up, when a plan has steps left, when credits are sitting unused, or when a refresh reminder you set falls due. These are about your own use of Future Ready and are on by default; you can switch them off on your account page at any time.
• Occasional insights from Kanso. Roughly monthly: what's changing in AI and work, what's worth learning, what we're building. We send this only to people who have expressly asked for it by ticking the optional box on sign-up, on the terms notice, or on their account page. The box is never pre-ticked and it isn't a condition of using the service. Every such email carries an unsubscribe link, and you can also untick the box on your account page; we act on that immediately.

We record when you gave or withdrew consent. We don't buy, rent, or sell email lists, and we don't share your address with anyone for their own marketing. This is how we meet our obligations under the Spam Act 2003 (Cth).

When an organisation pays for its people to use Future Ready, we usually allowlist its email domain so that colleagues signing up with a work address receive the organisation's credit allowance automatically. Here is what that does and doesn't mean for your personal information.

• Your reports are yours. The organisation funds credits. It does not get access to your briefs, reports, or follow-up questions, and we won't share them with it — or with your manager — unless you ask us to or share them yourself.
• What the organisation can learn from us. On request we may tell the paying organisation, in aggregate, how many accounts at its domain have signed up and how many credits have been used, so it can judge whether the rollout is worth continuing. We don't report who ran what.
• Quote requests. If you ask for a team quote, the details you provide (your email, approximate headcount, preferred contact, and any notes) are stored as a support ticket and used only to prepare and follow up the quote.
• If you leave. Your account and reports stay with you. You stop receiving organisation-funded credits and return to the standard individual allowance. The organisation can't delete or take over your account.

A work email address identifies your employer to us, so if you'd rather keep your Future Ready use entirely separate from work, sign up with a personal address instead.

We use a small set of subprocessors to operate Future Ready. Each only sees the personal information they need to do their job.

• Anthropic — receives your check-up brief and follow-up question text to generate AI responses. Anthropic does not use API inputs to train its models (per their published policy).
• Clerk — handles sign-up, sign-in, email verification, session management, and bot protection.
• Neon — hosts our PostgreSQL database (Sydney region). Stores your account record, reports, follow-ups, tickets, and credit ledger.
• Vercel — hosts the application and processes inbound requests. Standard access logs are retained per Vercel's policies.
• Cloudflare — provides the Turnstile bot-protection challenge during sign-up (via Clerk).
• Upstash — provides a Redis cache used for rate limiting on cost-sensitive endpoints.
• Resend — delivers the emails described above. Receives your email address and name; if you've opted into insights emails, your address is also held as a contact there so unsubscribes are honoured automatically.
• Microsoft Entra ID, Google — only if you sign in via one of these identity providers; receives a sign-in request and returns your profile information to Clerk.

Future Ready is free for individuals and we don't currently process payments. If we introduce paid options, Stripe will join this list as the processor for billing data and we'll update this policy before that goes live.

Your primary account and content data is stored in our database (Neon) in Sydney, Australia. Some subprocessors (Anthropic, Clerk, Vercel, Cloudflare, Upstash, Resend) operate globally and may process data outside Australia in the course of providing their services. We choose subprocessors that publish meaningful security and privacy commitments.

We keep your account record, reports, follow-ups, and ticket history while your account is active. If you ask us to delete your account, we remove your Clerk identity and cascade-delete the linked records in our database (account row, reports, follow-ups, ticket history, and credit transactions). Backup snapshots taken by our hosting providers may persist for a short rolling window afterwards as part of normal operations.

Anonymous or aggregated metrics derived from usage may be retained indefinitely.

All traffic to the platform is served over HTTPS. The database is encrypted at rest. Access to administrative tools is restricted to email addresses on a server-side allowlist, enforced on every page load and every admin action. We rate-limit cost-sensitive endpoints to prevent abuse, and we hold an audit ledger of every credit movement to support investigation if anything goes wrong.

No system is perfectly secure. If we become aware of a breach affecting your personal information, we'll notify you and the relevant regulator in accordance with the Notifiable Data Breaches scheme.

You have rights over the personal information we hold about you. These vary by jurisdiction but generally include:

• Access — ask for a copy of the personal information we hold about you.
• Correction — ask us to correct information that's inaccurate or out of date. Most account details can be updated yourself via your Clerk account.
• Deletion — ask us to delete your account and the personal information associated with it. This is irreversible.
• Objection / restriction — for users in the EU, UK, and similar jurisdictions, you can object to or restrict certain processing.
• Complain — if you're unhappy with how we handle your data, you can complain to the Office of the Australian Information Commissioner (oaic.gov.au), or to your local data protection authority if you're outside Australia. We'd also appreciate the chance to address it first.

To exercise any of these rights, contact us via the Kanso contact form. We'll respond within a reasonable timeframe (typically 30 days).

Future Ready is intended for use by adults (16+ at minimum, with full adult access from 18). We do not knowingly collect personal information from children under 16. If you believe a child has provided us with personal information, please contact us and we'll delete it.

We may update this policy from time to time. Material changes (new subprocessors, expanded uses of your data, jurisdiction shifts) will be communicated to signed-in users via an in-app notice or email before they take effect. The “Last updated” date at the top of this page always reflects the current version.

For privacy questions, deletion requests, or to update your information, please use the Kanso contact form.