Digital administration for FluConf.online is provided by cryptography.dog OÜ and is governed by their privacy policy, which will be briefly summarized below.
With the exception of Linode LLC., who qualify as a data sub-processor under the terms of the GDPR through their role as a server hosting provider, we do not share, sell, publish, or license any user/visitor/participant information with any third parties without written consent unless absolutely required by law.
We aim to collect only as much information as is useful for the purpose of organizing the event, and are committed to following adequate protocols for protecting whatever information is collected.
Furthermore, we will not use any submitted content for training so-called artificial intelligence or machine learning systems. More information regarding our stance on such technologies can be found in our AI use policy.
If you have any questions or concerns regarding privacy at FluConf, you may contact us by email:
Visitors to our site
Information about visitors to our site is governed according to cryptography.dog's general data collection policy. In short, this means no cookies or third-party tracking services are used, however, we do process internal web-server logs for a basic measure of how many visitors access our online resources.
Information collected from conference contributors
Additional information will be requested from potential contributors to the event. Such data will be treated according to cryptography.dog's extended data usage policy, with any personal information being retained only for as long as is necessary for its intended purpose.
We expect to display information about accepted proposals indefinitely, however, contributors are welcome to request that we remove or correct their details at any time in the future and for any reason. The details of rejected proposals will be deleted once the event's program has been finalized, however, we will retain a record of the number of proposals received, accepted, and rejected.
Proposals submitted for consideration as part of the official FluConf program will include details about the content and its author(s). Submission content will remain the authors' copyright, however, we will require permission to display it.
We may also ask for some personal information, some of which will be displayed on our site (authors' preferred name(s), pronouns, and biographical information), and some of which will be used only in aggregate for the purpose of evaluating how diverse of a community we have included (self-reported gender and age range, country of residence, etc.). Information that we expect to publish will be clearly labeled as such, and non-essential fields will include "prefer not to say" options.
Some of this information may be shared with those who have volunteered to assist with the event's organization. Such volunteers will be strictly screened to ensure participant safety, informed as to their responsibility for treating such information responsibly, and educated on practical measures they will be expected to apply for the purpose of safeguarding such information.
Participant privacy on services we do not operate
FluConf is being organized in a short timespan and on a minimal budget. For that reason, we will rely on some third-party resources to promote the event or communicate in real-time. While we are selective about which services we will encourage among participants, they will be operated according to their own privacy policies.
We currently moderate a real-time chat channel on the Libera Chat IRC network due to their very reasonable privacy policy. Likewise, we encourage audience participation via the fediverse.
Contributors to the conference might organize spinoff events, or invite participants to discussions on other online services. We encourage such community members to choose privacy-friendly, FOSS infrastructure, however, our ability to enforce such behaviour may be somewhat limited. Again, should you have any questions or concerns, you may reach us by email: