Privacy

Our privacy policy is being written properly.

Handling candidate data is the whole job, so this document is going to a solicitor before it goes on a website. What's below is true today and isn't a substitute for it.

Where things stand

We process candidate and client records on behalf of the agency that holds them. The agency is the controller of that data and GoodBuild is a processor acting on its instructions. The full policy, the sub-processor list and the data processing agreement are issued on request now and published here once they have been reviewed.

In the meantime. Email build@goodbuild.io and we'll send you the current document. We would rather hand you the real thing than leave a page of text here that a solicitor hasn't read.

Client Finder

The people it shows you.

Client Finder tells you which companies are hiring and who to speak to there. Some of that is information about a person, so here it is in full rather than in a sales call.

What it reads to find a company

Job adverts the company published itself. A vacancy on a job board was put there by the employer to be seen. No candidate data is involved, and no agency's own records are used to build it.

What it shows about a person

Name, job title, employer and business contact details, from a licensed business to business data provider under contract and named in our sub-processor register.

What it never does

Personal email addresses are switched off in the request we send, not filtered out afterwards. No scraped social profiles, no bought lists, and no profile of anybody beyond the working details above.

Nothing is fetched until asked

Contact details are only retrieved when a consultant opens one company and asks for them. Searching does not pull details for everybody it finds.

Who is responsible for what

We are responsible for obtaining those business details and putting them in the platform. The agency is responsible for deciding who to contact and what to say. Which of us answers for what is set out in the data processing agreement with the contract.

Taking yourself out of it

If your details have appeared and you would rather they had not, email build@goodbuild.io with your name and company. We will remove you, block you from being picked up again, and tell you which provider we got them from so you can ask them too. You do not have to give a reason.

True today

How we handle records today.

Separated at the database

One agency can't read another's records. The rule lives in the database rather than in a filter in the application above it.

Read, never emptied

Connecting your CRM doesn't move it. Switch GoodBuild off and your system is exactly as you left it.

Outbound is blocked on a trial

No email, text or call can reach a candidate or a client during a trial. The block is in the database, not in a setting.

Deleted on request

Anything held on our side is deleted when you ask after an account closes, and we confirm in writing when it's done.

Sub-processors named in writing

Ask and we'll send the current list of every third party that touches your data and what it does. It isn't published here because it changes.

Support access is asked for

If we need to look at your records to solve something, we ask first.