Last updated 4 August 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.
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.
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.
The marketing site and dashboard use only essential cookies (session auth). We do not use third-party advertising trackers. If we add analytics in future, we'll update this section first.
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 — which tool ran, which provider served it, timing and outcome — together with the ask that started the run: the prompt you typed, not the surrounding conversation, and no agent replies. Personal data is redacted before anything is stored. Turn it off at any time with hyreflow telemetry off (or HYREFLOW_TELEMETRY=0); once disabled, no traces are recorded for that installation. Check the current setting with hyreflow telemetry status.
One exception, so it is stated plainly: a workspace can have recording pinned on or off for the whole workspace, as a support or debugging arrangement agreed with us. A pin takes precedence over the per-installation setting above, and hyreflow telemetry status reads only the local setting, so it can report that telemetry is off while a pin is recording. Ask us and we will tell you what your workspace is set to, or clear it.
To provide and bill the service, respond to support requests, send product and security notices, and meet legal obligations. We do not sell your personal information to third parties.
We use reputable cloud infrastructure and payment providers to run Hyreflow and process payments. 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.
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. You can request deletion of your account data at any time, subject to what we're legally required to keep.
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.
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.
We'll update the date at the top of this page when this policy changes, and notify active accounts by email of material changes.
Questions about this policy or your data: [email protected].