Legal
Privacy Notice
How Plekko processes personal data.
Effective: 9 September 2026 · Version: 1
Who is responsible for your data (the controller):
Arkstasis, a Dutch sole proprietorship trading as Plekko
Chamber of Commerce (KvK): 42057592 · VAT: NL005462594B13
Registered business address: Torenlaan 5, 1402 AT Bussum, the Netherlands
Privacy contact: privacy@plekko.eu
Content and moderation contact: dsa@plekko.eu
Supervisory authority: Autoriteit Persoonsgegevens, autoriteitpersoonsgegevens.nl
Data Protection Officer: not appointed. Under Article 37(1) GDPR a DPO is required where an organisation's core activities involve regular and systematic monitoring of people on a large scale, or large-scale processing of special categories of data. Plekko does not ask for or intentionally infer special-category data, and at its current scale its processing is not large-scale monitoring. We review this position as the service grows and will appoint a DPO if the threshold is met.
1. In short
Plekko is a small Dutch app for university students. We keep what we collect deliberately narrow: enough to run your account, your listings, your messages and your safety, and nothing beyond that.
- Your account, listings, photographs and messages are stored in the European Union, in Amazon Web Services' Frankfurt region (
eu-central-1). Limited data leaves the EU for push delivery, app updates, and only when you deliberately open a Google Maps route. Section 5 explains each flow. - We use no advertising trackers, behavioural analytics, session replay or third-party crash-reporting software. If the app catches a screen error, it sends Plekko a tightly limited stability signal; it does not send the error message, stack, user content or screenshot. There is nothing measuring what you look at.
- We do not ask for your date of birth, your precise location, your identity documents or any payment details. Plekko never handles money.
- We do not sell your data, and we never will.
- You can request a copy of everything we hold about you by emailing our privacy team from inside the app, or delete your account entirely in the app.
2. What we collect, why, and how long we keep it
| What | Examples | Why we process it | Legal basis | How long |
|---|---|---|---|---|
| Email address and university | The university email address you verify, and the university that its domain belongs to | To create your account, confirm you are eligible to use Plekko, and contact you about the service | Article 6(1)(b) — necessary to provide the service you signed up for | While your account exists; removed when you delete it |
| Sign-in data | Your account identifier, your password (stored only in hashed form by Amazon Cognito), and session tokens held on your own device | To sign you in and keep your account secure | Article 6(1)(b) — contract | While your account exists |
| Identity recovery evidence | A daily encrypted copy of account identifiers, verified email attributes, account status and university group membership. Passwords and sessions are never included | To recover account links and eligibility after a serious identity-service failure | Article 6(1)(f) — our legitimate interest, and users' interest, in service resilience | 35 days |
| Optional profile details | A first name, a username, study details, a profile photo | To let other students recognise you. These details are optional unless a feature clearly says otherwise | Article 6(1)(b) — contract | Until you change or remove it, or delete your account |
| Your city and coarse room area | A city name you type yourself, plus the four-digit postcode a host provides for a room listing. We resolve that postcode inside Plekko against a dated official PDOK/CBS snapshot and keep only its approximate area centre | To show relevant rooms and give an approximate comparison with an official university campus. We request no location permission, collect no GPS position and never ask for a full room address for this feature | Article 6(1)(b) — contract | While the related listing or request is active; afterwards only while needed for its conversations, safety handling or legal claims, or until account deletion |
| Room and marketplace listings | Titles, descriptions, prices, availability, area, condition | To publish what you are offering or looking for | Article 6(1)(b) — contract | While active. Withdrawn or archived records remain only while needed for related conversations, safety handling or legal claims, or until account deletion; no automatic 90-day deletion currently applies |
| Room-seeker profile | Your university-derived search city and chosen radius, monthly rent range, dates, room types, a housing-search introduction of up to 500 characters, and exactly two room-seeker profile photos | To publish your room request to hosts in the selected area. Your legal name, contact details, exact location and private fit answers are not shown | Article 6(1)(b) — contract | The request must be renewed after 30 days and expires earlier if your move-out date is sooner. A paused request is not published; request content is then deleted or retained only as stated for reports and decisions below |
| Photographs you upload | Photos attached to listings, your profile or a room-seeker profile | To show the relevant listing or profile after safety review | Article 6(1)(b) — contract | Until you delete the relevant content or your account, subject to the report and decision records below |
| Messages | The text of messages between you and another student, timestamps, read receipts, and the listing a conversation relates to | To let you contact each other about a room or an item | Article 6(1)(b) — contract | Each message is deleted automatically 180 days after it was sent. Later messages in the same conversation do not extend that period |
| Move-in checklist | Which tasks you have completed, and when | To keep your checklist between sessions | Article 6(1)(b) — contract | While your account exists |
| Study groups | Group name and purpose, sessions, who has been invited and who has joined, and an optional coordination link you add | To run the study-group feature | Article 6(1)(b) — contract | Groups have a 180-day active window. Group records are retained for 90 days after that window; session records are retained for 90 days after the session ends |
| Classmate directory (optional) | Your consent, first name, last initial, username and optional faculty or year, made searchable to verified students at your own university | To let classmates find you. This is off unless you switch it on | Article 6(1)(a) — your consent | Until you switch it off or delete your account |
| In-app notifications | What the notification is about and when you read it | To show your notifications list | Article 6(1)(b) — contract | 90 days |
| Push notification registration | A device token issued by Apple or Google, and which conversation a notification relates to | To deliver a notification when you receive a message. Only collected if you allow notifications | Article 6(1)(b) — contract | While your device stays registered; removed on expiry or account deletion |
| Security and service logs | IP address and request details at our service boundaries; route, status, timing and a one-way hash of your account identifier in application logs. If the app catches a screen error: error category, app/build version, operating-system family, coarse app area, time and a SHA-256 fingerprint. We do not receive the error message, stack, user content, screenshot, device identifier or location | To keep the service running, detect repeated app failures, investigate faults and detect abuse | Article 6(1)(f) — our legitimate interest, and users' interest, in a secure and working service | 90 days |
| Reports you make or receive, and report decisions | Who reported what, the reason and evidence supplied, the action taken and the reason for it | To assess reports about content or behaviour and communicate the outcome | Article 6(1)(f) — our legitimate interest, and other users' interest, in a safe platform; Article 6(1)(c) where a Digital Services Act statement of reasons is required | 180 days from the report |
| Room-request publication decisions | A pseudonymous content and owner reference, the automated or human checks applied, the outcome, timestamps and any policy reason. Raw introductions, photos and private fit answers are excluded | To apply our publication rules, demonstrate consistent safeguards and establish or defend legal claims | Article 6(1)(f) — our legitimate interest, and users' interest, in platform safety, accountability and legal claims | 6 years from the decision. This minimal evidence is held in compliance-locked storage and cannot be shortened for an individual record |
| Data-access request records and exports | A request identifier, status, timestamps and the secure export location | To fulfil and demonstrate your access request | Article 6(1)(c) — compliance with data-protection obligations | The request job record is kept for 1 year; the export and its download access expire after 7 days |
| Account-deletion audit records | A pseudonymous request identifier, timestamps and proof of completion. Deliberately no request free text or deleted content | To demonstrate that we completed the erasure process and to establish or defend legal claims | Article 6(1)(c) — compliance with data-protection obligations; Article 6(1)(f) — our legitimate interest in accountability and legal claims | 7 years from completion in compliance-locked storage; the record cannot be shortened individually during that period |
| Partner applicant account and application data | Organisation and contact details including a contact name, role, work email and optional phone number; application answers, declarations, registration references and supporting evidence | To create the separate organisation application account, assess the application, contact the applicant and prevent fraudulent submissions | Article 6(1)(b) — steps requested before a partnership agreement; Article 6(1)(f) — our legitimate interest in reviewing and securing applications | While the partner account or application relationship remains active. After it ends, only while needed to resolve review, complaint, fraud or legal-claim issues. Applicants may request deletion at privacy@plekko.eu |
| Strictly necessary partner-session cookies | plekko_partner_id and plekko_partner_refresh | To secure the organisation application sign-in and renew the requested session | Article 6(1)(b) — necessary to provide the partner application portal requested by the applicant | 1 hour for the sign-in cookie; 30 days for the refresh cookie, or earlier when revoked on sign-out |
Things we deliberately do not collect
We do not ask you to provide, and we do not intentionally infer, your date of birth, precise or GPS location, health data, biometric identity, political or religious views, sexual orientation, government identity documents, payment or bank details, browsing history, contacts, or activity in other apps or websites. Free-text messages and uploaded images can nevertheless contain information you choose to include. Please do not include sensitive information that is unnecessary for the conversation, listing or housing search.
Some information never reaches us at all. Your room preferences and shared-home comparison are calculated on your own device from preferences held in encrypted storage there; no score, comparison or pairing is sent to Plekko. If you connect the university planner, your classes live in a separate Plekko calendar in your phone's own calendar app — we read only that calendar, and event details, imported .ics files and calendar links are never sent to us.
Providing your data
A verified university email address is a condition of using Plekko. Without it an account cannot be completed and the service cannot be used. Your name, study details, general profile photo, city, notification permission and classmate-directory visibility are optional for using Plekko generally. Individual features can require the information needed to publish them: a room-seeker request, for example, requires exactly two approved photos, a housing-search introduction and the practical search details listed in the table above.
For a prospective organisation partner, the organisation identity, registration reference, authority declaration, contact name and role, work email, application answers and at least one supporting evidence file are required so Plekko can assess the application. A phone number is optional. Without the required information, the application cannot be submitted or reviewed.
3. Automated publication and safety checks
Every image uploaded to Plekko passes through an automated safety pipeline before it can be shown to anyone: a malware scan, removal of embedded metadata including any location data the camera recorded (EXIF), and automated content moderation. Images that fail are quarantined and are not included in a preview or published.
Room-seeker requests apply additional checks. Each of the exactly two room-seeker profile photos must contain one clear face and no other face; the check counts detectable faces but we do not identify or compare faces, infer identity or demographics, or create biometric templates. The introduction is checked for threats, abuse and housing-search relevance. Marketplace items above €30 receive a photo-to-description consistency check. Deterministic checks also validate required fields and permitted values.
These tools decide whether a draft is ready for publication; they do not make a legal or similarly significant decision about you. Ambiguous results can receive human review. If we restrict your content or account, we give you a statement of reasons and a way to challenge the decision — see our Terms, section 9.
4. Who else processes your data
We use a small number of service providers and platform operators. Amazon Web Services processes hosted application data on our instructions. Apple, Google and Expo also process technical data under their own terms where they provide app distribution, device notifications, update delivery or a route you deliberately open.
| Provider | What they do | Where |
|---|---|---|
| Amazon Web Services EMEA SARL | Hosting and storage — sign-in, databases, files, messaging infrastructure, email delivery, content delivery, keys and monitoring | Frankfurt (eu-central-1), with EU content-delivery locations |
| Apple Inc. | App Store distribution, and delivering push notifications to iPhones and iPads | United States |
| Google LLC | Google Play distribution, Android push notifications and, only after you tap Open directions, showing a route from the coarse postcode-area centre to an official campus | United States |
| 650 Industries, Inc. (Expo) | Building the app and delivering app updates | United States |
We do not share student personal data with advertisers, data brokers, analytics companies or partner organisations. If we ever introduce a feature that shares student data with a partner, we will ask for your explicit consent first, tell you exactly what would be shared and why, and update this notice before it starts.
Organisation application data is reviewed by Plekko for the applicant's requested partnership. Supporting evidence is private and is not published. If an application is approved, only the organisation content intended for publication — such as its name, website, deal or event details — may be shown to students. The applicant's private contact details and evidence are not shown to students.
We may disclose data where the law requires it — for example to comply with a valid order from a Dutch authority — or where we must report a suspected criminal offence involving a threat to someone's life or safety, as the Digital Services Act requires.
5. Data leaving the European Union
The data described in section 2 — your account, listings, photographs, messages, checklist, notifications and logs — is processed in AWS eu-central-1 in Frankfurt. Three flows leave the European Economic Area:
- when you enable notifications, your device token and the notification content are sent to Apple or Google in the United States so the notification can be delivered;
- app builds and updates are delivered through Expo in the United States, which processes technical delivery data including your IP address.
- when you deliberately tap Open directions on a room, the approximate postcode-area centre and the official campus coordinates are sent to Google Maps in the United States. We do not include your account identifier or a full address, and no route request is made before you tap.
These transfers rely on the EU–US Data Privacy Framework where the recipient is certified, and otherwise on the European Commission's Standard Contractual Clauses (Decision (EU) 2021/914) together with a documented transfer risk assessment. You can request a copy of the safeguards by emailing privacy@plekko.eu.
We use no advertising network, no analytics service, no font or script delivered from a third-party network, and no other integration that would send your data outside the EEA without it being stated here.
6. How long we keep things, and dormant accounts
The table in section 2 gives the period for each category. Two general rules apply on top of it.
If you delete your account, we remove your profile and personal details promptly, and a background process then deletes or anonymises the rest of your account data and files. Completion can take time. We keep only the minimal request, deletion and moderation evidence described in the table for its category-specific period so we can demonstrate compliance and establish or defend legal claims.
We keep your account and its data for as long as your account exists, because that is what the service needs in order to work. You can delete it yourself at any time from inside the app. We do not currently delete accounts automatically after a period of inactivity. If we introduce that, we will tell you before it starts and give you the chance to sign in first.
7. Your rights
You can exercise any of these free of charge. We reply within one month, as Article 12(3) GDPR requires.
| Right | How |
|---|---|
| See your data (Article 15) | In the app: Profile → Request my data → Email privacy team, or email privacy@plekko.eu directly. Sending the email does not start an export automatically. We identify the account from the request and confirm it through the university email address already stored on your account before starting the export. If you no longer control that address, we use a manual identity-verification process. The completed export is delivered through a time-limited secure download |
| Correct it (Article 16) | Edit your profile in the app, or email privacy@plekko.eu |
| Delete it (Article 17) | In the app: Profile → Edit profile → Delete account. If you cannot use the app, start a request from the deletion page on plekko.eu. The page opens an email to privacy@plekko.eu; sending that email does not delete the account. We look up the account independently and send confirmation to the university email address already stored on your account. Deletion begins only after successful confirmation. If you no longer control that address, we use a manual identity-verification process |
| Take it elsewhere (Article 20) | The same export as above |
| Restrict processing (Article 18) | Email privacy@plekko.eu |
| Object (Article 21) | Email privacy@plekko.eu. This applies to processing based on our legitimate interests — our security logs and our handling of reports. There is no marketing or analytics processing to object to |
| Withdraw consent (Article 7(3)) | Switch off the classmate directory in the app at any time. Withdrawing does not affect what we did while the consent was valid |
| Complain (Article 77) | To the Autoriteit Persoonsgegevens at autoriteitpersoonsgegevens.nl, or to the supervisory authority where you live. We would rather you told us first, but you do not have to |
Two limits worth knowing. Your data export contains your conversations as you already see them in the app: the other person appears under the display name you already see, and we do not add their email address, account identifier or any other detail about them, because Articles 15(4) and 20(4) GDPR do not allow us to hand over information in a way that harms someone else's rights. After you delete your account, the minimal request, deletion and moderation evidence in section 2 remains for its stated period.
Plekko makes no decisions about you by automated means alone that produce legal effects or similarly significantly affect you.
8. Security
| Measure | What we do |
|---|---|
| In transit | TLS 1.2 or higher everywhere; HSTS on the website; App Transport Security enforced in the app |
| At rest | Database and file storage encrypted |
| Access control | Private account data requires authorised access; our servers reject attempts to read another user's private data. Content you choose to publish is deliberately visible to its stated audience, while file storage and administrative access remain scoped and logged |
| Secrets | Held in a managed secrets service and rotated |
| Code | Automated dependency scanning and static analysis on every change |
| Images | Malware scan, metadata stripping and automated content moderation before publication |
| Backups | Point-in-time recovery and encrypted identity-recovery evidence for 35 days; file versioning with a controlled retention period; no password or session export |
| Testing | Security self-assessment against the OWASP mobile and application standards for version 1.0. An independent external test will be commissioned before we introduce any payment feature |
If a personal data breach is likely to result in a risk to people's rights and freedoms, we notify the Autoriteit Persoonsgegevens without undue delay and, where feasible, within 72 hours after becoming aware of it, as Article 33 GDPR requires. If it is likely to result in a high risk to you, we also tell you directly without undue delay, as Article 34 requires.
9. Young people
Plekko is for people aged 16 and over, and our Terms say so.
We want to be precise about what that means. We do not ask for your date of birth, and verifying a university email address does not verify your age — we do not claim otherwise. What it does do is limit Plekko to people who hold a mailbox at a participating university in the Netherlands, which in practice means our users are students rather than children.
If you believe we hold data about someone under 16, email privacy@plekko.eu and we will review and delete it promptly.
10. Cookies and storage on your device
In the app there are no cookies. We store sign-in tokens in your device's secure keychain, along with the key protecting a small cache of public listings. Your account preferences are held in encrypted storage on the device. Directory search results, notifications, profile data and study-group details are held in memory only. The app contains no behavioural analytics and sends no analytics events. Its bounded stability signal is used only when a screen error is caught, as described in section 2.
On plekko.eu the public pages set no analytics, advertising or tracking cookies, and load no third-party scripts, fonts or images — which is why you see no cookie banner. The signed-in partner application uses strictly necessary first-party cookies, listed in our Cookie Policy. We provide separate privacy information directly to authorised administrators at sign-in for the restricted internal administration area. The public account-deletion page has no student sign-in, sets no cookies and only opens an email request. We never ask you to send a password or verification code by email.
11. Language
Plekko is provided in English. This Privacy Notice, our Terms of Service and all communication about your account are in English, and English is the language of your agreement with us. For communications with regulators about content and moderation we also accept Dutch, as explained in our Imprint.
12. Changes to this notice
If we change how we handle your data in a way that matters, we will tell you in the app or by email before the change takes effect, and update the version and date at the top of this page. The current version is always at https://plekko.eu/en/legal/privacy.
13. Contact
Questions, requests or complaints about your data: privacy@plekko.eu
Reports about content, accounts or moderation: dsa@plekko.eu
Everything else: support@plekko.eu
Arkstasis, a Dutch sole proprietorship trading as Plekko. KvK 42057592. VAT NL005462594B13. Registered business address: Torenlaan 5, 1402 AT Bussum, the Netherlands.