Privacy Policy

Who runs the service

Refolk operates anysearch, a tool for discovering people, repositories, and organizations from public data sources. For privacy questions, contact hello@refolk.ai.

Data collected

• Account data. Email, name, and avatar provided by your sign-in provider (Google or GitHub). If you connect GitHub, an OAuth token is stored and used only to query GitHub on your behalf.
• Usage data. Search queries, conversations, credit ledger entries, and basic request metadata (timestamps, IP, user agent) needed to operate, secure, and bill the service.
• Payment data. Stripe handles all card data. Only the Stripe customer/charge identifiers needed to reconcile credit top-ups are stored.
• Search results. Public data about third parties returned by GitHub, third-party people/company data providers, GH Archive, and Anthropic web search. Results are cached transiently to make follow-up questions fast.

How it is used

• To run searches you request and return results in your conversations.
• To operate accounts, credits, billing, and customer support.
• To prevent abuse, fraud, and to protect the service and its users.
• To improve product quality (aggregated, de-identified usage analysis).

Refolk does not sell personal data, and does not use your conversations to train third-party models.

The browser extension

Refolk AutoApply is an optional Chrome extension that fills a job application form in from what your Refolk account already holds. It is what makes an application possible on boards that only accept a submission made in your own browser. It never presses submit: it fills the form in, scrolls the employer’s own submit button into view, and stops.

• Where it runs. Only on four job board domains and on refolk.ai. It cannot read any other site, and on those four it acts only when you click it.
• What leaves your browser. The address of the job page you clicked it on, the access key described below, and anything you type into the note box yourself. Nothing else. The contents of the page are read in the tab and are not sent anywhere.
• What comes back. Your own answers, your resume, and the cover letter written for that one application. This is fetched per application, used to fill the form in, and gone when the tab closes. The extension stores none of it.
• What it stores. One access key, in the browser’s own extension storage. That key is issued when you press connect on your account page, it is not your sign-in, and only its hash is kept server-side. Revoking it from that page stops the extension working and leaves you signed in everywhere else.
• Telling Refolk something. The extension has a note box, in its toolbar popup and under the message left after a form is filled in. What is sent is what you typed, the address of the board page you were on, the line the extension had just shown you, and its version - and only when you press send. It arrives as an email to the support address with your own address as the reply-to, so a reply comes back to you. Nothing is read off the page to fill it in.
• Verification codes. Some boards email a one-time code before they will accept a form. If you have connected your mailbox, the extension asks for that code so it can be typed in for you. The code is used once and never stored.

What the extension does not collect, stated because the permissions it asks for would allow some of it and it does not do it:

• No browsing history. The address of the one job page you clicked it on is sent, so the right application can be identified. No list of pages you have visited is collected, and it can see no page outside the four job board domains and this site.
• No other tabs, and no activity. No keystrokes, clicks, mouse position, or scrolling are recorded anywhere.
• No credentials of yours. The only credential involved is the key this account issued to the extension. Your password and your sign-in are never read, and no password you type into a form is collected.
• No mailbox access from the extension. Where a board holds an application until an emailed code is typed back in, that code is looked up server-side under the read grant you gave separately, and the extension receives the code and nothing else. It cannot read your email.
• No location, health, or financial data. A city or country you have put on your own answer sheet is filled into forms that ask for it, which is your answer being reused rather than your position being measured.

Nothing the extension collects is sold, used for advertising, used to build a profile for any purpose other than filling in your applications, or passed to a third party. There is no analytics or tracking code in it.

Reading your mailbox for the hiring pipeline

On the hiring side you can let the pipeline read your Gmail so that candidates move along on their own: to the stage set for "when you email them" when you write to them, and to the stage set for "when they reply" when they answer with interest. This is a separate, read-only permission from the one used to send email, and it is off until you connect it.

• What it asks Google for. Only messages to or from the email addresses of people on your own pipeline. Every message is checked against that list again before anything is done with it, and mail with anybody else is never read.
• What it keeps. For each message: its id, which candidate it was with, and how a reply read (interested, a question, not interested, out of office), with a one-line summary on the candidate's card. The subject and the body of your mail are never stored.
• Who reads it. A reply is read by an AI model to label it and write that one line, and by nothing else. It is not used to train models and not shared.
• Stopping it. Disconnect at any time. The record of which messages were read goes with the connection; the moves it already made stay on the candidates' timelines.

The sourcing extension

Refolk Sourcer is an optional Chrome extension for the hiring side. On a LinkedIn profile you are viewing, it shows a button that adds that person to one of your roles in Refolk.

• What it reads. Only when you open its panel on a profile page: the name, headline, location, current title and company shown on that page, and the profile's address. You can edit all of it before anything is sent.
• What it sends. When you open its panel, the profile's address, so your account can say which of your roles that person is already on. When you press add, those fields, any email you type, and the role and stage you picked. All of it goes to your own Refolk account and nowhere else.
• What it stores. The sign-in token Refolk issued it, in extension storage. Connecting goes through a Refolk sign-in and approval page, so the extension never sees your password, and the connection can be revoked from your account at any time.
• What it does not do. It reads no page other than the profile you opened its panel on, runs no background collection, sends nothing to anyone but Refolk, and carries no analytics or tracking code.

Subprocessors

Only the minimum data required is shared with these processors:

• Supabase / Neon (Postgres hosting)
• Vercel (application hosting)
• Anthropic (LLM and web-search)
• Stripe (payments)
• Resend (transactional email)
• Google & GitHub (sign-in)
• Third-party people/company data providers, GitHub API, Google BigQuery (data sources)
• PostHog (product analytics, session replay and error tracking)
• Microsoft Clarity (session replay and heatmaps)
• DataFast (web analytics)
• Umami (web analytics)

Third-party data and your rights

anysearch surfaces public information about third parties from sources like GitHub. If you are a data subject and want your information removed from results returned to Refolk users, email hello@refolk.ai and the request will be actioned within 30 days where the law requires.

Under GDPR/CCPA you may request access, correction, deletion, or export of your account data. Account holders can delete their account at any time at refolk.ai/account/delete or from the account screen of either phone app, or by emailing the address above. Deleting removes the account, conversations, published searches and credit ledger at once; payment records stay with the payment processor for as long as the law requires.

Retention

Account and conversation data are retained for as long as your account is active. Payment records are kept by the payment processor for as long as financial recordkeeping requires. Logs and telemetry are retained for up to 90 days.

Security

Data is encrypted in transit (TLS) and at rest. Access to production systems is limited to authorized personnel using SSO and least-privilege controls.

Children

The service is not intended for users under 16.

Changes

Material changes are posted here and the “Last updated” date changes. Continued use of the service after a change means you accept the updated policy.