RPG Con Assist
Sign In Register

Privacy Policy

I am striving to keep personal data collection to an absolute minimum. That is a guiding principle. If you see a place I'm asking for more information than I need, please tell me, and I'll work to remove that data request.

No data will be sold.

No personal data will be shared with unrelated third-parties. GM/BR reports are accessible to the convention HQ staff for submission to Paizo. The convention staff may maintain a copy of submitted reports for troubleshooting after the convention.

Aggregate usage data may be shared -- total number of reported games at a convention, total number of GMs reporting games; total number of unique players, etc.

This site uses cookies to implement some required site functionality. There are no tracking, marketing, or analytics cookies.

The site's processed data on three classes of people. A given person may fall into multiple categories with their use of the application at a single convention.

  1. Players are not end-users of the application, but your data will flow through the system.
    • Players' personal data (Organized Play Id, Character Number, and Character Name) is captured via the GM Report form to allow for reporting to Paizo. Any corrections requested later would need to flow through the event reporter and be inputed directly on Paizo.com.
    • Players' email address would be collected in the event that they win a prize (a boon, or a gift voucher) at the event. The event organizers need the email address for prize distribution. We reserve the right to use the table prize email addresses for an emailed announcement like 'The event coordinator has indicated they have processed all table prizes won; if you have not received your prize ...'.
  2. Game Masters (GMs) are end-users of the system, but do not require an account. They are the ones entering the player data described above, initially collected by any of a variety of their chosen sign-in forms. Those forms are out of scope of this policy. The should still retain their copy in case of player disputes of accuracy of information.
    • GMs' personal data (Organized Play Id, Character Number, and Character Name) is captured via the GM Report form to allow for reporting to Paizo. Any corrections requested later would need to flow through the event reporter and be inputed directly on Paizo.com.
    • GMs' email address would be collected in the event that they win a prize (a boon, or a gift voucher) at the event. The event organizers need the email address for prize distribution.
    • GMs' email address is collected on every GM report to allow us to send a confirmation email showing what we received from you. This is also used to allow event staff to contact you in the event of an error that makes your submission impossible to report to Paizo. We reserve the right to use the GM email address in the form submission process to send either/both of 'Your report has been submitted to Paizo' or 'All reports have been submitted; we're closing the reporting form' style announcements.
  3. Convention Organizers/HQ/Site Staff are the only users required to have an account.
    • Personal Data name and contact information. Our user form requests a name, username, and a contact email address. Name can be an alias, but it should be one that's recognized by the community. This email address will only be used by the site to send you administrative concerns (password confirmation, reset, etc)
    • We need per-event contact information from each organizer or HQ. This will likely include a required email address (which may be a mailing list that all event staff use), and may optionally include Discord aliases, etc. There may be 2-3 categories of email addresses required, some at a per-staff member level and some at an event level. For instance we need the following destinations (which may be the same):
      • Administrative Announcements pertaining to your event — 'Its been 30 days since your last session, we plan to archive/delete/anonymize GM and player data by XYZ if you don't take action.'
      • Player Inquiries — for providing players a mechanicsm to reach you
      • Reporting Correction Address — for GMs/players reporting an issue with the reporting
      We expect in most cases these will be a committee-wide shared mailing address, rather than personal addresses. These will likely be editable after an event has been generally archived, but we do not anticipate auto-erasing them.