{% extends 'base.html' %} {% load i18n %} {% load bootstrap_tags %} {% load humanize %} {% block content %}

Privacy Policy

This service section is not ready yet; here is a draft of what it'll be:

We do store some user data. In this document, we explain what, why and how.

Convention/event attendee (app user)

What?

  1. Random device identifier
  2. All convention-provided events that got a star
  3. A count of how many stars were given
Emphasis: room parties are kept only in the device and are shared only through QRCodes and URLs.

Why?

Give the event organizers an estimate on how many people are going to attend each room and tell if attendees are using the app.

How?

On every database syncronization, the newest database is retrieved and the 3 informations listed in "What?" section are sent, identified by the unique name given in the conbook. For your own privacy, the app itself provides no way to see your random device identifier.

Convention/event organizers

What?

  1. Username, email and hashed password
  2. All the convention data that is shown in the app
  3. Payment status (paid/unpaid)

Why?

  1. Ensuring only authorized staff can change the data in attendee's app and password recovery
  2. Send the latest data for all devices anytime attendees' devices requests
  3. Billing

How?

  1. Tables in a PostgreSQL database
  2. A set of anonymous but timestamped records registered on every request that can, after the event, serve as a way to estimate how many users per event day is going to be charged. An empty list means no debt.

{% endblock content %}