You decide what leaves your device.

Controller

Data we process

Account data

On iPhone and Mac, when you sign in with Apple, we receive an Apple account identifier and, where Apple provides them, your name and email address. We also store an internal account identifier and authentication information.

On Mac, sign in also uses Sign in with Apple. A development sign in based on a seller name exists only in internal debug builds and is not available in a released app.

Video and optional audio

ClipBid processes the video you choose to upload. Microphone capture is switched on by default on both iPhone and Mac. Mac system audio is also on by default and has its own independent toggle; it can be recorded together with the microphone or separately. You can disable each source before recording or remove it before upload. The service may require particular sources for submissions; the app shows these requirements before recording and checks them again before submission.

Video or audio may contain people, homes, screens, voices, objects, or other personal information visible or audible in the recording.

Recording and security data

We process technical recording details such as timestamps, duration, resolution, frame rate, file size, hashes, capture identifiers, and privacy mask coverage. Depending on the device and settings, optional motion or interaction signals may accompany a recording.

On supported iPhones, capture may also include a secondary camera video, depth information, and device or headphone motion signals. These files are uploaded with the primary recording when available.

If you record while wearing an Apple Watch, ClipBid also receives wrist motion from the watch, the limb placement you select in the app, and details the watch reports about itself: which wrist it is worn on, the digital crown orientation, the model, and the system version. The placement you choose is stored alongside the clip and affects what we offer for it, because placements we hold little data for are paid more.

On Mac, input capture can include mouse positions, clicks, scrolling, keyboard key codes, and modifier keys. It is switched on by default and is required for Mac submissions in the initial beta. You must grant macOS Input Monitoring permission before this capture can start. The service rejects submissions without the required input recording. Key codes and modifier keys can reconstruct typed text, so review recordings carefully and stop recording before entering confidential information.

The Mac privacy shield is an optional extra safeguard that uses Accessibility permission. While recording, it inspects the focused control's role and labels on your device to identify password and payment fields. The inspection does not read field values, selected text, typed characters, or clipboard contents, and the inspected labels are not uploaded. When it detects a sensitive field, it suppresses input events, substitutes black video frames, and pauses microphone and system audio capture. If permission is missing or a control cannot be inspected, recording continues normally. Afterward, a local notice identifies affected apps where possible and remains with the clip during review. These safeguard notes are not uploaded. Inspection is best effort: custom controls, misleading labels, and information elsewhere on screen may escape detection. Review the recording and only upload what you are comfortable sharing.

On Mac, a recording also notes which applications were in the foreground while it ran, including the application name and how long it was active. Applications you exclude from recording are also excluded from this list. This application usage information is uploaded with the input sidecar and can be removed before upload with the same control.

Offers, contracts, and payouts

We store price offers and, when you sell, the sale contract version and acceptance record, seller name, acceptance time, IP address, user agent, payout amounts, currency, status, and Stripe account references. Stripe receives the identity and payment information needed to set up and send payouts. ClipBid does not store your bank account details.

What happens on your device

Your recordings remain local until you choose to upload them. You can review the recording first. On iPhone, you can apply face redaction and remove microphone audio. On Mac, you can exclude selected apps, apply privacy blur, and independently remove microphone or system audio. A recording without a currently required source cannot be submitted.

These controls process the recording on your device. ClipBid uploads the version you select. Privacy tools reduce risk but cannot guarantee that every sensitive detail is detected, so you should always review the result.

Why we use the data

• To authenticate your account and operate ClipBid.
• To receive, secure, review, and assess a submitted recording.
• To generate a price offer and let you decide whether to sell.
• To document an accepted sale and use acquired clips for robotics and machine learning work in line with the accepted agreement.
• To prevent fraud, duplicates, abuse, unlawful material, and security incidents.
• To process payouts, accounting records, taxes, and legal claims.

Processing needed to create an account, provide an offer, complete a sale, and pay you is based on Article 6(1)(b) GDPR. Compliance records are processed under Article 6(1)(c) GDPR where a legal obligation applies. Security, fraud prevention, service reliability, and the defence of legal claims are based on Article 6(1)(f) GDPR.

Automated price offers

ClipBid uses automated analysis of the submitted recording and associated technical capture data to generate a purchase offer for that clip. You are never required to accept it. You may decline the offer, explain your point of view, or request human review by email.

Service providers and recipients

We use providers for hosting and API delivery, database services, media storage, automated analysis, Apple sign in, email, and payouts. The current system uses Vercel, Neon, Backblaze B2, Modal, Apple, Stripe, and GMX for these functions.

Providers receive only the categories needed for their role. A sold clip may be made available to research or commercial data buyers in line with the clip sale agreement you accept. Unsold clips are not sold to buyers.

Some providers may process data outside the European Economic Area. Where required, transfers must rely on an applicable adequacy decision, certification, or standard contractual clauses under Chapter V GDPR.

Retention and deletion

The current service schedules database linked unsold media for deletion after seven days by default. You can also delete a database linked unsold clip from your account. Local recordings remain on your device until you remove them through the app or operating system.

In Settings, choose Delete account to permanently close your account and request deletion of unsold uploads, their associated sidecars, and attributable derived representations used by the pricing service. Sold recordings and their associated data remain with the buyer under the sale agreement; closing your account does not undo a completed sale. This does not override applicable data protection rights, which you can exercise using the contact details below. Account access ends immediately. Cloud cleanup normally finishes within 48 hours; failed cleanup is retried. You can check progress using Account deletion status in the app after signing out. The final storage sweep waits for previously issued upload links to expire and removes historical object versions as well as the current files.

The pricing service links new derived representations to their source clip so they can be removed. Legacy contribution representations without a source link require a separate retention and privacy review because they may include purchased data. Interrupted uploads tracked by the service are included in account cleanup. Unsubmitted recordings on Mac remain local until you remove them.

Sold clips and their sale records are retained for as long as needed to exercise the acquired rights, provide the dataset, meet accounting or legal obligations, and resolve claims. Account, payout, and security records are kept only while needed for the relevant purpose and any mandatory statutory period.

You may also request deletion by email. Limited sale and payment records, including the seller name on completed contracts and records needed to settle unpaid earnings, may be retained after closure where required. Account deletion does not forfeit earnings already owed. If no revocable Apple token is available, the app provides instructions to remove ClipBid from Sign in with Apple manually. Mandatory data protection rights remain unaffected.

Your choices and rights

Who can contribute

ClipBid is for adults. You must be at least 18 years old to create an account, accept an offer, or receive a payout. Selling a clip is a contract, and payout onboarding has its own age requirements.

Uploading and accepting an offer are optional. The app shows any audio or input sources required for an eligible submission; you can decline to record or submit. You should not upload footage that you do not have the right to provide, confidential information, or recordings of children or other people unless you have a valid legal basis.

Subject to the conditions in data protection law, you may request access, correction, deletion, restriction, or portability of your personal data. You may object to processing based on Article 6(1)(f) GDPR. You may also complain to a competent data protection supervisory authority. The authority competent for us is: Der Hessische Beauftragte für Datenschutz und Informationsfreiheit (HBDI), Wiesbaden — competent for companies with their registered seat in Hesse.

Personal data about people visible or audible in a recording is obtained from the contributor, not directly from each person depicted. It may be processed for clip assessment and, after an accepted sale, robotics and machine learning use or disclosure to buyers. The legal basis, notice duties, and safeguards for third party data must be assessed for each launch use case.

If you appear in a ClipBid recording submitted by someone else, contact us with enough information to locate the recording. We will assess your request and the rights of everyone involved.