eQuest is the middle step, not the destination
eQuest is a job distribution platform. We take job ads that are already published on your career site and send them to the job boards you choose, so more people see them. We're not a job board and we're not an applicant tracking system.
Your ATS or system
Workday, Oracle Recruiting Cloud, another ATS through our API, your career site, or a job file. This is where your jobs are created and where candidates end up.
Your organization
You decide which jobs go out, which boards they go to, and who at your company can use eQuest. Your own job board accounts stay yours.
eQuest
We receive the job content you send, format it for each board, and deliver it. We process it only to provide the service, and only as your agreement with us allows.
Jobs go out. Applications don't come through us.
Job ads flow from your systems, through eQuest, to the boards. When a candidate applies, they go straight to your career site, your ATS, or the board. eQuest is never in that path.
A short list, on purpose
We keep what we need to deliver your jobs and nothing more. Most of it is job ad content that's meant to be public anyway.
What eQuest handles
- Job ad contentTitle, description, location, pay, and the other details a board shows. It's written to be published.
- Job codes and settingsJob function and industry codes, posting rules, and which boards each job goes to.
- Your users' work email addressesFor the recruiters and admins at your company who use eQuest. Used for sign in and access.
- A job contact email, only when neededA few boards require an email on the job. When they do, it's the recruiter or team address you provide.
- Account setupYour posting accounts, permissions, board accounts, and integration settings. Credentials are stored encrypted.
- Anonymous activity countsViews, clicks, and completed applies per board. We count that an apply happened, not who applied.
What eQuest doesn't handle
- Candidate dataNo resumes, applications, candidate contact details, or screening answers. Candidates apply on your site, your ATS, or the board.
- Sensitive personal dataNo health, financial, government ID, biometric, or other special category data. Our agreements don't allow it to be sent to us.
- Hiring decisionsWe don't screen, score, or rank candidates, and we don't make automated decisions about people.
- Selling or sharing your dataWe don't sell personal information or give it to outside parties without your consent.
- Marketing to your usersWe don't use work emails for marketing or profiling, and we don't send unsolicited email.
- Consumer sign upsNobody signs up for eQuest on their own. Your organization sets up and manages every user.
The details, by type of data
| Data | Type | Where it comes from | Why we need it | Who receives it |
|---|---|---|---|---|
| Job ad content | Public by design | Your ATS, API, career site, or job file | To build and deliver the job ad | The job boards you choose |
| Job codes and posting rules | Configuration | You, or set up by eQuest for you | To classify jobs and send them to the right boards | Boards receive the codes they need |
| User work email | Personal data | Your organization, or your sign in system | Sign in, account setup, and board access | No one. It stays in eQuest. |
| Job contact email | Personal data | The job, when you include one | Only for boards that require an email on the job | Only those boards |
| Accounts and credentials | Configuration | Your eQuest admins | To connect to your systems and your board accounts | No one. Stored encrypted. |
| Views, clicks, and applies | Anonymous | Job boards and an optional tracking pixel | To show which boards are working for you | You, in eQuest reporting |
Once a job is live on a board, it's public, and the board's own terms and privacy policy apply to how it's shown. Your board accounts are yours, and eQuest doesn't control a board's publishing.
The one piece of personal data, and how we treat it
A work email is usually already public through company websites and job listings. We still protect it like any other personal data.
Sign in and access only
It signs your users in, often through single sign on from your ATS, and ties each user to the boards and accounts they're allowed to use.
No marketing, no profiling
We don't use it for marketing or any other purpose, we don't share it outside of delivering the service, and we never send unsolicited email.
Encrypted, and yours to remove
It's encrypted in transit and at rest. Your organization adds and removes users, and any address can be permanently deleted on request.
How we protect what we hold
Our security and privacy policies are owned by our security team and reviewed at least once a year.
Protecting the data
- Our API only accepts encrypted HTTPS connections.
- Work emails are encrypted in transit and at rest.
- Integration credentials are stored encrypted, and we ask that they're entered directly into eQuest, never sent by email.
- Systems are monitored for intrusions and unexpected file changes, and our security controls are monitored continuously.
- Independent penetration tests cover both our network and our application.
- New and changed systems go through a privacy review before they launch.
People and process
- Only staff who need access to do their job get it, and it's removed as soon as they don't.
- Everyone with access is bound by confidentiality and trained on data protection.
- All staff follow a code of conduct that covers ethics, conflicts of interest, and anti-bribery.
- Our critical hosting providers are risk assessed, and their SOC 2 reports are reviewed every year.
- Concerns can be reported anonymously, and no one is penalized for raising one in good faith.
- We carry cybersecurity insurance.
If something goes wrong
If we discover a breach involving your data, we contain it first, then tell you without undue delay, and within 48 hours when possible. We'll help you with any report you need to make to a regulator.
Built to keep running
eQuest runs in a U.S. data center in California, with backup and recovery systems on Amazon Web Services in the United States and Europe.
Backups
Databases are copied off site in real time, with daily, weekly, and monthly backups and a six month archive.
A ready standby
A dedicated standby environment is continuously tested and validated every day, ready to take over production if needed.
Office independent
Production runs off site. If an eQuest office is affected, the service isn't, and our team keeps working remotely.
Your data, your call
Our privacy program is built around the main data protection laws in the places we do business.
Laws our program is built around
When data moves between countries, we use the safeguards those laws call for, like standard contractual clauses.
Requests and retention
- Your users can ask to see, correct, or delete their information. We respond within one month, and act on deletion requests without undue delay.
- We keep your data while you use eQuest, unless you ask us to delete it or the law requires otherwise.
- When your agreement ends, we delete or anonymize your data, whichever you choose.
- Beyond delivering your jobs, we only disclose data when the law requires it or your agreement allows it.
Need more detail?
Our reports and policies are available in the eQuest Trust Center. Documents there are shared under an NDA.
Your Data Processing Agreement and Service Level Agreement are part of your agreement with eQuest. Ask your account manager for a copy.
Visit the Trust CenterCommon questions
Does eQuest store resumes or job applications?
No. Candidates apply on your career site, in your ATS, or through the job board's own apply. Applications never pass through eQuest.
Do job boards get any personal data from eQuest?
Generally no. The job ad is the only thing we send. A few boards require a contact email on the job, and in those cases they get the recruiter or team address you provide.
Is eQuest a data controller or a data processor?
A processor. Your organization is the controller and decides what we process and why. We only process data to deliver the service you've signed up for.
What does eQuest track for reporting?
Job views, apply clicks, and, if you add our tracking pixel to your career site, completed applies. These are counts. We record that an apply happened, not who the candidate is.
Where is our data stored?
In a data center in the United States. Backup and recovery systems run on Amazon Web Services in the United States and Europe.
Can we get the list of providers eQuest uses?
Yes. Provider details are shared under an NDA. Request them through the eQuest Trust Center.
Does eQuest have a Data Protection Officer?
The laws we follow only require one for organizations that process sensitive data or monitor people on a large scale, and eQuest does neither. Privacy and data protection are owned by our security team.
What happens to our data if we stop using eQuest?
When your agreement ends, we delete or anonymize your data, whichever you choose. If you use one of our ATS integrations, your admin should also turn off the connection so eQuest stops reading from your system.
Do we need an agreement before we connect?
Yes. Every customer and partner needs an agreement in place with eQuest before building or turning on an integration. That's also where the Data Processing Agreement comes in.
Questions about your data?
Your eQuest account manager can answer questions about your account. For security reports and policies, use the Trust Center. Documents there are shared under an NDA.