Live nowResume builderUse BuildR FREE
HyeRHub.ai
Legal

Security

How we protect the data you trust us with on hyerhub.ai and BuildR. This page describes measures that are in place today and makes no claim beyond them.

Security
HyeRHub.ai
Last updated
25 September 2026
Reading time
2 min
Sections
8
Ask a question

At a glance

A quick summary. The full text below is what applies.

  • 1Everything runs on Microsoft Azure and is encrypted in transit and at rest.
  • 2Each BuildR account can see only its own data, and the database itself enforces that.
  • 3We don't claim certifications we don't have. We'll update this page when that changes.
  • 4Found a vulnerability? Email info@hyerhub.ai with "Security" in the subject line.
On this page8 sections ▾
  1. 01Certifications
  2. 02Infrastructure
  3. 03Encryption in transit
  4. 04Account isolation in BuildR
  5. 05Secure development
  6. 06Human oversight of AI
  7. 07If something goes wrong
  8. 08Reporting a vulnerability

01Certifications#

Please note

HyeRHub.ai does not currently hold SOC 2, ISO 27001 or any similar certification. When that changes, we will update this page. If your organisation needs a completed security questionnaire, contact info@hyerhub.ai.

02Infrastructure#

The website and BuildR are hosted on Microsoft Azure, in data centres operated by Microsoft with their own physical and environmental security. Data stored in our Azure services is encrypted at rest by the platform.

03Encryption in transit#

All traffic to hyerhub.ai uses HTTPS. Requests over plain HTTP are redirected to HTTPS, and the site sends a Strict-Transport-Security header, so browsers refuse unencrypted connections to it and its subdomains. The emails our forms generate are handed to Azure Communication Services over HTTPS.

04Account isolation in BuildR#

Every read in BuildR is scoped to the signed-in account. That separation is enforced in the database itself, not just in the interface, and automated tests verify it on every code change.

05Secure development#

  • Every change passes automated linting, content checks and a full production build before it can be deployed.
  • Deployment credentials, API keys and connection strings are held in secret stores, never in source code.
  • Form input is validated on the server and escaped before it is placed in any email.
  • File uploads are limited by type and size: CVs sent with job applications must be PDF or Word files of up to 4 MB, and BuildR uploads are limited to 10 MB.
  • Analytics runs only after consent, and the site embeds no third-party advertising or social media trackers.

06Human oversight of AI#

BuildR suggests changes and you decide what goes into your resume. Our hiring products, TalentOS and Assess, are not yet available. They are being designed so that offers, rejections and other decisions affecting a candidate are routed to a human reviewer, not taken automatically.

07If something goes wrong#

If we become aware of a breach affecting personal data, we will contain it, investigate it, and notify the people affected and the Data Protection Board of India as the DPDP Act requires.

08Reporting a vulnerability#

If you believe you have found a security vulnerability, email info@hyerhub.ai with "Security" in the subject line. Include enough detail for us to reproduce it. We will acknowledge your report and keep you updated while we fix it.

Please give us reasonable time to fix the issue before you disclose it publicly. Do not access, change or keep other people's data, and do not degrade the service for others. We will not pursue legal action against good-faith research that follows these rules.

Questions about this policy?

Write to us and a person on our team will reply.

Back to top