GDPR Guide for Architecture Job Seekers

GDPR matters in an architecture job search because your CV, portfolio, contact details, salary information and employment history are personal data.

This guide is practical, not legal advice. The key point is simple: candidates should know who has their details, where they are being sent and why.

Watch: what happens behind the scenes in recruitment

This Architecture Social video is useful because GDPR becomes easier to understand when candidates know how recruitment processes actually work.

Watch the video

Related audio: behind the scenes in architecture recruitment

This related episode adds more context on recruitment process, representation and what candidates should understand before sharing documents.

What GDPR means in a job search

When you apply for a role or speak to a recruiter, you are usually sharing personal data for recruitment purposes. That data should be handled clearly and fairly.

• Your CV should not be sent to practices without a clear reason.
• You should understand who is representing you.
• Your details should be accurate and relevant.
• Old or unnecessary data should not be kept forever.
• You can ask what data is held about you.

What hiring teams usually hold

Hiring creates personal data quickly: CVs, portfolios, contact details, salary expectations, right-to-work information, interview notes and sometimes sensitive context. Those files often travel between hiring managers, directors, HR, recruiters and sometimes clients. Ask who has seen your details and why.

GOV.UK data protection guidance says organisations must use personal data fairly, lawfully and transparently, and only in a way that is adequate, relevant and limited to what is necessary. You can ask what data an organisation holds about you.

If you are hiring

Keep recruitment data clear, limited, secure and respectful. Only collect what you genuinely need for the role. Interview notes should be factual and tied to the selection criteria. Do not keep unsuccessful candidate data indefinitely just in case.

You need a lawful basis for processing recruitment data. Consent is not always the neat answer, especially where there is an imbalance between candidate and employer. The ICO says you must have a valid lawful basis, and consent is only one of the available bases.

Use the ICO recruitment and selection guidance and the ICO lawful basis guide for the current official position. Get a data protection adviser for a live situation.

Recruiter consent matters

A good recruiter should tell you where they want to send your CV and why the opportunity fits. Blanket CV sending damages trust and can create problems if multiple people approach the same practice on your behalf.

If you are unsure, ask directly: which practice is this, what role is it for and have you already sent my details anywhere?

Keep your own records

Track where you have applied and who has represented you. This helps avoid duplicate submissions and gives you a clearer view of your own job search.

Common mistakes

• Letting multiple recruiters send your CV without coordination.
• Not asking where your details are going.
• Sending outdated CVs and portfolios.
• Ignoring privacy policies completely.
• Assuming every recruiter works the same way.

Architecture Social view

Stephen’s recruiter view is that GDPR should not be used to make recruitment feel cold or robotic. It should make representation clearer, more respectful and easier to trust.

Next step

Use this with the follow-up guide, the architecture interview guide, live architecture jobs and the Architecture Social privacy policy.

For practical next steps, compare the architecture salary guide, browse current architecture jobs, set up architecture job alerts or contact Architecture Social for tailored advice.