How Extroid handles your data

1. Scope

This Privacy Policy describes how Extroid (“we”, “us”, or “our”) collects, uses, and protects information when you use the Extroid Chrome extension, mobile web app, website, and related services (collectively, the “Service”).

2. What we never collect

We do not collect or store:

• Your video stream. Video is not stored by Extroid and is not used for analytics.
• Your audio stream. Extroid is currently focused on camera video and does not store audio content.
• Email contents or contacts. Google sign-in is used for authentication and device pairing, not for reading Gmail or contacts.
• Your Google Drive files. Extroid uses the restricted Google Drive appdata scope for its own temporary signaling files only.
• Full browsing history. Extroid does not build a profile of the websites you visit.
• Payment information. Extroid does not process payments through the Service.

3. Data used for pairing and connection

Extroid uses service data to pair your browser with your phone and establish a WebRTC connection. This may include:

• Google account identifier or email address provided by Google authentication.
• Session ID and connection ID.
• QR pairing metadata.
• Trusted-device identifiers, public keys, and encrypted short-lived connection invitations.
• A Firebase installation identifier when you explicitly enable trusted-device notifications. The shared trusted-pair key remains on your devices.
• WebRTC signaling data, including offers, answers, and ICE candidates.
• Temporary files written to your Google Drive appdata folder.

These files are used to let your browser and phone find each other and complete the connection. They are restricted to Extroid’s application data area and are not visible in your main Google Drive interface.

4. Analytics and diagnostics

Extroid uses analytics and diagnostic events to understand where setup or connection failures happen and to improve the product.

This may include:

• Extension or app version.
• App area, such as extension, mobile page, content script, or offscreen document.
• Setup and connection events, such as QR generation, QR scan, camera permission, connection success, and camera activation.
• Session ID or connection ID used to debug a single pairing flow.
• Browser, platform, and device category.
• Meeting page host or target host when needed to diagnose compatibility issues.
• Error group, error name, short error message, and related diagnostic context.

We do not send video content, audio content, QR payloads, access tokens, full URLs, or full stack traces to analytics.

5. Feedback and support data

If you send feedback or contact support, we may process the information you provide, such as your message, email address if provided, browser information, app version, and diagnostic context.

We use this data only to answer support requests, fix bugs, and improve Extroid.

6. Local storage on your device

Extroid may store non-sensitive data locally in your browser or on your phone using browser storage. This may include:

• Session preferences.
• Device pairing state.
• Camera settings and UI preferences.
• Temporary connection state.
• Trusted-device keys and notification registration state.

This data remains on your device unless you clear browser data, remove the extension, or use a product control that deletes it.

7. How we use data

We use data only for the following purposes:

• To authenticate the user and enable device pairing.
• To exchange temporary WebRTC signaling data between the browser and the phone.
• To start, maintain, and troubleshoot the camera connection.
• To understand where users fail during setup or connection.
• To diagnose exceptions, compatibility problems, and permission failures.
• To respond to support and feedback.
• To improve Extroid’s reliability and user experience.

8. Chrome extension permissions

Extroid requests browser permissions only to provide its core functionality.

• Identity / Google sign-in: used to authenticate the user and access the restricted Google Drive appdata area for pairing and signaling.
• Storage: used to save preferences and temporary connection state locally.
• Camera access on mobile: used only when you actively start a camera session on your phone.
• Host permissions for supported video-call pages: used to make Extroid Camera available inside compatible browser video calls.
• Background / offscreen extension functionality: used to keep the browser-side connection and media handling working inside Chrome’s extension architecture.
• Native messaging: used to communicate with Extroid Desktop when it is installed, including local signaling and optional desktop-control features.
• Notifications: requested on your phone only after you choose to enable faster trusted-device connections.

9. Third-party services

Extroid uses the following third-party services:

• Google OAuth 2.0: for user authentication.
• Google Drive API: for temporary WebRTC signaling data in the restricted appdata folder.
• Google Analytics: for product analytics, funnel diagnostics, and error/exception reporting.
• Firebase Cloud Messaging: for optional trusted-device connection notifications. The notification contains an encrypted, short-lived invitation rather than unencrypted connection secrets.
• Chrome Web Store: for extension distribution and installation.

10. Video transport

Extroid uses WebRTC to transmit video between your phone and browser. WebRTC media is encrypted in transit using WebRTC security mechanisms such as DTLS-SRTP.

Extroid does not store your video and does not use your video for analytics.

11. Retention

• WebRTC signaling data: intended to be temporary and removed after the session ends or when it is no longer needed.
• Local browser data: remains on your device until cleared by you, the browser, or the extension.
• Notification registration: remains associated with the trusted device until browser data is cleared, notification registration changes, or the trusted relationship is removed.
• Analytics and diagnostics: retained according to the configured Google Analytics retention settings.
• Feedback and support messages: retained as long as needed to handle support, debug issues, and improve the Service.

12. Data sharing

We do not sell your personal information.

We do not share your video or audio content with third parties.

We use third-party service providers listed in this policy only as needed to operate, secure, diagnose, and improve Extroid.

13. Security

We use reasonable technical measures to protect service data, including HTTPS for communication with Google services and encrypted WebRTC media transport.

Access tokens and credentials should not be shared by the user. Extroid is designed not to log access tokens or expose them in analytics.

14. Children’s privacy

Extroid is not directed to children under the age of 16. We do not knowingly collect personal information from children under 16.

15. Changes to this policy

We may update this Privacy Policy from time to time. If we make material changes, we will update the date at the top of this page and may notify users through the website, extension, or another appropriate channel.

16. Contact

If you have questions about this Privacy Policy or how Extroid handles data, contact:

• Email: zhelonkin.ru@gmail.com
• Website: extroid.alittle.pro
• Compatibility guide: extroid.alittle.pro/compatibility