Welcome toLivecodeshare-pro. We are committed to protecting your privacy. This policy describes how Livecodeshare-pro collects, uses, and protects your information when you use our real-time collaborative workspace atlivecodeshare-pro.vercel.app.
By using our service, you agree to the collection and use of information in accordance with this policy.
1. Architecture & zero-knowledge commitment
Livecodeshare-pro is designed with a decentralized, zero-knowledge architecture.
- All code editing, chat messages, and web-sharing streams are encrypted client-side using WebCrypto AES-GCM 256.
- Your data is encrypted in your browser before it is sent over any server infrastructure. We do not store, log, or have the capability to decrypt your workspace code or chat messages.
- We do not host user files on centralized databases. All storage is managed locally on your machine or directly on your own cloud storage.
2. Information we collect
While using our service, we may collect or access certain information.
- Google OAuth profile information:If you log in using Google OAuth, we receive basic authentication info from Google — your email address, name, and profile picture — used solely to identify your session.
- Local storage:We use your browser's local storage to persist display names, screen themes, and temporary workspace history locally.
- Room connection metadata:To facilitate peer-to-peer communication, we process transient metadata such as WebRTC signaling data and encrypted room names. This data is processed in-memory and discarded when the room is terminated.
3. Google API services & Drive integration
Livecodeshare-pro offers integrations with Google Drive to allow users to back up and import workspace files.
- Authorized scopes:We request the
https://www.googleapis.com/auth/drive.filescope exclusively to create, modify, and view files created or opened by Livecodeshare-pro. - How Drive data is used:The app uses the Google Drive API to save collaborative code files and fetch previously saved workspaces, triggered solely by your manual requests.
- Data transmission & storage:Google Drive files are read from and written to directly from your browser using your OAuth access token. File contents are encrypted client-side before transmission. Your Google Drive data and OAuth token are never transmitted to or stored on Livecodeshare-pro servers.
Google Limited Use Disclosure
Livecodeshare-pro's use and transfer to any other app of information received from Google APIs will adhere to theGoogle API Services User Data Policy, including the Limited Use requirements.
4. Data sharing & third-party services
We do not sell, trade, rent, or share your personal information or workspace content with third parties. Because we do not store your private keys or decrypt your workspace data, we cannot view or share your collaborative work even if requested.
5. Control over your data
You have complete control over your data.
- Revoking Google access:You can revoke Livecodeshare-pro's access to your Google Account at any time throughmyaccount.google.com/permissions.
- Deleting workspace data:Because your workspace files reside in your personal Google Drive or browser local storage, you can delete them permanently by deleting files inside Google Drive or clearing your browser's site data.
6. Security of your data
We use end-to-end encryption for collaborative code editing, chat messages, and multimedia streams. Security is a shared responsibility — you are responsible for maintaining the confidentiality of your room passwords. If you lose your room password, we cannot recover or decrypt your data.
7. Changes to this privacy policy
We may update this Privacy Policy from time to time. We will notify you of changes by posting the new policy on this page and updating the "Last Updated" date above. You are advised to review this policy periodically.
8. Contact us
If you have any questions or suggestions about this Privacy Policy, please contact the developer directly.