Jitsi

jitsi.org
Jitsi

Encrypted, free and open source video calling app, which does not require creating an account/ providing any personal details. Available as a web app, and native app for Windows, MacOS, Linux, Android and iOS. You can use the public Jitsi instance, self-host your own, or use a community hosted instance.

Open Source

Jitsi Privacy Policy

Privacy Policy Summary

  • There is a date of the last update of the agreements
  • This service collects your IP address, which can be used to view your approximate location
  • The service provides a complaint mechanism for the handling of personal data
  • Your personal data is used for limited purposes
  • The service can delete your account without prior notice and without a reason
  • You maintain ownership of your data
  • Prohibits the posting of pornographic content
  • The service provider makes no warranty regarding uninterrupted, timely, secure or error-free service
  • This service throttles your use
  • This service does not condone any ideas contained in its user-generated contents
  • This service prohibits users sending chain letters, junk mail, spam or any unsolicited messages
  • They may stop providing the service at any time
  • You waive your right to a class action.
  • You have the right to leave this service at any time
  • Users agree not to use the service for illegal purposes
  • This service prohibits users from attempting to gain unauthorized access to other computer systems
  • If you offer suggestions to the service, they may use that without your approval or compensation, but they do not become the owner
  • Failure to enforce any provision of the Terms of Service does not constitute a waiver of such provision
  • Any liability on behalf of the service is only limited to USD $10
  • This service does not guarantee that it or the products obtained through it meet the users' expectations or requirements
  • Invalidity of any portion of the Terms of Service does not entail invalidity of its remainder
  • The service provides information about how they intend to use your personal data
  • The service provides details about what kinds of personal information they collect
  • The court of law governing the terms is in New York, USA.
  • The court of law governing the terms is in a jurisdiction that is less friendly to user privacy protection.
  • Your personal data is not sold
  • The service is provided 'as is' and to be used at the users' sole risk
  • This service is only available to users over a certain age
  • Business Users are solely responsible for claims made against the service and agree to indemnify and hold harmless the service.
  • The service may change its terms at any time, but the user will receive notification of the changes.
  • Third parties are involved in operating the service
  • The copyright license that users grant this service is limited to the parties that make up the service's broader platform.
  • The service allows you to use pseudonyms
  • This service assumes no liability for any losses or damages resulting from any matter relating to the service
  • User logs are deleted after a finite period of time

Score

B

Documents

Domains Covered by Policy

  • jitsi.org
  • meet.jit.si

About the Data

This data is kindly provided by tosdr.org. Read full report at: #2201

Jitsi Source Code

Author

jitsi

Description

Jitsi Meet - Secure, Simple and Scalable Video Conferences that you use as a standalone app or embed in your web application.

#debian#deep-video#jitsi#jitsi-meet#scalable-video-conferences#sfu#video#video-communication#video-conferencing#webrtc

Homepage

https://jitsi.org/meet

Repository

  • LicenseApache-2.0
  • Created16 Dec 13
  • Primary languageTypeScript
  • Size390,070 KB
  • Stars30,221
  • Forks8,128
  • Watchers30,221

Language Usage

Language Usage

Project Health

  • Last commit12 minutes ago
  • Open issues179
  • Latest releasevtesting1.2.3

Top Contributors

Recent Commits

  • Calinteodor(11 Nov 26)

    dep(@react-native-google-signin/google-signin): update to 12.2.1 (#18312) * Update dep version and generate the google-signin codegen spec and handle its sign-in URL directly.

  • Muskan Kumari(09 Nov 26)

    fix(settings): add accessibility label to native server URL input

  • Muskan Kumari(10 Nov 26)

    fix(authentication): add accessibility labels to native login inputs

  • Muskan Kumari(11 Nov 26)

    fix(calendar-sync): add accessibility role and label to native permission button

  • Hristo Terezov(10 Nov 26)

    test(lobby): check the pre-join join button through its enabled state The join button no longer carries a "disabled" class, so asserting that the class list does not contain it always passed and verified nothing. Checking the enabled state keeps the test meaningful for both the lobby screen and the pre-join screen.

  • Hristo Terezov(10 Nov 26)

    fix(prejoin): round the outer corners of the join options button The options button used to inherit its right-hand corner radius from the main button it was nested in. Now that the two are siblings in a plain wrapper there is nothing to inherit, so the corners resolved to zero and the hover background and focus outline stuck out past the rounded main button. Taking the radius from the theme directly restores the shape.

  • Hristo Terezov(10 Nov 26)

    fix(prejoin): keep Enter working on the join and options buttons The prejoin screen renders ActionButton inside a Popover, whose keypress handler calls preventDefault on Enter and Space. For a native button that cancels the click the browser would fire, so pressing Enter on "Join meeting" or on the options arrow did nothing after the buttons became native. Stopping the keypress at the button, the same way the chat message menu and reaction triggers do, lets the click go through.

  • Hristo Terezov(10 Nov 26)

    test(prejoin): assert the disabled join buttons via their native state The join button and its options arrow are now native buttons that use the disabled attribute, so they no longer carry a tabindex. The test checked tabindex="-1" and "0", which is why it failed; checking the enabled state verifies the same behaviour (both controls are out of the tab order while the name is missing and usable again afterwards) without depending on how it is implemented.

  • Hristo Terezov(06 Nov 26)

    fix(prejoin): make the join options arrow a sibling of the join button The options arrow on the pre-join screen was a role="button" div nested inside the "Join meeting" role="button" div. ARIA treats a button's children as presentational, so some screen readers flatten the pair into one control or hide the arrow and its expanded state entirely, which undoes the tab order and state fixes made for the same control. Render both as sibling native buttons inside a plain wrapper. Native buttons give the tab order, Enter/Space activation and the disabled state on their own, so the custom key handlers and the role/tabIndex props go away. The hover colour is driven from the wrapper so the whole control still highlights as one, and the visuals stay the same.

  • Hristo Terezov(10 Nov 26)

    test(large-video): treat an empty alt as a decorative stage avatar A decorative picture avatar has alt="" and no aria-hidden, so the helper returned "" instead of null and the decorative check timed out whenever participants had an avatar picture, for example from a token or settings.

  • Hristo Terezov(10 Nov 26)

    fix(large-video): keep the stage avatar in step with the name label for screen shares For a screen share participant the stage name label stays in the DOM while the toolbox is hidden, only faded out, and screen readers still read it. The avatar followed the visibility rule instead, so with a screen share on stage and no track yet the name was read twice each time the toolbox auto-hid, and the avatar flipped back to hidden when it showed. Both now share one selector for whether the label is rendered, so they cannot drift apart again.

  • Hristo Terezov(10 Nov 26)

    fix(avatar): resolve the announced name only for avatars that announce it Every connected Avatar (filmstrip, participants pane, chat, ...) ran the display name lookup on each store update, including a translation call for screen share participants, although only three call sites announce the name. Skipping it unless accessibilityAnnounceName is set keeps the cost on the few avatars that need it.

  • Hristo Terezov(10 Nov 26)

    fix(avatar): do not announce the default local name A local participant who has not typed a name yet is shown as "me", which does not identify anyone. Announcing it made the pre-join avatar say "me, image" before a name was entered, and did the same for a nameless local participant on the stage. Remote participants keep the default remote name, which is what everyone else in the meeting sees for them.

  • Hristo Terezov(10 Nov 26)

    test(large-video): check what the stage avatar announces Covers both sides of the rule so a later refactor cannot silently make the stage avatar decorative again or double up the name: a participant with display names hidden must get the remote name from the avatar, and one with the stage name badge visible must not.

  • Hristo Terezov(10 Nov 26)

    fix(large-video): keep the stage avatar decorative while the name badge is shown With display names on and tile view off, the stage already shows the participant's name as text in the name badge, so announcing it from the avatar too made screen readers read it twice. The avatar now announces the name only while the badge is hidden, which is exactly the case where nothing else on the stage identifies the person. The decision lives in a small connected component so it follows the badge as the layout or the display name settings change, instead of being frozen at render time.

  • Hristo Terezov(10 Nov 26)

    fix(avatar): announce the name the rest of the UI shows for a participant The announced name was the raw participant name, which is empty for someone who never set one and, for a virtual screen share participant, a copy of the owner's name taken when the share started. Screen readers therefore got nothing for a nameless person the badges and thumbnails call "Fellow Jitster", and a stale "Alice" instead of "Alice's screen". Resolving it through getParticipantDisplayName keeps the avatar in step with every other label, while the initials still come from the raw name.

  • Hristo Terezov(09 Nov 26)

    fix(avatar): announce the name on the large video and second screen avatars Since avatars became decorative by default (#18227), the two places where the avatar is the only thing identifying the person with the camera off went silent for screen readers: the large video stage and the single-participant second-screen window. Opt both in with accessibilityAnnounceName so they announce who is shown, the same way the pre-join preview does.

  • ravindra-RKB(11 Nov 26)

    test(iframe): add specs for setLocalSubject command (#18257) * test(iframe): add specs for localSubject command Signed-off-by: Ravindra <[email protected]> * test(iframe): drop the redundant redux subject wait The subjectChange event is emitted after the new subject is stored, so once p2 has it the header check alone shows that the local subject wins. --------- Signed-off-by: Ravindra <[email protected]> Co-authored-by: damencho <[email protected]>

  • Navya(11 Nov 26)

    fix(external-api): make iframe requests return the documented result (#18283) * fix(external-api): make iframe requests return the documented result * fix: made changes as per the review * fix(external-api): wait for prejoin before the iframe check and retry the join click

  • Navya(11 Nov 26)

    fix(external-api): reject on failure invite and captureLargeVideoScreenshot (#18296) * fix(external-api): return readable errors from invite and captureLargeVideoScreenshot * fix(external-api): reject invite and captureLargeVideoScreenshot on failure * refactor(external-api): share one transport error helper

  • damencho(10 Nov 26)

    fix(tests): wait for the file's chat message after the upload The file shows up in the file-sharing list as soon as its upload starts, but the chat message for it is added only when the upload reaches 100%. Reading the message right after the file appears can run before that, so poll for it instead.

  • Aarav Anand(10 Nov 26)

    fix(whiteboard): detect new collaboration session when roomKey changes in conference metadata

  • Aarav Anand(10 Nov 26)

    test(redux): add unit tests for ReducerRegistry and foundational base reducers (#18016)

  • Ravindra(07 Nov 26)

    test(iframe): add non-moderator authorization checks in avModeration spec Signed-off-by: Ravindra <[email protected]>

  • Jitendra Rewar(10 Nov 26)

    fix(virtual-background): preserve aspect ratio for custom background images (#18200) * fix(virtual-background): preserve aspect ratio for custom background images * fix(virtual-background): apply cover crop at draw time in stream effects * fix(virtual-background): scale down uploads without cropping and deduplicate cover crop drawing

  • Puneet Yadav(10 Nov 26)

    fix(shared-video): support YouTube Shorts URLs in shared video (#18277) * fix(shared-video): support YouTube Shorts and Live URLs * fix(shared-video): support YouTube Shorts URLs and add regression tests * refactor(shared-video): extract YouTube URL parsing to leaf module * docs(shared-video): restore JSDoc blocks and comments in youtube.ts

  • Navya(10 Nov 26)

    fix(external-api): restore toggleShareAudio and fix resizeLargeVideo and getParticipantsInfo (#18286) * fix(external-api): restore toggleShareAudio and fix resizeLargeVideo and getParticipantsInfo * fix: made changes as per the review * test(iframe): move the getParticipantsInfo and toggleShareAudio checks into participantsPresence Saves a separate grid session and conference join for these checks. --------- Co-authored-by: damencho <[email protected]>

  • Hristo Terezov(10 Nov 26)

    fix(participants-pane): give drawer-mode context menus an accessible name The participant, breakout room and moderation context menus never passed accessibilityLabel, so now that ContextMenu forwards it to its Drawer the narrow-screen dialogs for them would still be announced without a name. Name the per-participant menus after the participant (the first row they show), the room menu after the room, and the footer menu after the button that opens it.

  • Hristo Terezov(10 Nov 26)

    fix(participants-pane): name the lobby participant drawer The admit/reject drawer for a knocking participant is a role=dialog with no label, so screen readers announced an anonymous dialog. Name it after the participant it acts on, which is also the first row shown inside.

  • Hristo Terezov(10 Nov 26)

    fix(gifs): name the GIPHY drawer The GIF picker opens as a role=dialog Drawer on narrow screens without a label, so screen readers announced an anonymous dialog. Reuse the GIPHY title mobile already uses for the same screen.

Jitsi Security

5.6/10

Repo Security Summary

Updated 24 Aug 26

  • Security-Policy10/10
  • Code-Review10/10
  • Maintained10/10
  • Dangerous-Workflow10/10
  • CII-Best-Practices0/10
  • Token-Permissions0/10
  • Binary-Artifacts6/10
  • License10/10
  • Signed-Releases0/10
  • Branch-ProtectionN/A
  • Packaging10/10
  • Pinned-Dependencies3/10
  • Fuzzing0/10
  • SAST0/10

Security Advisories (5)

Jitsi Website

Website

Free Video Conferencing Software for Web & Mobile | Jitsi

Learn more about Jitsi, a free open-source video conferencing software for web & mobile. Make a call, launch on your own servers, integrate into your app, and more.

Redirects

Does not redirect

Security Checks

All 65 security checks passed

Server Details

  • IP Address172.64.154.22
  • LocationSan Francisco,California,United States of America,NA
  • ISPCloudFlare Inc.
  • ASNAS13335

Associated Countries

  • USUS
  • CACA

Safety Score

Website marked as safe

100%

Trackers

No known trackers found

Blacklist Check

jitsi.org was found on 0 blacklists

  • AntiSocial Blacklist
  • Artists Against 419
  • Badbitcoin
  • Bambenek Consulting
  • CERT Polska
  • CoinBlockerLists
  • CRDF
  • CryptoScamDB
  • EtherAddressLookup
  • EtherScamDB
  • Fake Website Buster
  • MetaMask EthPhishing
  • NABP Not Recommended Sites
  • OpenPhish
  • PetScams
  • PhishFeed
  • PhishFort
  • Phishing.Database
  • PhishStats
  • PhishTank
  • Phishunt
  • RPiList Not Serious
  • Scam.Directory
  • SecureReload Phishing List
  • Spam404
  • StopGunScams
  • Suspicious Hosting IP
  • ThreatFox
  • ThreatLog
  • TweetFeed
  • URLhaus
  • ViriBack C2 Tracker

Website Preview

Website preview

Jitsi Reviews

More Secure Conference Calls

  • Jami

    Jami

    jami.net

    A free and open source, distributed video, calling and screenshare platform with a focus on security. Jami is completely peer-to-peer, and has full end-to-end encryption with perfect forward secrecy for all communications, complying with the X.509 standard. Supported natively on Windows, macOS, iOS, GNU/Linux, Android and Android TV. Video quality is quite good, but very dependent on network speeds, some of the apps are lacking in features.

About the Data: Jitsi

Edit Jitsi Data

You can edit Jitsi's entry in this section of awesome-privacy.yml by submitting a PR to our GitHub repo.
Note that some of the information shown above has been aggregated from external sources, a list of these can be found data documentation.

Origin Data

Modify Data

API

You can access Jitsi's data programmatically via our API. Simply make a GET request to:

https://api.awesome-privacy.xyz/v1/services/jitsi

The REST API is free, no-auth and CORS-enabled. To learn more, view the API Docs or read the API Usage Guide.

Share Jitsi

Help your friends compare Secure Conference Calls, and pick privacy-respecting software and services.
Share Jitsi and Awesome Privacy with your network!