legal

Privacy Policy

Last updated 6 November 2026

AutoMindz Solutions LLC ("AutoMindz", "hyreflow", "we", "us") operates hyreflow.ai and the hyreflow recruitment-automation platform. AutoMindz Solutions LLC is registered in Dubai, United Arab Emirates. This policy explains what we collect, why, and the choices you have.

1. How we handle your recruiting data

hyreflow is infrastructure your agent calls, not a data warehouse. Candidate, company, and contact records you source or enrich through the platform are scoped to your workspace, processed to complete the call you made, and are not read, inspected, or repurposed by us. We do not sell recruiting data, candidate data, or customer records to third parties, ever.

2. Information we collect from the website and product

When you sign up, book a demo, or contact us, we collect what you give us directly: name, email, company, and any message content. When you use the CLI, SDK, or dashboard, we collect account and workspace metadata needed to operate the service: API key usage, credit balance and spend, session identifiers, and tool-call records (which tool ran, which provider served it, cost, timestamp) for billing, support, and abuse prevention.

We also keep a security log of account and access activity: sign-ins and failed sign-in attempts, and changes to members, invites, API keys, connected apps, billing settings and spending limits. Each entry records what happened, when, which account did it, and the IP address and browser or device it came from.

When you ask for one of our playbooks, we collect the name and email address you enter, which playbook you asked for, and the campaign tags in the page address that brought you there (the utm_source, medium, campaign, content and term, when present). We email you a personal link to the playbook. Each time that link opens a playbook we record the visit, so we know which playbooks you read. The link works like a password for the playbooks, so don't share it with anyone you wouldn't share the playbooks with.

3. Cookies and analytics

The dashboard uses essential cookies (session auth), plus the product analytics cookie described below only if you choose “Accept all”. For the Meta Pixel, Google Analytics and Dub described below, the rule depends on where you are. If you are in the United States, they are on by default and you can switch them off at any time by choosing “Reject all” in the cookie banner. Everywhere else, including the UK and the EU, they stay off unless you choose “Accept all”. We tell where you are from the country our network provider derives from your connection, and keep that two-letter country code in a cookie for one day so the page knows which rule applies. Wherever you are, if your browser sends a Global Privacy Control signal we treat it as “Reject all” and don't show the banner. You can change your choice at any time with “Your privacy choices” at the bottom of our marketing pages.

Where it is on, the Meta Pixel runs on the public marketing pages. It sets a cookie and reports the pages you view, and which call-to-action buttons you click (the button’s label, the section it sits in, and where it links to), to Meta Platforms so we can measure and improve our advertising; Meta’s use of that data is governed by its own privacy policy. It is never loaded in the signed-in product.

Under the same rule, our servers report two moments to Meta so the ad that brought you here can be credited: creating an account, and the first time an email address asks for one of our playbooks. Each report carries a one-way hash of your email address and first name, your IP address, browser type and country, the pixel’s cookie values if your browser has them, and, if you came from one of our Meta ads, that ad’s click identifier. A playbook report also says which playbook it was. They never include your password, anything you do inside the product, or the link to your playbooks. When you arrive from one of our Meta ads, we keep the ad’s click identifier in a first-party cookie for 90 days for this purpose, again only where the rule above allows.

Under the same rule, our servers also report the same two moments to LinkedIn, creating an account and the first time an email address asks for one of our playbooks, so a LinkedIn ad that brought you here can be credited. Each report carries a one-way hash of your email address and, if you arrived from a LinkedIn ad, LinkedIn’s own click identifier; it never includes your name, your password, anything you do inside the product, or the link to your playbooks. When you arrive from one of our LinkedIn ads, we keep that click identifier in a first-party cookie for 30 days for this purpose, again only where the rule above allows.

Under the same rule, Google Analytics runs on the public marketing and documentation pages. It sets cookies and reports the pages you view, the site that referred you, and your approximate location and device type to Google, along with the same call-to-action clicks reported to Meta (the button’s label, the section it sits in, and where it links to) and, when you request a playbook, which playbook it was, so we can see how visitors find and use the site; Google’s use of that data is governed by its own privacy policy. It is never loaded in the signed-in product.

Under the same rule, the LinkedIn Insight Tag runs on the public marketing pages. It sets cookies and reports the pages you view to LinkedIn, along with a conversion when you click a call-to-action button, book a call or request a playbook, so we can measure our LinkedIn advertising and show our ads to past visitors; LinkedIn reports these to us only in aggregate, and its use of that data is governed by its own privacy policy. It is never loaded in the signed-in product.

Under the same rule, Dub, a referral and affiliate link-tracking service, runs on our public marketing pages and the signed-in product. It sets a cookie (dub_id) for 90 days that remembers the referral link you arrived through, so we can credit the right partner or affiliate if you later create an account; it is readable on both hyreflow.ai and recruit.hyreflow.ai so that credit survives signing up on the product site.

When you arrive through a link tagged with a campaign source (a utm_sourceparameter, e.g. from a LinkedIn post), or open a shortlist page we sent you, we store that source name — and, if the link names them, the team member who shared it and the campaign (for a shortlist page, that page’s link name) — in first-party cookies for 30 days. If you then create an account, we read them once so our team can see which channel (and whose post or page) the sign-up came from. If you have accepted cookies, those values (source, team member and campaign) are also recorded with your sign-up in PostHog, as described below; otherwise it is never sent to a third party.

The docs assistant — the chat button on our documentation and marketing pages — keeps your conversation in your browser’s session storage so it survives a page reload, and clears it when you close the tab or after 24 hours, whichever comes first. That is storage on your own device, not a cookie and not a tracker: it is never sent to a third party and never used to recognise you elsewhere. The questions themselves are answered by software we run on our own infrastructure, using only our public documentation as source material; they are not used to train anything.

We use PostHog, an analytics service hosted in the EU, on our marketing pages and in the signed-in product, to see which pages and features are used. PostHog receives your IP address, which it uses to derive your approximate location. It records the pages you view, the links and buttons you click (inside the product, without their text), how far you scroll, page load performance, the referring site, and your browser and device type. Until you choose “Accept all” it sets no cookie and stores nothing in your browser, so it cannot recognise you from one visit to the next. If you accept, it keeps an identifier in a cookie and local storage so your visits can be linked; choosing “Reject all” later deletes it. Accepting also turns on session recording: a replay of the pages you see and what you do on them (mouse movement, clicks, scrolling, page changes and page load timing), which we watch to find what is confusing or broken. Anything you type into a form is hidden from the recording, and the addresses of the pages you visit are recorded without their search or sign-in details. Inside the product all text on the page, link addresses and images are hidden too, so the candidate and contact details you work with are not recorded. Recordings are kept for 30 days. Choosing “Reject all” stops new recording; recordings already made are kept until those 30 days run out. While you are signed in, what you do in the product is linked to your account, and PostHog holds your account ID, email address and name. Our servers also send it a record of certain actions you take (signing in, connecting a provider key, submitting feedback, starting a checkout or changing a subscription) and of errors you run into. When you book a call with us, we also record that a call was booked and which kind, without your name or email address. PostHog processes this data on our behalf. Analytics data is never sold or used for advertising.

Your cookie choice applies across hyreflow.ai and recruit.hyreflow.ai, so you are only asked once. We keep it in a small cookie that shares your choice between the two sites. Before you choose, the page you came from and any campaign tags in the link are recorded with that anonymous page view, but nothing is kept in your browser and it is not linked to you. If you accept, the campaign and site that brought you to us are kept and linked to your account. Once you sign in, having accepted, your visits to hyreflow.ai in the same browser are linked to your account until you sign out. If you are signed in and have accepted, you may see a short, optional survey inside the signed-in dashboard. You can ignore it.

4. Product telemetry is on by default

Session-level telemetry used for support and debugging is enabled by default for CLI and agent runs, and the CLI tells you so at install time. It records run traces, including tool inputs and outputs, the provider, timing and outcome, and the request your agent supplies with a run: the ask you typed, sent when a session starts or alongside a tool call. We do not capture your surrounding agent conversation. Traces include workspace and user identifiers, account email, and client version when available so we can investigate your runs. Traces are stored with our observability providers, Langfuse and PostHog. We filter recognized contact fields and recognizable email addresses, profile links, and phone numbers from trace payloads. This filtering does not anonymize all free-form text.

Recording is decided in two places. Your workspace can be set to always record, never record, or to follow each installation's own preference; where it is set, it takes precedence. hyreflow telemetry on|off (or HYREFLOW_TELEMETRY=0) sets that per-installation preference, and hyreflow telemetry status reports only it, so it can print "off" while your workspace is still recording. Ask us what your workspace is set to, or to turn recording off for it.

5. How we use personal information

To provide and bill the service, respond to support requests, send product and security notices, send the playbooks you ask for and understand which of them people read and which campaigns bring them, keep accounts secure, investigate misuse, show who changed what for compliance and audits, and meet legal obligations. We do not sell your personal information to third parties.

6. Sub-processors and hosting

We use reputable cloud infrastructure and payment providers to run hyreflow and process payments, and an email delivery provider to send sign-in links and the playbook emails you ask for. PostHog, an EU-hosted product analytics service, processes the analytics data described in section 3 on our behalf. Any vendor adapter you configure (BYOK or managed) is invoked directly to fulfil your request. Vendor credentials you provide are used only to call that vendor on your behalf and are never shared with other customers or used for purposes outside your own workflows.

7. Data retention

Account and billing records are retained for as long as your account is active and for a reasonable period after (typically up to 7 years) to meet accounting and legal obligations. Website contact-form submissions are retained up to 2 years. Playbook requests (your name, email, campaign tags and the playbooks you opened) are kept for as long as we offer the playbooks, unless you ask us to delete them sooner; deleting them also stops your playbook link from working. The security log is kept for 12 months, then deleted. It is kept for that period even if you delete your account or workspace, so we can investigate misuse. You can request deletion of your account data at any time, subject to what we're legally required to keep.

8. Security

Data in transit is encrypted. Access to production systems is limited to staff who need it, behind multi-factor authentication. API keys are hashed at rest; we never store vendor credentials in plaintext. We record security-relevant actions, including our own staff's access to customer accounts, in a log that can't be edited through the product.

9. Your rights

Depending on where you're located, you may have rights to access, correct, export, or delete your personal information, including under the UAE's Personal Data Protection Law (Federal Decree-Law No. 45 of 2021) and, for EU/UK residents, the GDPR/UK GDPR. To exercise any of these, contact us below.

10. Changes to this policy

We'll update the date at the top of this page when this policy changes, and notify active accounts by email of material changes.

11. Contact us

Questions about this policy or your data: [email protected].