Remixel logoRemixel
Privacy Policy
Effective October 23, 2026

Privacy First

Local rendering, with clear choices about sharing

This policy covers Remixel on Mac, iPhone, and Apple TV. It explains local rendering and chat history, saved visuals and deliberately queued requests in private iCloud storage, the permissions each feature uses, and the content sent to OpenAI or to the model provider used by your MCP assistant.

Privacy at a glance
Privacy at a glance
The short version for users, reviewers, and support.
  • Applies toRemixel on Mac, iPhone, and Apple TV
  • OperatorJake Kinchen
  • Mac bundlecom.kellyclaudeai.remixel
  • iPhone bundlecom.kellyclaudeai.remixel.companion
  • TV bundlecom.kellyclaudeai.remixel.display
  • PlatformsmacOS, iOS, tvOS
  • Effective dateOctober 23, 2026

Core Principles

How Remixel approaches privacy

Visuals render on your device. Saved-library synchronization uses private iCloud storage, and AI requests use your connected OpenAI account or your MCP assistant’s configured provider.

Local-first by default
Remixel renders visuals locally on Mac, iPhone, and Apple TV. The Mac handles authoring through the assistant; supported connected devices can control or play visuals without moving rendering to an external service.
Permissions only for chosen features
Camera, microphone, photo library, folder access, and screen capture are tied to the pairing, audio-reactive, import, save, or app-audio workflows you choose.
No app tracking
Remixel does not use app data for advertising or cross-app tracking. Device connections and optional assistant requests use the data described below to provide the features you choose.
Optional AI creation
The built-in assistant uses your connected OpenAI account. An assistant you connect through MCP uses its configured model provider. Requests can include prompts, selected files, relevant chat and visual context, and rendered preview images used to review your requested changes.

Permissions

What access Remixel may request

Permissions are tied to the exact feature you turn on. If you do not use a given feature, the related permission is not needed.

Pairing camera
Pairing camera
Remixel requests camera access when you choose to scan a device pairing QR code. Camera frames are processed on your device, not sent to iCloud or OpenAI. You can choose a QR image instead.
Microphone
Microphone
Remixel uses microphone input for audio-reactive visuals.
Photos
Photos
Remixel uses your photo library only when you choose photos for visuals or save captures there.
Folder access
Folder access
Remixel uses folder access only when you choose local media or My Visuals content.
Screen and System Audio Recording
Screen and System Audio Recording
If you enable app or system audio capture, macOS may require Screen and System Audio Recording permission before Remixel can browse or capture app audio.
Saved visuals in private iCloud
Remixel uses Apple CloudKit's private database for your saved visual library across supported devices signed in to your Apple Account.

Saved content can include visual source, compiled rendering programs, required assets, saved settings, names, favorites, and lists. Devices also keep local copies for playback and recovery. Live selection, playback timing, audio samples, and current beat features are session data; iCloud library storage does not keep a live playback clock. Device permissions and pairing secrets are separate from saved library content.

Removing a visual hides it on other updating devices when they receive the removal. You can restore it for 30 days unless you permanently remove it sooner. Recovery records, cached copies, and resources shared with other visuals can remain. Pending or conflicting changes remain available for recovery until resolved. Completed saved-setting receipts are kept in bounded local history; completed library-metadata receipts become eligible for cleanup after 48 hours. Removal does not immediately erase every cached or shared resource.

Local chats and requests queued for your Mac
Chat archives stay local by default. A connected device can view and resume chat with its selected Mac through an authenticated connection.

If you enable private iCloud delivery and choose Queue for Mac, Remixel stores that selected message, selected files, and generated native previews for its result in a separate private iCloud transfer area for the selected Mac. A failed or interrupted Send is never automatically queued. The Mac must be awake with Remixel running to accept work.

When the Mac accepts queued work, its assistant can send the request and relevant content to OpenAI under your assistant sharing permission, as described below. Downloading a result does not save it into My Visuals or authorize further work. Enabling saved-library synchronization or queued delivery does not automatically upload your complete chat archive to iCloud.

A queued request can be accepted for up to 24 hours. Confirmed accepted, rejected, or expired delivery records become eligible for cleanup seven days after that deadline, when an authorized device next runs cleanup. If acceptance is uncertain, the request and selected files may remain longer so the original operation can be reconciled. Deleting a local chat or disabling delivery does not erase accepted work or immediately remove retained iCloud records.

No app tracking
No app tracking
These declarations describe the native apps. Website analytics are described separately below.
Remixel does not use tracking domains.
Remixel does not declare tracking in its privacy manifest.
Connection identifiers and selected content shared with the assistant are used for app functionality, not advertising or cross-app tracking.
Device connections
Device connections and relay records
Mac and iPhone remote connections can use Remixel's secure relay service.

The service stores pseudonymous device identifiers derived from public keys, enrollment public keys, pairing authorization and revocation records, and routing metadata. These records authenticate your devices and route encrypted traffic. They are retained beyond a single request; they are not advertising identifiers.

Forgetting a device revokes its connection. Enrollment and revocation records can remain for connection security and replay prevention; unpairing does not promise immediate erasure of every server record. Contact support below for privacy or deletion requests. Visuals and commands travel encrypted through the relay.

Mac and iPhone features use device identifiers for connectivity, and selected photos, videos and other user content for authoring with the assistant. Selected content shared with the assistant can be associated with your connected OpenAI account. The Apple TV app does not run the assistant; its rendering and private iCloud library are separate from the authoring flow.

AI-assisted creation
AI-assisted creation
For AI remixes, use the built-in OpenAI assistant or connect an assistant through MCP on Mac.

The built-in assistant uses your connected OpenAI account for chat, remixing, and scene combination. The Mac handles these requests, including requests sent from paired devices. This built-in option requires an active OpenAI subscription. Remixel also offers a free MCP connection for use with your own assistant and provider. A connected assistant can access visual source and previews you share with it and may send them to its model provider under that provider’s privacy practices.

Content sent to OpenAI can include your prompts, chosen files, relevant chat history, visual source or settings, and rendered preview images used to review the requested result. This applies to assistant work you start directly or deliberately queue for your Mac.

For the built-in assistant, enabling sharing identifies OpenAI and the request and context being shared. Remixel remembers that permission until you revoke it or its scope changes. Account sign-in alone does not enable sharing. Saved-library sync, device control, queued execution, and operating-system permissions are separate choices; an enabled Queue action does not need a repeated confirmation for every request.

You can disconnect your OpenAI account in Settings to stop using that account for assistant requests. OpenAI's own terms and privacy policy apply to its processing, including retention and account settings. Turning off sharing stops new requests; use Stop for work already sent or queued. It does not erase content a provider has already received.

Local history and device backups

Your iPhone's local chat history and selected reference files may be included in iCloud Backup or a computer backup, depending on your device settings. These backups are separate from saved-library sync and live conversation handoff. Remixel does not turn off your operating-system backups.

The private downloaded job-preview cache is excluded from device backups. A restored chat may need its original Mac or a still-available cloud result to recover preview files. Retained preview information alone does not mean those files are available to play.

Pairing keys use device-bound Keychain protection and do not migrate to a different device through restore. Restored messages and saved actions retain their original ownership; they do not authorize a new Mac, Apple Account, or assistant recipient.

Protection and live connections

Saved and queued content uses Apple's private CloudKit storage and protection. Some routing information remains ordinary CloudKit metadata. Advanced Data Protection can add protection for covered iCloud data when enabled for your Apple Account. Remixel does not provide its own application-level end-to-end encryption or control that account setting. Content sent to OpenAI is processed under OpenAI's terms and privacy practices.

Authenticated live connections carry device control, working previews, authoring streams, and needed resources. Nearby networking, an enabled tailnet route, and an optional relay are connection routes. They do not authorize a different Mac or grant execution permission. Live transport does not upload your entire chat archive to iCloud.

The remixel.app website

The marketing website uses Google Analytics, Google Ads, and Meta Pixel to measure page visits, plays of the homepage demo clip, and download or license-claim clicks, plus Vercel Speed Insights to measure website performance. These browser services can receive information about your visit and may use cookies or similar technologies under their own policies. The native apps' no-tracking declarations do not describe these website services.

License claims and delivery use Polar's hosted service. Information you choose to provide there, such as your email address, is handled through Polar. If you email support, your email address and the message or attachments you send are used to respond to your request.

Contact
Questions about privacy or support
Contact the Remixel support address if you need clarification about this policy or the app's permissions.

Jake Kinchen

jakekinchen@gmail.com

Copyright 2026 Jake Kinchen