PrivacyPolicy

Welcome toLiveCode Pro("we", "our", or "us"). We are committed to protecting your privacy. This Privacy Policy describes how LiveCode Pro collects, uses, processes, and protects your information when you visit and use our real-time collaborative workspace application located athttps://livecodeshare-pro.vercel.app(the "Service").

Please read this policy carefully. By using our Service, you agree to the collection and use of information in accordance with this policy. If you do not agree, please do not access or use the Service.

1. Architecture & Zero-Knowledge Commitment

LiveCode Pro is designed with a decentralized, zero-knowledge architecture. This means:

• All code editing, chat messages, and web-sharing streams are encrypted client-side using industry-standard 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 LiveCode Pro 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 choose to log in using Google OAuth, we receive basic authentication info from Google, including your email address, name, and profile picture. This is used solely to identify your session and permit secure, authorized requests to the Google APIs on your behalf.
• Local Storage:We use your browser's local storage to persist display names, screen themes, and temporary workspace history locally in your browser for convenience.
• Room Connection Metadata:To facilitate peer-to-peer real-time communication (voice, video, screen share) and coordinate collaboration, we process transient metadata (such as WebRTC signaling data and encrypted room names). This data is processed in-memory and is discarded when the room is terminated.

3. Google API Services & Drive Integration

LiveCode Pro offers integrations with Google API services to allow users to backup and import workspace files directly to and from their personal Google Drive.

• Authorized Scopes:We request thehttps://www.googleapis.com/auth/drive.filescope. This permission is requested exclusively so you can create, modify, and view files created or opened by the LiveCode Pro application.
• How Drive Data is Used:The application uses the Google Drive API to save your collaborative code files (e.g. text/plain documents) and fetch previously saved workspaces. This operation is triggered solely by your manual requests (e.g., clicking "Save to Google Drive" or "Import from Drive").
• Data Transmission & Storage:Google Drive files are read from and written to directly from your web browser using your Google OAuth access token. File contents are encrypted client-side using your room's decryption key before being transmitted. At no point is your Google Drive data or your OAuth access token transmitted to or stored on LiveCode Pro servers.

4. Data Sharing & Third-Party Services

We strictly 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. Your Google Drive files are strictly accessible by you and the collaborators with whom you share your Google Drive files or room passwords.

5. Control Over Your Data

You have complete control over your data:

• Revoking Google Access:You can revoke LiveCode Pro's access to your Google Account at any time through your Google Security Settings page athttps://myaccount.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 at any time by deleting the files inside Google Drive or clearing your browser's site data.

6. Security of Your Data

We take security very seriously. We use end-to-end encryption for collaborative code editing, chat messages, and multimedia streams (WebRTC). However, 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 our Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last Updated" date at the top of this policy. You are advised to review this Privacy Policy periodically for any changes.

8. Contact Us

If you have any questions or suggestions about this Privacy Policy, please contact the developer directly at: