oorja is built to be a privacy-focused product, and it
does not cannot pry on collaborating users.
- Whether it's terminal-streams or any other collaboration app, no content-data is stored on any server. By content-data we mean terminal-stream-text, chat-messages, diagrams, code or any data created among room-participants using the collaborative apps.
- Content-data is synced among participants using secure transports (TLS) when they are online in the room. Content-data is also end-to-end encrypted using 128-bit AES: oorja servers, and even trusted certficate authorities cannot read into it without the secret key. (kept is room's secret link's fragment). Only the room participants have the key.
- Collaborative apps store content-data on users personal devices (browser storage). It is not stored by any cloud service.
- Media comms (camera, mic, screen) are encrypted. However, not e2e due to current available browser technology.
- How you do you collect, store and secure user data ?The only sensitive info we collect is the user's email and profile from the provider they chose - Google/Github. The sign-in process is used as an authentication challenge (to prove you're not a robot), to ensure fair-use, or payment accounting if any. Your email is not visible to the room participants you collaborate with.
Data is stored within the US, and not shared with any third party. There are no ads or tracking on this website.
- How can users access, update or request the deletion of any personal data collected about them.You can email email@example.com.
- How are users are notified of updates to your policy ?While we don't see policy values changing, we're working on notifications so that users are up to date on any minute changes.
- Contact details, so that users can make enquiries about their data or submit a privacy complaintYou can email firstname.lastname@example.org