Scout

Data processing agreement

Version 2026-10-27 · Last updated 27 October 2026

This agreement is between the organisation that uses Scout (“the customer”) and WELCO AI S.R.L. (“Scout”). It applies to the personal data that Scout processes on behalf of the customer in providing the service described in the terms of service, and is part of them. It is accepted together with them when the organisation is created.

It meets the requirements of Article 28(3) of the General Data Protection Regulation (Regulation (EU) 2016/679, “GDPR”). The customer is the controller of the data and Scout is its processor. Terms used here have the meaning they have in the GDPR.

1. Subject matter, duration, nature and purpose

Subject matter and purpose. Scout provides recruiting software. The customer uses it to find, read, assess, rank, contact and keep track of people in connection with its own recruitment. Scout processes personal data only to provide that service to the customer.

Nature. Storing, organising, reading, extracting facts from, scoring and ranking with AI models, drafting messages, sending messages and connection requests when the customer asks, searching, exporting, and deleting.

Duration. For as long as the customer uses Scout, and afterwards until the data is deleted or returned under section 11.

The types of personal data and the categories of people are in Annex 1.

2. Documented instructions

Scout processes the data only on the customer’s documented instructions, including for transfers to a third country, unless EU or Member State law requires otherwise, in which case Scout tells the customer before processing unless that law forbids it.

The customer’s instructions are this agreement, the terms of service, and what its users ask the service to do in the app: starting a run, adding or deleting a candidate, sending a message, or setting a retention period. Further instructions need to be in writing and within what the service can do. Scout tells the customer without delay if it believes an instruction breaks data protection law.

Scout processes some data as a controller in its own right: the accounts of the customer’s users, billing, the usage ledger and the security of the service. That is covered by the privacy policy and not by this agreement. Scout will not use the personal data it processes for the customer for its own purposes, including to train AI models.

3. The customer's responsibilities

The customer is responsible for:

  • having a lawful basis for processing, and a documented assessment where it relies on legitimate interest;
  • the notices owed to people whose data it holds, including the Article 14 notice to people it did not collect the data from, no later than its first message to them;
  • answering the requests of the people concerned, with the help in section 6;
  • choosing how long to keep the data and setting that in the app, and not adding data it has no right to add;
  • the decisions it takes about people, which must be taken by a person and not by a score alone.

4. Confidentiality

Scout makes sure that the people it authorises to process the data have committed themselves to confidentiality or are under an appropriate statutory duty of confidentiality, and that they process the data only as far as their work needs.

5. Security

Scout takes the measures required by Article 32 GDPR, taking into account the state of the art, the cost, the nature, scope, context and purposes of the processing, and the risks to people. The measures in place on the date of this agreement are summarised in Annex 2. Scout may change them if the change does not lower the level of protection.

6. Sub-processors

The customer gives Scout a general authorisation to use sub-processors. The ones in use are listed on the sub-processors page, with what each does, what data it handles and where.

  • Scout tells the owner of the customer’s organisation by email at least 30 days before it adds a sub-processor or replaces one, or gives one a new kind of data or a new location.
  • The customer can object within that time, on reasonable grounds relating to data protection. Scout then tries to find a way to serve the customer without the change. If it cannot, the customer can end the affected service before the change takes effect, and receives a refund of the prepaid fee for the time after that.
  • Scout binds each sub-processor by a contract that imposes the same data protection obligations as this agreement, in particular sufficient guarantees of appropriate technical and organisational measures. If a sub-processor fails to meet them, Scout remains fully responsible to the customer for it.

7. Helping with the rights of the people concerned

Taking into account the nature of the processing, Scout helps the customer, by appropriate technical and organisational measures, to answer requests to exercise rights under Chapter III GDPR: access, rectification, erasure, restriction, portability and objection.

  • Scout provides tools in the app: in Organisation > Data and privacy an owner can find everything held about one person across the organisation, export it, erase it, and add the person to a suppression list so that they are not collected again. Scores come with the evidence behind them, which helps answer a request for an explanation.
  • If a person writes to Scout about data it processes for the customer, Scout does not answer the request itself. It tells the person to ask the customer, and passes the request on to the customer within five working days unless the person asks it not to.
  • For anything the tools do not cover, Scout helps on request within a reasonable time, and may charge for help that goes beyond what is reasonable.

8. Impact assessments and Articles 32 to 36

Scout helps the customer to meet its obligations under Articles 32 to 36 GDPR (security, breach notification, data protection impact assessments and prior consultation), taking into account the nature of the processing and the information it has. It provides on request a description of what the system does, the security measures, and the information about the AI systems that the customer needs for an impact assessment, including under Article 26(9) of the AI Act.

9. Personal data breaches

Scout tells the customer without undue delay after becoming aware of a personal data breach affecting the customer’s data, and in any case within 48 hours, by email to the owners of the organisation. The notice includes what Scout knows at that point: the nature of the breach, the categories and approximate number of people and records concerned, the likely consequences, and the measures taken or proposed. Where it is not possible to give all of it at once, Scout gives it in stages without further undue delay.

Scout acts at once to contain and fix the breach, and works with the customer so that it can meet its own duty to notify the supervisory authority and the people concerned. Scout does not tell them itself, or name the customer publicly, unless the law requires it or the customer agrees.

10. Audits

Scout makes available to the customer all the information needed to show that it meets Article 28 GDPR, including this agreement, the description of the measures in Annex 2 and its record of processing as a processor, and allows for and contributes to audits.

The customer should first use that information. If it is not enough, or after a breach, or when an authority requires it, the customer or an independent auditor it chooses, bound to confidentiality, may audit Scout once in any 12 months, on 30 days’ written notice, during business hours, in a way that does not disrupt Scout or its other customers and does not give access to other customers’ data. The customer bears the cost of the audit, including Scout’s reasonable time.

11. Deletion or return at the end

When the service ends or the organisation is closed, Scout, at the customer’s choice, returns or deletes the personal data. The customer can export lists and one person’s data from the app before that, and can ask Scout within 30 days for anything else in a common format. Scout then deletes the data within 30 days after the end or the closure, and deletes the existing copies unless EU or Member State law requires it to keep them, such as invoices. Copies in the backups of Scout’s database provider disappear as those backups expire, on the provider’s schedule. Scout confirms the deletion in writing on request.

During the service, the customer controls how long candidates are kept with the retention setting in Organisation > Data and privacy, and the careers pages keep applications for the period their notice states. Scout deletes on those instructions.

12. International transfers

Scout keeps the customer’s database and files in the EU (Frankfurt). Some sub-processors work from the United States, and Scout transfers personal data to them only on a basis allowed by Chapter V GDPR: the EU-US Data Privacy Framework where the sub-processor is certified under it, and otherwise the standard contractual clauses adopted by Commission Implementing Decision (EU) 2021/914 (Module Three, processor to processor), with a transfer impact assessment and the additional measures it calls for. The sub-processors page says which applies to which.

Where processing by Scout is itself a transfer from the customer to a third country and no other basis applies, the parties agree to the standard contractual clauses (Module Two, controller to processor), which are incorporated here by reference, with these choices: clause 7 (docking) applies; clause 9(a), option 2, general authorisation, with the time in section 6 above; clause 11(a), the optional wording does not apply; clause 17, option 1, the law of Romania; clause 18(b), the courts of Romania. Annex I of the clauses is Annex 1 here, Annex II is Annex 2, and Annex III is the sub-processors page. The competent supervisory authority is that of the customer’s establishment, and for a customer in Romania the ANSPDCP.

13. Artificial intelligence

Parts of Scout are AI systems that evaluate candidates, which the EU AI Act (Regulation (EU) 2024/1689) classes as high-risk (Annex III, point 4). Scout is their provider; the customer is their deployer. The two have different duties, which apply from the dates the Act sets.

Who does what under the AI Act
Scout, as providerThe customer, as deployer
Designs the system so that a person oversees it: every score shows its evidence, scores only order a list and never reject anyone or change a stage, and a person can set any stage by hand.Assigns people with the competence and the authority to oversee it, and makes sure they know the limits of the system and the risk of trusting its output too much.
Keeps records of each reading: the model, the prompt version, the input and the per-criterion result.Keeps the logs under its control for at least six months, unless other law says otherwise.
Gives instructions for use, including what the scores are and are not, their limits and the measures for human oversight.Uses the system as the instructions say, and makes sure the data it adds is relevant to the purpose.
Tells the customer of anything it learns about a risk or a serious incident that the customer should act on, and cooperates with the authorities.Monitors the use, tells Scout of risks and serious incidents it notices, and stops using the system if it believes it presents a risk.
Does not use the customer's data to train models.Tells candidates that an AI system is used in assessing them, and explains its role in a decision on request.

Neither party will use the service for a practice the Act prohibits, such as inferring emotions at work or using a person’s protected characteristics to rank them.

14. Term, changes and liability

This agreement lasts as long as Scout processes personal data for the customer. Its sections on confidentiality, deletion and liability carry on after that. The terms of service say how it can be changed, and the sub-processor list changes as section 6 says. The limits of liability in the terms of service apply to this agreement, unless the law says otherwise. The law of Romania governs it, and the courts named in the terms of service have jurisdiction.

Questions and notices: contact@scoutnext.io.

Annex 1. Details of the processing

Details of the processing
ItemDetail
Who the people areCandidates the customer sources from public LinkedIn profiles, adds from CVs, pastes or imports; people who apply through the customer's careers page; people named in a CV (referees, previous employers' contacts); and the customer's own users.
Profile dataName, headline, location, public profile address, work history, education, skills, languages and anything else a public profile shows, as the recruiter's browser reads it.
CVs and application filesThe file, the text read from it, and whatever it contains: contact details, work history, qualifications, and anything else the person chose to write, which can include a photograph, a date of birth and, without anyone asking for it, special categories of data.
Contact detailsEmail address, phone number, LinkedIn address.
AssessmentsScores and per-criterion findings, the quotes from the CV or profile that support them, strengths, gaps and questions to ask, and the text vectors (embeddings) used to search.
Messages and relationshipsThe text of the messages and connection requests the customer sent through Scout, their status, replies the customer pastes in, and the facts read from a pasted conversation (interest, salary expectations, notice period).
NotesNotes by the customer's users about a candidate, and mentions of colleagues.
Careers applicationsName, email, phone, LinkedIn address, CV and other files, the answers given, the version of the privacy notice shown and accepted, and whether the person agreed to be kept for other roles.
Users of the customerName, work email, picture, role and access in the organisation, chats with SEI (kept 30 days), and records of what they did that cost credits.
Run recordsA log of each browser run: which step, which page (address and title), warnings shown and the first part of what was there.
Retention in the serviceUntil the customer deletes the data, or the retention setting does. Careers applications are deleted six months after the last application or after the role closes, whichever is first, unless the person agreed to be kept longer. At the end of the service: section 11.

Annex 2. Security measures

A summary of what is in place. The full description, including what is planned and not yet done, is available to customers on request.

  • Separation between customers. Every record belongs to an organisation, and the database itself, through row-level security, refuses to show or change a record to anyone outside it. This does not depend on the application behaving.
  • Access by role. Owners and members have different rights. A member can be limited to the candidates assigned to them. The database enforces that, and so do checks in the server for the work the system does on the member’s behalf.
  • Privileged access kept narrow. The server keys that bypass row-level security are used only on the server, only for the few things a person’s own session cannot do, and each such use is limited to one organisation by its identifier. Actions by Scout staff in the admin area are logged.
  • Encryption. Data is encrypted in transit (TLS) and at rest by the hosting and database providers.
  • Location. The database and the stored files are in the EU. The application is served from the United States, so data passes through there in use.
  • Sign-in and requests. People sign in with a single-use link sent to their email, and sessions can be ended. Requests that change data are checked to come from Scout, abusable routes are rate limited, and billing and scheduled-job routes verify who is calling.
  • The extension. It has permission only for LinkedIn and Scout, no access to other tabs or browsing history, and stops when LinkedIn shows a warning.
  • Backups and recovery. The database provider keeps backups, which let Scout recover from a failure.
  • Secrets. Keys and passwords are held in the hosting provider’s environment and never in the code or the browser.
  • Records and procedures. Scout keeps a record of its processing, a written breach procedure, and a list of its sub-processors with their contracts.

Annex 3. Sub-processors

  1. The list of sub-processors as it stands, with its date, is part of this agreement.