Privacy policy

PyBCN is a volunteer association. This page says what personal data this website involves, why we have it, who else sees it, and how to ask us to change or remove it. We wrote it to be read, so it is short. If something is not covered here, ask us.

Who is responsible

Associació Python Barcelona (CIF G67254045) is the data controller.

• Email: pybcn@googlegroups.com
• Registered address: pending. The association must add its registered address here before this page is published.

The Management Board handles requests about personal data. We have no data protection officer: the law does not require one for an association of our size and activity.

What data this site involves, and why

People pages

The site has pages for the people who organise our events, speak at them, mentor at workshops, or collaborate with the association. Each page shows a name, a photograph, a short biography, the role in PyBCN or at an event, and links to the person’s own profiles (GitHub, LinkedIn, Twitter, personal site).

• Where it comes from: the person. Each one sent the photograph and wrote or approved the text for publication here. Someone who did not want a photograph did not send one, and the page shows a silhouette instead.
• Why we have it: with the person’s consent (GDPR article 6.1.a). You can withdraw it at any time, and we remove the page. Withdrawing consent does not affect what was published before.
• How long we keep it: until the person asks us to remove it, or until we take the page down ourselves because it is out of date.
• One thing to know: the source of this site is a public Git repository on GitHub. When we remove a page, it disappears from the site and from the current version of the repository. The old text remains in the repository history, as with any Git project. Tell us if you also want it gone from there and we will work it out with you. Copies kept by search engines and web archives are outside our control.

Forms

A few pages link to or embed a Google Form:

• the membership form, to become a member of the association;
• the propose a talk form, for a talk at a PyBCN meetup;
• the PyLadies BCN call for proposals form;
• the call for proposals of each PyDay BCN edition (workshops and lightning talks), and the speaker, mentor, and attendee forms of some workshops.

Each form asks for what it needs to handle your request: usually your name, an email address to answer you, and the content of your proposal or your membership details.

• Where it goes: into a Google Forms spreadsheet in a Google account run by the association’s organizers. Google stores it under its own privacy policy.
• Why we have it: to do what you asked for, which is the membership agreement or the steps you take to propose a talk or join a workshop (GDPR article 6.1.b).
• Who sees it: the organizers of that event or working group.
• How long we keep it: responses to an event form are needed until the event is over and its programme is published. We have no automatic deletion after that. Ask us and we delete your response. Membership data stays in the member register for as long as you are a member; the law requires associations to keep that register and the related accounting records for some years after.

Membership payments

The membership fee is paid on PayPal’s site through a Subscribe button. PayPal tells us your name, your email address, and the amount paid. We never see your card or bank details. PayPal is a separate controller under its own privacy statement. We keep the payment record because the accounting and tax rules require it.

Email

Our contact addresses, such as pybcn@googlegroups.com and pyladies-bcn@googlegroups.com, are Google Groups. A message you send there is stored in the group and read by the organizers who are members of that group. We use it to answer you and to follow up on what you asked (GDPR article 6.1.b and 6.1.f). The thread stays in the group archive; ask us and we delete it.

Embedded Google content

A few pages embed a Google Form or a Google Calendar in a frame. The frame is served by Google: when the page loads, Google sees your IP address and browser details, and may set its own cookies inside the frame. Google’s privacy policy applies to that.

Cookies

This site sets no cookies of its own, and runs no analytics or tracking scripts. Your browser also loads a few images from unsplash.com (page headers) and paypalobjects.com (the PayPal button). Like any image host, those servers see your IP address and browser details.

Hosting

The site is served by GitHub Pages. GitHub may log the IP address and request details of each visit for security and operation, under the GitHub privacy statement. We do not see or receive those logs.

Who else sees your data

Nobody buys or receives your data from us. The companies named above see it because we use their services: Google (forms, calendar, mailing lists, documents), PayPal (payments), and GitHub (hosting and the source repository). All three are based in the USA. Each publishes the safeguards it applies to data from the EU, and we rely on those.

Your rights

You can ask us to:

• see the data we hold about you (access);
• correct it (rectification);
• delete it (erasure), including a whole people page;
• limit how we use it (restriction), or object to a use (objection);
• give it to you in a usable format (portability);
• withdraw your consent, for a people page or anything else.

To do so, write to pybcn@googlegroups.com. Say what you want and which page or form it concerns. For a people page, write from the email address or one of the profiles linked on the page, so we know it is you. The law gives us one month to answer. We do it by hand, as volunteers, so a few days is normal.

If you think we handle your data wrongly, you can complain to the Spanish data protection authority, the Agencia Española de Protección de Datos.

Changes to this policy

We may update this policy. Every change is visible in the history of this page on GitHub.

Last updated: 2026-10-07