Pre-production registry
Last updated August 23, 2026On this page
HireHint publishes verified provider appointments, not a reconstructed list of every integration or development option in the codebase.
The current empty production registry is intentional and truthful. It must be completed from the approved production architecture before customer data is processed by an external provider.
Current registry status
HireHint has not approved a production subprocessor registry for external publication. Development code, a provider catalog, an environment-variable option, a disabled integration, a trial account, or a local test does not establish that a provider processes production customer data.
The registry will list a provider only after the production service, data categories, purpose, location, transfer path, agreement, security review, and activation evidence are approved.
| Provider | Purpose | Data and people | Processing location | Status |
|---|---|---|---|---|
| No production subprocessor entry is approved for publication. | ||||
What counts as a subprocessor
A subprocessor is a third party appointed by HireHint to process customer-controlled personal data on HireHint’s behalf. A customer-selected integration may instead act directly for the customer, depending on who determines the purpose, configuration, and instructions.
A software dependency, public website link, payment prospect, provider option, or internal business vendor is not automatically a subprocessor for customer-controlled candidate or employee data.
Required entry evidence
- Approved provider legal name and service description.
- Specific processing purpose and product feature.
- Categories of people and personal data involved.
- Hosting and support locations and any remote-access locations.
- Controller, processor, or independent third-party role classification.
- Executed processing and confidentiality terms and any approved transfer mechanism.
- Security, privacy, resilience, deletion, and incident-notice review.
- Production activation owner, date, evidence, and change-notice classification.
Service categories under review
- Application hosting, managed databases, object storage, backup, delivery, and monitoring.
- Authentication and identity services.
- Customer communications and calendar delivery.
- File scanning, document processing, and electronic signature services.
- Payment processing and subscription administration.
- AI and model providers for explicitly enabled, permission-scoped features.
- Customer support and incident-management services.
These are review categories, not provider appointments or evidence that customer data has been transmitted externally.
Customer-selected integrations
HireHint may display integrations that a customer can choose to configure. The product distinguishes catalog, configured, ready, active, failed, disconnected, and deferred states. The customer should review the provider’s terms, permissions, data use, retention, and destination before activation.
Where HireHint appoints the provider on the customer’s behalf, the approved registry should identify it. Where the customer contracts with or directs the provider independently, the customer remains responsible for the corresponding notice and agreement.
Changes and customer objections
The final Data Processing Addendum must define the advance notice period and delivery method for a new or replacement subprocessor. It must also define the customer’s reasonable objection period, the grounds for objection, remediation options, and any termination right.
Emergency substitutions needed to protect security or continuity should receive notice as soon as reasonably possible and remain subject to the same approval controls.
Questions and updates
Use HireHint Support for questions about this registry. A production registry should offer an approved update-subscription method only after the notification channel and privacy contact have been operationally established.