Skip to content
Quick actions
Ask a question
Announcements
About
Contributors

Privacy policy / Datenschutzerklärung

What data the PSA FAU Community Forum processes, why, and what your rights are.

Last updated

1. Who is responsible

The joint controllers under the EU General Data Protection Regulation (GDPR) for this forum are the two people who run it:

Mahad Khalid Tarar and Abdul Moeez

Our postal address will be added soon. Until then, contact us at psa.community.forum@gmail.com.

Email: psa.community.forum@gmail.com. We have not appointed a data protection officer; we are not required to.

2. In short

  • The PSA FAU Community Forum is a free, non-commercial community project run by volunteers.
  • You can read everything without an account. You only need one to post, vote or save threads.
  • We use your data only to run the forum. We do not sell it, show ads, or use analytics or tracking.
  • You can download all your data or delete your account at any time on your account page.

3. What we process and why

Visiting the site

Every time you open a page, our host Vercel processes technical data needed to deliver it: your IP address, date and time, the page requested, browser and operating system (user agent) and the referring page. Vercel keeps these in short-lived request logs that we use only to find errors and stop abuse. We do not combine them with your account.

Your account

Accounts are handled by Supabase Auth. When you sign in we store your email address, how you signed in (email link or Google), when the account was created and when you last signed in. Supabase keeps security logs of sign-ins that include your IP address. When you sign in with an email link, Supabase sends that email to you.

If you choose “Continue with Google”, Google tells Supabase your name, email address, your Google account ID and the link to your profile picture. We use only your name, as the starting value of your display name, which you can change. We never show your Google picture.

Bot check on the sign-in page

When you open the sign-in page, your browser loads Cloudflare Turnstile, which checks that you are a person and not a bot, usually without showing anything. For this Cloudflare processes your IP address, technical details of your browser and connection (user agent and TLS fingerprint) and which site the check is for. Turnstile does not see what you type into the form. Our form only receives a token, which it sends along with your sign-in request.

Your profile

Your display name, your @username, the optional affiliation badge you choose (for example student or graduate), your role (member, moderator or admin), your reputation points and the date you joined. These are shown publicly next to your posts and on your profile page.

What you post and do

  • Threads, comments and replies, including earlier versions of edited threads, which moderators review. Published posts are public, with your name.
  • Votes: the totals are public; who voted is visible only to you.
  • Bookmarks, followed threads and guide progress: visible only to you. If you ticked guide steps while signed out, they are copied to your account when you sign in.
  • Reports, update requests and moderator applications, with the reason or text you entered. Moderators see them so they can act on them.
  • Feedback you send with “Send feedback”: your message, your account and the page you sent it from.

Notifications

Notifications about replies, mentions, followed threads and moderation decisions, whether you have read them, and your notification settings (which types you muted and how often you want emails).

Moderation and abuse prevention

When moderators approve, reject or archive threads, hide comments, handle reports, or mute or ban an account, we keep a moderation log entry with who did it, to whom, and the reason. Restrictions on an account are stored with their reason. To limit spam, the forum counts how many posts, votes and reports an account made recently; this uses the posts themselves and stores nothing extra.

5. Service providers and recipients

We do not sell or share your data for marketing. These providers process data for us under data processing agreements, or independently where noted:

Supabase (database and sign-in)

Supabase Pte. Ltd., 65 Chulia Street #38-02/03, OCBC Centre, Singapore 049513. Our database and accounts are stored on Amazon Web Services in London, United Kingdom (region eu-west-2). The EU has recognised the UK as providing adequate data protection (adequacy decision under Art. 45 GDPR). Where Supabase staff or sub-processors outside the EU or UK access data, the EU Standard Contractual Clauses in Supabase’s data processing agreement apply. Supabase privacy policy.

Vercel (hosting)

Vercel Inc., 440 N Barranca Ave #4133, Covina, CA 91723, USA. Vercel runs our server code in London (region lhr1) and delivers pages through its global content delivery network, so a request may be answered by the server nearest to you. Vercel states that it is certified under the EU-US Data Privacy Framework (Art. 45 GDPR); its data processing agreement also includes the EU Standard Contractual Clauses. Vercel privacy policy.

Cloudflare (bot check on the sign-in page)

Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA. Cloudflare runs the bot check for us. It also uses the same data as its own controller to improve its bot detection, and states that the purpose is not to identify, profile or target individuals. Cloudflare states that it is certified under the EU-US Data Privacy Framework (Art. 45 GDPR); its data processing agreement also includes the EU Standard Contractual Clauses. Cloudflare privacy policy and Turnstile privacy addendum.

Backblaze (backups)

Backblaze, Inc., 2261 Market Street STE 81006, San Francisco, CA 94114, USA. Backblaze stores our encrypted database backups in a private bucket in Amsterdam, Netherlands (region EU Central). It cannot read them, because they are encrypted before they are uploaded. Backblaze states that it is certified under the EU-US Data Privacy Framework (Art. 45 GDPR); its data processing agreement also includes the EU Standard Contractual Clauses. Backblaze privacy policy.

Google (only if you choose “Continue with Google”)

If you sign in with Google, you are sent to Google, which learns that you are signing in to this forum and then passes your name, email and profile picture link to Supabase. Google processes this as its own controller under its privacy policy. Signing in with an email link involves no Google service.

GitHub (Contributors page)

The Contributors page shows the public GitHub profiles of people who contributed code. Our server fetches that list from GitHub; it sends no data about you. When you open the page, your browser loads the profile pictures directly from GitHub, which then sees your IP address and browser, as described in the GitHub privacy statement. No other page loads anything from GitHub.

Moderators and authorities

Volunteer moderators see reports, update requests, applications, feedback and the moderation log so they can look after the forum. We disclose data to authorities only where the law obliges us to.

6. Cookies and local storage

We only store what the forum needs to work or what you chose yourself. There are no analytics, tracking or advertising cookies. The only third-party script is Cloudflare’s bot check on the sign-in page (section 5), which protects sign-in. That is why there is no cookie banner: storage and access that are strictly necessary for a service you asked for need no consent (§ 25(2) no. 2 TDDDG). The font is served from our own domain.

  • sb-…-auth-tokenCookie

    Keeps you signed in. Set by Supabase Auth when you sign in; large sessions are split into .0, .1, … parts.

    Kept: Until you sign out, at most 400 days

  • sb-…-auth-token-code-verifierCookie

    Secures the sign-in link and Google sign-in against interception.

    Kept: Removed when sign-in completes

  • view_as_memberCookie

    Moderators only: remembers that they chose to see pages the way members see them.

    Kept: Until switched off, at most 1 year

  • export_atCookie

    Limits “Download my data” to one download every 10 minutes.

    Kept: 10 minutes

  • themeLocal storage

    Your light or dark mode choice.

    Kept: Until you clear your browser data

  • psa-announcements-seen-atLocal storage

    When you last saw the announcements, to mark new ones.

    Kept: Until you clear your browser data

  • psa-guide-progress:…Local storage

    Which guide steps you ticked while signed out.

    Kept: Until you clear your browser data

7. How long we keep data

  • Account and profile: until you delete your account.
  • When you delete your account, we immediately delete your sign-in data, profile, votes, bookmarks, followed threads, guide progress, notifications, notification settings, moderator applications, reputation and account restrictions. Your published threads and comments stay, so that answers others rely on and the replies to them still make sense, but they are no longer linked to you and show “Deleted user” instead of your name. Reports, update requests, feedback and moderation log entries are kept without the link to your account. If you also want posts removed, send us their links.
  • Feedback: until we have dealt with it.
  • Backups: we keep nightly encrypted copies of the database in a private Backblaze bucket in Amsterdam, 7 daily and 4 weekly copies. Data you delete can therefore remain in these backups for up to 4 weeks, until the copy holding it is replaced.
  • Server and sign-in logs: deleted automatically by Vercel and Supabase after their short retention periods.
  • Local storage: until you clear it in your browser.

8. Your rights

Under the GDPR you have the right to:

  • access the data we hold about you (Art. 15),
  • have incorrect data corrected (Art. 16),
  • have your data deleted (Art. 17),
  • restrict processing (Art. 18),
  • receive your data in a machine-readable format (Art. 20),
  • object at any time, on grounds relating to your situation, to processing based on legitimate interests (Art. 21).

Most of this you can do yourself on your account page: edit your profile, use “Download my data” for a copy of your data as a JSON file, or “Delete account”. For anything else, email psa.community.forum@gmail.com.

9. Right to complain

You can complain to any data protection supervisory authority, in particular the one where you live or work. The authority responsible for us is:

Bayerisches Landesamt für Datenschutzaufsicht (BayLDA)
Promenade 18, 91522 Ansbach, Germany
Postal address: Postfach 1349, 91504 Ansbach

Complaint form on lda.bayern.de

10. No automated decisions

We make no decisions about you based solely on automated processing, including profiling (Art. 22 GDPR). Automatic rate limits only pause posting for a short while; moderation decisions are made by people.

11. Changes to this policy

We update this policy when the forum or the services we use change. The date at the top shows the latest version.

12. Contact

Questions about your data: psa.community.forum@gmail.com. See also our Impressum.