Know what you share.
Know what happens next.

Early access, explained.

Scout is operated by OCTO Labs Inc., the controller responsible for the personal information described in this notice. Scout is an early-access product branded by Hire DTC. C. reviews the requests and applications described here. Privacy questions can be sent to c@hiredtctalent.co.

This notice covers Scout’s public founder and candidate forms on this website. It also explains how the separate October hiring enquiry differs. It does not describe a future, fully launched search service.

Registering interest does not start a candidate search, create a verified account, guarantee access or commit you to a fee. The founder page’s example people and work are illustrative, not verified candidates.

What you send when you join.

On Scout for founders and its dedicated signup page, we collect the following at final submission:

• Your name, email and brand website.
• Your self-reported revenue band, hiring timing, and interest in early access, hiring support or both.
• Your contact permission, a request reference, timestamps, and the source information described below.

We use this information to understand interest in Scout, organise requests by business stage, and respond to the early access or hiring support you requested. Revenue bands are context you provide; they are not verified financial records.

The final form asks you to allow Hire DTC to contact you about your request and Scout early access. Older registrations may also contain country, hiring constraints, desired outcomes or experience requirements entered in an earlier form.

Your work, with its context.

The separate candidate application collects your name, email, professional links, specialisms and a work example. That example can include the brand, dates, engagement type, problem, your ownership, measures, results and an evidence link.

It also asks about the work you want next: engagement preferences, availability, hours, timezone, next challenge, and any feedback or additional thoughts you choose to share.

These answers are sent when you submit the application, for C. to review and contact you about candidate early access. The current form keeps unfinished answers in the open page rather than sending them as an application.

A submitted application is stored privately and marked as awaiting a claim or invitation. Identity, email, work ownership and results are not verified by submitting the form. It is not automatically published to founder search, and submission does not automatically send an invitation email.

Different forms save differently.

Dedicated Scout founder registration

Contact answers are sent at final submission, not as you type. Before that, the form records a visit, the revenue band you select and progress through its steps. These are linked to a random visit identifier. This is separate from saving your name, email or brand website.

Older Scout forms with “Save my details”

Earlier Scout forms included a separate, unchecked save-progress option. If a version you are using shows that option and you turn it on, valid name, email and website fields can be saved independently; timing and interest are added as selected. The owner can review the draft and receive an internal alert. Saving a draft does not enrol you in Scout emails.

On those forms, turning the option off or choosing “Remove saved draft” requests removal of the saved contact details. If removal fails, the form shows a retry option. You can also email C. Unfinished contact details are not kept in browser storage by these Scout forms.

October hiring enquiries

The October call-request form is a separate hiring enquiry. Its visible notice explains that a valid brand and email start saving an incomplete enquiry. Later answers update that same record, which is marked submitted only when you finish. Drafts do not automatically send you an email.

That form also keeps its answers and retry state in the browser tab’s session storage to support reloads and retries. This is different from Scout early-access registration.

How we understand where interest comes from.

Scout records the source, medium, campaign, creative and ad-set labels supplied in a link, plus visit time, form steps, selected revenue band and page variant. A later tagged link can update the current campaign while preserving the original attribution for that visit. This helps distinguish paid, direct and other incoming interest.

Some older landing tests assign a page variant to a visit and record whether it loaded and led to a registration. Page assignment and campaign labels are kept separately. These records are first-party information in Scout’s database.

Form cookie

scout_visit is a random identifier used for the Scout form session. It lasts one day, is sent securely on HTTPS, and cannot be read by page JavaScript.

Abuse protection

The application uses a daily salted hash derived from a network address to limit repeated attempts. The raw network address is not saved in the Scout signup record. Hosting services also process network requests to deliver and protect the site.

Meta advertising measurement is off on these public Scout forms.

The current public founder and candidate forms do not load a Meta Pixel or send a Scout Lead event. Source labels in an advertising link can still be saved as described above. Visiting or registering here does not opt you into Meta measurement.

Who handles the information.

C. can review registrations, applications and hiring enquiries in private owner views. Records and internal notes are not a public candidate directory. Hiring enquiries may also appear in Hire DTC’s private owner reporting view; that connection does not provide candidate-profile access.

Vercel

Serves the public website and forwards form requests to the application backend.

OpenAI Sites & Cloudflare

The Sites backend, running on Cloudflare with its D1 database, processes and stores form records and provides the private owner workspace.

Resend

Delivers Scout messages and internal notifications. Delivery requires recipient addresses and message content; delivery identifiers, status and retry information are retained by the application.

Google Fonts

Some Scout landing pages request fonts from Google. Those font requests include network and browser information needed to deliver them. This privacy page uses system fonts. Google’s explanation.

Opening an external link, such as a professional profile or a mail service, takes you to that provider’s service. Its handling of that visit is governed by its own notice.

What follows a registration.

Founder emails

A new, non-test Scout founder registration can enter a welcome-email sequence from c@hiredtctalent.co. Depending on your timing and interest, it can include one relevant follow-up: an evidence-preview reminder scheduled after two days, or hiring support after three days. “Later / exploring” is scheduled for the welcome only.

Delivery checks, a pause, or relevant card activity can stop a follow-up. Replies go to C.’s inbox; Scout does not automatically read them. Messages include a private link to stop automated Scout emails or remove the related request. A message already in delivery cannot be recalled automatically.

Internal notifications

Scout can send C. an internal alert containing saved registration details and source information. Older forms with permitted draft saving can send a draft alert too. This does not authorise marketing to an unfinished entry. Candidate applications use a separate flow and are not enrolled in this founder sequence.

Your private Scout card

A founder registration can receive a reference and private card link. The reference identifies a record; it is not a queue position or a count of members. An email hash helps keep it consistent across retained requests.

The private link can reveal your first name, revenue cohort, timing and interest, and provides management access. Keep it private: someone with the link can use those controls. Opening the preview, copying an invite or opening the hiring-support link on the card records that action. Copying an invite does not show that anyone received it.

What expires, and what needs a request.

Scout registrations & visits

Registration, visit and email-queue records are eligible for cleanup after 90 days. Cleanup runs during later form activity, rather than at an exact deletion time. Private cards stop loading after 90 days.

Legacy Scout drafts

Unfinished drafts are eligible for removal after 30 days without an update. Cleanup runs during later site activity or private review. Completing a registration clears its draft contact fields.

Rate-limit records

Protection records expire after two days and are removed during later cleanup.

Candidate applications & hiring enquiries

These separate records are not included in the Scout registration cleanup above. Contact C. to ask for access, correction or removal. The current candidate flow does not provide a self-service deletion account.

For a founder registration, the private management link can stop automated emails across retained requests for the same email address. Choosing removal deletes the linked registration, its queued messages and related owner-alert and CRM records. Other requests for the same email are not automatically deleted.

Delivered emails, mailbox copies and provider records are separate from the application record. Deleting a registration does not automatically recall delivered messages or erase every provider copy. Ask C. about those copies when requesting removal.

Earlier Hire DTC enquiries imported from Netlify can retain their original fields, dates and spam status, including network or browser metadata supplied by the former form service. They are separate from Scout registration records and their 90-day cleanup.

You can ask about your information.

You can ask what information Hire DTC holds about you, request a correction or deletion, or ask to stop contact. Use the mailbox below to describe the request and the record it concerns.

To stop contact, tell C. what you want to stop. Founder registration emails also include the private management controls described above. You do not need to submit another application or hiring enquiry to make a privacy request.

Include the email you used and, if available, your request reference. Do not send passwords, private card tokens or identity documents in an initial email. We may need enough information to identify the correct record before handling a request.