Privacy Policy

Effective June 5, 2026

RipDock is a local-first app for connecting to AI runtimes that you choose or operate. This policy explains how RipDock handles information in the beta version of the app.

Contact

RipDock can be contacted at [email protected].

Beta App

In the beta release, RipDock does not operate a backend service for chat, file storage, runtime hosting, analytics, crash reporting, subscriptions, or push notifications.

Information RipDock Does Not Collect

In the beta release, RipDock does not collect or store your chat history, files, runtime credentials, API keys, pairing secrets, or runtime session secrets on RipDock-operated servers.

Information Stored On Your Device

RipDock may store information locally on your device, including runtime settings, workspace and chat data, generated files or artifacts, preferences, logs, device identity material, and runtime session material.

Sensitive local material is intended to be stored using platform security features such as iOS Keychain or Android Keystore-backed storage where applicable.

Information Sent To Runtimes

When you connect RipDock to a runtime, the app sends information needed to use that runtime to the system you selected. This may include messages, files, runtime connection details, pairing information, and other content you choose to send.

Those systems are not operated by RipDock in the beta release. Their handling of your information depends on your setup and any third-party services you choose to use.

Device Backups

Local app data may be included in operating system backups, device transfers, or cloud backups depending on your device, platform settings, and app configuration.

Support

If you contact RipDock for support, RipDock may receive your email address and any information you choose to include in your message.

Children

RipDock is not intended for children under 13. RipDock does not knowingly collect personal information from children under 13.

Changes

RipDock may update this policy as the app changes. Future versions may add backend features for subscriptions, push notifications, or minimal user configuration. If that happens, this policy will be updated to describe those practices.