2do — Privacy Policy (Working Draft)

Last updated: [DATE] · Applies to: 2do.net and its associated applications

This is a working draft, not a document ready to publish — the same status `/terms` already carries, for the same reason: it is built from real, specific product and hosting decisions (see below), so the language matches what is actually happening rather than generic boilerplate, but it has not been reviewed by qualified counsel and must be before it governs real users' data. Specifically, before publishing:

  1. Get it reviewed by counsel qualified in Polish/EU law, alongside `/terms`. A platform accepting registrations beyond one institution's own members, running active moderation, and offering federated sign-in has real obligations under GDPR and, for the notice-and-action/moderation side specifically, the EU Digital Services Act (DSA) that go beyond what is drafted here.
  2. Confirm this is reviewed and formally adopted by the hosting institution's own Data Protection Officer (IOD) before any real personal data is collected — see `SECURITY_AND_COMPLIANCE.md` §4.1 in this repository for the specific governance steps (RCPD registration, a DPIA) this deployment needs before go-live, not after.
  3. Fill in the retention periods marked [TBD] below with real, decided values — this draft states honestly that these are not yet decided rather than inventing plausible-sounding numbers.
  4. Confirm the named contact and DPO details in Section 12 — currently a placeholder pending the hosting institution's own decision.
  5. Have both this and the Polish version checked by a native-speaking legal reviewer, same requirement `/terms` already states for the same reason.

1. Who this policy covers, and who is responsible for your data

This policy describes how 2do ("the Platform," "we," "us," "our") collects, uses, and protects personal data when you use it. As of this draft, the Platform is hosted and administered by the Faculty of Physics, University of Warsaw (FUW) — see `federation-analysis.md` in this repository for why that is not necessarily permanent for every user: the intent is for FUW to be data controller primarily for FUW-affiliated users and for the platform's own operation, and for federated identity providers (Section 3 below) to remain responsible for the credentials they each vouch for, rather than FUW being sole custodian of everyone's data indefinitely.

If you signed in through your own institution, ORCID, or another identity provider, that provider is separately responsible for the account data it holds about you under its own privacy policy — this policy covers what 2do itself does with your data once you're using the Platform, not what your identity provider does on its own side.

2. What personal data we collect

  • Account and profile data: your display name, a system-generated handle, avatar, and any bio/location/external links you choose to add.
  • Content you author: Projects, Tasks, Problems, Needs, Plans, Comments, Posts, and any other Content type you create, edit, or interact with (reactions, votes on Polls, reviews you give or receive).
  • Credentials and verification records: attestations peer-issued to or by you (Section 6 of `/terms`), and any institutional-affiliation signal your chosen identity provider asserts at sign-in.
  • Moderation and audit history: Reports you file or that are filed against you, Tribunal poll participation, and moderation decisions — retained even after the underlying content is edited or removed, for the reasons `/terms` Section 8/10 already state (a coherent audit trail, appealability of decisions).
  • Financial/expense records, where you use that feature: amounts, categories, and approval status of Expenses you submit or approve.
  • Technical data: the essential cookies listed in the cookie preferences panel (open it from the banner shown on first visit, or any page footer), and ordinary server access logs once a real backend exists.

3. Federated sign-in — what happens when you "Continue with" a provider

2do offers signing in through your own institution (via the PIONIER/eduGAIN academic federation), ORCID, Google, or Microsoft, alongside a plain local account. This is a deliberate design choice, not just a convenience — see `federation-analysis.md` for the full reasoning — and it changes what 2do actually sees about you.

When you sign in this way, your chosen provider authenticates you and tells 2do who you are (typically a name and a stable identifier); 2do does not see, store, or have any way to recover your password with that provider. Your relationship with your identity provider, and any data it holds about your authentication, is governed by that provider's own privacy policy, not this one.

A local, 2do-managed email-and-password account remains available as a fallback for anyone without an institutional or commercial identity provider they're willing to use — for that account type only, 2do does directly store your email and a securely hashed password.

4. Why we process your data (lawful basis)

  • Account/profile data and the content you author: processed to perform the contract you enter into by creating an account (Article 6(1)(b) GDPR) — we cannot provide the service without it.
  • Moderation and audit records: processed under our legitimate interest in maintaining a safe, functioning platform and being able to explain and, where needed, defend a moderation decision (Article 6(1)(f)), balanced against your own rights — this is exactly the balancing a real DPIA (see `SECURITY_AND_COMPLIANCE.md` §4.1) needs to document formally, not just assert here.
  • Essential cookies: processed because they are strictly necessary to provide the service you asked for (exempt from consent under ePrivacy Article 5(3), and disclosed, not just assumed, in the cookie preferences panel).
  • Any future analytics or non-essential cookies: only ever processed with your freely-given consent, via that same panel — none are set today.

5. How long we keep your data

  • Account and profile data: for as long as your account is active, plus a reasonable period after closure to handle disputes or legal obligations — exact period: [TBD, pending the hosting institution's own records-retention policy].
  • Authored content: for as long as it remains on the Platform, per the license terms in `/terms` Section 5 — if you delete it, per that section's own terms.
  • Moderation and audit records: retained longer than the content they concern, since their whole purpose is remaining explicable after the fact — exact period: [TBD].
  • Data connected to an anonymized account (Section 8 below): identity fields are redacted immediately upon anonymization; the tombstoned content/comment rows themselves are retained per the two rules directly above, now correctly attributed to a redacted identity rather than your real one.

6. Who we share your data with

  • Your chosen identity provider, if you sign in federated (Section 3) — limited to the authentication handshake itself, not an ongoing data feed in either direction.
  • Other users, to the extent your own visibility settings and a Project's own membership rules make your content visible to them — the same visibility model `/terms` Section 2 already describes.
  • Moderators and, for a Tribunal vote specifically, the relevant moderator roster, when you are the subject of a Report — see `SECURITY_AND_COMPLIANCE.md` §3 for the open governance questions (due process, appeal rights) this specific mechanism still needs resolved before it should be treated as final.
  • Infrastructure/hosting providers acting as processors on our behalf (e.g. the servers the Platform runs on) — a full, named list of processors is a real requirement of a finished policy and does not exist yet as a settled decision, per this document's own disclaimer above.
  • We do not sell personal data, and do not share it with third parties for their own independent marketing purposes.

7. International data transfers

As of this draft, the Platform is hosted within Poland/the EU, and no transfer outside the EU/EEA occurs for data 2do itself stores. This may change if federated sign-in (Section 3) is extended to identity providers based outside the EU/EEA, or if `federation-analysis.md`'s own Phase 2 (data hosted by other, possibly non-EU, participating providers) is ever pursued — either would require a real Chapter V GDPR transfer mechanism (an adequacy decision or standard contractual clauses) to be put in place first, not assumed.

8. Your rights, and how to exercise them today

Under GDPR you have the right to access, correct, delete, or receive a portable copy of your personal data, and to object to certain processing. Several of these are already real, working features on this Platform, not something you need to submit a separate request for:

  • Right of access and portability (Articles 15, 20): open Settings → Account → "Export My Data" for a complete, structured JSON download of the personal data the Platform holds about you.
  • Right to rectification (Article 16): edit your profile fields directly from your own profile page; edit your account email/username/password (or see Section 3 above if you signed in federated) from Settings → Account.
  • Right to erasure (Article 17): Settings → Account → "Delete Account & Anonymize" permanently redacts your identifying information. Consistent with `/terms`' own Section 5 and Section 6 above, existing comments and authored content are not deleted outright — they remain attributed to an anonymized identity, so moderation history and other users' own conversations stay intact rather than breaking. If you want something closer to full deletion of specific content rather than account-level anonymization, contact us using Section 12 below.
  • Right to object and right to lodge a complaint: contact us (Section 12), or lodge a complaint with the Polish supervisory authority, the Urząd Ochrony Danych Osobowych (UODO), or your own EU member state's equivalent.

9. Cookies

What cookies this app sets, and why, are listed in full in the cookie preferences panel — open it from the banner shown on first visit, or from any page footer's "Manage preferences" link. Essential cookies (keeping you signed in, remembering your language) are always on, since the service cannot function without them; any non-essential category is off by default and only ever enabled with your explicit consent.

10. Children's data

Consistent with `/terms` Section 3, you must be at least 16 years old to create an account. GDPR Article 8 sets 16 as the default age of consent for information-society services, and Poland's own implementing legislation (the Act of 10 May 2018 on the Protection of Personal Data) has not lowered that default — confirm this remains current before publishing, and adjust per-country if the Platform ever operates on a legal basis reaching users outside Poland.

11. Security

We take reasonable technical and organizational measures to protect your data, consistent with GDPR Article 32 — see `SECURITY_AND_COMPLIANCE.md` in this repository for the specific requirements this deployment is being held to. As that document states plainly: as of this draft, no production backend exists yet, so there is no live system processing real user data to describe the protections of — this section will need a real, specific update once one does, not a generic assurance.

12. Contact and Data Protection Officer

Questions about this policy, or requests beyond what Section 8's self-service tools cover, can be directed to [contact email / registered address — pending the hosting institution's own decision]. As a public university, the hosting institution already has an appointed Data Protection Officer (Inspektor Ochrony Danych) under GDPR Article 37(1)(a); this deployment's own specific IOD contact channel is a real, near-term decision — see `SECURITY_AND_COMPLIANCE.md` §4.1 — not yet filled in here.

13. Changes to this policy

We may update this policy from time to time. Material changes will be announced via an in-app notice, the same mechanism this app already uses for other platform-wide disclosures, with reasonable advance notice before they take effect.

enpl