Last updated: 1 October 2026
Clarity Club (clarityclub.jiffi.co, including the Clarity desktop app) is run by Jiffi (“we”, “us”). This policy explains what personal information we collect, why, who we share it with, how long we keep it and what you can do about it. We handle personal information in line with the Australian Privacy Principles in the Privacy Act 1988 (Cth).
When you sign up we collect your name and email address, and the campaign that brought you to us (for example a LinkedIn or email link). We check your email’s domain against a list of personal and disposable email providers to decide whether you qualify for the work-email credit bonus; this check happens on our own servers. We do not use passwords: you sign in with a link we email to you.
We record page views, reading progress and button interactions in our own database. Each record carries a random session identifier and, once you are signed in, your account ID. We also store an approximate location (country, region, city and rough coordinates) that our hosting provider, Vercel, derives from your IP address on each request; we do not store the IP address in these records. The location is removed from each record after 90 days, and the records are deleted after 400 days. Visits you made before signing up are linked to your account when you create it.
We use PostHog, a product analytics service, to understand how Clarity Club is used and where it needs to get better. For members who are signed in, this is linked to your account: your account ID, name, email, role, sign-up date, plan and the campaign that first brought you to us, together with what you do in the app (for example starting a health check, planning an idea or buying credits). For visitors who are not signed in, it is anonymous. PostHog receives your IP address so it can estimate your location. Query parameters are removed from every URL before it is sent. We may occasionally show you a short in-app survey through PostHog.
Session recordings. PostHog records how pages are used (clicks, scrolling, page changes and messages our code writes to the browser console) so we can see where people get stuck. This applies to all signed-in members, and to visitors who accept the cookie banner. Everything you type into a form is masked in your browser before anything is sent, and we also mask sensitive content such as your idea8 conversations, health check results and billing details. Recordings are kept for up to 90 days.
Error diagnostics. When something breaks, we send the error, the page it happened on and the steps leading up to it to PostHog so we can fix it, linked to your account if you are signed in.
AI usage. For each AI response we record the model, token counts, cost and response time. We do not send the content of your conversations to PostHog.
When you use idea8 we store your conversation, the summaries, dashboards and documents it produces, and the research it gathers. Your messages are sent to Anthropic, whose Claude models generate idea8’s responses.
Files you upload. When you add a file to a session, we extract its text and immediately discard the file itself. We keep the extracted text (up to 30,000 characters per file) with the session and send it to Anthropic as context.
Web research. To research your idea, idea8 sends short search queries it writes from your conversation to Tavily (a web search service) and to the public Hacker News search, which is run by Algolia. These queries do not include your name or email, but they may describe your idea.
If you connect GitHub to idea8, we ask GitHub for access to your repositories, including private ones. We store your GitHub username and ID and an encrypted access token. When you pick a repository, we read its description, README, languages, file list, recent commits (including commit authors’ names), open issues and pull requests, configuration files and a few main source files. We store a summary of this with your idea8 session and send it to Anthropic so idea8 can reason about your project. You can disconnect GitHub at any time: we ask GitHub to revoke the token and delete our copy straight away. To be certain access has ended, you can also revoke Clarity Club under Settings, Applications in your GitHub account.
The Deputy Health Check analyses a business’s Deputy workforce account. It only runs after a Deputy administrator for that business signs in to Deputy and grants access. By connecting, you confirm you are authorised to share the business’s Deputy data with us for this purpose.
What we read. Company and location settings, pay periods and rules, employment agreements and contracts, employee records, timesheets, rosters and similar records. From employee records we keep names, roles, start and end dates, dates of birth and pay rates; from timesheets we keep times, hours, cost and approval status. We do not keep contact details, addresses, payroll IDs or free-text notes.
How we hold it. Deputy gives us an access token that expires after 24 hours. We store the token and the data we read encrypted, only while the check runs, and delete both as soon as the run finishes or fails. A daily clean-up deletes anything older than 24 hours as a backstop. What we keep is the report: the findings, which can name individual employees (for example someone whose recorded age or pay looks wrong), plus a log of which Deputy endpoints we called. Health Check data is not sent to Anthropic or to PostHog.
Who can see the report. The member who started the check, the Deputy administrator who connected it, and our team. Either member can delete the report at any time. We also use a summary of the results to decide whether to offer the business a consultation.
Inviting your Deputy administrator. If you send a Health Check link to someone else and they connect as a Deputy System Administrator, we create a Clarity Club account for them using the name and email from their Deputy profile and email them a sign-in link. We only add them to marketing if they later opt in.
Payments are handled by Stripe. We give Stripe your name, email and account ID; we never see or store your full card details. We keep a record of your purchases, subscriptions, credits and refunds. When you claim free credits, we record your email address and IP address so we can stop the same person claiming them repeatedly.
When you register for a Clarity session we record your registration, how you paid and whether you attended. Sessions run on Google Meet: we give you the meeting link, and Google handles your participation under its own privacy policy. We do not send your details to Google.
If you send feedback on a document, we store your message and, if you give it, your email address so we can reply. To review feedback in bulk, we may send messages (without email addresses) to Anthropic to summarise them.
When you sign in to the desktop app, we email you a sign-in link and briefly store a one-time code and a record of the sign-in request. These are deleted shortly after they expire. Downloads of the installer are counted anonymously.
To protect sign-in and other forms from abuse, we limit how often they can be used from one email address or network. We keep these limits as one-way hashes rather than your actual email or IP address.
We do not sell your personal information.
If you opt in to updates, your name and email address are added to our email marketing list in Klaviyo, together with events such as the pages you read. All marketing emails include an unsubscribe link. You can opt out at any time without affecting your access to Clarity Club.
CRM (Pipedrive). When you verify your email and have opted in to updates, we also create a contact for you (name and email address) in Pipedrive, the customer relationship management tool we use to keep track of who we are in touch with. If you have not opted in, neither of these happens.
We use the following essential cookies, which are always on:
We also keep a few values in your browser’s storage: a random session identifier for our own usage records (jiffi-sid), your cookie choice (jiffi-cookie-consent), your light or dark theme (jiffi-theme), the campaign that brought you to us for the current visit (jiffi_utm), and an unsent idea8 message so it is not lost if you reload. When you are signed in, PostHog keeps its visitor and session IDs in browser storage so your activity is recognised across tabs and visits.
With your consent, we also load two third-party advertising pixels to measure how well our marketing works:
_fbp and related cookies to attribute visits to our ads.li_* cookies for the same purpose.These load only after you choose “Accept” in the cookie banner. If you decline, they are never loaded and set no cookies. For visitors who are not signed in, accepting also allows PostHog to remember your anonymous visitor ID between visits and to record your session as described above; if you decline, PostHog stores nothing in your browser and does not record your session. To change your choice, clear this site’s data in your browser.
Embedded content. Some pages embed videos from YouTube, Vimeo or Loom, and our booking pages use Calendly. These services may set their own cookies when the content loads. If you book a call through Calendly, the details you enter go to Calendly under its own privacy policy.
Your data is stored in a PostgreSQL database hosted for us through Vercel. All connections use TLS encryption. Access tokens for Deputy and GitHub are stored encrypted. We do not store passwords. Keys for our service providers are kept on our servers and never sent to your browser. We test changes on a separate copy of our systems; before any real data is copied there, names, emails, conversations, Health Check reports and other identifying data are removed or replaced.
Access by our team. A small number of our team can view member accounts, idea8 sessions (including uploaded file text) and Health Check reports to provide support, investigate problems and keep the service safe. Every time someone on our team opens a member’s idea8 sessions, it is logged.
How long we keep it. Usage records and recordings are kept for the periods set out in section 1. Your account, idea8 sessions and Health Check reports are kept until you delete them or ask us to. When you delete an idea8 session, it is removed from your account and the text extracted from its files is permanently deleted; the rest of the session stays in our records until you ask us to erase it. Payment and credit records are kept as long as tax law requires. Free-credit claim records are kept to prevent repeat claims.
Each service processes data under its own privacy policy. We only share the minimum data each service needs to work.
Overseas processing. Several of these providers store or process data outside Australia, including in the United States. We choose providers that protect personal information to a standard comparable to the Australian Privacy Principles.
You have the right to:
Deleting your account. You can delete your account from your Account page. This deletes your account, your reading progress and the Health Check reports you started, and signs you out. Purchase, credit and usage records stay in our records but are no longer linked to your account. Free-credit claim records, which hold your email and IP address, are kept to prevent repeat claims. Your idea8 sessions, GitHub connection, feedback, and the copies held by Klaviyo, Pipedrive and Stripe are not removed automatically yet: email us and we will erase them.
To exercise any of these rights, contact us at privacy@jiffi.co. If you are not happy with how we handle your request or a privacy complaint, you can contact the Office of the Australian Information Commissioner (oaic.gov.au).
We may update this privacy policy from time to time. Significant changes will be communicated via email or a notice on Clarity Club. Your continued use of Clarity Club after changes constitutes acceptance of the updated policy.
For privacy-related questions, contact us at privacy@jiffi.co.