Last updated: 9 November 2026 · Version 2.22
1. Who we are
Piaar is operated by Saad Abdullah, PhD, trading as PiaarTech, based in Västerås, Sweden. PIAAR is a registered trademark of Saad Abdullah. For the purposes of GDPR, Saad Abdullah is the data controller for the personal data described in this policy. Contact details are at the bottom of this page.
If you're in the EU/EEA, your local data protection authority can hear complaints if you ever feel we've mishandled your data. In Sweden that's the Integritetsskyddsmyndigheten (IMY).
2. What we collect
Information you give us
- Account data — name, email, and a profile photo if you choose to add one. If you sign up with email, your password is stored only as a secure hash by our authentication provider (Firebase); we never see it.
- Sign-in through Google, Apple, or LinkedIn — if you choose to sign in with Google, Apple (on iOS), or LinkedIn, we receive your name and email address from that provider, plus a profile picture where the provider shares one. We never receive your password for those accounts, and we never post to them or read anything else from them. If you use Apple's "Hide My Email", we only ever see the private relay address Apple gives us.
- Profile data — bio, role, organization, workplace, the skills you offer and look for, custom skill proposals. Your workplace field is public, so it goes through the same automated content check as events and articles before it's shown to anyone else.
- Location — your coordinates, used to find matches near you. Precise location is off by default on new accounts. An account created before that became the default may already have it switched on, so it's worth checking the app's privacy settings, where you can turn it off at any time. Either way, other users only ever see an approximate area on your public profile — never your exact position.
- Location shared in chat — you can optionally share your live location with a connection inside a conversation, for example when you're meeting up. Each share is your explicit choice and applies only to that conversation. Each share is a one-time pin of your exact position, applies only to that conversation, and is shown as live for 30 minutes. Shortly after it expires, our server deletes the position from the conversation; the message stays, marked as expired. If the other person opened it in a maps app while it was live, that copy is outside Piaar.
- Communications — messages you send through the app, connection requests, support emails.
- Blocks and reports — if you block someone, we store that block so we can enforce it: you and the blocked person disappear from each other's search, map, and matches, and any conversation between you is deactivated. The other person is never told they were blocked. If you report someone, the report reaches us by email and is handled under our terms of service.
- Preferences — discoverability settings, search radius, notification toggles, and whether you're available for new connections. That last one is on unless you turn it off in Account › Network, including on an account that existed before the setting was added. While it's on, anyone who can open your profile sees an "Available for new connections" label on it; it doesn't appear in Discover, on the map, in search results, on your shared profile link, or in anything a recruiter sees. Turning it off removes the label and nothing else — it doesn't hide you, and it doesn't stop anyone contacting you. To stop appearing in Discover, turn off Discoverable instead (see Sharing, below).
- Event contact sharing — when you RSVP to an event, its organizer can already download lists that carry your name, headline and the skills you offer. Turning both contact switches off for an event takes you off those lists entirely, and so does leaving the RSVP; see Sharing, below, for who is listed. A row only ever carries the detail you are currently sharing — share your email address and not your phone number, and the phone column is empty. What is optional, and off unless you switch it on, is including your email address (and phone number, if we hold one) in the organizer's CRM export (see Sharing, below) — the only download that can ever carry your contact details. It's a separate choice for each event, and leaving the RSVP removes you from future exports. We record each decision in your consent log.
- Your agreement to our terms and privacy policy — when we make a significant change, the app asks you to agree to the new versions before you can carry on using it. We add a row to your consent log with the date and the version numbers you agreed to; earlier rows are never changed. If you'd rather not agree, you can sign out or delete your account.
- Event check-in — if an event uses in-app check-in, we record that you checked in, visible to that event's organizer as part of their attendance record.
Interests (optional)
Alongside the skills you offer and the skills you are looking for, you can add a short list of interests to your profile: things you enjoy outside work, such as hiking, board games or choir singing.
- Optional, and separate from your skills. You choose from a fixed list that we provide, up to 10. You cannot type your own, so free text cannot bring anything sensitive in. The list leaves out anything that would reveal religion or belief, health or disability, politics, trade-union membership, sex life or sexual orientation, or racial or ethnic origin.
- Who can see them. They sit on your profile and are as visible as the skills you offer. When you open someone else's profile you see which interests you share. Turning Discoverable off doesn't hide them from people who can already open your profile (see Sharing, below).
- What we use them for. In this version, only to seat people at an event whose organizer creates groups (see "Event groups," below). We do not use them to rank people in Discover or on Home, in job matching or job alerts, or in your searches, and a search record never holds them.
- Changing or removing them. You can edit or clear the list in your account at any time. Deleting your account deletes it.
Event groups
An organizer of an organization's event, who has been given this feature, can seat the people at the event in groups — for example one table per group at a dinner. In the app the organizer taps Create groups. It works only for people who tapped "I'm here" (check-in) at that event. Tapping "I'm here" records that you were there, and the organizer can already see who checked in. Check-in is a button you press — it does not check where your phone is. Here is what groups mean for you.
- What we use. To choose who sits with whom we use: the skills you offer; the skills you are looking for, but only when the organizer picks "Matched"; your interests, when the organizer picks "Shared interests"; whether your profile is discoverable; and your blocks. The organizer picks one of three modes. Shared interests seats people who share an interest or a skill together. Matched seats people who are looking for a skill near people who offer it, as far as the room allows. Mixed gives each table a variety.
- What we never use. Your languages, skills you typed in yourself, your location and your messages. Nothing that could reveal religion, health, politics, union membership, sexuality or ethnicity is used. We never seat you with someone you have blocked, or who has blocked you.
- What you get. One message from the event with your group number (the group number is the table number), and a "Your group" card on the event page. If you check in after the groups were sent, we place you in the best group that still has a seat, and we tell only you. Nobody else is moved.
- What the others in your group see. The other members, by name and profile when their profile is discoverable. A member whose profile is not discoverable appears only as "1 person going privately", with no name, photo or profile to open. If you are not discoverable, that is how you appear to them. A group can have a name such as "Hiking", built only from what at least two members with a discoverable profile offer or enjoy. The name never comes from what anyone is looking for, and no reason is shown for any one person.
- What the organizer sees. Every group, and every member's name, including members who are not discoverable. Your name is shown this way even if you are not discoverable, but only to the event's organizer. The organizer also sees your name and profile photo in the event's attendee list (see “What an event's organizer can do”, above). The organizer can already see who RSVP'd and who checked in (see Sharing, below), so groups add the group number next to a name. The organizer is given no reason for any one person's seat.
- No download. Groups are not part of any list an organizer can download. After the event the organizer's report keeps counts — how many groups, their sizes, how many late arrivals were placed, and how many connections were made inside groups — and, when 10 or more people were in groups, what each numbered group had in common, such as "Hiking", built only from what at least two members with a discoverable profile offer or enjoy. It never names anyone and never says who sat where.
- Deleted 7 days after the event. We delete the groups, the record of who sat where, the group number on your check-in, and the message with your group number 7 days after the event ends. We keep a frozen summary — the counts and what each group had in common, as described above — with the event after the groups themselves are gone, so the organizer's event report can still show it later. It never names anyone and never says who sat where. If you delete your account, your place in any group is removed straight away. As with other deleted data, a copy can survive in our providers' short recovery window (see "Deletion request handling" under Retention, below).
- Nothing important is decided about you. It is a seating plan. It does not decide whether you may attend.
- Your choices. You can leave the event, or not tap "I'm here". You can object at any time (see "Your rights," below): write to our privacy mailbox, or ask the organizer to pass your request on, and we will take you out of that event's groups. If you ask for a copy of your data, it includes your group, and the other members appear as placeholders because who they are is their data.
What you have to provide
To finish setting up an account you need a sign-in — an email address and a password, or Google, Apple or LinkedIn, which pass us your name and email — your agreement to our terms and privacy policy, confirmation that you're 18 or over, a name, a short bio, a location, and at least three skills you offer and three you're looking for. The location can be a city you search for, a point you tap on the map, or your current position; it doesn't have to be precise, and precise location stays off by default. You also have to answer the Discoverable and “Help improve Piaar” questions, though either answer is fine and both start switched off.
None of that is required by law. It's what the app needs in order to work, and if you don't provide it, setup can't be finished and the app can't be used. Everything else is optional: a photo, headline, work experience, workplace, category, profile link, interests, phone number, precise location, availability, “Open to opportunities”, sharing details with recruiters, and event contact sharing. The one thing the law requires us to collect is the invoice information behind a paid plan, which Swedish accounting law makes us keep (see Retention, below).
If you are a business customer
Separately from individual accounts, we hold records for organizations and individual customers who buy organizer plans, event promotion or event reporting:
- Organization details — organization name, the owner account, and any members invited to manage it.
- Workspace activity — a record of who in the workspace did what, for example invitations, permission and plan changes, members leaving, publishing, and opening, downloading or exporting reports.
- Billing contact — a name and email address, and a phone number if the customer chooses to give one. This is the only place a phone number is held anywhere in Piaar; the app never asks individual users for one.
- Commercial records — plan terms, entitlements, invoices and payment records.
Information we generate
- Match scores — computed from your skills against other users' skills; never stored as a permanent attribute, regenerated when inputs change.
- Activity signals — when you last opened the app, last updated your profile, accepted connections.
- Push notification token — a device token from Firebase Cloud Messaging, used to deliver the notifications listed under “Why we collect it”. You choose which ones you get in settings. The token is removed when you delete your account.
- Nearby-meet proximity signals (Bluetooth) — the app's Meet feature can help you find someone you've agreed to meet in a crowded place. It activates only when both people accept a meet request, uses Bluetooth signal strength to show a coarse sense of closeness ("far", "warmer", "very close"), and stops when the session ends. It shows no direction and no map position, we never derive or store your location from Bluetooth, and there is no background scanning — if you never use Meet, Bluetooth is never used.
- Device data — device type and OS version, app version, and your IP address, used for security purposes.
- Usage data (only if you turn it on) — if you switch on "Help improve Piaar", we record which screens you open, whether a search returned matches, and whether a meet actually happened. These events carry a random app-instance identifier, never your name, email, or account id. This is off until you switch it on, and switching it off deletes the identifier and stops collection immediately.
- Your Piaar code — a short random code (for example k3nf8a72) that stands in for your account in a shareable link. It is deliberately not your account id. Any signed-in Piaar user holding the link can open your public profile while your profile is discoverable. You can reset the code at any time, which immediately breaks every link you have already shared.
- Profile views — when you open someone's profile, they can see that you did, under “Who viewed your profile”: with your name, headline and photo if you're discoverable, or as an anonymous visit if you're not. The same applies when people open yours. A visit is recorded at most once per person per day, and never between people who have blocked each other.
- Search history — which skills you searched for and which profiles were shown to you as a result. We use this to run the matching service, and we also keep it for our own internal analytics and reporting on how people search and what the network surfaces for them. It isn't shared outside the company, sold, or used to advertise to you. See Retention, below, for how long it's kept.
Information we do not collect
- We don't track you across other apps or websites
- We don't import your contacts
- We don't record audio or use your microphone
- We don't use motion sensors
- We don't scan for Bluetooth devices in the background — proximity is used only during a meet session both people accepted
- We don't scrape public profiles from LinkedIn, GitHub, or anywhere else
- We don't use third-party advertising trackers
- We don't take photos or video — the camera is used only to read a Piaar code, the image is processed on your device, and nothing is stored or uploaded
3. Why we collect it
Every piece of data has a specific purpose.
- To help you finish signing up — if you create an account but don't finish setting up your profile, we send you up to two reminder emails: the first about 2 days after you signed up and the second about 10 days after you signed up. There is never a third, and we send none of them more than 30 days after you signed up. Each one carries an unsubscribe link that stops them for good, and it arrives with the same update that makes the second email possible. Finishing your profile or deleting your account also stops them, and you can object at any time (see "Your rights," below).
- To deliver invitations you send — if you invite someone by email who isn't on Piaar yet, we email them an invitation from Piaar with your name and a link to Piaar. We use their address only to send that email, and we don't store it.
- To match you with people — skills and location are the inputs to the matching engine
- To deliver the app — account data, device data, and activity signals are needed for the product to work
- To notify you — your push token lets us tell you about new messages, connection requests, meet requests, event reminders, organizer announcements, moderation decisions about your own content, important account or service notices, and (if you've opted in per the Recruiters section below) job alerts; every notification type can be turned off in settings
- To help you meet safely — chat location sharing and Bluetooth proximity exist only to help two people who chose to meet actually find each other
- To keep you safe — your IP address and security logs help us detect abuse and respond to attacks
- To respond to you — your support emails and in-app messages are stored so we can follow up
- To improve the product — if, and only if, you switch on "Help improve Piaar", pseudonymous usage events tell us which parts of Piaar work and which don't. Nothing here is used for advertising or sold
- To understand how the network is used — your search history (see "What we collect," above) feeds our own internal analytics and reporting on how people search and what Piaar surfaces for them. This runs regardless of the "Help improve Piaar" toggle, and is never used for advertising or sold
- To keep content safe — events, articles, event announcements, job posts, job-alert messages, and the "workplace" field on your profile are checked automatically before they're shown to anyone else, so that abusive or explicit content is caught early
- To show organizers what their event produced — attendance, connections made and the skills present in the room, so an organizer can see whether the networking actually worked. This reporting carries no contact details — your email address or phone number reaches an organizer only through the separate CRM export described under Sharing, and only if you switched on event contact sharing for that event
- To seat you with other people at an event — when you have checked in to an organization's event and its organizer creates groups, we use the skills you offer, the skills you are looking for, your interests and your blocks to choose your group (see "What we collect," above). Interests exist for this and for nothing else in this version
- To meet legal obligations — limited retention for tax, fraud, and statutory compliance
4. Legal basis under GDPR
For each category of data, the legal basis is one of the following:
- Consent — for optional features: discoverability, sharing your location in a chat, Bluetooth proximity during a meet session, sharing your contact details with an event organizer, and usage analytics ("Help improve Piaar"). Each of these is off until you turn it on, and you can withdraw consent in Account settings (or simply end the share/session, or leave the RSVP) at any time. Precise location is on the same consent basis and is off by default on new accounts; an older account may already have it on, and you can turn it off in Account settings at any time.
- Contract — for processing necessary to provide the service you signed up for (matching, messaging, account, notifications).
- Legitimate interest (Art 6(1)(f)) — for security, fraud prevention, keeping published content safe, keeping a record of who searched for what (see Retention, below), showing you who viewed your profile, letting an organization admit its own registrants through a registration code, sending the sign-up reminder emails, delivering the invitation emails you send to people who aren't on Piaar yet, and giving event organizers the banded per-attendee counts described under Sharing, used only to the extent it doesn't override your own rights and interests. Product improvement through usage analytics is not covered here — that runs on consent only, and nothing is collected until you switch it on.
- Legal obligation — for retention periods imposed by Swedish or EU law, including the seven-year retention of invoices and accounting records under bokföringslagen.
Two features need spelling out separately:
- Event groups, and the optional interests list that feeds them — seating you in a group at an event you checked in to rests on contract, because the seating is part of the event service you use when you RSVP to an organizer's event and tap "I'm here". Where that does not apply, we rely on legitimate interest — yours and the organizer's — in sitting with the right people at an event you chose to attend. You can object at any time (see "Your rights," below).
- What an organizer sees and can download about your RSVP — your name, your headline and the skills you offer rest on contract, as part of the service you request when you RSVP to an organizer's event. The banded per-attendee counts and the organizer's event totals rest on legitimate interest, as described above.
5. Sharing
Shared connections. When you open the profile of someone who is discoverable, Piaar shows the people in your own trusted network who are also connected to them. So if you're discoverable, people who open your profile may see which of their connections also know you.
We share your data with a short list of service providers (“processors”) that we use to run Piaar:
- Google Firebase / Google Cloud — authentication, database (Cloud Firestore), file storage, push notifications (Cloud Messaging), server functions, the matching service, App Check (which uses Play Integrity on Android and App Attest on iOS to confirm a request comes from our real app), and Remote Config. Our database runs in Google Cloud's eur3 multi-region and our server functions and matching service run in europe-west1 (Belgium) — both inside the EU. Push notifications, authentication infrastructure, App Check, and Remote Config are global Google services by design and aren't pinned to the EU. On iOS, notifications are delivered through Apple's Push Notification service (APNs).
- Google Cloud AI — text and images you publish are checked automatically by Cloud Natural Language and Cloud Vision before they appear publicly: events, articles, event announcements, job posts, job-alert messages, and the "workplace" field on your profile. Both are called through Google's EU endpoints. It runs only on that public content — never on your private one-to-one messages or your location.
- Google Analytics for Firebase — only if you switch on "Help improve Piaar". Receives usage events tied to a random app-instance identifier. Not linked to your account, and never used for advertising. This identifier is pseudonymous, not anonymous — it can persist across a sign-out and sign-in with a different account on the same device, so we don't call it anonymous.
- Sign-in providers — if you sign in with Google, Apple, or LinkedIn, that provider knows you use it to sign in to Piaar. Their own privacy policies govern what they do with that fact. We receive only your name, email, and (where offered) profile picture from them. If you sign in with LinkedIn and it shares a profile photo, that photo is loaded directly from LinkedIn's own servers rather than copied to ours, so opening your profile picture also sends a request to LinkedIn's content delivery network.
- OpenStreetMap — the map in the app loads tiles from OpenStreetMap's servers, and city lookups use its Nominatim service. Like any web request, those requests expose your device's IP address and the map area being viewed to OpenStreetMap. We never send them your name, account, or profile data.
- Email infrastructure — for transactional email — we send email through STRATO GmbH (Berlin, Germany), which also hosts this website. That covers sign-in emails (verification and password reset); invitations to events, connections and workspaces; plan and billing notices; the sign-up reminder emails described above; and invitations you send to people who aren't on Piaar yet.
Event organizers
An event organizer is not one of our processors — they are a separate controller of whatever they receive from us, and their own privacy policy governs what they do with it afterwards. Several things can reach them:
- Your contact details, in the CRM export. An organizer can download a HubSpot or Salesforce export of the people who RSVP'd to their event, with each person's name, headline and the skills they offer. Your email address and your phone number are each added only if you are currently sharing that particular detail for that specific event. Accepting our terms, or switching on usage analytics, never counts as that consent. Withdrawing it, or leaving the RSVP, stops you appearing in future exports — but we cannot recall an export the organizer has already downloaded.
- Event outcome reporting. Organizers see how their event performed: how many people attended, how many connections and skill-matches it produced, invitations sent, and the most common skills in the room. Their analysis export also lists each attendee's name, headline and skills with a banded count — 0, 1, 2 to 4, or 5 or more — of the connections that person made with other attendees of the event (the file's "Matches" column) and of the invitations they sent or received. In a small event, those bands can show who connected with whom. The exact figures appear only in a single "event total" row. There is also a "Boost taps" column, which is blank on every person's row: it carries only the event-wide number of taps on the organizer's own paid promotion of the event, and that figure appears in the event-total row alone. For a personal event, the person who created it can download it; for an organization's event, its owner can, and so can any team member the owner has allowed to. This analysis spreadsheet is a separate download from the CRM export above, and carries no email address, phone number or account identifier — the CRM export is the only download that can carry your contact details. Once an organizer has downloaded either file we cannot recall it.
- Who checked in. The organizer can see who tapped "I'm here" at their event, and when.
- Event groups. An organizer who has this feature can seat the people who checked in to an organization's event in groups, as described under "What we collect," above. The organizer sees every group and every member's name, including members who are not discoverable. Groups are not part of any download. The organizer's report afterwards keeps counts, and what each numbered group had in common, but never a name and never who sat where.
Who is on those two downloads. The CRM export and the analysis spreadsheet list exactly the same people. You are listed if you are sharing either your email address or your phone number for that event, or if your profile is discoverable and you have never made a choice about it. You are not listed if you have turned both off — whether you had switched one on earlier or turned them down the first time you were asked — if your profile is not discoverable and you are sharing neither, or if you leave the RSVP. The analysis spreadsheet has a totals row that says how many people are not listed, as a number with no names: for example "10 people are not listed (private profile or no consent to share)". At a small event, that number tells an organizer how many people opted out.
If you turn Discoverable off
Turning Discoverable off keeps you out of search, out of Discover and Home's matches, and out of profile links and QR codes — someone holding your Piaar link sees the same "This profile isn't available" they would get for a handle that never existed, so it doesn't reveal that you're there at all. It doesn't hide your profile from people who already have a way to reach it: your connections and favourites, anyone you have a connection request or a chat with (including a message request), a recruiter whose job you tapped "I'm interested" on, and anyone who can open a personal event you host yourself — an organization's event shows the organization instead. It also doesn't hide you from anyone who can open an event you are attending, because the event is stored together with its attendee list: see “Other people at an event” below. At an event you attend rather than host, the app doesn't put your name in the attendee list other attendees see — but whoever runs the event does see your name and profile photo there.
Other people at an event
In Piaar 1.5.3 and later, attendees who aren't discoverable are shown only as a count (“+3 people going privately”) — with one exception: the people you are connected with also see you on the event page in a “N from your network going” row, with your profile picture, or your initials if you haven't added a picture, and they can open your full profile from it, whether or not you are discoverable. Older versions of the app still show every attendee with name, photo, skills and match score. That is what the app displays, not what it stores. An event is stored together with the list of who is attending it, and anyone who can open the event can read that list and look up each person on it, which returns the profile we hold for them — as much as they have filled in, which for most accounts means name, photo, headline, bio, work experience, the skills they offer and seek, their city and an approximate area — whether or not they are discoverable. Anyone signed in to Piaar can open a public event; a private event can be opened by the people its host chose and by anyone who follows an invite link the host has turned on. So treat an RSVP as visible to other people using Piaar, even if Discoverable is off.
Registration codes
An organization can require a registration code to join one of its events — for example for people who registered or paid with the organization somewhere other than Piaar. When you enter a code, we check it against the codes the organization gave us and record that your account used it, so the same code can't be used twice. The organization sees which of its codes have been used and when and, as for any event you join, your name, headline and skills. We never receive your ticket or payment details. We do this so an organization can let its own registrants in (legitimate interest). Codes and the record of their use are deleted 30 days after the event ends.
What an event's organizer can do
If you join an event, whoever runs it sees your name and profile photo in the attendee list, even if you are not discoverable, and can remove you from the event. For an organization's event that means its owner and any member allowed to edit the event; for a personal event, the person who created it. This applies to every event, not only an organization's. If you're removed, we keep a record of that so you can't rejoin the same event, until 30 days after it ends. We don't store who removed you, and we don't send you a message about it. Revoking a registration code you joined with removes you in the same way.
Private events
When you create a private event, you choose who can see it: everyone you're connected with, including people you connect with later, or only the connections you pick. The people who can see it get a notification when the event is published, and again if they are added later, where the creator chose to send one. If you are removed from a private event, or you disconnect from its creator, you can no longer see it and your RSVP is removed. Apart from them, a private event isn't shown to other people — but if its host turns on an invite link or QR code for it, anyone signed in to Piaar who opens that link can see the event and join it, whether or not they're connected to the host. The link is off unless the host turns it on.
Organizers of public events
If you create a public event, anyone who opens it sees you as its organizer, with your name, photo and headline, even if Discoverable is off.
Recruiters
If you're Discoverable and switch on "Open to opportunities," you can see jobs a workspace posts and choose to act on them. Just being shown a job, or eligible for a job alert, does not share anything about you with the recruiter — our server checks eligibility against your coordinates and a recruiter composing an alert only ever sees a rounded count of how many people it reached, never who they are.
Tapping "I'm interested" on a job is different: it requires a separate standing consent, "Share details with recruiters" in Account settings, because it's what lets a recruiter see more of you. Once given, it covers every future job until you turn it off. From that point, the workspace owner can see your public profile (name, headline, category, city, photo, bio, and the skills you offer) and the match score you held at the moment you applied, and can download that alongside your email address in a spreadsheet export — but only while your standing consent is currently switched on. Your exact coordinates and phone number are never part of this. Turning off that consent, or withdrawing from a specific job, stops future sharing; it can't recall a profile or an export a recruiter has already seen or downloaded.
How a job match is worked out. Your score against a job is a count of how many of the job's skills you have, worked out by fixed rules from the skill names: a skill you both name counts in full, a catalogue alias counts a little less, a hand-curated synonym less again, averaged across the job's skills. No AI model is used for it, and the job page shows it as "X of Y skills". Job alerts stay limited while the recruiter features are under review. When one is sent, it reaches only people who have switched on "Open to opportunities", are inside the job's area, and have at least one of the job's skills — a recruiter can ask for a closer match than that, at 50, 60 or 70 percent. Only people who have switched that setting on have their skills checked for an alert at all. A job can list spoken languages, but they are never counted in your match and never used to decide who gets an alert. Every alert tells you why it reached you. When you tap "I'm interested", the score at that moment is saved with your application, and the organization can sort applications by it. Nothing on Piaar makes a decision about you with legal or similarly significant effect by automated means alone (GDPR Article 22): the organization decides, and you can ask us how a score was worked out.
We do not sell your data. Not to advertisers, not to data brokers, and not for money to recruiters either — but if you apply to a job, a recruiter does legitimately receive some of your data with your consent, exactly as described above. We'd rather be precise about that than imply recruiters never see anything about you. If Piaar is ever acquired, we intend that your data would only transfer to the buyer after you re-consent — that's a commitment about how we'd handle an acquisition, not something our systems can enforce on their own.
6. Retention
We keep data only as long as we need it for the purpose we collected it.
- Profile data — until you delete your account
- Message history — kept until you or the other person deletes their account; "clearing" a chat in the app only hides it on your device, it doesn't delete it
- Block records — until you unblock the person or delete your account
- Shared locations in chat — shown live for 30 minutes; the position is deleted from the conversation shortly after
- Meet (Bluetooth) sessions — deleted automatically shortly after the session expires
- Push notification tokens — kept until you delete your account. Signing out stops notifications to that device.
- Search history — which skills you searched and which profiles were shown to you, kept under a 90-day automatic-deletion policy
- Profile-view log — who viewed your profile and when, kept for 90 days and then deleted automatically. The total number of views on your profile is kept until you delete your account.
- Usage analytics — only if you switched "Help improve Piaar" on, kept for Google Analytics for Firebase's standard retention window. Switching it off deletes the app-instance identifier on your device and stops collection immediately
- Sign-up reminder record — that we sent you the reminder, and the address we sent it to, deleted 30 days after the last reminder we send you
- Your agreement to our terms and privacy policy — each row in your consent log is kept until you delete your account
- Event registration codes — the codes themselves and the record that your account used one, deleted 30 days after the event ends
- A removal from an event — the record that you were removed, kept so you can't rejoin, and deleted 30 days after the event ends, when the event is deleted, or when you delete your account
- Security and operational logs — most are kept for 30 days; Google Cloud's own audit logs are kept for 400 days
- This website's server logs — STRATO, our host, keeps a visitor's IP address for at most seven days, to spot and fend off attacks. The access logs we can see go back six weeks with the visitor's address already anonymised, and error logs five days
- Emails you send us — kept while we deal with your request and any follow-up, then deleted. An email exercising one of your rights is kept as the record that we handled it. The contact form on this site stores nothing itself: it opens your own mail app, so your message reaches us as an ordinary email
- Event contact sharing — your consent decision is kept while you hold the RSVP; contact details an organizer has already exported are held by that organizer under their own retention rules, not ours
- Interests — until you remove them or delete your account
- Event groups — deleted 7 days after the event ends: the groups, the record of who sat where, the group number on your check-in, and the message with your group number. If you delete your account, your place in any group is removed straight away. a frozen summary — the counts, and what each group had in common — is kept with the event after the groups are deleted, so the organizer's event report can still show it; it is deleted when the event is, and it never names anyone and never says who sat where
- What an organizer downloads about your RSVP — either file, the CRM export or the analysis spreadsheet, belongs to the organizer from the moment it is downloaded, and the organizer keeps it under their own rules. We cannot recall it
- Business customer records — invoices and related accounting records are kept for seven years, as Swedish accounting law (bokföringslagen) requires; organization and plan records are kept while the customer relationship is active; workspace activity records are kept for 2 years and then deleted automatically; a job report PDF is kept for 24 months and then deleted automatically
- Deletion request handling — deleting your account in the app takes effect straight away: your profile is removed from search and matches and your personal data is deleted. You're signed out on that device at once; any other device signed in to your account loses access within about an hour. Copies can remain in our cloud provider's recovery systems for up to 7 days, and in a backup for about three months. A few things intentionally continue to exist after deletion because they're someone else's record or a legal record: messages you sent remain in the other person's copy of a conversation (shown as from a deleted account), events belonging to an organization stay with that organization, and paid invoices are kept for seven years as described above. We also keep a short record that your account was deleted, and a workspace you belonged to keeps its activity record; both are linked to your former account id (see our deletion page). Email deletion requests are handled as described under “Your rights,” below.
7. Your rights
Under GDPR, you have the right to:
- Access the personal data we hold about you (data export)
- Correct inaccurate or incomplete data
- Delete your account and the data attached to it — see how deletion works
- Restrict processing for specific purposes
- Object to processing based on legitimate interest
- Portability — on request by email, we'll send you your data in a structured, machine-readable format
- Withdraw consent at any time, without affecting prior lawful processing
- Lodge a complaint with your local data protection authority
To exercise any of these, email privacy@piaartech.com. We respond within statutory windows: one month, extendable by up to two further months for complex requests.
8. Security
All app data lives in Google Firebase, which encrypts data in transit (TLS) and at rest. On top of that we use Firebase App Check to block unauthorized clients from talking to our backend, database security rules that are designed to restrict reads and writes to what a signed-in user should be allowed, password hashing handled by Firebase Authentication (we never store or see passwords), and access to production data limited to the operator. No system is 100% secure. If a breach happens, GDPR requires us to notify our supervisory authority (IMY) within 72 hours of becoming aware of it; if the breach is likely to put you at risk, we will also tell you directly — the law doesn't set a fixed deadline for that part, only "without undue delay."
9. International transfers
Your core data — account, profile, and messages — is processed within the EU: our database (Cloud Firestore) runs in Google Cloud's eur3 multi-region, and our server functions and matching service run in europe-west1 (Belgium). Some processing is not confined to the EU by default: services like push notifications, authentication, and Remote Config are global Google infrastructure by design, not something we can pin to the EU ourselves, while content moderation uses Google's EU endpoints (see Sharing, above). Google Cloud's operational logs, which include IP addresses and account ids, are also kept in Google's global location rather than pinned to the EU. Where your data reaches Google in the United States, we rely on the EU–US Data Privacy Framework: Google LLC is certified under it, and the European Commission's adequacy decision behind it (2023/1795) is in force. For transfers to any other country outside the EU/EEA, Google's Standard Contractual Clauses apply. You don't need to ask us for either — both are published, at cloud.google.com/terms/sccs/eu-c2p for Google Cloud and firebase.google.com/terms/firebase-sccs-eu-c2p for Firebase. STRATO, which hosts this website and sends our email, operates in Germany, so nothing there leaves the EU. If you sign in with Google, Apple, or LinkedIn, those providers process your sign-in under their own infrastructure and transfer safeguards.
10. Children
Piaar is not intended for users under 18. We don't knowingly collect data from anyone under that age. If you believe a child is using the service, contact privacy@piaartech.com and we will delete the account promptly.
11. Changes to this policy
This policy changes as Piaar changes, and this page is the record. The version number and "last updated" date at the top change with every revision, and every revision is listed in the change log below. When a change starts us collecting something new, or changes what we do with data we already hold, we publish it here with the date it takes effect, so you can read it before it applies. When we make a significant change to this policy, the app asks you to agree to it before you can carry on using Piaar, so you see the change rather than having to look for it. Smaller changes are published here with their date, so this page is still worth checking.
Change log
- 9 November 2026 — recorded that the sign-up reminder change took effect on 5 November 2026. The 5 November entry said only that it would take effect with the next server update, and so left standing that until then you would get at most one reminder with no unsubscribe link. Both have been in force since 5 November.
- 5 November 2026 — the sign-up reminder becomes up to two emails instead of one, the first about 2 days and the second about 10 days after you sign up, and every reminder carries an unsubscribe link that stops them for good. This page previously said we would send one and only one, ever; that is no longer true, and this entry is the record of the change. Both took effect on 5 November 2026. The record that we sent it is now deleted 30 days after the last reminder rather than 30 days after the single one.
- 5 November 2026 — corrected what the app shows about an attendee who isn't discoverable. The page said such attendees are shown only as a count; in fact the people you are connected with also see you on the event page, in a “N from your network going” row with your picture or initials that they can open your profile from, whether or not you are discoverable. This is how the app has behaved since 1.5.3, not a change.
- 3 November 2026 — described the screen that asks you to agree to a significant change before you can carry on using the app, and the row it adds to your consent log.
- 3 November 2026 — said plainly that an event is stored together with its attendee list, that anyone who can open the event can read it and look up the people on it, and what such a lookup returns. The page already warned that an attendee record is shared; the warning was written so that it could be read as applying only to older versions of the app, which it never did. The list of people who can still reach your profile when Discoverable is off now says that anyone who can open an event you attend is one of them.
- 2 November 2026 — described registration codes on an organization's events, and what an event's organizer can see and do: your name and photo in the attendee list even if you are not discoverable, and removal from the event.
- 2 November 2026 — corrected what a private event's invite link does. The page said nobody else could see or join a private event even with its link; in fact, when a host turns the link on, anyone signed in who opens it can join. Also restored the three-month backup figure, now that a backup schedule exists.
- 26 October 2026 — named the safeguards behind transfers outside the EU and where to read them, said what you have to provide to use Piaar and what happens if you don't, and gave retention periods for this website's server logs and for emails you send us.
- 26 October 2026 — described the "Available for new connections" setting, which is on unless you turn it off and shows a label on your profile to anyone who can open it.
- 25 October 2026 — said how a job match is worked out: by fixed rules over skill names, not by an AI model. Added that no decision with legal or similar effect is made by automated means alone, that languages listed on a job are never counted, and that only people open to opportunities have their skills checked for an alert.
- 20 October 2026 — said precise location is off by default on new accounts, instead of referring to "this release", which no longer identified anything a reader could check.
- 20 October 2026 — said what turning Discoverable off does and does not do. It keeps you out of search, Discover and profile links; it does not hide your profile from people who already have a way to reach it. The Interests section said the opposite and was wrong.
- 18 October 2026 — said who appears in the two downloads an organizer can take, now that both list the same people, and that the analysis spreadsheet says how many people are not listed. Turning off contact sharing, or turning it down when first asked, now takes you off both.
- 18 October 2026 — Piaar 1.5.3 shows attendees who aren't discoverable as a count rather than by name, so "Other people at an event" now says what each version of the app shows.
- 17 October 2026 — if you object to being seated in a group, we now say that we will take you out of that event's groups.
- 17 October 2026 — described private events, and the choice of who can see one. Interests and Event groups are now live in the app, so the 14 November date announced on 15 October has been removed and both are described in the present tense.
- 15 October 2026 — described how we publish changes to this policy, in place of an earlier promise to notify you in-app and by email 30 days ahead.
- 15 October 2026 — added Interests and Event groups, and described what an organizer can download about an RSVP.
All privacy and general questions: privacy@piaartech.com
Postal: Fiholmsgatan, Västerås, Sweden — see Trader details on our contact page.