What is Flyby?

Flyby helps you to collaborate with your team. Instead of having countless meetings during the day, you can collaborate using super quick screen record, screenshot and images. Create a quick session with your team and communicate with them in-context with the help of chats, screenshot and quick screen records. No more frequent tiring meetings for every small thing and doubt. All of the conversations and recordings get automatically organised around different sessions so that you can access them anytime afterwards. It gives you the ability to search around any conversation since the sessions are small snippets of chats/recordings around specific topics and objectives. In the section below we have explained the different parts about privacy and policies.

How should I contact Flyby?

You can reach out us anytime at [email protected]

What are the permissions you provide to us and why we need those?

DesktopCapture: The tool has a feature of capturing the entire screen to record it and sharing with the team once the video is fully captured. The capture is triggered by the user when he/she writes "recDesktop". The captured screen is marked during the time of the recording and the user is asked to click on the entire screen. Only then we start capturing. User can stop capture by clicking the stop button once the key is captured. We record the screen video stream and the audio of the microphone.

Notifications: User gets a notification in the following scenarios- When she is invited in the session- When she is mentioned in the session (Session in flyby is a short-lived thread of discussion analogous to rooms in IRC).

ActiveTabs: User can create a session around a webpage or an untitled session (without associating to a webpage). We read the URL, title and meta tags (OG tags only) of the page from the active tab when a user decides to create a session around the webpage. (Session is a short-lived thread of discussion analogous to rooms in IRC)

Tabs:Flyby injects a popup in iframe in the host environment which is completely isolated from host. The iframe is injected so that it stays open unless user decides to close it. Once closed it will is closed from all the tabs.

We use tab API to determine in which tab the extension is opened. There could be multiple tabs where the extension is opened simultaneously. When the popup is closed then it's closed from all the tabs. Tabs API is needed to manage this above-mentioned communication

**Storage:**Storage is required to store public user identity, this is required because we provide a better experience when a browser is closed (cmd+q) and opened again

**User Identity:**We use identity only to open a login window where user can login using their existing google account using oauth2. We only use https://developer.chrome.com/apps/identity#method-launchWebAuthFlow method

Host Permissions: Permission: ":///*",We enable individuals to start a discussion around any webpage.

What data do we take from a user?

For the rest of the time we don’t take/track/store/extract any other information.