UpStage v1


What data is collected?

UpStage servers collect network metadata as part of normal traffic processing. This is only used for debugging and usage statistics purposes. It is compressed and deleted over time, and only anonymized statistics are kept long-term.

UpStage identifies your browser, in order to determine if the Firefox configuration information needs to be displayed. This is not stored or connected to any other data.

If you register an account on an UpStage instance, you will be required to enter your email address. This is stored in the database and is only accessible to Admins of that UpStge instance. Passwords are encrypted using modern encryption algorithms.

Player / Audience Counter

The Player/Audience Counter shows how many players and audience are connected to a stage at the current moment. The counter is always visible in the top right corner of a stage. The number of logged in players on the stage is shown next to a person icon, and the number of connected devices in audience view is shown next to a screen icon.

Note that in many situations there can be more than one audience member at a device. For example two or three people may be watching together around a computer, or the stage may be projected in a physical location for a larger proximal audience. The counter simply shows the number of connected devices.

Hover your mouse over the counter and a dropdown will display the usernames of players and audience on the stage.

If you are a logged-in player, you can click on another player's name in this list to send them a message via the player chat.

The player/audience statistics are also shown in the Backstage, on the Stages list. This can be useful if you are working on multiple stages and want to see where your collaborators are, or if you are making changes to a stage that might disturb others on the stage.

When a stage is live, the player/audience counter also shows on that stage's image on the Foyer.

Il y a une erreur de communication avec le serveur Booktype. Nous ne savons pas actuellement où est le problème.

Vous devriez rafraîchir la page.