Privacy policy

Last updated: 19 September 2026

This policy covers the Looper apps, the control plane you run on your computer, and looper.fyi. Looper is maintained by Ayush, whose public maintainer account is heyAyushh on GitHub. See Contact and privacy requests below for how to reach the maintainer.

How Looper handles information

Looper connects your coding-agent sessions with your devices. Its control plane runs on your computer and stores operational data there. Companion apps keep local state and cached information so they can reconnect and display your sessions. Information can leave your devices through paired connections, coding-agent providers, configured integrations, and notification services described below.

Depending on the features you use, Looper processes:

• Session and project information: session identifiers and titles, agent/provider names, project names and paths, activity and status, prompts and responses, command requests, and project context such as work items, goals, summaries, and insights. This supports displaying sessions, sending your instructions, continuing work, and restoring state after reconnecting.
• Connection and authentication information: computer and device names, endpoint addresses, pairing identifiers and credentials, passkey/session information, and connection preferences. This is used to connect and authenticate your devices. Do not share pairing codes or credentials publicly.
• Notification information: device installation identifiers, push tokens, delivery state, and notification content when push features are configured. This is used to deliver the relevant alert or activity update.
• Diagnostics and support information: app and system versions, errors, connection and performance information, local logs, and anything you choose to include in a support request. This helps diagnose failures and respond to you. Logs and screenshots can contain session identifiers, paths, or private content; review them before sharing.

Paired devices, agents, and other services

Your phone communicates with the Looper computer you pair with over a reachable connection, such as your LAN or a Tailscale route. Session data and commands travel between those devices. Network services you configure, including Tailscale or a proxy, operate under their own privacy terms.

Configured coding agents, AI providers, and project integrations can receive prompts, commands, session information, and project context needed for the operations you use. Some providers process information on remote servers. Their account settings, permissions, and privacy policies determine their handling and retention of that information. Connecting an integration or submitting content to it can therefore send information beyond your own computer.

If remote notifications are enabled and configured, Looper sends device tokens and notification payloads through Apple Push Notification service. Payloads can include computer or session identifiers, alert text, and project or work-status summaries; they are not limited to an anonymous wake-up signal. Notification previews and Live Activities may display information on a lock screen. You can manage these in your device's notification settings.

The iPhone pairing scanner uses the camera, or a photo you choose, to read a connection code on your device. The decoded connection details are then used to connect to the computer. You can deny or revoke camera access in system settings and use the other pairing methods available in the app.

Apple system features, such as Siri, Spotlight, Handoff, and Live Activities, may receive the session or project information needed to present those features. Apple controls the operating-system services and their privacy settings. If you use TestFlight, Apple also processes beta-testing information, including crash and usage information and feedback you submit, as described in TestFlight & Privacy.

If you use the Apple Watch companion, session snapshots, permission-review information, replies, and approvals pass through the paired iPhone using WatchConnectivity. Text entered with Apple Watch system dictation becomes a reply draft and is sent to the coding-agent session when you send the reply. Apple's dictation settings govern voice processing by that system feature.

Website visits and downloads

looper.fyi is hosted on Vercel. Serving a page or download request involves technical information such as your IP address, requested URL, browser information, and request timing. Vercel may process and retain operational and security logs. See Vercel's privacy notice.

The current website does not embed advertising or behavioral-analytics scripts. That does not prevent hosting providers from processing the technical request information above. Following a link to GitHub, Apple, an agent provider, or another site is subject to that service's privacy practices. Release downloads are hosted on GitHub when available.

Retention, deletion, and your choices

Local session, project, connection, and command data remain in Looper's application storage according to the record's purpose, configured settings, and any applicable pruning or cache limits. Some event and cache records are pruned automatically; this is not a promise that all session content disappears after a fixed period. Provider histories, device backups, and data already sent to another service have separate lifecycles.

You can stop Looper, disconnect integrations, revoke a paired device through the computer's connection controls, and disable optional system permissions or notifications. Revoking a pairing stops its authorized access and disables its associated push registration; it does not erase copies already received on other devices or by providers. Disabling a permission does not delete information already processed.

Uninstalling an app or package does not necessarily remove all Looper data. In particular, the Linux package's normal uninstall preserves configuration and session data, and removing a desktop app can leave its application-support files. To remove local information, use the relevant app or package's data-removal controls and remove remaining Looper application data and backups on the devices you control. Ask for help before deleting files if you are unsure which data belongs to Looper. Removing Looper data does not remove the original history held by a coding-agent provider.

For support messages or other information you have sent to the maintainer, you can request access, correction, or deletion using the contact route below. Applicable rights depend on your location and the information involved. The maintainer can address information they hold; information held only on your devices or independently by a provider must also be managed there. Hosting, support-platform, and provider records may be retained under those services' policies and applicable requirements; no single retention period applies to all of them.

Contact and privacy requests

Contact the maintainer through the Looper issue tracker. To start a privacy request, post only that you need a private contact channel. Issues are public: do not include personal information, prompts, logs, tokens, or pairing codes. The maintainer can arrange an appropriate way to continue the request privately.

Changes to this policy

Updates will be published at this URL with a revised date. Review the policy when enabling new integrations or optional features.

Home · Setup guide