Privacy Policy

This policy explains what personal data PyBlade (“we”, “us”) collects when you use this website and its subdomains — the feedback portal, PyBlade accounts and waitlists — what we do with it, and what you can ask of us. The short version: we collect what the services need to work and what helps us improve them, and we don't sell anything about you.

1. What we collect

When you create an account

• Your email address, your name, and your password — stored only as a one-way hash, which nobody can read back.
• When you accepted these terms and this policy.
• When you confirmed your email address. The six-digit codes we send for that, and for password resets, are stored as hashes too, and stop working after 30 minutes at most.
• If you sign in with Google or GitHub, what that provider shares with us: your name, your verified email address and the address of your profile picture. We never see your Google or GitHub password.

When you use the feedback portal

• The posts, comments and files you publish, with your name and profile picture next to them. These are public.
• Your votes on posts and likes on comments. A post's page shows the profile pictures of its latest voters, so a vote is visible to others too.

When you join a waitlist

• Your email address, the event you are waiting for, and when we wrote to you about it.

Technical data

• Like most websites, our servers may record requests — your IP address, the page asked for, your browser's user agent and the time — to keep the service running and to investigate abuse.
• Anyone who tries to sign in to the administration pages of the site has the username they tried, their IP address and their user agent recorded, so we can spot and block attacks.

2. Why we use it

• To run your account and the feedback portal — signing you in, showing what you post, counting votes. This is necessary to provide the service you asked for.
• To email you the codes your account needs, and the one message each waitlist you joined is about. Joining a waitlist is your consent to that message; you can take it back at any time.
• To keep the service secure and stop spam and attacks. This is in our legitimate interest, and yours.
• To decide what to build next, from what people post and vote for, and from how the site is used.

We don't use your data for advertising, and we don't sell or rent it to anyone.

3. Cookies

We use cookies, and similar storage in your browser, for two reasons:

• To make the site work — keeping you signed in across our subdomains, protecting forms from being submitted by other sites, and remembering preferences such as the light or dark theme. The site cannot work without these, so they are always on.
• To understand how the site is used — which pages are visited, how people arrive and how long they stay, measured with Google Analytics. This tells us what to improve; it is not used for advertising.

The first time you visit, we ask whether you allow the second kind; nothing measures your visit until you say yes. You can change your answer at any time with cookie settings, a link also found at the bottom of our pages.

You can also delete or block cookies in your browser's settings. Blocking the first kind will sign you out and stop some features from working.

4. Who else sees it

• Everyone can read what you publish on the feedback portal, with your name and picture.
• Google or GitHub, if you choose to sign in with them. Their own privacy policies apply to what happens on their side.
• Google Analytics, which measures visits for us. Google receives information about your visit, such as the pages you view, your browser and an approximate location derived from your IP address, and processes it under its own privacy policy.
• Google Fonts: our pages load their fonts from Google's servers, which see your IP address when they do.
• Service providers that host the site and deliver our emails, only as far as they need to do that for us.
• Authorities, when the law requires us to hand data over.

5. How long we keep it

• Your account and what you published: until you ask us to delete your account. Deletion starts 7 days after your request, so you can change your mind and cancel it in the meantime; your posts, comments and votes are deleted with the account.
• Waitlist entries: until the event has happened and we have written to you, or until you ask us to remove you.
• Confirmation and reset codes: they stop working after 30 minutes at most, and are kept only as hashes.
• Security records, including attempts to sign in to the administration pages: as long as they are useful for protecting the service.

6. Your rights

You can ask us to show you the personal data we hold about you, to correct it, to delete it, to send it to you in a portable format, or to stop using it for a given purpose. Write to the address at the bottom of this page, from the email address of your account if you have one, so we know the request is yours. We answer within a month.

A request to delete your account is carried out 7 days after we receive it. Those days are yours to cancel it, if the request was a mistake or you change your mind.

If you think we got something wrong, you can also complain to the data protection authority where you live.

7. Security

Passwords and codes are stored only as hashes, pages are served over HTTPS, and only the people who run PyBlade can reach the data behind the site. No system is perfectly secure; if something goes wrong that affects your data, we will tell you.

8. Children

Our services are not meant for anyone under 16, and we don't knowingly collect their data. If you believe a child has given us personal data, tell us and we will delete it.

9. Changes to this policy

When what we collect or how we use it changes, we update this page and the date at the top of it. If the change is significant, we will say so on the site, or by email if you have an account, before it applies.

The rules for using the site itself are in the terms of service.