RobCom Demo Privacy
What the RobCom demo stores and who can see it
Information used in the demo
Contact the person running the demo at support@robcom.org with questions or requests about your information.
The demo stores usernames, password hashes, profile details you add, team activity, messages, application answers and files you upload. Use fictional information and sample files. Leave personal documents and sensitive details out of the demo.
RobCom uses this information to run accounts, teams, chat and applications. It uses a sign-in cookie, records technical activity for troubleshooting and uses IP-based limits to reduce abuse.
RobCom tracks unread messages for your account. If you enable desktop alerts, your browser stores that preference and can show a generic reminder while a workspace tab is open.
When a super admin issues a password reset code, RobCom stores a hash of the code with the account and its expiry time until it is used or replaced, or an expired code is cleared.
Optional email updates
When newsletter sign-up is open, Buttondown receives the address you enter and handles confirmation, delivery and unsubscribe requests. The newsletter is optional and separate from RobCom accounts. You can unsubscribe from any update.
Who can see information
In the site, signed-in members can view visible member profiles. Team chats are available to current team members and direct chats to their participants, subject to blocking. A person with access to the server or database can also read stored messages and files.
Super admins can view profiles for account management and review applications. Event managers with an assigned publisher can review the team roster, individual answers and evidence submitted to competitions for that publisher.
Retention and requests
The demo keeps account content during testing. Contact support@robcom.org to ask what information is held about you or to request a correction or deletion.