For contributors & people in recordings

Privacy policy

What we collect, why we need it, and how to ask us to stop.

Effective October 13, 2026. This notice describes the India pilot for Mimicry Capture, operated by Mimicry, Inc., a Delaware corporation (operator details). Contributor collection and buyer delivery have not started yet.

1. Data we collect and why

We collect recordings to prepare calibrated sensor datasets for robotics and AI research, verify assigned work, check quality and protect the integrity of collection.

Household video
A chest-mounted smartphone records hands, objects and work surfaces during household tasks. Faces, bystanders, screens and documents can accidentally appear. We inspect video for quality, calibration and privacy processing; a chest mount does not guarantee that faces stay out of view.
Movement and environmental sensors
Accelerometer and gyroscope readings (IMU) capture movement. Available magnetometer and barometer readings capture magnetic field and pressure. These provide sensor context and support calibration and recording checks. Availability varies by phone.
Camera and frame information
Frame timestamps, exposure, focus, camera settings and calibration metadata describe how each frame was recorded. We use them to align sensor data, check recording quality and calibrate the recorded image.
Device and integrity information
Device model, operating-system/build information, installation identifiers and Google Play Integrity signals help check phone compatibility, app authenticity and authorized submissions.
Sign-in and participant information
Your phone number is used for SMS sign-in through Amazon Cognito and AWS SMS services. Participant IDs, enrollment, assignments and work records support participation, work acceptance and earnings. Identity and payment information are separated from recording records.
Consent records
We record the consent document version and hash, language, choices and acceptance time to keep evidence of what you agreed to, including separate public-release and audio choices.
City
Location is limited to your city, supplied by you or derived at city level. We do not collect GPS coordinates through the capture program.
Audio
Audio is off by default and stays off in the ordinary pilot. Any future program that records audio would need a separate enabled program and your explicit audio consent.

The program is open only to adults aged 18 or older. Contact us if a recording may contain you or a child.

2. Access, processing and sharing

Recording records use pseudonymous participant IDs. They are not a promise of anonymity: raw images can contain identifying details. Identity and payment records are isolated from capture and processing access.

The production design places raw storage and restricted processing in AWS Mumbai, India. Authorized processing and privacy-review staff may inspect unredacted recordings there. Server-side face, screen and document redaction, with review, is required before delivery.

Robotics and AI labs receive approved, redacted, pseudonymous sensor recordings under license. Datasets include timing, sensor and camera/calibration information, task metadata, quality information, redaction masks and provenance. A public dataset release requires separate consent.

Service providers include AWS for hosting, storage and Cognito identity, including SNS for SMS; Google for Play distribution, Integrity checks and Google Workspace email; and Cloudflare for this website. SMS, identity, email, website and other provider processing may involve destinations outside India. Mumbai raw storage does not mean all personal data stays in India. See provider details.

3. Security and this website

The production design uses encrypted transport and storage, private storage, restricted roles, authenticated access and file hashes to check integrity. Application logs must exclude personal identity, media and credentials. Deployment and recovery checks remain required before live collection.

This website has no analytics, tracking scripts, third-party fonts, forms or application cookies. Email links open your email service; they do not submit a request automatically. Hosting and email services still process requests and messages; see provider details.

4. How long data is kept

We keep data for the periods below.

Raw recordings and sensor data
Normally no more than 12 months. Withdrawal can end permitted use earlier.
Processed releases
Kept for the period allowed by the applicable consent and license, which may extend beyond raw-data expiry. Each release’s expiry is set in its license.
Submitted copies on your phone
We plan to remove submitted copies from your phone about 72 hours after the upload is verified.
Database backups
A 14-day backup window. Withdrawal records are preserved separately so restored backups cannot reopen withdrawn data.
Temporary storage
Interrupted uploads are removed within 1 day, upload staging copies within 14 days, temporary processing files within 7 days and delivery caches within 30 days (details).
Identity, earnings and legal records
Account deletion removes your account identity and associated content. We keep earnings and payment records only as long as tax and accounting law requires, up to 8 years, and records of your consent, withdrawal and requests for up to 3 years after your account closes, as proof (details). Nothing is kept indefinitely.

5. Consent, withdrawal and your rights

Consent is required before capture. Public release has a separate choice. Review and explicit submission are required before upload; after submission, removal uses withdrawal.

You may request information about your personal data and its sharing, correction, completion, updating or erasure, withdraw consent, raise a grievance, or nominate someone to exercise applicable rights in the event of death or incapacity. These rights apply as provided under India’s Digital Personal Data Protection Act, 2023 and its Rules.

To withdraw particular recordings or request full account deletion without the app, follow the email request steps. For other rights, use the same privacy contact and describe your request. We acknowledge deletion requests within 7 days and complete them within 30 days, and answer other requests within 30 days (details).

Withdrawal stops new processing, publication and download grants for affected recordings, deletes managed raw and derived copies and all storage versions, and notifies buyers. Managed deletion, backup expiry and buyer acknowledgment are separate steps. We cannot remotely erase copies buyers have already downloaded. Our team handles deletion requests directly and confirms completion by email.

Withdrawal ends future consent-based use and may prevent further participation; it does not undo processing that was lawful before withdrawal. Earned pay is preserved when content is deleted.

6. Questions and grievances

Use privacy@mimicrydata.com for privacy questions, rights or a grievance. Put “Privacy grievance” in the subject and describe the issue. Our Privacy Officer answers within 30 days. Our postal address is on the contact page.

If our grievance process does not resolve your concern, you may complain to the Data Protection Board of India once its complaint process is available, after first using our grievance route (details).