knowhash — Privacy

What every knowhash product reads

When you're on a LinkedIn profile page, the extension reads that page — the name, headline, company and city visible on screen — to fill in the template you choose.

If you've asked a contact whether WhatsApp would be easier, knowhash also reads your open LinkedIn conversation with that person, to spot a phone number they replied with and offer to save it. Nothing is saved unless you confirm.

It reads nothing else: no other tabs, no other sites, and no other LinkedIn pages or conversations.

What stays on your device only

• Your templates — the messages you write, saved in your browser's local storage.
• Your own details — the name/company/position you enter under "Your details," used to fill your own identity into templates, and your own WhatsApp number if you choose to add it.
• Follow-up reminders — the reminders you set on people's profiles, with any notes you add.
• WhatsApp numbers — the numbers of contacts who chose to share them with you, saved only after you confirm, along with a note of when you last messaged them.

This is stored in Chrome's own chrome.storage.local and never leaves your browser, whether you're using free knowhash or knowhash Recruit.

knowhash (the free tier) does exactly this and nothing more — no backend, no server, no network requests of any kind. It never sends a message for you: when you message a contact on WhatsApp, knowhash opens WhatsApp with your message ready, and you choose whether to send it. Desktop alerts for reminders are optional and only turned on if you allow them.

If you've only ever installed the free knowhash extension, the rest of this page doesn't apply to you.

knowhash Recruit — account & licence data

Recruit is licensed per browser install, not per person. The first time the extension runs on LinkedIn, it quietly creates a record for that install so your free month can start straight away. That record is identified by a randomly generated install ID (not tied to your identity by itself) and, until you choose to verify an email address, holds only:

• The install ID
• When the install was first used, and when your free month started
• When the extension was last used (updated at most about twice a day, so we can see whether installs are active — not a record of what you do)
• Your approximate country, detected automatically from your network location — not precise location, not tracked afterwards
• Your licence status (free month, active, past due, cancelled)

If you verify your email inside the extension (needed to subscribe or to send candidate detail requests), the same record also holds:

• Your email address (used to verify you and for account communication — not shown to anyone else, not unique across installs)
• The name and agency you provide
• Your LinkedIn member ID, only if the extension happened to be open on your own LinkedIn profile during setup — entirely optional, used only to link your installs together in our own records
• If you subscribe, your subscription status, kept in sync with Stripe

This data is used solely to run licensing, feature access, and basic support/marketing visibility (e.g. which countries our customers are in). It's never sold, shared with advertisers or data brokers, or used to build advertising profiles.

Payment details

Billing is handled entirely by Stripe. We never see or store your card number — Stripe's own checkout and customer portal manage that directly. We store only a Stripe customer/subscription reference so we know your account is active.

kSIP — collecting candidate details on your behalf

Recruit lets you send a candidate a secure link requesting specific details (e.g. availability, salary expectations, or custom questions you choose). Here's what happens to that information:

• The candidate's answers are submitted to our server and held briefly in encrypted storage, identified by a one-time link credential only you and the candidate have.
• Your extension retrieves the answers the next time you're on LinkedIn, after which they're deleted from our server.
• If a link is never opened or completed, any partial data is automatically deleted after 14 days.
• We do not read, use, or share candidate answers ourselves — the sole purpose is relaying them from the candidate back to the recruiter who requested them.

Branded briefs & shortlists

If you choose to send a candidate brief or shortlist as a branded link, we store the logo and colour choices you upload against your account, so links you send are styled consistently with your own agency's branding rather than knowhash's. The brief/shortlist content itself is held on a time-limited, secure link and automatically deleted after 14 days.

Your roles stay yours

knowhash is built by a recruiter, and we know that typing a vacancy into a recruiter's tool can feel like handing over a lead. So here is our promise. knowhash is run separately from Team Employment, the recruitment agency behind it. We never use the roles you enter in knowhash, or anything about them, to approach your company, your clients or your candidates, and we never sell them or show them to other knowhash users. Your roles are used for one thing: drafting your documents.

knowhash Role, on knowhash.com

knowhash Role turns your notes about a role into candidate questions, a position description and a job ad. When you use it:

• What you write (the role title, your notes, the options you pick) is stored with your role so you can come back to it, and is sent to our AI provider, Anthropic, to draft your documents. Anthropic processes it only to produce the draft; it isn't used to build advertising profiles.
• Your email, if you give it, is used to send you your private link, copies of documents you ask for, and candidates' answers. Nothing else.
• Candidates' answers to your questions are stored with your role so you can read them, and emailed to you if you've given an email. The AI never reads, scores or ranks them. You decide.
• Documents you share are visible to anyone with the share link, read-only. The link never opens your role page or anyone's answers.
• The start form and the candidate form are protected by Google reCAPTCHA, which checks for bots. Google's own privacy policy and terms apply to that check.

To delete a role and its answers, email us. See also How we use AI.

What knowhash Recruit does not do

• Does not send messages or invites on your behalf — it only fills the compose box or generates a link. You review and click Send yourself, every time.
• Does not use your data, or a candidate's data, for advertising or profiling of any kind.
• Does not sell or share data with third parties, except the minimum needed to operate the service itself (Stripe for payment, SendGrid for email, Anthropic for drafting knowhash Role documents, and Google reCAPTCHA for bot checks).
• Does not let anyone at knowhash read your messages, templates, or candidate submissions as a matter of course — access is limited to what's needed to fix a specific issue you've raised.

Uninstalling & account deletion

Uninstalling either extension deletes everything stored locally in your browser — templates, your details, reminders and saved WhatsApp numbers — immediately. You can also delete any reminder or saved number yourself at any time. Your server-side Recruit account record (email, licence status, etc.) is kept so that reinstalling doesn't lose your paid status; if you'd like that deleted entirely, email us and we'll remove it.

Questions

Contact feedback@knowhash.com. knowhash and knowhash Recruit are products of Optimum Internet Pty Ltd (ACN 117 538 173).