privacy policy

Multiplayer Labs, Inc. ("multipeer", "we", "us" or "our") provides the multipeer desktop application, the website at multipeer.sh and related services (together, the "Services"). This Privacy Policy explains what information we collect when you use the Services, how we use and share it, and the choices you have.

By using the Services you acknowledge that you have read and understood this Privacy Policy. It forms part of our Terms of Service.

multipeer is a shared canvas for your terminals, agents and files. It is designed so that the contents of your work stay on the computers in your session. We do not collect, transmit or store:

• The contents of your terminals, including commands, output, and anything you send to or receive from an agent.
• The contents, names or paths of your files and folders.
• The contents of your canvas, such as notes, zones and layout. A canvas is synchronized directly between the computers in a session over an encrypted connection and does not pass through our servers.
• The API keys, tokens or logins your agents use. Your agents keep those themselves, on your computer.
• A password. multipeer has no passwords; you sign in with Google, GitHub or a one-time code sent to your email.

Account information. When you sign in with Google or GitHub, we receive your email address, name and profile picture from that provider. When you sign in by email code, we receive your email address. We also store the avatar you choose in the app, the sign-in method you used, and the dates you signed up, completed onboarding and last used the app.

Device information. For each computer you sign in on we store a name, a public key used to identify it to your teammates, the app version, your operating system version and processor type, and when it was first and last seen. The corresponding private key never leaves that computer.

Team information. If you create or join a team, we store the team's name and owner, each member's role and join date, and any invitations sent: the invited email address, who sent it and when it expires.

Usage information. The app reports a limited set of events so we can understand how multipeer is used: that the app launched, that you signed in or out, that you progressed through onboarding, that a component was created and its kind (for agents, the tool's name if it is one we recognize), that a canvas was hosted, joined or reconnected, and that you opened the link to our community server. Each event carries the app version and the time. Events never include code, commands, file contents or paths.

Diagnostic information. If the app encounters a crash or error, we record the type of error and where in the application code it occurred. We never record the error message itself, because it could contain a file path.

Waitlist. If you join the waitlist on our website, we store your email address and the platforms you selected.

Communications. If you contact us, we keep the correspondence and the information you choose to provide.

Website. The website at multipeer.sh does not set cookies and does not run analytics. Our hosting provider keeps standard server logs, including IP addresses, for security and operation of the site. To show how many people are in our community server, your browser asks Discord for the count directly, so Discord receives your IP address under its own privacy policy.

We use the information we collect to:

• Provide, operate and maintain the Services, including signing you in and keeping you signed in.
• Operate teams, so teammates can join each other's canvases and invitations reach the right people.
• Understand how the Services are used and improve them.
• Diagnose and fix crashes and errors.
• Roll out features gradually, by enabling them for some people before others.
• Protect the Services and their users, including enforcing rate limits, preventing abuse and ending sessions where necessary.
• Communicate with you about the Services, including sign-in codes, team invitations, security notices and, if you joined the waitlist, news about the platforms you asked for.
• Comply with legal obligations and enforce our terms.

We do not sell personal information and we do not use it for third-party advertising.

Where the law of the European Economic Area, the United Kingdom or Switzerland applies, we process your information on the following bases: performance of our contract with you (providing the Services you asked for); our legitimate interests (improving and securing the Services, understanding how they are used, and communicating with you), balanced against your rights; your consent, where we ask for it; and compliance with legal obligations.

With other users. Your teammates can see your email address, name, avatar and the names of your computers. People in a canvas session with you can see your name and avatar.

With service providers. We use third-party providers to operate the Services. Each receives only the information needed for its function and is bound by its own privacy commitments:

• Supabase, which hosts our database and provides authentication and session management.
• Google and GitHub, which provide sign-in when you choose them.
• PostHog, which receives usage and diagnostic events together with your email address and name, and records your operating system and an approximate location derived from your IP address.
• Resend, which delivers our emails, such as sign-in codes and team invitations.
• Vercel, which hosts the website.

With our team. Authorized members of our team can view account, team, device and event information through an administrative console. Access is restricted to designated administrators and every administrative action is logged.

For legal reasons. We may disclose information if we believe it is reasonably necessary to comply with a law, regulation, legal process or governmental request; to enforce our terms; to detect or prevent fraud, abuse or security issues; or to protect the rights, property or safety of multipeer, our users or the public.

Business transfers. If Multiplayer Labs, Inc. is involved in a merger, acquisition, financing, reorganization or sale of assets, your information may be transferred as part of that transaction. This Privacy Policy will continue to apply to it.

If you sign in with Google, we receive your email address, name and profile picture. We use this information only to create and operate your multipeer account, to show you to your teammates, and to attach the usage and diagnostic events described in Section 3 to your account so we can improve multipeer. We do not use it for advertising and do not sell it. Our use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

We keep information for as long as needed for the purposes described in this Privacy Policy:

• Account, device and team information: for as long as your account exists.
• Usage and diagnostic events: for as long as they are useful for understanding and improving the Services, after which they are deleted or aggregated.
• Team invitations: 14 days, after which they expire.
• Rate-limiting records: one day.
• Waitlist entries: until we have released on the platforms you selected and notified you, or until you ask to be removed.

When your account is deleted, we delete your profile, your devices, any team you own and the keys of devices you removed. We may retain information where required by law or to resolve disputes and enforce our agreements.

We take reasonable technical and organizational measures to protect your information. All communication between computers in a session is encrypted, and anyone who is not a teammate must confirm a code shown on both screens before joining. Your sign-in session is stored in your computer's secure credential store: the macOS Keychain, where signed releases allow only multipeer to read it, or the Windows Credential Manager, which programs running under your Windows account can read. Our database enforces row-level access rules so that you can read only your own records, and the credentials that could read everything never ship in the app. No method of transmission or storage is completely secure, and we cannot guarantee absolute security. If you discover a vulnerability, please report it to hello@multipeer.sh.

We are based in the United States and our service providers store information there. If you use the Services from outside the United States, your information will be transferred to, stored and processed in the United States, where data protection laws may differ from those in your country. Where required, we rely on appropriate safeguards for such transfers, such as standard contractual clauses.

Depending on where you live, you may have the right to access, correct, delete or receive a copy of your personal information, to object to or restrict certain processing, and to withdraw consent where processing is based on it. To exercise these rights, contact us at hello@multipeer.sh from the email address on your account. We respond within the time required by applicable law and in any case within 30 days. If you are in the EEA, the UK or Switzerland, you may also lodge a complaint with your local supervisory authority.

California residents. The California Consumer Privacy Act gives you the right to know what personal information we collect and how we use and share it, to request its deletion, to correct it, and not to be discriminated against for exercising these rights. We do not sell or share personal information as those terms are defined in the CCPA, and we have not done so in the preceding 12 months.

In the app. Signing out removes your session and team information from that computer. Removing a device in Settings prevents it from joining your canvases. Your name and profile picture come from your sign-in provider and can be changed there; the avatar you chose in the app can be changed in the app.

Email. Sign-in codes, invitations and security notices are part of operating the Services. To leave the waitlist, reply to any waitlist email or contact us.

Usage events. The usage and diagnostic events described above are integral to operating the Services and cannot be disabled separately. They never include the contents of your work.

The Services are not directed to children under 13 (or the minimum age required in your country), and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, contact us and we will delete it.

We may update this Privacy Policy from time to time. When we do, we will revise the date at the top of this page. If the changes are material, we will provide additional notice, such as in the app or by email, before they take effect. Your continued use of the Services after the changes take effect means you accept the updated policy.

If you have questions about this Privacy Policy or our data practices, contact us at:

Multiplayer Labs, Inc.
hello@multipeer.sh