Privacy notice
Last updated: 16 November 2026
Community Z attaches great importance to protecting your personal data. This privacy notice explains which data we process when you register, take part in an MDT trajectory and/or the FastForward trajectory, and use the platform, why we do so, on what legal basis, how long we keep it, who we may share it with, and which rights you have.
Who is responsible?
Community Z is the data controller for the data processed through your registration, the MDT trajectory, the FastForward trajectory and this platform. You can reach us as follows:
- Community Z
- Lulofsstraat 55, 2521 AL The Hague, Netherlands
- Chamber of Commerce (KvK) number: 89933907
- Email: info@communityz.nl
Who does this notice apply to?
This notice applies to everyone whose data we process through the platform and the associated trajectories: participating students, coaches, and contact persons at schools, clients and partner organisations (in their professional capacity).
Are you a coach? Then the privacy notice for coaches, tailored to that role, also applies to you.
Which data do we process?
Depending on where you are in the trajectory and which role you have, we process the following data:
From participating students
- Identity: your name and date of birth.
- Contact details: your email address.
- Gender: with the option not to share this.
- Intake data: your school and study programme, your motivation to take part, previous experience and education/employment status.
- Benefits situation: during registration we ask whether you receive benefits. This question is mandatory, but you can always indicate that you would rather not share it - this has no consequences for your participation and does not count towards the progress of your registration.
- Support situation: you can optionally indicate whether one of nine situations applies to you, for example that you have no basic qualification, that you are a status holder, or that you have had dealings with youth care. Two of those nine answers are a special category under the GDPR: 'I have a disability or a chronic condition' concerns your health (article 9) and 'I have been in detention' concerns a criminal record (article 10). That is why we ask for your separate, explicit consent for this one question, with its own checkbox that is never ticked in advance. If you do not tick it, we do not store your answer. You may also skip the question entirely. Both are fine, and neither has any consequence for your participation, nor does it count towards the progress of your registration.
- Development scan: your motivation, goals, challenges and coaching needs.
- Trajectory data: data about your participation in the MDT trajectory (Maatschappelijke Diensttijd / social service period) and/or the FastForward trajectory, including your progress.
- Account: your registration in the Community Z platform and app, your role, linked project and team, language preference and date of last sign-in.
- Content you create: submitted assignments and files, chat messages and reactions, project board cards (Kanban), feed posts and comments, and hackathon submissions.
- Attendance at sessions: whether you were there, the time at which you checked in, the number of minutes between the actual start and that time, and the outcome derived from it (present, late, very late or absent). See below, 'Attendance and arrival time'.
- Talent profile: skills, education level, LinkedIn URL, availability, employment status and profile photo if uploaded. By default your profile is visible to fellow students within the platform; employment status and availability are visible only to the Community Z team. You can change the visibility of your profile to fellow students yourself at any time in your settings.
- Gamification: awarded badges, badge progress, points and level - visible only to you and the Community Z team, with no ranking between students.
- Surveys: your survey answers are recorded under your name and are visible only to the Community Z team, not to your coach or fellow students.
- Recorded activity: which items you view, what you react to or comment on, which events you sign up for, what you submit and which steps you complete. We do NOT record your IP address, NO precise browser information and NO dwell time.
- Image material: photos and videos in which you are recognisably in view, taken during trajectories or events. We process this only if you have given separate consent for it.
- External contacts: if you approach organisations or professionals as part of your project assignment, you can record their contact details in the project environment (see below, ‘Contact details recorded by our students’).
- Feedback/support: if you submit a report through the feedback button, we record your report, the page you reported it from, limited device information, a screenshot of your own screen and your email address.
- Push notifications: if you opt in, your push subscription per device and your notification preferences.
- Technical: strictly necessary session data to keep you signed in.
- IP address at two moments: when you agree to this privacy statement and when you sign the sign-up form, we record the IP address it happened from. We do this solely to be able to demonstrate that the consent and the signature really took place. We do not use it to follow you and we do not link it to your behaviour on the platform. Only the Community Z team can see it, and you yourself in the download of your own data. How long we keep it is set out below under 'How long do we keep them?'.
Attendance and arrival time
If you check in at a session with the QR code, the platform records the time of that check-in and calculates how many whole minutes lie between the actual start of the check-in and your scan. Your attendance follows from that in four gradations: up to and including 10 minutes you are present, from 11 up to and including 30 minutes you are late, from 31 minutes you are very late. Absent is not determined by the clock, but established when the check-in closes, for everyone without a registration.
The measurement starts at the moment an administrator actually clicks 'Start check-in', and not at the time written in the programme. If a session itself starts a quarter of an hour later, you are simply on time if you check in within ten minutes of that actual start: a delay on the organisation's side is not counted against you. If your coach or a partner registers you manually, no time is measured and the minute count stays empty. A later correction never changes the measured minutes; only the scanning path records them.
Who sees this? You do, right after scanning. Your coach sees the outcome, the time and the number of minutes per participant in their check-in screen, and can add or correct a registration but not delete one. The Community Z team sees the same. In the room, the projector view deliberately shows only a counter and no breakdown by lateness, so that nobody is publicly singled out. A programme partner sees only counts per session by default, without names. Only when the Community Z team switches this on per project does that partner also see the outcome per name in the four gradations; the time and the number of minutes are not retrieved for that screen.
What we do not record here: your location or GPS, your departure time and how long you were present. To prevent one phone from checking in two accounts, your browser does store a randomly generated code; that is explicitly not a hardware identifier and not an IP address. Every manual registration and every correction is recorded separately, with the old and the new outcome, who carried it out and when.
From contact persons at schools, clients and partners
- Name, business email address, organisation and role.
- Invitation and account status.
- Proposals submitted by the partner including attachments, and shared/returned documents (which may contain personal data of signatories) with the accompanying messages.
Contact details recorded by our students
As part of their project, Community Z students sometimes approach organisations and professionals. When that happens, we record the contact details exchanged in the process (name, job title, organisation, contact details, source of the contact) in our project environment. This is done solely for the purpose of supervising the student project and is visible only to the student's own team and the Community Z team. We keep this data for up to 6 months after the project is completed; after that it is deleted automatically. Would you like to know which data we have recorded about you, or would you like us to delete it? Contact us at info@communityz.nl. If you have indicated that you would like to be kept informed by Community Z itself, we also use your data for that purpose with your consent.
What do we use it for?
We use your data for the following purposes:
- Registration and account: processing your registration and creating and managing your account.
- Contact and coaching: staying in touch with you, coaching you during the MDT and/or FastForward trajectory and tracking your progress.
- Platform functionality: making the project board, chat, community feed, events, certificates and talent network work.
- Participant registration and accountability: registering your participation and sharing your name, address details and telephone number with MDT (Maatschappelijke Diensttijd) for the purpose of the subsidy and the related accountability.
- Attendance and punctuality: establishing whether you were at a session and whether you were on time, so that we can coach you and account for participation in the trajectory towards your school or client. The outcome counts towards your progress and towards the points system with badges.
- Programme improvement: anonymised/aggregated insight into how the programme is used, in order to improve the trajectory and the platform, and to power the points-and-badges system.
- Image material: using photos and videos for Community Z's communications, only with your separate consent.
- Updates: sending you updates, news and invitations by email, only with your separate consent.
- Relationship management: maintaining the business relationship with schools, clients and partners.
What is the legal basis?
We process your data to carry out your application and your participation in the trajectory (performance of the agreement/application). For maintaining contact, your coaching and the operation of the platform, we additionally rely on our legitimate interest; we limit the processing to what is necessary.
For the use of image material, for sending email updates and for recording your support situation we ask for your separate, specific consent. For the support situation that consent is explicit, because special category data can be involved. You are never obliged to give any of these consents, and you can withdraw a consent you gave at any time without consequences for your participation. If you withdraw your consent for the support situation, we delete the answer you gave there.
The platform and the trajectory are intended for young people aged 16 and over. One of the questions can capture special categories of personal data: in the support situation you can indicate that you have a disability or a chronic condition (health data, article 9 GDPR) or that you have been in detention (criminal record data, article 10 GDPR). For data like that an ordinary legal basis is not enough. We therefore only process it on the basis of your explicit consent (article 9(2)(a) GDPR), which we ask for separately at that one question. If you do not give that consent, we do not keep the answer. Beyond this we process no special categories: we do not ask about your origin, your religion, your political views or your sex life. We handle both the benefits situation and the support situation with extra care, and sharing them is never mandatory.
Automated decision-making
We do not take decisions about you based solely on automated processing that produce legal effects concerning you or similarly significantly affect you (Article 22 GDPR). Concretely: no sanction is attached to a late status, the platform excludes nobody, assesses nobody and sends no message or e-mail about it. What does happen automatically is that the outcome counts towards your progress and towards your badges and points. An assessment of your work is always done by a person, by your coach.
How long do we keep it?
We do not keep your data longer than necessary for the purposes set out above:
- Programme and participant data: at least 2 years after the programme ends, partly for accountability towards MDT. At most 24 months after your last project finishes we make your account unidentifiable: name and e-mail address go, and the rest of your data is deleted. A daily task carries that out automatically.
- Accounts that have never been signed in to: 12 months after creation. An account you never started using does not stay in the system indefinitely.
- External contact details (recorded by students): up to 6 months after the project is completed; after that they are automatically removed from the platform.
- Documents with schools/clients/partners: for as long as the collaboration runs; signed contracts and official documents are kept until the statutory (tax) retention period has expired, also after the collaboration ends.
- Your email address for updates: for as long as you remain subscribed. You can unsubscribe at any time.
- Image material: for as long as needed for the communication purposes, unless you withdraw your consent.
- Attendance data (including arrival time and minutes): there is currently no fixed retention period and no job that clears them after a while. They do go along in one action with an erasure request: all your attendance registrations, arrival times and the code in your browser are then deleted.
- The IP address at your consent and at your signature: the IP address at the signature belongs to your sign-up form and goes with it in one move, both on a deletion request and when your account is made unidentifiable after the retention period. The IP address at your consent to this statement sits in the record of that consent; that record stays because otherwise we can no longer demonstrate that consent was asked for, but once your account is deleted it can no longer be traced back to you.
- Recorded activity data (who-did-what-when): 90 days by default, after which it is automatically deleted.
- Push notification subscription: for as long as it is active; it lapses as soon as you turn push off.
What we log about your activity
To give the Community Z team insight into the programme and to award points and badges, we record some of your actions on the platform.
- What we log: which items you view, what you comment on or react to, which events you sign up for, what you submit and which steps you complete - each time with who, which action, which item, and the timestamp, plus a coarse device category (mobile/desktop). We do NOT log your IP address, NO precise browser information, and NO dwell time. We use no external tracking services for this (such as Microsoft Clarity or comparable tools) - everything stays first-party.
- Why: solely to (1) give the Community Z team insight into the programme and (2) power the points-and-badges system. We do not sell this data and do not use it for selection or grading.
- How long: 90 days by default (configurable), after which it is automatically deleted.
- Who sees it: only the Community Z team. Coaches and other students cannot see your identifiable activity.
Push notifications
If you allow it, we can send you push notifications on your device (for example for new messages or deadlines). This only works after your own consent at device level and can be turned off at any time in your settings. The content of every notification is end-to-end encrypted, so the push service of your browser/operating system (such as Google or Apple) cannot read the content - it does see the moment of delivery.
In-app feedback and support
Through the feedback button in the app you can submit reports or ideas, optionally with a screenshot of your own screen. Your report and email address are recorded for follow-up in our issue system (GitHub, a US party with a valid data processing agreement); screenshots stay in our own, shielded storage and can only be opened through short-lived, secure links.
Who do we share it with?
We do not sell your data and do not share it with third parties for their own purposes. We do share data with the following recipients and processors, which act solely on our behalf or in coordination with us:
- Community Z team members: they process your data to handle your registration, your coaching and the trajectory.
- MDT (Maatschappelijke Diensttijd): we share your name, address details and telephone number for the purpose of the subsidy and the related accountability.
- HubSpot: our system for relationship management and e-mail communication. There is no technical connection between the platform and HubSpot; a Community Z team member enters data there by hand, and only where that is needed for the contact or the e-mail communication.
- GitHub: our issue tracker for the follow-up of in-app feedback and reports.
- Supabase (database, authentication and storage) - hosted in the EU.
- Vercel (application hosting).
- Resend (sending transactional emails, such as welcome and recovery emails).
- The push service of your own browser/operating system (such as Google or Apple), solely for the delivery of push notifications you turned on yourself.
- YouTube and Vimeo: some knowledge base articles show a video hosted by those services. When you open such an article, your browser fetches the video directly from YouTube or Vimeo, and that service sees the request. For YouTube we use the variant that only places a cookie once you actually play the video.
- External AI assistants, but only where the Community Z team creates a key for one: the platform has a protected interface a team member can use to give an assistant such as Claude or Codex access to platform data. Every key has an owner, a limited scope and an expiry date, can be revoked at any time, and every use is logged. Without such a key nothing goes that way.
- Programme partners: external organisations (schools, clients and delivery partners) that run a programme or project together with us. They get their own, walled-off environment in the platform and see only the participants of their own groups or programme. What exactly they get to see is set out below under 'What a programme partner sees about you'.
What a programme partner sees about you
A programme partner is an external organisation that runs a programme or project with us. Such an organisation never sees the whole platform: its access is tied to the groups or the programme it is linked to, and most of it sits behind a separate per-project switch that only the Community Z team can turn on. Those switches are off by default. Below is what a partner sees per part once a switch is on.
- Even with nothing switched on: the names of his own groups, the assignments running there, and the submissions of those groups. A submission means the content itself: the uploaded files, the link supplied with it and the note the student wrote alongside. He also sees the attendance records of his programme, but without any names attached.
- Group allocation on: he sees the names of the participants in his own groups and of the participants from his programme who are not in any group yet, and he can put someone in a group or take them out. Beyond your name and your group he gets nothing.
- Attendance on: your name appears next to the attendance records of his own groups, and he can add or correct a registration. The time and the number of minutes are not fetched for that screen.
- Assessment on: he can write feedback on those submissions, ask for a revision and set the status. With the switch off he may read the submissions but record nothing about them.
- Group chat on: he reads and writes in the project channel and in the channels of his own groups, including the messages that were already there. Conversations between two teams and private conversations stay out of his reach. On the messages in those channels he sees the name of whoever wrote them, for the same participants as in the group allocation: those in his own groups and those from his programme who are not in any group yet. He gets nothing more than your name.
- Contacts on: he sees the external contacts that students in his groups recorded in the project environment, with name, organisation, role, e-mail address, telephone number and the notes alongside, and he may correct those details.
- Workspace on: he sees the board of his own groups, so the cards and who is working on them, the team roles, the notes, the targets and the mindmaps. With the management switch on top of that, he may work in it himself.
- Hackathon on: he sees the submissions of the participating teams. Team names are visible then; the names of individual participants only where the Community Z team switches that on separately.
- Opportunities: if a partner organisation posts a vacancy, internship or side job, your name, the school you chose in your profile, your motivation and your CV go to that organisation as soon as you apply. That does not hang on a project switch but on your own choice to respond. If you withdraw your application, the reason you give goes to Community Z only.
- Events: if a partner organisation hosts an event and has access to the participants, it sees the name, e-mail address, signup status and the answers to that event's questions for everyone who signs up. If your talent profile is set to visible for the community, it also sees your headline and your study from it.
What a programme partner never gets to see: your intake form, your development scan, your 0 and 1 measurement, the surveys, your certificates, a letter of recommendation, your talent profile outside an event signup, and the community timeline. From the platform's participant register the system moreover hands him only your name, your group and your project; your e-mail address, your language preference and your onboarding progress stay out of it, even if he were to request them directly. If you sign up for an event of such an organisation, it does see your e-mail address: that is covered above.
Transfers to third countries
Some of our recipients and processors are based in the United States: Vercel, Resend, HubSpot, GitHub, YouTube and Vimeo, and the push service of your browser or operating system (Google or Apple). A recognised safeguard applies to all of them - a DPF certification (EU-US Data Privacy Framework) and/or Standard Contractual Clauses (SCCs/UK IDTA) - guaranteeing a level of protection comparable to that within the EU. Supabase, our main database and storage provider, runs entirely in the EU (Ireland region). If a team member gives an external AI assistant access through a key, where the data ends up depends on that assistant; Community Z makes that choice case by case.
How do we secure your data?
We take appropriate technical and organisational measures to protect your data against loss and unauthorised access. Access to personal data is limited to the people who need it for their work, data is transmitted encrypted, and the platform enforces strict separation between projects (row-level security), so users only ever see their own project. Files are held in private storage buckets, accessible only through short-lived, signed links.
Apart from the two moments above we record no IP addresses ourselves; your ordinary use of the platform is not linked to an IP address. When securing sign-in we do use your IP address briefly to count how many attempts were made, but we store it encrypted so that it can no longer be traced back. Our hosting provider (Vercel) separately keeps short-lived technical logs (including IP address), independent of our own database, to detect faults and prevent abuse.
Cookies
This platform uses strictly necessary cookies only. There are no analytics or tracking cookies. Specifically, we use:
- A Supabase session cookie to keep you signed in.
- A language cookie (NEXT_LOCALE) that remembers your preferred language. It is set when you arrive at an address without a language in it and we redirect you; if you switch language with the button, your choice sits in the address itself.
- A preference cookie (comz_sidebar_collapsed) that remembers whether you had the side menu collapsed.
- For partner contacts only: a cookie (comz_partner_project) that remembers which project you looked at last, for those who have more than one.
- For the Community Z team only: a cookie (cz_impersonate) that exists while a team member temporarily views the platform through a participant's eyes, for instance to follow up a report. This does not happen silently: a bar on screen says so at the time.
- For the Community Z team only: two cookies (onboarding_preview, wachtkamer_preview) that remember a team member opened a preview of the sign-up screen or the waiting room.
- For the Community Z team only: a preference cookie (comz_dashboard_layout) that remembers which dashboard layout a team member chose.
All of these cookies are functional: they make the service you asked for work, or remember a preference you set yourself. None of them is an analytics or tracking cookie and we do not use them to follow you across other websites. That is why no consent is required under the GDPR/ePrivacy rules and why we show no cookie banner.
Your rights
Under the GDPR you have the following rights regarding your personal data:
- Access to the data we process about you.
- Rectification of inaccurate data.
- Erasure (right to be forgotten).
- Objection to the processing.
- Withdrawing a consent you gave earlier, at any time and for the future.
- Restriction of the processing.
- Portability: a copy of your data in a readable format.
- Lodging a complaint with the Dutch Data Protection Authority (Autoriteit Persoonsgegevens).
How do you exercise your rights?
You can download your data and submit a deletion request via Settings → Data & privacy. You submit the request yourself; a Community Z team member carries it out. On deletion your profile is made unrecognisable and the rest of your data is genuinely removed: your account, your activity data, your badges and points and your personal files go, and anything attached to them goes with it. What deliberately remains is the record that you agreed to the privacy statement at the time, and to which version. That record can no longer be linked to you once your account is gone, and it stays because otherwise we could not demonstrate that consent was ever asked for. If you only want to withdraw consent you gave earlier, for image use or e-mail updates for instance, you can do that separately from a deletion request via info@communityz.nl. We respond as quickly as possible and within the statutory period at the latest.
Changes to this notice
We may update this privacy notice from time to time, for example when the trajectory, the platform or applicable laws change. You will always find the most recent version on this page, with the date of the latest change shown at the top. For each user we record which version of this notice applied at the moment of consent.
