Privacy

We do not and will not share your data to any 3rd parties, we just ask that you be civilised and respect other people that is our terms at szSocial.com and szSocial.xyz

We believe at szSocial in freedom of information and the freedom to post theories and conspiracies in the name of freedom and freedom of thought, we encourage knowledge sharing and in general the freedom of all information within reason and logic.

szSocial Media is an independent website owned and ran by a hosting and SEO expert who has a passion for knowledge and information that can help others.

We do monitor traffic patterns and usage statistics but not conversations or voice calls, video calls are checked if they are flagged by the anti-spam system. Also, we don't want anyone using our services for any kind of sexual communication activities. Anything else is ok we don't care.

For video.szsocial.xyz Read below:

Had a problem with someone coming to your live feed or live stream? Here is what may have happened and there are a few possibilities.

  1. You were using an easy to guess meeting name

  2. You had advertised your meeting in a public space and random people could view it or find it over the web.

  3. Someone from the circle of people you trusted decided to disrupt your meeting.

  4. is trickier but not impossible.

The simplest thing would be to make sure that you create a meeting name that is unique and hard to just guess. Using the randomly generated 4-word names you get on meet.jit.si is one way to do that. If you want more security just generate a UUID here:

https://www.uuidgenerator.net/ 64

Use that UUID for your meeting name.

Make sure that the meeting name is only known to the people who will be joining you on your panel and that it is not publicly available on the internet.

If your event is recurring you may also want to change the meeting venue every time you have it.

You can also set a password yourself when you join first.

For problem 3, you should start by figuring out who in your circle might have wanted to disrupt your meeting and simply not invite them in the following instances (which, as we agreed above you should keep private).

Also, remember you always keep full control of your YouTube Livestream. Make sure you keep a tab open there and stop the live stream (or make it private) the minute something wrong is happening.

 

Users are not required to enter any personal information and we cannot share what we do not have. In the event that users choose to enter their name or profile picture then they are not stored by the service but they are shared with the other participants on the call … because that is the point of entering them. Chats are being stored for the duration of the session then destroyed.

We do store things that we need in order to debug, maintain and develop the service. For example, we would store various performance characteristics. How much packet loss there was, how much available bandwidth, how much were we able to ramp up and essentially everything you see in chrome://webrtc-internals. Same goes for product analytics that helps us determine if and how often a particular feature is used.

There is plenty of work that needs to be done in order to make Jitsi a solid video experience and they and we need these stats in order to do it.

Again, in the event that users chose to enter an email or name, they never reach our analytics backends and we have no way of associating any analytics data with them.

URLs would also get stored as they allow us to map general performance patterns to specific webrtc time series. URLs are also how we advise partners to tag their conferences (e.g. homeschool-UIID) so that we can better plan resources for such usage.

This is also part of the reason why, by default, we suggest fully anonymous unique identifiers as conference names.

As far as a private instance goes: the collection of stats is not enabled by default. Components like nginx may log things like IP addresses and URLs to stop attacks and scanning from internet bots and hackers.

We hope this helps you understand our services better, remember we use open source software for our services, see below for information on what we use and which service it is, example: which domain.

 

video.szsocial.xyz  Open source software name and information ask Google: Jitsi meet self hosted

Requirements: VPS Server or Dedicated Server.

 

szsocial..xyz Open source software name and information ask Google: OSSN or OpenSource-SocialNetwork

 Requirements: VPS Server or Dedicated Server.

 

szSocial.com Open source software name and information ask Google: Matrix Riot

Requirements: Website Hosting or VPS Server or Dedicated Server.

 

szSocial.com szSocial.xyz and subdomains are managed by szSocial.com