Synapse is a mobile control plane for compatible egocentric capture rigs and cameras. Camera controls work without an account. Where enabled, an optional contributor account connects to a separate cloud service for supervised data contributions and payments. Capture devices remain the primary storage for local recordings. Synapse communicates with cameras over the local network, sends camera health and status reports to the configured fleet registry, sends optional product analytics only after affirmative consent, and contacts software-update services as described below.
Synapse reads device status, identifiers, diagnostics, recording metadata, previews, and footage from compatible cameras over the local network. Recordings are created and retained by the camera.
When you play footage, the camera streams it through the app. When you export a recording, Synapse temporarily downloads the selected file into its private cache and opens the system share sheet. The destination you choose controls any resulting copy. Export does not require photo-library access. Separately, optional support attachments let you take or choose photos as described below.
Synapse may store camera IP addresses, device identifiers and nicknames, app settings, analytics consent, recent onboarding network names, separate opaque analytics and fleet-report identifiers, and an optional camera access token. These settings are kept locally; identifiers used for analytics, fleet reporting and contributor assignments are also transmitted as described below.
Uninstalling Synapse removes that app-local data, but it does not delete recordings on cameras or copies previously shared to another app or service.
The FAQ can be used without contacting the support service. Before you send a support message, Synapse asks permission to share messages, selected photos, contact details and a limited app/camera summary with Anthropic for AI assistance. You can cancel and keep using the FAQ and camera controls. Do not send passwords, bank details, or other sensitive information in support chat.
The summary includes app and camera versions, app update identifiers and status, phone model and operating-system version, contributor sign-in status, camera identifiers and nicknames, health and connectivity information, and saved support request identifiers. It excludes camera IP addresses, Wi-Fi network names and MAC addresses. Selected photos are re-encoded as JPEG in the app’s private cache before upload and may remain cached until the operating system clears them or the app is removed; the app does not intentionally send the original photo's location metadata. Photos are attached only when you choose them and send a message.
The 6thSense support service runs on Railway. Active chats and photos are held in server memory. A chat stops being available after an idle hour; expired chats are removed during subsequent request cleanup or a service restart. Anthropic processes the conversation to generate replies. When a request needs the team, relevant contact details, conversation details and selected photos can be stored in Linear; the company hub imports support requests into its CRM and can send triage notifications to the team's Slack. These support records are separate from the temporary chat and are not deleted when the chat expires.
The phone keeps unsent message text, remembered support contact details and request identifiers locally. Its displayed conversation is kept in memory while the app runs. Removing the app clears app-local records but does not delete support requests or processor records. Contact ops@6thsense.dev to request access to or deletion of support records; retention may be required for legal, security or operational reasons. We do not use support content for advertising or cross-app tracking.
Wi-Fi passwords used while onboarding a camera are held only in memory for the active setup session. They are sent directly to the camera over the local network, cleared when the session ends or the app backgrounds, and never included in analytics.
Synapse sends no usage analytics unless you affirmatively consent. If you consent, the app sends product-interaction events and an opaque installation identifier to PostHog so 6thSense can understand feature use and improve reliability.
These events do not include video, audio, still images, recording contents, filenames, Wi-Fi passwords, camera access tokens, or an account identity. Synapse does not use this data for advertising or cross-app tracking. You can disable analytics at any time in Settings to stop future sending.
When fleet reporting is configured, Synapse sends limited camera health and status information over HTTPS to 6thSense's registry hosted by Supabase. Reports include the camera identifier, observation time, app and camera software versions, camera model, recording status, storage and SD-card status, temperature, capture frame rate, clock and calibration status, and an upload-configuration status. Reports can be queued locally and sent when an internet connection is available.
These reports help maintain camera availability and diagnose recording and upload problems. They use a separate opaque reporter identifier, not the installation identifier used for optional PostHog analytics. A camera identifier can be linked to your contributor account when that camera is assigned to you. The reports do not contain footage, audio, preview images, Wi-Fi passwords, camera access tokens, bank details or upload credentials.
Fleet reporting is separate from the optional analytics setting; disabling analytics stops PostHog events but does not disable configured fleet reporting. Contact ops@6thsense.dev for questions or requests concerning fleet records associated with you or your camera.
Synapse uses Expo Updates to check 6thSense's configured app-update service. It may also contact a configured HTTPS manifest and download endpoint to retrieve camera software. These requests transmit standard network information such as IP address and user agent to the receiving service. Camera software is cached privately before it is sent to a selected camera over the local network.
Synapse requests only the access needed for its current features:
Where contributor enrollment is enabled, account authentication uses Amazon Cognito, including your phone number, verification status, and regional routing information. The contributor service stores your name, agreement receipts, operator-confirmed camera assignments, footage and review metadata, and payment records. Sign-in credentials and a deletion-status receipt may be kept in secure storage on this phone.
Korean contributors register bank details on the website after accepting the payment notice. The account-holder name, bank, full account number, email, date of birth, phone number and address are sent over HTTPS through the 6thSense backend hosted by Railway to Wise, which registers you as a payment recipient; a backup copy of the name, bank and account number is kept in a private Google spreadsheet accessible to authorized staff. The website database keeps a masked receipt and the Wise recipient ID. Registration does not send a payment; staff separately review footage and approve payments. In the supervised pilot, an operator imports recordings from the camera storage card; creating an account does not upload footage from your phone.
Regional notices and agreements explain the collection, sharing, international transfers, and retention that apply to participation. Enrollment stays unavailable where the required final documents have not been published. This public policy does not replace those agreements.
Use Delete account in the contributor account area, including before enrollment or agreement acceptance. The service records the request and stops new contributor activity and approvals. Deletion may require operator work; a request or deactivation is not confirmation that data has been erased. The app displays request status and any configured completion estimate, and keeps a private status receipt so you can check completion after the login has been removed.
Completion requires removal of the Cognito login, scrubbing of the contributor profile and bank summary, confirmed removal of the bank spreadsheet row, and an operator record of footage and processor cleanup. Any legal or payment records that must be retained require a recorded scope, reason, and review date. The applicable regional documents describe retention; this policy does not promise a fixed deletion period. Deleting the cloud account does not erase independent copies on your camera or previously shared destinations.
Synapse is an operations tool for robotics data collection. It is not directed at children, and 6thSense does not knowingly collect data from children under 13 through Synapse.
If this policy changes materially, 6thSense will update this page and the date above. Questions about Synapse privacy can be sent to:
목적: 보수 정산·지급 준비, Wise 수취인 등록 및 관련 문의 처리. 항목: 예금주명, 은행·계좌번호, 이메일, 생년월일, 전화번호, 주소(참여자 ID 및 동의 기록과 연결).
보유기간: 최소 정산 증빙은 참여 종료일과 최종 정산일 중 늦은 날부터 5년, 그 밖에 불필요해진 지급정보는 해당 시점부터 30일 이내 삭제합니다.
동의를 거부할 수 있으며, 거부 시 온라인 계좌 등록은 진행되지 않습니다. 이미 발생한 보수와 업로드 권한에는 영향이 없습니다. 대체 지급 방식, 동의 철회, 열람·정정·삭제 문의: alex@6thsense.dev.
개인정보처리자: 6thSense AI, Inc.(미국). 연락처: alex@6thsense.dev.
항목·시기·방법: 위 지급정보, 참여자 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
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.
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