Privacy notice
Who is responsible for your data
Each contracting authority (for example a council) that runs a procurement on Below Threshold is the controller of the personal data in that procurement. It decides what it collects and why. Young Procurement, which provides Below Threshold, is its processor: we hold and handle the data on the authority's behalf, under a data processing agreement, and only on its instructions.
For the running of the website itself (security logs, the public demo, and accounts for the people who run the platform), Young Procurement is the controller.
Contact: privacy@belowthreshold.co.uk. For a question about a particular procurement, contact the authority running it.
What we hold
- Buyer staff: name, work email address, role, sign-in records.
- Suppliers: the email address you confirm with a code, your name and organisation, your questions, your submissions and files, and any outcome letter sent to you.
- Everyone: an audit record of actions (who did what, and when), kept to show how each procurement was run, and essential cookies (see cookies).
We do not use your data for marketing, we do not sell it, and we do not use any AI or automated decision-making: people evaluate and decide.
Why, and the lawful basis
To run procurements and keep a record of them. Each authority decides its lawful basis; for most public bodies this is that the processing is needed for a task in the public interest (UK GDPR Article 6(1)(e)). For the website's own security logs, our basis is legitimate interests in keeping the service secure.
Where it is held
Hosting region: to be confirmed before any live procurement.
Sub-processors
| Company | What it does | Where |
|---|---|---|
| Railway Corporation | Hosting: runs the application, the database, stored files and backups | Hosting region above. Railway is a US company. |
| Email service: not connected yet | When connected, it will send codes, invitations, clarifications, receipts and outcome letters. It will be IONOS (our own mailbox) or Resend; this notice will name it. | To be confirmed |
The virus scanner (ClamAV) runs inside our own hosting: files are not sent to another company to be scanned.
Where data goes to the United States, it is protected by [safeguard to be confirmed before live use, for example the UK Extension to the EU-US Data Privacy Framework or the International Data Transfer Agreement].
How long we keep it
- Procurement records: for the period the authority sets after the procurement is closed or cancelled (7 years by default). Then submissions, files, assessments, invitations and questions are deleted. A summary, the decision, the contract entry, notices and the audit trail are kept as the authority's record. A procurement under legal hold is kept until the hold is lifted.
- Email log: 90 days.
- Supplier codes: work for 15 minutes and are deleted within a day.
- Files that fail the virus check: kept in quarantine for 30 days, then deleted.
- Backups: 35 days.
- Demo sandboxes: 7 days. Do not put real information in the demo.
If something goes wrong
If we become aware of a personal data breach affecting an authority's data, we will tell that authority without undue delay, and in any case within 24 hours. The authority decides whether to report it to the Information Commissioner, which must normally be done within 72 hours, and whether to tell the people affected.
Your rights
You can ask for a copy of your data, ask for it to be corrected or deleted, or object to how it is used. For data in a procurement, contact the authority running it; we will help them respond. You can complain to the Information Commissioner's Office.
Organisations: see the data processing agreement and DPIA templates.