Privacy Policy

This policy covers the 6thSense cloud contribution service and recordings submitted for robotics data collection. Synapse camera controls work without an account; optional contributor accounts and cloud submissions have additional data flows described here and in the applicable regional agreements.

Who this covers

This policy applies to the cloud contribution service and submitted recordings. 6thSense builds tactile-capture hardware and software that records human demonstrations for robotics datasets. The separate Synapse Privacy Policy covers local camera control, optional analytics, and app updates. Participation also requires the published agreements for the applicable region.

What we collect

The capture app records demonstration sessions. Depending on the hardware connected, a session can include:

Video — first-person (egocentric) RGB video, and where a depth camera is attached, per-frame depth. This can include your hands, the objects and surfaces you interact with, and whatever is in the camera's field of view.
Tactile data — contact and pressure signals from the 6thSense Skin sensors (for example, contact onset and pressure over time across the sensor channels).
IMU / motion data — accelerometer and gyroscope readings and derived motion cues from the rig and wearables.
Session and device metadata — timestamps, device identifiers, hardware and firmware versions, capture settings, calibration values, and quality-check metrics used to align and validate the recording.
Contributor account information — your name, phone-based authentication and verification information, regional routing, agreement receipts, supervised camera assignments, and footage and payment records. Korean bank registration collects the account-holder name, bank, full account number, email, date of birth, phone number and address to register you as a Wise payment recipient, and keeps a backup of the name, bank and account number in a private Google spreadsheet; the website database keeps a masked receipt and the Wise recipient identifier for operator-approved payments.
Basic technical logs — app version, error and diagnostic logs, and upload status used to keep capture and upload working.

What we do NOT intentionally collect

The app is built to capture task demonstrations, not to surveil you. We do not intentionally collect precise location tracking, contacts, browsing history, or advertising identifiers. Because video captures whatever is in frame, please avoid recording bystanders or sensitive surroundings you do not intend to share, and get consent from anyone who may appear in a recording.

How we use the data

We use the captured data to:

Build, curate, and improve robotics training datasets and the models trained on them.
Align, calibrate, and quality-check recordings across video, touch, and motion so episodes are model-ready.
Operate, debug, and improve the capture app and pipeline.
Provide processed datasets and results to the 6thSense partners and customers those datasets are captured for.
Meet legal, security, and safety obligations.

Where data is stored

Submitted recordings are stored in cloud storage hosted on Amazon Web Services (AWS), including Amazon S3 and supporting databases. In the supervised contributor pilot, an operator imports camera storage cards; registering or signing in on the phone does not upload footage. Contributor API requests use HTTPS, and account authentication uses Amazon Cognito.

We restrict access to captured data to the people and systems that need it to build and deliver datasets, and we rely on AWS's physical and infrastructure security for the underlying storage.

How long we keep it

The applicable regional notices and agreements describe retention for contributed data. Account deletion is an operator-supervised process that records footage and processor cleanup separately from any legally required retention of consent or payment records. Retained records require a documented scope, reason, and review date. The payment notice below states bank-record retention; overall account-deletion completion depends on confirmed footage and provider cleanup.

Third parties we share with

We do not sell your data. We share it only as needed to run the service:

Amazon Web Services (AWS) — Cognito account authentication, cloud hosting, and storage for submitted recordings and supporting services.
Google and Railway — private spreadsheet storage and backend processing for bank details submitted with the payment notice. Full account numbers are accessible to authorized spreadsheet users.
Wise — payment-recipient registration with the details submitted under the payment notice, recipient verification, and operator-approved transfers.
Partners and customers — the specific partner or customer that a dataset is captured for, under agreement.
Service providers — vetted vendors who help us operate the pipeline (for example, infrastructure and error monitoring), limited to what they need.
Legal and safety — authorities when required by law, or to protect rights, safety, and security.

Security

We use encryption in transit, access controls, and reputable cloud infrastructure to protect captured data. No system is perfectly secure, so we cannot guarantee absolute security, but we work to protect your data and to limit who can access it.

Your rights and choices

Depending on where you live, you may have rights to access, correct, or delete your data, or restrict certain processing. Use Delete account in the contributor area to initiate account deletion, including before enrollment. The request stops new contributions and approvals; it is not itself confirmation of erasure. The app retains a private receipt for checking status after login removal. Required legal or payment retention is recorded separately, and camera-local or independently shared copies are outside the cloud account deletion process.

Children

The capture app is intended for use by professionals and partners, not by children. It is not directed to anyone under 16, and we do not knowingly collect data from children.

Changes to this policy

We may update this policy as the product evolves. When we make material changes, we will update the date at the top of this page. Continued use of the app after an update means you accept the revised policy.

Contact us

Questions about this policy or your data? Reach us at:

지급정보 수집·이용 안내

목적: 보수 정산·지급 준비, Wise 수취인 등록 및 관련 문의 처리. 항목: 예금주명, 은행·계좌번호, 이메일, 생년월일, 전화번호, 주소(참여자 ID 및 동의 기록과 연결).

보유기간: 최소 정산 증빙은 참여 종료일과 최종 정산일 중 늦은 날부터 5년, 그 밖에 불필요해진 지급정보는 해당 시점부터 30일 이내 삭제합니다.

동의를 거부할 수 있으며, 거부 시 온라인 계좌 등록은 진행되지 않습니다. 이미 발생한 보수와 업로드 권한에는 영향이 없습니다. 대체 지급 방식, 동의 철회, 열람·정정·삭제 문의: alex@6thsense.dev.

개인정보처리자: 6thSense AI, Inc.(미국). 연락처: alex@6thsense.dev.

처리위탁·국외이전 안내 (Google·Railway·Wise)

항목·시기·방법: 위 지급정보, 참여자 ID 및 동의 기록을 제출 시와 지급정보 관리 시 암호화된 인터넷 통신으로 전송합니다. 6thSense는 미국에서 위 목적과 보유기간에 따라 수집·관리합니다.

Google LLC — 미국 / 연락처: https://support.google.com/a/contact/googlecloud_dpr / 목적: 지급정보 백업 보관·동기화 / 보유기간: 위 항목별 기간. 서비스에서 삭제한 뒤 내부 잔여 사본 삭제에 최대 180일이 걸릴 수 있습니다.

Railway Corporation — 미국(캘리포니아) / 연락처: privacy@railway.com / 목적: 계좌 등록 서비스와 관련 기록 호스팅. 계좌정보는 서버를 거쳐 전달되며 저장 기록의 계좌번호는 마스킹됩니다. 보유기간: 위 항목별 기간, 호스팅 로그 7일(전체 계좌정보를 의도적으로 기록하지 않음).

Wise US Inc.(및 그 계열사) — 미국(30 W. 26th St, Sixth Floor, New York, NY 10010) / 연락처: privacy@wise.com / Wise는 표준계약조항 또는 적정성 결정에 따라 데이터를 국외로 이전할 수 있습니다. / 목적: 보수 수취인 등록·확인 및 보수 송금 / 항목: 위 지급정보(제출 시 전송) / 보유기간: Wise 개인정보처리방침과 지급서비스 제공자로서의 법령상 의무에 따름. 6thSense 데이터베이스에는 마스킹된 계좌번호와 Wise 수취인 ID만 보관하며, 예금주명·은행·계좌번호는 위 지급정보 스프레드시트(Google)에 백업으로 보관합니다.

Google의 유지보수·보안·데이터센터 처리는 다음 국가에서도 이루어질 수 있습니다: 미국, 아르헨티나, 호주, 벨기에, 브라질, 캐나다, 칠레, 덴마크, 핀란드, 프랑스, 독일, 홍콩, 인도, 아일랜드, 이스라엘, 이탈리아, 일본, 멕시코, 네덜란드, 뉴질랜드, 필리핀, 폴란드, 싱가포르, 대한민국, 스페인, 스웨덴, 스위스, 대만, 영국. 처리가 미국에만 한정되지는 않습니다. 아래 수탁자 목록에서 해당 계열사와 업무를 확인할 수 있으며, 선택적인 고객지원 요청에는 계좌 문서를 공유하지 않습니다.

거부·철회 방법 및 효과: 국외이전에 동의하지 않거나 alex@6thsense.dev로 철회를 요청할 수 있습니다. 동의 없이는 온라인 계좌 등록이 진행되지 않으며, 이미 발생한 보수나 업로드 권한을 잃지 않고 대체 지급 방식을 협의할 수 있습니다.

Google 수탁자 목록: https://workspace.google.com/terms/subprocessors/

Railway 수탁자 목록: https://trust.railway.com/item/subprocessors

Payment privacy notice

Purpose: earnings settlement, payment preparation, registering you as a payment recipient with Wise, and payment enquiries. Data: account holder name, bank and account number, email, date of birth, phone number and address, linked to your contributor ID and consent record.

Retention: minimal settlement evidence for five years after the later of the end of participation or final settlement; other unnecessary payment information is deleted within 30 days of that point.

You may refuse consent; online bank registration will then remain unavailable. Refusal does not cancel earned payment or prevent uploading. For an alternative payment method, withdrawal, access, correction or deletion, contact alex@6thsense.dev.

Controller: 6thSense AI, Inc. (United States). Contact: alex@6thsense.dev.

Service providers and overseas processing (Google / Railway / Wise)

Data and timing: the payment details, contributor ID and consent record above are transmitted electronically over encrypted connections when you submit and when payment records are managed. 6thSense collects and manages them in the United States for the purposes and periods stated above.

Google LLC — United States; contact: https://support.google.com/a/contact/googlecloud_dpr. Purpose: backup storage and synchronization of payment records. Retention: the periods stated above; residual internal copies may take up to 180 days to be deleted after service deletion.

Railway Corporation — United States (California); privacy@railway.com. Purpose: hosting the payment-registration service and its records. Bank details pass through the service; stored records use a masked account number. Retention: the periods stated above; hosting logs are retained for seven days and do not intentionally contain full bank details.

Wise US Inc. (and its group companies) — United States (30 W. 26th St, Sixth Floor, New York, NY 10010); contact: privacy@wise.com. Wise may transfer data internationally under standard contractual clauses or adequacy decisions. Purpose: registering and verifying you as the recipient of your payments and sending those payments. Data: the payment details above, sent when you submit them. Retention: as Wise's privacy policy and its legal and regulatory obligations as a payment provider require; The 6thSense database keeps only a masked account number and the Wise recipient ID; the name, bank and account number are also kept as a backup in the payment spreadsheet described above (Google).

Google service maintenance, security and data-centre processing may also occur in: United States, Argentina, Australia, Belgium, Brazil, Canada, Chile, Denmark, Finland, France, Germany, Hong Kong, India, Ireland, Israel, Italy, Japan, Mexico, Netherlands, New Zealand, Philippines, Poland, Singapore, South Korea, Spain, Sweden, Switzerland, Taiwan and United Kingdom. No US-only processing guarantee is made. The provider directory below identifies the relevant affiliates and activities; bank documents are not shared in optional support cases.

Refusal or withdrawal: leave the overseas-transfer consent unchecked or contact alex@6thsense.dev. Online registration cannot proceed without this consent; alternative payment arrangements can be discussed without forfeiting earned payment or upload access.

Google subprocessors: https://workspace.google.com/terms/subprocessors/

Railway subprocessors: https://trust.railway.com/item/subprocessors