Project Pulsar Contributor Project Terms

VERSION 1.2 · NOVEMBER 5, 2026 · SCHEDULE A TO THE TASKALPHA TERMS AND CONDITIONS · TASKALPHA PTE. LTD.

These Project Terms set the project-specific terms on which a Contributor participates in Project Pulsar. They are a Schedule to, and form part of, the TaskAlpha Terms and Conditions between the Contributor and TaskAlpha Pte. Ltd. (Singapore company registration / UEN 202557199Z), which operates the TaskAlpha platform at taskalpha.io ("TaskAlpha"). Project Pulsar produces a first-person video dataset of real work for an end customer. By accepting these Project Terms, taking custody of a Device, or recording or submitting any content under Project Pulsar, the Contributor agrees to be bound by them. Version 1.2 replaces version 1.1 of October 21, 2026.

1. Introduction and Incorporation

1.1 Relationship to the Terms and Conditions. These Project Terms are Schedule A to the TaskAlpha Terms and Conditions (the "Agreement"). The Agreement governs the overall relationship between the Contributor and TaskAlpha, including the master terms on independent contractor status, intellectual property, confidentiality, data protection, non-circumvention, term, termination, governing law, and dispute resolution. These Project Terms add the terms that are specific to Project Pulsar. They do not replace the Agreement.

1.2 Order of precedence. If there is a conflict, the documents apply in this order: (a) the Agreement; (b) these Project Terms; (c) the Project Pulsar Capture Guide, the Device Instructions, and any written technical specifications issued for the Project; and (d) the Project Pulsar Contributor Guide and other operational materials. On matters of technical detail (Device operation, capture settings, file formats, submission steps), the Capture Guide, the Device Instructions, and written technical specifications control over the general descriptions in these Project Terms.

1.3 Definitions. "Episode" means a single, clearly defined task recorded as one continuous recording, with a distinct start and end, together with its associated metadata. "Qualifying Filmed Content" means an Episode accepted under Section 5. Only Qualifying Filmed Content is compensable. "Approved Hour" means one hour of Qualifying Filmed Content, calculated on the aggregate accepted runtime of a Contributor's Episodes and associated metadata, prorated to the nearest second. "Portal" means the TaskAlpha platform at taskalpha.io through which sessions are registered and Episodes are uploaded, configured, submitted, and invoiced. "Capture Guide" means the Project Pulsar Capture Guide, as updated from time to time, which sets the controlling technical and operational specifications for the Project. "Flipside" means Flipside Digital Content Company, Inc., the Project Owner for Project Pulsar on the Portal, which holds the Devices as custodian and loans them to Contributors. "Device" means the head-mounted recording hardware loaned to the Contributor by Flipside for the Project, together with its power bank, accessories, components, software, firmware, documentation, and any replacement. "Device Instructions" means the written operating, safety, charging, storage, transport, and return instructions issued for the Device by Flipside or TaskAlpha, as updated from time to time. "Environment Category" means one of the environment categories listed in Section 6.1, as assigned by TaskAlpha to the venue at session registration. "Restricted Location" has the meaning given in Section 8.5. "Vendor" means a business that has a TaskAlpha Vendor Agreement for Project Pulsar. "Operator" means a Contributor who records for Project Pulsar as an owner or employee of a Vendor.

1.4 Operators engaged through a Vendor. A Contributor who records as an Operator of a Vendor accepts these Project Terms in full, except that Sections 6 and 7 do not apply to that Contributor. Approved Hours recorded by an Operator are credited to the Vendor under the Vendor Agreement, and the Vendor, not TaskAlpha, pays the Operator. TaskAlpha does not pay the same Approved Hour twice, whether to a Contributor and a Vendor or under any other arrangement. All other Sections, including the Device, privacy, consent, intellectual property, and confidentiality terms, apply to an Operator directly.

2. The Project

2.1 Description. Project Pulsar collects first-person, task-based egocentric video, with hands visible, of real work performed in non-residential work environments across the Environment Categories listed in Section 6.1 (for example retail, food and beverage, hospitality, repair services, warehousing and logistics, industrial manufacturing, construction, automotive, agriculture, laboratory, and healthcare-adjacent settings). The footage is used to build training datasets for artificial intelligence and robotics systems. The Contributor wears the Device while carrying out real tasks that form part of the Contributor's own work, performed naturally and at normal speed at the Contributor's own workplace, then reviews each Episode and submits it through the Portal.

2.2 Contributor role and independent status. The Contributor performs the Project as an independent contractor under the Agreement. Nothing in these Project Terms creates an employment, agency, partnership, or joint venture relationship. The Contributor sets their own schedule and is free to provide services to others, subject to the confidentiality and non-circumvention terms of the Agreement. Use of a Device loaned by Flipside does not change the Contributor's independent status and does not create an employment or other relationship between the Contributor and Flipside.

2.3 No guaranteed volume. Participation in Project Pulsar does not guarantee the issue of a Device, any minimum number of assignments, any minimum quantity of accepted content, or any minimum level of earnings. Assignments and acceptance depend on Project needs, diversity caps (including caps per venue, per task, and per Contributor within a venue), and quality. Devices are allocated where they are used: a Device that is not used regularly may be recalled under Section 3.6.

3. Eligibility, Device, and Equipment

3.1 Loaned Device. Recording for Project Pulsar is done on a Device loaned to the Contributor by Flipside. The Device is owned by Flipside's client and held by Flipside as custodian. It is loaned, not sold, and the Contributor acquires no ownership, security, intellectual property, or other interest in it. A Device is released only after (a) the Contributor has completed onboarding and Device training, (b) Flipside has confirmed that the Contributor is approved as an authorized user of the Device, and (c) the Contributor has signed Flipside's Equipment Turnover and Accountability Form, which records the Device identifier, condition, and named user. The Contributor's obligations under this Section 3 are owed to Flipside as well as to TaskAlpha, and Flipside may enforce them directly.

3.2 Permitted use. The Contributor may use the Device only for Project Pulsar, only in venues and assignments authorized under Section 8, and only in accordance with the Device Instructions and the Capture Guide. The Contributor must not lend, rent, transfer, or allow any other person to use the Device, and must not use it for any personal, commercial, research, or other purpose.

3.3 No alteration. The Contributor must not open, alter, repair, reconfigure, factory-reset, wipe, or remove markings from the Device; extract its software, firmware, credentials, or recordings; connect unapproved software, equipment, networks, or storage; or bypass or interfere with any security, logging, telemetry, geofencing, or remote-management feature. Flipside, or TaskAlpha on its behalf, may configure, monitor, locate, update, lock, disable, or remotely wipe the Device at any time, and the Contributor must not interfere with those functions.

3.4 Care and safety. The Contributor must keep the Device secure and protected against loss, theft, damage, and environmental exposure; follow the Device Instructions for fit, hygiene, charging, storage, and transport; inspect the Device before each session; and stop using and set aside any Device that is damaged, overheated, unsafe, or malfunctioning, reporting it under Section 8.7. The Device must not be used while driving, operating heavy machinery, or in conditions that are unsafe for the Contributor or others.

3.5 Loss and damage. The Contributor is responsible for the Device from receipt until Flipside confirms its return, and bears the cost of loss, theft, or damage occurring during that period other than ordinary wear and tear from proper use. Flipside may recover the reasonable cost of repair or replacement from the Contributor, and, to the extent permitted by law, TaskAlpha may apply that amount by set-off against the Contributor's accrued earnings and remit it to Flipside.

3.6 Return. The Contributor must stop using and return the Device, with all accessories, within five (5) business days of a request from Flipside or TaskAlpha, the end of the assignment for which it was issued, or the end of the Contributor's participation in the Project, using the return method set out in the Device Instructions. Flipside may request return at any time, including where the Device is not being used regularly. The Contributor must not reset, wipe, or remove any recordings from the Device before return. Return is complete only when Flipside confirms receipt and condition.

3.7 Contributor's own equipment. Flipside issues a power bank with the Device where the Device Instructions call for one, and that power bank forms part of the Device. The Contributor must provide and maintain, at their own cost, a smartphone or computer with internet access for Portal registration, review, and submission. Loss, theft, damage, repair, and replacement of the Contributor's own equipment are the Contributor's sole responsibility, and TaskAlpha is not liable for any loss, damage, or wear to it arising from participation in the Project.

4. Technical Specifications and Submission

4.1 Capture specifications. Every Episode must be recorded on the loaned Device, as configured by Flipside, in line with the Capture Guide. The Device is worn head-mounted, forward and slightly downward facing in line with natural gaze, so that the Contributor's hands, tools, and the task workspace are visible. The Contributor must not change the Device's recording, lens, or sensor configuration. Audio is recorded only where the assignment specifically enables it. Each session must be registered in the Portal before recording starts, so that the venue, Environment Category, job, and task metadata are attached to the Episode; recordings made without a registered session are not accepted. Recordings made on any device other than the loaned Device, or on a Device that has been altered, are not accepted.

4.2 Episodes. Each Episode must be one task with a clear start and end. Short tasks should run 30 seconds to 5 minutes; longer multi-step tasks may run up to 30 minutes and should ideally stay under 10 minutes. Episodes shorter than 30 seconds or longer than 30 minutes, and recordings that concatenate unrelated tasks, are not accepted. Episodes must show real work with visible task progress and real hand-object interaction; multi-step workflows that include setup, execution, transitions, and cleanup are preferred. Motion and gaze must be natural; deliberately slowed, sped-up, staged, re-enacted, or exaggerated footage is not accepted, and long runs of a single repeated motion, idling, or waiting are not accepted and may be cropped.

4.3 Submission. Episodes are submitted through the Portal: the Contributor logs in with their registered credentials, registers the session, records on the Device, uploads the recording by the method set out in the Capture Guide, confirms or configures one or more segments with a clear task description for each, and submits the Episode. The Contributor should review each Episode end-to-end before submitting it. The Contributor must not copy recordings from the Device to any personal device or account except as the Capture Guide directs for upload, and must delete any such working copies once the upload is confirmed.

4.4 No minimum recording requirement. There is no minimum number of hours the Contributor must record. The Contributor decides when and how much to record within their normal work, subject to Section 2.3 on Device allocation.

5. Acceptance, Rejection, and Remediation

5.1 Acceptance is per Episode. Each Episode, together with its metadata, goes through automated checks on the Portal and then review by the Project Owner against the Project specifications, and is accepted or rejected on its own merits. A single batch may contain both accepted and rejected Episodes. An Episode accepted at that review becomes Qualifying Filmed Content. TaskAlpha records each acceptance and rejection decision on the Portal, and the recorded decision is final and binding, subject to Section 5.3.

5.2 Common reasons for rejection. An Episode will be rejected if, among other things, it: does not meet the capture specifications; was recorded on a device other than the loaned Device, or on an altered Device, or without a registered session; contains personal information that cannot be redacted; contains financial information; captures any minor without documented consent; has audio when not enabled; is missing venue or location metadata; was recorded in an unauthorized venue, a venue that is not the Contributor's own workplace, or an unapproved Restricted Location; shows artificial, staged, exaggerated, or repetitive motion, idling, or hidden or occluded hands; duplicates content already submitted; exceeds caps for a task, venue, or Contributor-within-venue combination; concatenates multiple tasks; or is corrupt or technically deficient.

5.3 Remediation. Where an Episode is flagged for remediation, the Contributor will be notified of the Episode, the reason, and the timeframe to fix it. A remediated Episode is resubmitted and goes through the same review. Episodes not remediated within the stated timeframe are treated as rejected. Repeated quality or privacy failures may lead to suspension or removal from the Project under the Agreement, and to recall of the Device.

6. Compensation

6.1 Rate. The rate per Approved Hour of Qualifying Filmed Content (accepted video and associated metadata) depends on the Environment Category of the venue in which the Episode was recorded, as follows:

* Venues in these categories are, or commonly include, Restricted Locations under Section 8.5 (healthcare facilities, childcare and schools, public safety and law-enforcement sites). Recording there is available only once an assignment on the Portal shows the specific venue as approved. Until then, the rate shown is not available for that venue.

Where a band is shown, the exact rate within the band is fixed for each assignment and displayed on the Portal at session registration. The Environment Category of a venue is assigned by TaskAlpha at session registration and is final. Categories added after the version date of these Project Terms carry the rate displayed on the Portal for that assignment. No rate under these Project Terms is less than USD 6.00 per Approved Hour.

6.2 What is and is not paid. The Contributor is paid only for Qualifying Filmed Content. Time spent recording, effort, data cost, electricity, transport, and travel are not separately compensable. Rejected, duplicate, capped, cropped-out, or unattested content is not paid. There is no payment for content that does not become Qualifying Filmed Content.

6.3 Earnings ledger. Accepted earnings accrue to the Contributor's account in US dollars, calculated as Approved Hours multiplied by the applicable rate. The Portal records the running balance of accrued, accepted, and unpaid earnings.

7. Withdrawal, Invoicing, and Payment

7.1 Minimum withdrawal threshold. A Contributor may request a withdrawal only once their accrued, accepted, and unpaid earnings reach USD 10.00 (the "Minimum Withdrawal Threshold"). A balance below the Threshold rolls over and continues to accrue until the Threshold is reached.

7.2 Invoice required. To be paid, the Contributor must generate and submit an invoice for the accrued accepted amount, using the TaskAlpha invoice generator made available through the Portal. The invoice must be accurate and must correspond to the Contributor's accepted balance. No payment is released without a valid invoice.

7.3 Payment cycle. Invoices are processed on a two-week cut-off cycle. A valid invoice submitted on or before a cut-off is paid in the corresponding payment run for that cycle.

7.4 Payout method and fees. TaskAlpha pays in US dollars, or in the local currency equivalent where the payout method requires it, to the single payout destination the Contributor registers on the Portal. The payout methods available in the Contributor's country, any transfer fee, and the basis of any currency conversion are shown on the Portal before the Contributor confirms a payout destination. The Contributor is responsible for the accuracy of the payout details they register.

7.5 Taxes. The Contributor is an independent contractor providing services from outside Singapore. Amounts are paid gross. The Contributor is responsible for registering for, declaring, and paying all taxes and contributions due on their earnings in their country of residence. If a law requires TaskAlpha to withhold any amount from a payment, TaskAlpha will do so and will tell the Contributor what was withheld.

7.6 Adjustments and set-off. TaskAlpha may correct the earnings ledger and set off against amounts owed where an Episode is found, after payment, to have been wrongly accepted, duplicated, or to contain undisclosed personal data, or where an invoice was inaccurate. Overpayments, and amounts due under Section 3.5, may be recovered from future balances.

8. Privacy, PII, and Venue Authorization

8.1 Avoid personal information. The Contributor must make good-faith efforts to avoid capturing identifiable faces and personal or sensitive information ("PII"), and must not intentionally record bystanders or customers. The Contributor should frame, position, and time recording to keep faces and PII out of frame wherever possible. Where faces or PII are nonetheless captured incidentally, they may be redacted during processing or the Episode may be rejected. This does not permit deliberate recording of faces or PII.

8.2 Financial information must not be captured. Financial information must not be recorded under Project Pulsar in any circumstance. This includes payment cards, card and account numbers, PINs, one-time passwords, passwords, bank statements, and similar data. An Episode that captures financial information is rejected, not cleaned.

8.3 Minors are a strict line. If a person under 18 might appear or be audible in a capture, the Contributor must have documented, verifiable parental or guardian consent on file in advance. Episodes involving a non-consented minor will be rejected and may result in immediate removal from the Project and the Agreement.

8.4 Venue authorization. The Contributor may record only at their own workplace: a non-residential, registered business of which the Contributor is an owner or employee, that is authorized for the assignment, and at which the Contributor has the right to be and to record. At venue registration the Contributor provides the business details the Portal asks for (including the business registration number and size). Private residences, home environments, and other residential settings are not authorized under Project Pulsar. For any venue the Contributor does not own or operate, the Contributor must hold written, project-specific permission from the owner or operator, or the owner or operator must have signed a site agreement with Flipside for the Project, and must comply with all posted or communicated recording restrictions at the venue. Each distinct venue is registered once in the Portal and used for every session recorded there.

8.5 Restricted Locations. The following venues are Restricted Locations: health care facilities; religious facilities; locations intended primarily for minors (including childcare and schools); situations where there is a heightened risk of capturing nudity; government, law-enforcement, polling, political, detention, or union facilities; and locations where particularly sensitive data such as health records, financial records, or attorney-client privileged information may be present (for example inside a bank or law firm). Recording in a Restricted Location is permitted only where the assignment on the Portal shows the specific venue as approved and sets out the additional safeguards that apply (for example recording after hours or in non-sensitive areas only). The Contributor must not record in a Restricted Location without that approval.

8.6 Operator consent, data protection, and transfer. Personal data collected through the Project is processed in accordance with the TaskAlpha Privacy Policy and applicable law, including the Personal Data Protection Act 2012 of Singapore, which applies to TaskAlpha as controller, and the Philippine Data Privacy Act of 2012 (Republic Act No. 10173), which applies to Flipside's processing in the Philippines. By accepting these Project Terms the Contributor gives the following consent, which is recorded on the Portal before the Contributor's first session:

• Recording. The Contributor agrees to wear the Device, which records from the Contributor's own perspective, while performing their own work at authorized venues.
• Data collected. First-person video and, where enabled, audio of the Contributor's hand movements and work activity; data that may be considered biometric or behavioral, such as gait, hand geometry, and motion-sensor data; demographic data limited to age range, gender, and handedness; the Contributor's job or role; and Device usage data such as logs of when and for how long the Device was used. The Contributor is identified in the dataset only by a pseudonymous operator identifier.
• Use and onward transfer. The content and data may be provided, licensed, or sold by TaskAlpha and Flipside to the end customer and other authorized third parties, and used to develop, train, test, and improve artificial intelligence and robotics systems and related products and research. The Contributor consents to the processing and cross-border transfer of submitted content, metadata, and Device data for those purposes.
• Retention. Personal data is kept only as long as needed for those purposes or as the law requires.
• Voluntary participation. Participation is voluntary, and the Contributor may stop participating at any time by notifying TaskAlpha through the Portal. Content already accepted and delivered is retained and used as set out in the Agreement.
• Rights and questions. The Contributor may ask questions about their personal data, or exercise their rights under applicable law, through the privacy contact listed in the TaskAlpha Privacy Policy.

8.7 Incident reporting. The Contributor must report to TaskAlpha support, through the Portal or at support@taskalpha.io, within 24 hours if they accidentally capture sensitive personal information or a minor; discover after submission that an Episode contained unobscured sensitive data; lose the Device, have it stolen or damaged, or find it tampered with, compromised, or used by someone else (Flipside is notified by TaskAlpha); lose or have compromised any other capture equipment or account; receive any enquiry from a regulator, journalist, or third party about the Project; or receive a request from a person appearing in the footage.

9. Intellectual Property and Use of Content

All right, title, and interest in the Episodes, metadata, and other content the Contributor creates for the Project vest as set out in the Agreement. All data captured, generated, stored, or logged by or through the Device, including raw recordings, sensor outputs, identifiers, and logs, is not the Contributor's property; it is held for TaskAlpha, Flipside, and the end customer from the moment of capture and forms part of the content assigned under this Section. The Contributor assigns to TaskAlpha (and consents to TaskAlpha's onward transfer to Flipside and the end customer) all rights in the submitted content and metadata, on a perpetual, irrevocable, worldwide, royalty-free basis, including the right to store, reproduce, adapt, create derivative works from, and use the content to train, validate, and improve artificial intelligence and robotics systems. To the extent permitted by law, the Contributor waives any moral rights in the content. The Contributor must not retain, reuse, publish, or distribute the submitted content, and must delete any working copies of submitted Episodes from personal devices and accounts after upload is confirmed.

10. Confidentiality, Non-Circumvention, Term, and Governing Law

10.1 Confidentiality. Project Pulsar assignment details, these Project Terms, the Capture Guide, the Device Instructions, the Device, and the Portal are confidential. The Contributor must not share, post, screenshot, or otherwise disclose them or any footage outside the authorized Project channels, must not photograph or publish images of the Device, and must not discuss the Project's end customer, specifications, or footage publicly or on social media, without the prior written consent of TaskAlpha. This obligation continues after participation ends.

10.2 Non-circumvention. For 12 months after the Contributor's last activity on the Project, the Contributor must not circumvent TaskAlpha by dealing directly with the end customer, or with any party introduced through the Project, in respect of the same or similar data-collection services.

10.3 Term and termination. These Project Terms apply for as long as the Contributor participates in Project Pulsar and terminate together with, or as provided in, the Agreement. Sections relating to confidentiality, non-circumvention, intellectual property, data protection, taxes, Device return and liability, and accrued payment obligations survive termination.

10.4 Amendments. TaskAlpha may update these Project Terms, the Capture Guide, and the Device Instructions to reflect changes in the Project or the end customer's requirements. Material changes will be notified through the Portal or by email at least fourteen (14) days before they take effect. Continued recording or submission after a change takes effect constitutes acceptance of the updated terms.

10.5 Governing law and disputes. The governing law and dispute resolution provisions of the Agreement apply to these Project Terms.