Additional service terms

Scope and order of precedence

These draft additional terms describe service-level and messaging topics that may apply when an approved order activates the relevant commitment or external communications capability.

They do not create an uptime guarantee, service credit, delivery promise, provider appointment, telephone number, sender identity, or permission to contact a recipient. The approved order and main service agreement must identify any binding commitment.

Service availability and support

HireHint is designed with explicit loading, error, recovery, permission, audit, and data-integrity behavior. Those product controls do not by themselves create a contractual availability percentage or recovery objective.

A customer receives a service-level agreement only when an approved order expressly includes one. The final schedule must identify the covered production service, measurement source, measurement period, exclusions, support channel, priority definitions, response targets, remedy, claim process, and sole-remedy effect if applicable.

Current service-commitment register

Maintenance and exclusions

If a service-level schedule is later approved, it should define scheduled and emergency maintenance, customer-caused failures, unsupported configurations, third-party services, internet conditions, force majeure, suspended accounts, previews, beta features, and other justified exclusions.

An exclusion must not conceal a HireHint-controlled failure that the approved schedule requires HireHint to count.

Status communications and incidents

A production status page, incident channel, and post-incident process should be published only after the service, monitoring source, owners, update cadence, and subscriber behavior are active. Local health checks or test monitoring are not a public production status service.

Email and text messaging acceptable use

HireHint may support customer-authorized email, text message, invitation, reminder, calendar, or workflow communications when the required provider, sender, recipient, permission, and product state are active. A draft, preview, disabled provider, or visible button does not prove that delivery is available or authorized.

• Contact only recipients the customer is permitted to contact for the stated recruiting, employee, or business purpose.
• Provide required sender identity, notices, consent language, opt-out method, and frequency or charge disclosures.
• Honor opt-outs, suppression records, quiet-hour rules, reassigned-number risk, and applicable do-not-contact requirements.
• Do not send deceptive, discriminatory, harassing, unlawful, malicious, or unrelated promotional content.
• Do not use purchased, scraped, or unlawfully obtained contact lists.
• Do not bypass provider restrictions, delivery gates, rate limits, recipient validation, or audit controls.

Consent and communication records

The customer is responsible for determining the legal basis for each communication and maintaining any consent, notice, source, opt-out, and suppression evidence required by law. HireHint should preserve supported delivery and audit outcomes without representing a queued action as delivered.

Candidate or employee contact information should not be reused for a new purpose merely because it exists in the workspace.

Providers and delivery outcomes

External delivery depends on the configured provider and destination. HireHint distinguishes draft, queued, accepted, delivered, failed, deferred, suppressed, and unavailable outcomes where the provider evidence supports that distinction.

HireHint cannot guarantee that a third party will accept, display, or deliver a communication. Provider callbacks, bounces, complaints, and delivery receipts must not be claimed unless the corresponding integration is active and verified.

Restricted content and uses

• Credentials, authentication codes, payment-card data, or unnecessary sensitive personal data.
• Unlawful employment criteria, discriminatory instructions, retaliation, threats, or harassment.
• Malware, phishing, impersonation, fraudulent offers, or misleading sender information.
• Content that infringes confidentiality, privacy, publicity, intellectual-property, or contractual rights.
• High-volume marketing or automated outreach outside the customer’s approved service purpose.

Enforcement and restoration

HireHint may restrict a sender, template, destination, provider, workspace, or communication feature to investigate suspected abuse, protect recipients or the service, comply with law, or follow a provider requirement. Restoration may require verified remediation and renewed authorization.

The final agreement should define notice and appeal behavior while preserving emergency protective action where delay would create material risk.

Customer configuration responsibilities

• Verify the sender domain, sender identity, reply destination, templates, recipients, and provider configuration.
• Assign messaging permissions only to users who need them.
• Review sample or preview content before an external action is enabled.
• Monitor complaints, opt-outs, failures, and provider restrictions and correct the underlying cause.
• Protect exported recipient lists and message records outside HireHint.

Changes and contact

Material changes should receive an updated date and appropriate notice after these terms become effective. Use HireHint Support for questions or to report suspected messaging abuse or a service concern.