Legal
Privacy Policy
Asimov Capture is used by approved adult collectors to record assigned first-person robotics training data. This policy explains what information the app and related services collect, how Asimov may use it, and how collectors can request deletion or consent withdrawal.
- Last updated
- June 20, 2026
- Legal version
- 2026-06-20.us-launch
Information We Collect
Account information
- Name or display name, email address, phone number if provided, account status, role, login records, consent status, and account deletion requests.
Collector profile and task matching
- Self-reported height/body-scale metadata, country/region, languages, experience, environment, useful equipment, and profile completion status.
- Current releases use self-reported country/region for task matching and do not request device location permission.
Capture data
- First-person RGB video recorded during assigned tasks.
- Microphone narration audio only when an assignment requires narration or when a collector explicitly opts into optional narration for that assignment.
- Event markers such as privacy risk, interruption, bad camera angle, task changed, or important moment.
- Assignment snapshots, consent snapshots, device profile snapshots, local and remote session identifiers, and quality reports.
- Recordings remain local for review until the collector chooses to upload them.
Sensor and spatial data
- ARKit pose, camera intrinsics, LiDAR/depth data, IMU/motion data, frame counts, timestamps, tracking state, and related quality metrics, when supported and required by the assignment.
- No GPS or device location permission is used in the current release.
Device, upload, and fraud-prevention data
- Device model, OS version, app version, identifierForVendor as a weak local signal, App Attest status, DeviceCheck status, IP-derived server logs, upload timing, file sizes, checksums, retry counts, and suspicious activity flags.
- We do not collect MAC address and do not use private or undocumented identifiers.
Payment, payout, and review data
- Stripe Connect onboarding status, connected-account identifiers, payout eligibility, payable balances, payout records, transfer status, bank-payout status when Stripe reports it, failed payout status, and related payment metadata.
- Sensitive payment identity, tax, and bank details are handled by Stripe-hosted onboarding and payout services, not stored directly in the app.
- Reviewer decisions, rejection reasons, reviewer notes, accepted duration, payable amount, audit history, and reviewer/admin identifiers.
How We Use Information
- Provide collector accounts, assignments, recording, upload, QA, and payout status.
- Match collectors to assignments using self-reported profile metadata.
- Evaluate recording quality and decide whether sessions are accepted, rejected, or require reshoot.
- Create payable balances only for accepted sessions.
- Build, annotate, validate, improve, sell, license, sublicense, or share robotics and AI training datasets with customers and service providers, where the collector has provided required consent.
- Detect fraud, duplicate submissions, unsafe behavior, abuse, account compromise, or policy violations.
- Operate security, debugging, support, compliance, tax, payment, and audit workflows.
- We do not use capture data, ARKit/depth data, motion data, or device identifiers for advertising, cross-app tracking, or unrelated user profiling.
Licensing Or Sale Of Data
With explicit consent, uploaded data may be processed for review, QA, safety, fraud, support, and dataset preparation. Accepted data may be sold, licensed, sublicensed, shared, or otherwise provided to robotics, AI, annotation, QA, processing, storage, infrastructure, and customer organizations for robotics training, evaluation, dataset creation, model development, and related research or commercial uses.
Collectors should only record where they have permission. Collectors should not record private documents, screens, credentials, payment cards, bystanders without permission, minors unless explicitly allowed by an assignment and law, restricted facilities, or any content they do not have permission to record.
Third-Party Processors
Asimov may use processors including AWS for storage, upload processing, logs, and infrastructure; Stripe for Connect onboarding, identity/payment workflows, and payouts; product reliability and operational metrics providers if implemented; and annotation, QA, model-processing, or data-preparation providers if needed for robotics/AI dataset operations.
Retention and Deletion
Asimov retains account, consent, upload, QA, payout, fraud, and audit records as needed to operate the service and meet legal, tax, accounting, fraud-prevention, dispute, safety, and contractual obligations.
Collectors may request account deletion in the app. Asimov will delete or de-identify eligible information, subject to retention requirements and rights already granted for accepted data. Some uploaded data, accepted/licensed data, audit records, consent records, payment and tax records, dispute records, safety records, and fraud-prevention records may be retained where permitted or required by law or contract.
Account deletion does not automatically recall datasets already accepted, licensed, sold, shared with customers, or retained under prior consent.
Consent Withdrawal
Collectors may stop using the app at any time. The current app supports account deletion and support requests; collectors who want to withdraw consent should contact support@tryasimov.ai or use the account deletion flow.
Asimov will evaluate withdrawal and removal requests under this policy, the Contributor Agreement, applicable law, payment obligations, audit/fraud obligations, and customer/license commitments. Withdrawal may prevent new assignments, uploads, QA, or payouts until required agreements are accepted again. Withdrawal does not automatically undo uses of data already accepted, licensed, paid, sold, shared, or retained under prior consent where permitted by law and contract.
Children
Collectors must be at least 18 years old. The app is not intended for minors. Assignments should prohibit recording minors unless Asimov has created an explicit lawful workflow and obtained all required permissions.
Security
Asimov uses technical and organizational safeguards such as token-based access, Keychain token storage in the app, scoped presigned upload URLs, checksum verification, role-based admin access, audit logs, and file protection practices. No system is perfectly secure.
Privacy questions can be sent to privacy@tryasimov.ai. Support questions can be sent to support@tryasimov.ai.