Task family

Egocentric Makeup and Lash Application Data

Applying makeup, extending and tinting lashes, shaping brows and carrying out basic skin treatments, captured from the practitioner point of view with consented participants against a spec you write, for beauty robot training data and fast, on-demand custom personal-care data collection.
Catalog rows
Three, all in Hair Salon, Barbershop & Beauty Studio
Skill rating
Medium to Hard
Billing
Per validated hour
License
Buyer-owned

Requirements

What does makeup and lash application data need?

01

Named steps

Applying makeup, extending a lash, tinting, shaping a brow and cleansing the skin are different steps, so a spec names each one and the order they run in.

02

A stated service set

The catalog rows say makeup application, lash extension, tinting, shaping, brow styling, facial cleansing, moisturizing, exfoliation, foot spa and waxing, and no more, so the spec says which services your policy needs.

03

Hands and tool in view

A head-mounted view or a multiview rig keeps the practitioner’s hands and the tool in frame through the whole sequence.

04

Step boundaries on the same clock

Frame-accurate action segments mark where one step ends and the next begins against the accept criteria in the spec.

05

Consented participants and rights you can ship on

Every episode links to a signed contributor release, and the license is perpetual and buyer-owned.

Why it matters

What is egocentric makeup and lash application data, and why does it need its own page?

Egocentric makeup and lash application data is real-world video of the physical work of beauty services done close to a client: a practitioner applies makeup, extends or tints lashes, shapes and styles brows and carries out basic skin and beauty treatments. It is recorded against a written spec, with the streams the site states for its custom collections.

The hair salon and beauty page lists these three rows inside a table of thirteen. This page centres them. It describes task video only, and it makes no cosmetic brand, skin-safety, dermatological, hygiene or certification claim.

Catalog rows

Which catalog rows cover makeup, lashes and brows?

Three, all in the Hair Salon, Barbershop & Beauty Studio environment under the Beauty & Personal Care sector. "Makeup Application" is described as professional makeup application in a salon or studio. It is rated Medium and listed as Available on request. "Eyelash & Eyebrow Services" is described as lash extension, tinting, shaping and brow styling services. It is rated Hard and listed as Available on request.

"Basic Skin & Beauty Treatments" is described as facial cleansing, moisturizing, exfoliation, foot spa and waxing treatments. It is rated Medium and listed as Available on request. Every row lists a head-mounted phone or a multiview rig as the capture mode, and the steps inside each service are set by your spec. The site’s meaning for Available on request is that the work is scoped and recruited to spec when a buyer asks for it.

The difference

How does it differ from hair and nail rows in the same environment?

The Hair Salon, Barbershop & Beauty Studio environment has 13 rows, and three of them are the makeup, lash, brow and skin rows. The others are hair cutting, colouring and styling rows, nail rows, a general "Beauty Services / Personal Care" row and workspace sanitation, and they are separate listings.

For the whole environment, see the hair salon and beauty page. The site has no separate nail salon and manicure page, so the nail rows are covered only there.

Streams

What does a makeup or lash episode record?

Firsthand custom collections record ten hardware-synchronized streams aligned under 2 ms, with head and wrist RGB, depth, 3D hand pose with a per-joint visibility flag, contact and grasp events and frame-accurate action segments. The one language label the site states is a task instruction for each episode.

Standard capture is cameras, depth and IMU. A separate glove tier records a tactile signal, and the site does not state whether it applies to these rows. The site lists no label for the outcome of a service, such as the finish of a lash set or a makeup look. It does not state a working distance or how close-range work is handled, so settle both in the spec.

Privacy

How are consented participants, faces and screens handled?

Every episode links to a signed contributor release through a documented consent chain, and the consent record is part of the delivery. Faces, plates and screens are detected and irreversibly blurred at ingest, consented subjects are exempt from blurring, and a reviewer confirms the result before anything ships. Footage with bystanders who cannot be de-identified is discarded.

That is the whole of the privacy wording the site states. It does not state whether the person receiving a service is in frame for these rows, or how their face is handled beyond that general rule, so settle both in the spec. This is not legal advice, and the executed agreement controls.

Fast · on demand

How fast can a custom makeup and lash dataset be collected?

Where coverage is already deep, the first validated batch lands in a median of 48 hours from signed spec. Thin environments typically take three to four weeks, because vetting operators there is the bottleneck, and we quote that up front. All three rows here are listed as Available on request, and the site does not state which of the two timelines applies to them.

You describe the services, steps and tools your policy needs, and we turn that into a written spec covering tasks, environments, capture tier, annotation depth and accept criteria. A Spec Pilot, a small and fast first batch, can prove the spec before you scale. Billing is per validated hour, a reject log ships with every batch, and rejected items are recaptured at our cost.

At a glance

What you get.

Every collection runs through the same seven-stage end-to-end custom collection pipeline. End-to-end custom data collection is a managed service that takes an AI data need from problem to owned dataset in a single accountable pipeline.

Catalog rows

Which catalog rows name makeup, lashes and brows, and which are neighbours?

The three rows as listed in the task catalog, with the environment, description, skill rating and status, then nearby rows shown only to mark where these rows end. All rows list a head-mounted phone or a multiview rig as capture mode.
Catalog taskEnvironment and sectorCatalog descriptionSkillStatus
Makeup ApplicationHair Salon, Barbershop & Beauty Studio, Beauty & Personal CareProfessional makeup application in a salon or studioMediumAvailable on request
Eyelash & Eyebrow ServicesHair Salon, Barbershop & Beauty Studio, Beauty & Personal CareLash extension, tinting, shaping and brow styling servicesHardAvailable on request
Basic Skin & Beauty TreatmentsHair Salon, Barbershop & Beauty Studio, Beauty & Personal CareFacial cleansing, moisturizing, exfoliation, foot spa and waxing treatmentsMediumAvailable on request
Beauty Services / Personal Care (separate row, not makeup or lashes)Hair Salon, Barbershop & Beauty Studio, Beauty & Personal CareListed separately in the beauty environmentMediumReady to deploy
Manicure & Pedicure Service (separate row, nail work)Hair Salon, Barbershop & Beauty Studio, Beauty & Personal CareListed separately in the beauty environmentMediumReady to deploy

Streams and tasks

How do the stated streams map to makeup and lash tasks?

The streams the site states for Firsthand custom collections, set against what each carries in a makeup, lash or brow episode. Row-by-row stream coverage for each capture mode is confirmed in the spec.
Stream or labelStatus on this siteWhat it carries in a makeup or lash episode
Head and wrist RGB, depthStated; ten streams synced under 2 msKeeps the hands and the tool on one timeline
3D hand pose, per-joint visibilityStated for custom collectionsCarries how fingers hold a brush, a tweezer or an applicator
Contact and grasp eventsStatedMarks when hands meet a tool or a surface
Action segmentsStated; frame-accurateSeparates one step of a service from the next
Task instructionStated; one per episodeStates the service in plain language
Object labelsSet by your specNames the tools and steps in the terms your policy uses

What is not stated

Which details does the site not state?

Fields the site does not state for these rows, and where each one is settled.
ItemStatus on this siteWhere it is settled
Cosmetic brands or productsNot statedNot claimed on this page
Skin-safety, dermatological, hygiene or certification claimsNot statedNot claimed on this page
Whether the person receiving a service is in frame, and how their face is handledNot stated beyond the general blur rule and the consented-subject exemptionThe written spec
Outcome labels such as finish quality of a look or a lash setNot statedThe written spec
Tool models, lash and brow product types, service sequencesNot stated; the rows name the services onlyThe written spec
Working distance and close-range depth behaviourNot statedThe written spec
Salon names, regions, number of sites or practitionersNot stated beyond Western program marketsThe written spec
Which timeline applies to these rowsNot stated; all three are Available on requestQuoted against your spec
Cycle times, throughput, repetition countsNot statedQuoted against your spec
Force or tactile dataNot stated for these rowsThe written spec, if needed
Robot or policy resultsNot statedNot claimed on this page

Formats

Which formats carry makeup and lash application data?

Delivery formats stated on the site, set against what each format official documentation states where the documentation was read.
FormatWhat the official documentation statesUsed for here
RLDSA dataset is retrieved as episodes, and each episode holds a dataset of steps (RLDS repository README)Episode-based training loaders
LeRobotLeRobotDataset v3.0 is a standardized format for robot learning data, including multi-camera video, with many episodes stored per Parquet or MP4 file (LeRobot documentation)LeRobot dataset format and tooling
WebDatasetTar files in which files that belong together share a basename, split into numbered shards (WebDataset README)Sharded streaming for large training runs
HDF5 and zarrStated by Firsthand onlyArray storage for custom pipelines
Rerun .rrdStated by Firsthand onlyMulti-stream synchronized playback for review

FAQ

Beauty robot training data, answered.

What is egocentric makeup and lash application data?
Video of consented participants applying professional makeup, doing lash extension, tinting and shaping, styling brows and giving basic skin and beauty treatments, captured with a head-mounted phone or multiview rig against a written spec.
Which catalog rows does the site state for this?
Three, all in Hair Salon, Barbershop & Beauty Studio: "Makeup Application" (Medium, Available on request), "Eyelash & Eyebrow Services" (Hard, Available on request) and "Basic Skin & Beauty Treatments" (Medium, Available on request).
Does the data include cosmetic brands or skin-safety claims?
No. The site states no cosmetic brand, skin-safety, dermatological, hygiene or certification claim for these rows, and this page makes none. It describes task video only.
Are the people in the video consented?
Yes. Every episode links to a signed contributor release through a documented consent chain. Faces are irreversibly blurred at ingest, consented subjects are exempt from blurring, and whether the person receiving a service is in frame for these rows is settled in the spec.
Does the data show how good a finished look or lash set is?
No. The site lists no outcome or quality label for a service. Outcome labels would be written into the spec.
How fast can a custom dataset be collected?
From a signed spec to a first validated batch, a median of 48 hours where coverage is deep and three to four weeks where it is thin. The site does not say which applies to these rows, so ask when you request the quote.

Sources

Where are the delivery formats on this page documented?

Request a custom dataset.

Tell us the services, steps and tools your policy needs to handle. We will quote reach, timeline, and price against a written spec, with a first validated batch in a median of 48 hours where coverage is deep.