Pluro

Privacy

Pluro uses Firebase Authentication for organizer sign-in and Cloud Firestore to save workshop data.

Your organizer account

Organizers sign in with Google through Firebase Authentication. Pluro saves the name and email address from your Google profile, your Firebase user ID, and your Organizer role to connect you with your workspace.

If you upload a profile photo, Pluro saves it to your organizer account. You can remove it from your profile.

What a request contains

A help request includes the name you enter, your table or location, any note you add, and the request’s status and timestamps. Your facilitator can see your request in the queue. Leave out passwords and other sensitive information.

If the organizer assigns a helper, that person can see your name, location and request note. You, the helper and the organizer can read messages and screenshots in the assigned chat. Reassigning the request opens a new conversation and removes the previous helper’s access.

You can also message the organizer privately. When you draw on a screenshot, your browser sends the marked copy and keeps the original file intact.

Optional AI tools

When an organizer generates a map from an image, the image is sent to OpenAI for analysis. When an organizer requests a suggested chat reply, Pluro sends the text of up to 30 recent messages from their direct conversation with that participant. To generate a help summary and identify recurring questions, an organizer can send the message text from all direct and assigned-help chats in the current workshop to OpenAI. These actions are optional. Generated maps and replies are drafts for the organizer to review before saving or sending, and chat insights are shown only to the organizer.

Pluro requests that OpenAI does not store the generated response. OpenAI may retain API data under its own data policies. Avoid including passwords or sensitive information in room images and chat messages.

Word Cloud responses

When you answer a Word Cloud prompt, your response text appears with the room’s results. The app uses your browser session to allow one answer per round. Leave out personal or sensitive information. Word Cloud responses clear when the organizer starts a new round or closes the room.

What stays in your browser

Pluro keeps a random participant ID in your browser’s site storage and uses a session cookie so you can see or cancel your own request after refreshing. Organizer sign-in uses a Firebase browser session and a separate HttpOnly server session cookie.

What clears after a workshop

When the organizer ends the workshop, the app clears its help requests, chats, screenshots and participant sessions. The organizer account and saved room map remain for the next workshop.

Workshop surveys

If the organizer offers a survey, you can respond within seven days in the same browser you used to join. The app keeps a browser-specific eligibility record for that workshop and keeps it for one extra day to confirm a saved response. This browser may also keep links to recent workshops so you can return to them.

Answering is optional. The organizer can see your answers and when you submitted them for 90 days after the workshop. Survey responses are stored separately from your help requests. Leave sensitive information out of your answers.