What Oscar processes
Oscar may process account details, authentication records, billing status, usage counters, plan entitlements, workflow metadata, diagnostics, and support messages needed to operate the service.
Legal
Privacy
Oscar is built around local media processing. Cloud services are used for account access, billing, entitlements, usage control, support, and product operation.
Local media handling
Audio, video, image, and project media are designed to be processed locally in the web runtime or local CLI runtime where supported. Oscar does not need to upload source media for ordinary local workflows.
Local recovery and retention
Recent media projects and writing can stay in this browser for recovery for up to 45 days after you last open them. Cached transcripts can stay for up to 30 days after last use. Browser storage pressure may remove older work sooner, and removing an item from Recents also removes its locally stored project data and related caches. Downloaded exports are not kept by Oscar after delivery.
Cloud services
Cloud services may be used for sign-in, subscription checkout, entitlement checks, usage metering, lease validation, operational logs, error diagnostics, email/contact handling, and fraud or abuse prevention.
Transcript and AI features
When you request transcription, captions, or transcript-based AI editing, Oscar may create compressed audio and temporarily upload it to cloud storage and a transcription provider. Oscar deletes its temporary object-storage copy after processing. Transcript text, word timings, compact media analysis, and your selected editing intent may be sent to AI services when needed to return the requested review or edit.
Oscar Clear and writing
When you request an Oscar Clear edit, the writing you submit and the candidate edits needed to select the result are processed by cloud AI providers. This processing is used to create, evaluate, and return the requested clear version. Do not submit confidential or sensitive writing unless you are comfortable having it processed for that purpose.
Workflow metadata
Oscar may store metadata such as workflow ids, timestamps, plan usage, export minutes, command summaries, warnings, and non-media diagnostics so limits, billing, support, and reliability checks work across app and CLI.
Payments
Paid plan checkout and subscription management are handled through payment providers. Oscar stores plan and billing status needed to unlock features, but payment card details are handled by the payment provider.
Contact and requests
For privacy questions or requests, contact hello@oscareditor.com.
Beta note
Oscar is in beta. Providers, analytics, billing behavior, and diagnostics may change as the product matures, and this page will be updated when those changes affect privacy handling.