Scout

Sub-processors

Last updated 27 October 2026

Scout uses the companies below to run the service. For candidates’ data, they are sub-processors under our data processing agreement: our customers authorise them in general, and we are responsible for them.

This is the list as of 27 October 2026. It is checked against what the application calls, so a service that is not here is not used for personal data.

The list

Sub-processors used by Scout
Sub-processorWhat forDataWhereTransfer basis
SupabaseDatabase, sign-in and file storage.Everything the app stores: accounts and organisations, candidates and their scores, CVs and uploaded files, messages, notes, applications, billing state.EU, Frankfurt (Amazon Web Services, eu-central-1).Data stays in the EU. Supabase, Inc. is a US company; where its staff outside the EU can reach data for support, the standard contractual clauses in its data processing addendum apply.
VercelHosting of the application and the scheduled jobs that run it.Whatever passes through the application while it is used: requests and responses, which include candidate data, and the server logs of those requests. Vercel keeps no database of Scout’s.United States (Washington, D.C. region, iad1).Standard contractual clauses in Vercel’s data processing addendum, and the EU-US Data Privacy Framework where Vercel is certified under it.
OpenAIAI models and text embeddings: reading and scoring profiles and CVs, writing job descriptions, checklists and message drafts, running the sourcing agent, and the SEI assistant.The text of profiles, CVs, briefs, notes and messages sent for a task, and page images of scanned CVs. OpenAI keeps requests for up to 30 days to monitor for abuse and does not train its models on data sent through its API.United States.Standard contractual clauses in OpenAI’s data processing addendum, and the EU-US Data Privacy Framework where OpenAI is certified under it.
ResendDelivery of the emails Scout sends: sign-in links, invitations, billing and usage notices, mentions in notes, and confirmations to people who apply through a careers page.The recipient’s name and address and the email itself. An application confirmation names the applicant, the role and the organisation; a mention email names a candidate by first name and initial of the last name.United States.Standard contractual clauses in Resend’s data processing addendum.
StripeCard payments and subscriptions.The billing contact, name, address and VAT or tax number of an organisation, and its card details, which only Stripe holds. No candidate data.EU and United States (Stripe Payments Europe, Ireland, and Stripe, Inc.).Standard contractual clauses in Stripe’s data processing agreement, and the EU-US Data Privacy Framework where Stripe is certified under it.
SmartBillIssuing the Romanian fiscal invoice for each payment and filing it with e-Factura.The organisation’s name, address and tax number, and the invoice lines. No candidate data.Romania.None needed: the data stays in the EU.
ImprovMXForwarding of email sent to Scout’s contact and CV addresses to Scout’s own mailbox.Those emails and their attachments. A candidate who sends a CV to the CV address sends it through this service.United States and EU (ImprovMX Incorporated, Delaware).Standard contractual clauses in ImprovMX’s data processing addendum.
PostHogAnalytics on the public website, only after the visitor accepts the cookie banner. Not used inside the app.Page views, clicks and scrolling, and a replay of the session with form fields hidden. For a visitor who opens a personal link from us and accepts analytics, the name and company we wrote to them under.EU (PostHog Cloud EU, Frankfurt).None needed: the data stays in the EU.

Each processes data only to provide its service to Scout and under a contract that binds it to the same data protection duties we have towards our customers.

Changes to this list

We tell the owner of each organisation by email at least 30 days before a new sub-processor starts to handle their data, or before an existing one is given a new kind of data or a new location. The email says who, what for, what data and where.

An owner can object during those 30 days by writing to contact@scoutnext.io, with the reason. We then try to find a way to carry on without the change for that organisation. If we cannot and the owner still objects, they can end the subscription before the change takes effect, and we refund the part of any prepaid fee that covers the time after that.

Removing a sub-processor, or changing the details above without a change of the data they handle or where, needs no notice. The “Last updated” date at the top moves with every change.

What is not on the list

  • Scout’s servers never contact LinkedIn. The extension runs in the recruiter’s own browser, on their own session, and LinkedIn is not our sub-processor.
  • Customers’ own tools, such as the email or calendar a recruiter uses to reply to a candidate, are the customer’s.
  • Our accountants, lawyers and auditors see invoices and contracts under a duty of confidentiality; they do not handle candidates’ data.