This projects builds off from Traffic Safety Meets Public and Environmental Health. By leverages various sensing devices, we aim to capture data evidence of the pollution exposures and health risks associated with street-level working environments of outdoor gig workers (i.e., four-wheel drivers and/or two-wheel riders).

Our project employs three types of devices: (1) Fitbit / Google Health data for activity, physiology, and health responses; (2) air quality sensors for temperature, humidity, gas, and particulate matter; and (3) dashcam footage for video, and where enabled, audio, of the road environment.

Google Health API integration. The Study operates a Google API client that reads Fitbit / Google Health data from study-owned Google accounts into the Research Team’s secure research database, where it is analyzed alongside air quality and dashcam data. See our Privacy Policy and Terms of Service for how this data is accessed, used, stored, and shared.

Skills and Expertise Involved

1. Key areas of work include:
   • Sensor Design: Building IoT-based hardware for vehicle-mounted environmental sensing
   • Software Development: Implementing data collection, storage, and visualization tools across health, environmental, and video data streams
   • Human-Centered: Conducting real-world user studies with outdoor working drivers and/or riders
   • Multimodal Analysis: Extracting traffic-related features from dashcam footage, and correlating with environmental exposure and physiological health data
2. Core competencies required are:
   • Programming in Python, Go
   • Software engineering and management of data pipelines, database design, cloud-based deployments
   • Statistical modeling and evaluation of analytical methods

Opportunities may be offered on either a volunteer basis or through paid positions, depending on project needs and available resources.

Notice: About this page

This page and the two documents below exist to support SensAI Labs’ application for Google OAuth API verification for the Google Health API scopes listed in the Privacy Policy. Google requires an applicant to publish, on a single domain it owns, a homepage describing the app’s functionality together with a linked privacy policy and terms of service. This page serves that purpose.

This is not a recruitment page. No enrollment, sign-up, or consent to participate happens here. Participants are recruited and consented separately under the Study’s approved REB protocol, and nobody can join the Study through this site. Nothing here creates a participation agreement.

No one signs in here. The Study’s Google Health credentials belong to study-owned Google accounts created and controlled by the Research Team; no visitor or Participant ever authenticates with their own Google account through this site.

The Study

Devices & accounts: all devices are purchased or manufactured by Us and distributed to Participants — Participants don’t use their own. The Fitbit connects to a Google account We create and control, not the Participant’s personal account.

Anonymized at collection: all data is recorded under a study-assigned ID, never the Participant’s name.

Enrollment: the Study has enrolled on a rolling basis since June 2026.

Privacy Policy: read here

Terms of Service: read here

Privacy Policy

Last updated: September 16, 2026

This Policy covers what data We collect from Study devices — including sensitive Google Health data — and how it’s anonymized, secured, and controlled by Us.

Devices

The Fitbit, air quality sensor, and dashcam are all purchased/manufactured by Us and distributed to Participants; these devices remain Our property. The Fitbit is linked to a study-owned Google account, not the Participant’s personal one — a Participant’s own Google credentials are never used or accessed.

Data We Collect

Fitbit / Google Health Data, via the Google Health API:

Several categories above are sensitive or restricted under Google’s classification. We request them only where needed for the Study, with the Participant’s specific consent; a Participant may decline individual scopes where feasible.

Air quality sensor data: particulate matter, temperature, humidity, gas.

Dashcam data: video and, where enabled, audio of the road environment. This may incidentally capture other road users (pedestrians, cyclists, drivers). We blur/mask faces and license plates of non-participants where feasible, and never attempt to re-identify them.

Anonymization

All data is recorded under a study-assigned participant ID, not the Participant’s name — this name is never stored alongside the collected data. The ID-to-identity mapping is kept separately and accessed only for administrative purposes (e.g., processing a withdrawal or compensation), then removed once no longer needed. After that, the data can no longer be linked back to the Participant and may be retained indefinitely for research and publication.

Google API Limited Use Compliance

Our use and transfer of information from Google APIs adheres to the Google API Services User Data Policy, including Limited Use requirements:

• Used only to provide/improve the Study, per the Participant’s consent — never for advertising.
• Never sold or transferred to data brokers.
• Never read by humans except with the Participant’s consent, for security, to comply with law, or once aggregated/anonymized.
• A Participant can review or revoke access anytime via Google Account permissions.

Consent, Security & Retention

Given the sensitivity of this data, We rely on the Participant’s explicit, opt-in consent as the legal basis for collection, regardless of jurisdiction. Data is stored on access-controlled, encrypted systems limited to authorized Research Team members.

• Identifiable data (i.e., while the ID-to-identity mapping exists): retained while the Participant remains enrolled in the Study.
• Raw dashcam footage: deleted once blurring/analysis is complete.
• Anonymized/aggregated data: may be retained indefinitely for research and publication.

Participant’s Rights

A participant may, at any time and without penalty: withdraw consent and stop participation; request a copy, correction, or deletion of Participant data (unless it’s already anonymized or We have a legal/ethics obligation to retain it); and revoke Google Health access independently via Google Account permissions.

Terms of Service

Last updated: September 16, 2026

These Terms cover Study participation not already addressed in Our Privacy Policy.

Key Terms

• Company (“We”/”Us”/”Our”): SensAI Labs, Dalla Lana School of Public Health, 155 College St Level 4, Toronto, ON M5T 3M6, Canada.
• Participant: an enrolled User who has consented to data collection.
• Research Team: SensAI Labs researchers, students, and named academic collaborators.
• Service: the Study website, devices, and any associated dashboards.

Enrollment

The Study enrolls on a rolling basis since June 2026. Enrollment and consent take place directly with the Research Team under the Study’s approved REB protocol — not through this website.

Other Data We Collect

Enrollment details — the Participant’s name and phone number — for administrative purposes (contacting the Participant, scheduling device pickup and return, processing compensation and withdrawals).

No cookies: the site is a static GitHub Pages site and sets no cookies or tracking scripts. GitHub, as host, may log standard website Usage Data (IP address, browser type, pages visited) per its own Privacy Statement — outside Our control.

How We Use & Share Data

Used to run the Study, manage the Participant recruitment, and support research publication (anonymized/aggregated only). Shared only with the Research Team, bound Service Providers, and named academic collaborators (anonymized/aggregated data only) — never sold, and never used for marketing, advertising, or credit/employment decisions. We may disclose data if required by law, to protect legal rights, or as part of a merger/acquisition (with notice, and subject to Google’s Limited Use restrictions for health data).

Storage & Transfers

Stored on encrypted, access-controlled systems; may be processed at Our facilities, University of Toronto facilities, or Service Provider facilities outside the province, with appropriate safeguards where required by law. No storage method is 100% secure.

Withdrawal

A Participant may withdraw at any time without penalty — see Our Privacy Policy for details on what happens to the data.

Changes & Contact

We’ll post updates here and update the date above; material changes will also be notified directly to Participants via their phone numbers. External links (e.g., Google’s account pages) are outside Our control.

Questions: sensailabs.research@gmail.com