Privacy Policy for Coordinators
The Developer's Conference

Português

Privacy Policy and Data term of use for TDC Coordination
Version 2022/01.01 dated 21/12/2021

1. Introduction

This Privacy Policy and Data Term of Use refer to the collection, handling, disclosure and disposal, automatically or not, of registration data from participants named "TRACK COORDINATORS"; rules of use and access of data from third parties and participants, to which there will be access, besides their rights concerning such data in The Developer's Conference event environment.

Bidders to the title of "TRACK COORDINATORS" will be submitted to privacy policy and general data use terms, specific to each edition as of their interest submittal to the coordination title.

"TRACK COORDINATORS" holding participants receive such title after assessment and approval by The Developer's Conference technical committee and are entitled to this privacy policy and data term of use as of their holding moment to a specific edition.

This policy is valid to activities and services concerning The Developer's Conference for online or on-site editions carried on during 2022, as enrolled in the site, enrollment via Call4Trilhas application form, submittal to lectures by means of Call4Papers systems and access to the systems related to the event in the following domains and their sub-domains:

Personal data processing will follow the strict purposes regarding The Developer's Conference, and no further processing will take place as per such data that is out of the contexts provided herein.


2. On attainment personal and non-personal information

By submitting your proposal to enter the event tracks coordination, we request your personal information in order to fill out the event credentials, to access information regarding speakers selection and also for you to receive information on future upcoming editions.

Information required as per qualification:

COORDINATION
NAME requested
(mandatory)
CITY requested
(optional)
EMAIL requested
(mandatory)
STATE requested
(optional)
COMPANY requested
(optional)
COUNTRY requested
(optional)
ROLE/POSITION requested
(optional)
ETHNICITY requested
(optional)
PHONE NUMBER requested
(mandatory)
DISABLED PERSON requested
(optional)
PHOTO requested
(mandatory)
GENDER requested
(optional)

Additional information stored:


3. On the use of personal and non-personal information data attained

Name: Requested with the purpose of identifying participant's enrollment, prize draws and identification for interaction with partners and sponsors.

E-mail: Requested with the purpose of identifying participant's enrollment, prize draws and identification for interaction with partners and sponsors.

Company: Requested with the purpose of identifying the participant's enrollment and statistical analysis of the event coverage.

Role/Position: Requested with the purpose of identifying the participant's enrollment and statistical analysis of the event coverage.

Phone Number: Requested with the purpose of identifying the participant, for direct contacts on the issues related to charges and special activities of the profiles within the event and identification for interaction with partners and sponsors.

City: Requested with the purpose of identifying the participant's enrollment and statistical analysis of the event coverage.

State: Requested with the purpose of identifying the participant's enrollment and statistical analysis of the event coverage.

Country: Requested with the purpose of identifying the participant's enrollment and statistical analysis of the event coverage.

Ethnicity: In this version, data are a set and used to identify user. They are intended to promote the event coverage and diversity statistics view, following the event ideal of becoming more and more diverse. The platform is continuously improving so in future these data are anonymously logged.

Disabled person: In this version, data are a set and used to identify user. They are intended to promote the event coverage and diversity statistics view, following the event ideal of becoming more and more diverse. The platform is continuously improving so in future these data are anonymously logged.

Gender: In this version, data are a set and used to identify user. They are intended to promote the event coverage and diversity statistics view, following the event ideal of becoming more and more diverse. The platform is continuously improving so in future these data are anonymously logged.

Photo: Requested, based on the event contents tracks and other activities identification, pertaining the participant and fostering the participant presence as a member and content producer of the event.


4. Personal and non-personal information use

At any moment you can cancel the authorization for forwarding promotion emails and choose not to receive any other emails clicking on the link unsubscribing inserted in all emails forwarded by the event organization.

The only emails that are not enabled to prevent forwarding are the event operational emails, as enrollment confirmation, welcoming, and event information, researches, assessments and certificates, but all of the promotional emails can be canceled.

By taking part in the event, you can choose to share your information with any of the sponsors by means of your badge reading, button on the sponsor's virtual boot or accepting sharing your data with sponsors listed below at the moment of your enrollment, and mailing use term signed when sponsoring the event shall be followed.

Diamond Sponsors will be identified in the specific Privacy Policies and Data Use Terms of each event edition during 2022.

Sponsor's commitments and obligations:

All and any information granted directly by the sponsor without using platforms linked to TDC are not covered by this private policy and use of data. In this case, sponsor is its data controller.

Some of his/her data may be used to generate statistics in general and broadly, non-specific or identifiable, to assess future actions and improvements related to the growth guidelines and event management.


5. Access to Third parties' data

Concerning lectures selection

The person holder of "TRACK COORDINATOR" will be granted a series of third parties data, to which he/she will have access in exclusive period during the event, to which he/she holds the title and only related to the knowledge track to which he/she was selected as the coordinator person:

Such data comprises:

Access to such data is intended to assess and select submittal to compound knowledge track, and no type of contact is authorized between the "TRACK COORDINATOR" and the bidders and speakers out of the C4P platform environment before its approval and ratification as per his/her interest in taking part of the event edition.

The "TRACK COORDINATOR" holder is jointly responsible for secrecy and maintenance of data shared regarding biders and copy, reproduction or transference of any of those data is forbidden for any other bases out of the database in which they were made available.

Such co-responsibility will last for the period in which the "TRACK COORDINATOR" holder has access granted to The Developer's Conference CFP platform.

Regarding relationship with speakers approved

Phone data can be used to create communication lists in third parties apps (direct communication apps as WhatsApp, Telegram, Email). TDC responsibility goes as far as the lists created by our communication. Information relevant to the event development and management will be distributed by means of functions of "distribution lists" by such apps, and the "TRACK COORDINATOR’ holder will be responsible for not processing information relevant to the event development and management through free access groups and participants' data.

Participation, granting and access to third parties' data, occurred in communication groups environment, or communication lists, in third parties apps, which were not created by TDC organization is full responsibility of the group users and their administrators.

"TRACK COORDINATOR" holder can have access to speakers' data from the third parties’ apps (direct communication apps such as WhatsApp, Telegram, Email) and will be responsible for secrecy and maintenance of data shared as per the speakers and copy, reproduction, transference or use of such data is forbidden for any other purposes except the ones related to the event development and organization.

Such responsibility will last for the event accomplishment term to which the "TRACK COORDINATOR" holder was entitled, moment in which, communication lists in third parties’ apps, created by TDC will be concluded.


6. Storage Period

TDC is connected to its community during the whole year, bringing connections and knowledge to the whole technology development chain, besides boosting communities’ ecosystem.

Regarding this focus, participants' enrollment information are stored for the whole time while the account is active, keeping such connection for TDC information.


7. Users’ rights

TDC participants, regardless of their qualification, are the holders (natural people) of personal data, which personal data refer to, which will be collected by means of our enrollment channels.

TDC ensures transparency and control of personal data holders' access, in the terms described herein.

Personal data holder’s rights are the following:

1 - Right to request further information on his/her personal data that are not clear in this privacy policy and data use as per the holder's assessment;

2 - Right to request access to personal data collected and treated in this event edition;

3 - Right to request that his/her personal data are changed or updated when they are incorrect or incomplete;

4 - Right to request the removal of his/her personal data collected in this event edition, both from The Developer's Conference database and from his/her sponsors to whom the holder granted access. TDC is in charge of removing from all sites where the data is logged (Globalcode systems and sites mentioned herein) and for notifying Sponsors who have access that proceed with the removal. Personal data removal requests may imply in removing participant's data and background, including participation certificate, making it unfeasible to refer to the events enrollment and access to certain contents;

5 - Right to request that TDC interrupts the activity, temporarily or permanently, of processing all or some of his/her personal data;

6 - Right to request cancellation of his/her data use, general or specific, to one or more sponsors who have been given permission of use by TDC log. TDC is in charge of notifying Sponsors who have the data and they shall proceed with the exclusion as per the terms of use signed with TDC.

7 - Right to request a copy of his/her personal data in electronic format for personal use or transmission of such personal data to use in third parties' services.

All requests regarding users’ rights as per their personal data shall be performed by the email privacidade@thedevelopersconference.com.br TDC establishes up to 5-working-day term to reply on the request and notification of actions taken from the request.


8. On data security

Personal data collected are stored at The Developer's Conference database, using the latest version of security technologies on the market, and are mandatorily subject to the confidentiality terms and respect to your privacy as per this Privacy Policy and data use.

All data exchanges are encrypted, and are covered by monitoring tools, security policies, access controls to collaborators, with updated security software.

In case of noticing or awareness of any breach to own security or hosting companies ones, including invasions, data leakage or any other information security incident, we will notify national authorities, personal data holders, if affected, on such breach and will provide maximum details regarding the jeopardized data scope and extension within legal term.

It is nominated as The Developer's Conference Data Protection in Charge person Ana Abrantes, who can be contacted by the email privacidade@thedevelopersconference.com.br, or mail address (Rua Cunha Gago, 204 sala 5 Pinheiros, São Paulo - SP).


9. Validity and changes

This policy is valid for indefinite time and may be updated partially or on the whole by a new version according to the event edition.