Greenhouse Software, Inc.: data broker profile and opt-out route
This record explains how to contact Greenhouse Software, Inc., what the catalog currently records about its request workflow, what information may be needed to match a record, and what evidence to keep. It is a source-backed routing reference—not proof that Greenhouse Software, Inc. accepted, processed, or completed a request.
Quick answer
To request removal from Greenhouse Software, Inc., use the recorded provider route at greenhouse-privacy.relyance.ai ↗. The catalog currently records Both as the request method, an estimated processing time of Within the timeframe required by applicable law; no universal SLA stated, and latest evidence dated 2026-08-13.
Greenhouse Software, Inc. at a glance
- Domain
- greenhouse.com
- Request method
- Both
- Catalog difficulty
- 4/5
- Processing estimate
- Within the timeframe required by applicable law; no universal SLA stated
- Standard ID flag
- Not flagged in standard workflow
- Country scope
- US, EU/UK, Global
- Evidence grade
- First-party route checked
- Evidence status
- Current route evidence recorded
- Independent route observation
- URL route observed
- Read-only semantic disposition
- Not recorded
- Legal operator
- Not recorded
- Parent entity
- Not recorded
- Catalog lifecycle
- Active Catalog Record
- Lifecycle status
- Active Catalog Record
- Registry matches
- None recorded
- Evidence conflicts
- None recorded
- Recorded data domains
- b2b sales intelligence, professional identity, employment data, company affiliation
- Source checked
- 2026-08-13
- Entity reviewed
- 2026-08-12
- Next route review
- 2026-09-27
How to use this Greenhouse Software, Inc. opt-out record
- 1
Open the provider route and confirm that it matches Greenhouse Software, Inc. and the type of record you want to address.
- 2
Prepare only the matching information the provider asks for. The catalog records required fields as Information Sufficient To Identify The Relevant Greenhouse-Controlled Record, Request Type And Contact Information.
- 3
Review the request, submit it yourself, save any confirmation, and re-check the source listing after the provider window. A prepared draft is not a completed deletion.
Recorded workflow details
Request types
- Access Personal Information
- Correct Personal Information
- Delete Personal Information Where Applicable
- Opt Out Marketing Communications
- Opt Out Disclosure Or Sharing Where Applicable
- Object Or Restrict Processing
- Data Portability
- Withdraw Consent
Submission channels
- Data Subject Request Portal
- Privacy Email
- Job Seeker Opt Out Email
Required fields
- Information Sufficient To Identify The Relevant Greenhouse-Controlled Record
- Request Type And Contact Information
Optional or contextual fields
- Name
- Email Address
- Country Or State
- Job-Seeker, MyGreenhouse, Marketing-List, Or Product Context
- Authorized-Agent Documentation
Extra steps
- Greenhouse Says Its Policy Does Not Apply To Personal Information Collected And Used By Greenhouse Customers, Such As Information Submitted Through An Employer'S Greenhouse-Hosted Job Board; Those Requests May Need To Go To The Employer.
- The Current Policy Provides Access, Correction, Deletion, Objection, Restriction, And Portability Routes Through The Data Subject Request Portal.
- The Job-Seeker Opt-Out Route Applies To Users Of MyGreenhouse In The EEA, Switzerland, Or UK And Asks For Name, Email, And State Or Country; Do Not Generalize That Route To Every Greenhouse Product.
- Greenhouse May Retain Or Isolate Information In Backups Or For Legal, Tax, Accounting, Or Legitimate Business Needs.
Completion evidence to keep
- Privacy Form Confirmation
- Email Sent Record
- Broker Response
- Future Profile Or Job Seeker Recheck
What this record is associated with
The catalog and matched registry evidence associate this provider with the following data domains:
- b2b sales intelligence
- professional identity
- employment data
- company affiliation
These labels describe documented business or registry context. They do not prove that a particular person has a profile or that every listed domain uses the same request route.
Registry-declared data and regulatory signals
Data signals
Not recorded in matched registry rows.
Published sharing context
No positive sharing flag recorded.
Regulated contexts
No positive regulated-context flag recorded.
These are provider or registry declarations where available. They describe collection or business context; they do not prove that a particular person appears in the database or that removal will affect every downstream recipient.
Identity and verification boundary
Provider-specific expectation: Greenhouse routes privacy requests through its Data Subject Request Portal and may require information sufficient to verify the requester or authorized agent; the cited policy does not require a universal government-ID document.
Government-ID expectation: No universal government-ID requirement is stated in the cited current policy or request portal.
Do not attach a government ID or other sensitive document unless the provider's current instructions require it for the request you are making. Redact unnecessary fields where the provider allows it.
Legal entity and registry context
No matched government-registry profile is recorded for this catalog entry yet. Treat the provider name and route as source-backed catalog data, not as a confirmed legal-entity relationship.
Evidence, freshness, and limitations
Evidence grade: First-party route checked. Useful evidence: this record tracks 73/258 tracked fields across 100 evidence facts. Current route checked 2026-08-13. Next route recheck due 2026-09-27.
The source links below support the recorded route and workflow fields. A source page, HTTP response, registry row, or email address does not prove that a provider accepted a request, deleted data, or will not republish it.
Source ledger
| Evidence type | Source | Observed/checked |
|---|---|---|
| catalog route | https://greenhouse-privacy.relyance.ai/ ↗ | 2026-08-13 |
| provider-published workflow source | https://www.greenhouse.com/uk/privacy-policy ↗ | 2026-08-12 |
| provider-published workflow source | https://greenhouse-privacy.relyance.ai/ ↗ | 2026-08-12 |
| provider-published workflow source | https://www.greenhouse.com/march-3-2025-privacy-policy ↗ | 2026-08-12 |
Evidence label: Official Current First Party Policy And Live DSR Portal Confirmed Scope Limited. Source checked: 2026-08-13.
Latest web route observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://greenhouse-privacy.relyance.ai/.
Latest independent provider URL observation: 2026-08-13 · reachable · HTTP/status 200 · final URL https://greenhouse-privacy.relyance.ai/ · observed URL https://greenhouse-privacy.relyance.ai/. This is a read-only observation of a provider-published URL; it does not by itself establish canonical route semantics, form submission, request acceptance, or deletion.
Latest email-domain observation: 2026-08-13 · DNS reachable · greenhouse.io. Mailbox acceptance was not tested.
What is still unknown in this snapshot
This profile is intentionally explicit about its limits. “Not recorded” means no source-backed value is present in this snapshot; it does not mean the provider lacks the information.
Missing or unknown tracked fields (3 total):
- Aliases
- Parent Entity
- Suppression Group
Next evidence actions:
- Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.
- Classify the broker's products, data types, use cases, and operating scope from first-party or regulator evidence.
- Match regulator records to the legal entity and preserve jurisdiction-specific scope, collection, sharing, and request-metric evidence.
Incomplete evidence dimensions: Entity, Business, Regulatory, Workflow, Route, Privacy, Verification, Catalog, Provenance.
Evidence completeness by dimension
| Dimension | Documented | Coverage | Status |
|---|---|---|---|
| catalog metadata | 7/14 fields | 50.0% | partial |
| contact routes | 16/22 fields | 72.7% | partial |
| data categories | 2/32 fields | 6.3% | partial |
| entity identity | 4/20 fields | 20.0% | partial |
| privacy risk | 5/28 fields | 17.9% | partial |
| registry profile | 0/39 fields | 0.0% | missing |
| request workflow | 12/41 fields | 29.3% | partial |
| route checks | 12/38 fields | 31.6% | partial |
| source provenance | 15/24 fields | 62.5% | partial |
Coverage is the share of tracked fields with a recorded value in this evidence snapshot. It is not a quality score, removal rate, or proof that unrecorded information does not exist.
Related B2B & Sales Intelligence profiles
These records are grouped with Greenhouse Software, Inc. under the same catalog category. The grouping is for discovery; it does not establish common ownership, shared suppression, or a shared request outcome.
- 6sense Insights, Inc.
6sense.com
Current route evidence recorded
- Accurate Append Inc.
accurateappend.com
Current route evidence recorded
- Acquire Media U.S., LLC (Moody's Analytics NewsEdge)
newsedge.com
Current route evidence recorded
- Adapt.io
adapt.io
First-party request-route candidate; manual review required
- AdeptID, Inc.
adept-id.com
Current route evidence recorded
- AeroLeads
aeroleads.com
First-party request-route candidate; manual review required
Greenhouse Software, Inc. opt-out FAQ
How do I opt out of Greenhouse Software, Inc.?
Use the provider route at https://greenhouse-privacy.relyance.ai/. Review the fields and verification steps before submitting. A reachable page does not prove that the provider accepted or completed a request.
Does Greenhouse Software, Inc. require government ID?
No universal government-ID requirement is stated in the cited current policy or request portal.
How long does Greenhouse Software, Inc. take to process an opt-out?
The catalog estimate is Within the timeframe required by applicable law; no universal SLA stated. This is an estimate, not an SLA or proof of deletion. Check the provider response and re-check the source listing yourself.
What is still unverified about Greenhouse Software, Inc.?
This snapshot does not record source-backed values for Aliases, Parent Entity, Suppression Group. Confirm legal name, DBA names, ownership, shared suppression routes, and lifecycle from an official source.