PiaarFind your people

Privacy policy

This is the formal version. The plain-English version of what we do and don't do lives on Responsible AI.

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

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.

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 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:

Information we generate

Information we do not collect

3. Why we collect it

Every piece of data has a specific purpose.

For each category of data, the legal basis is one of the following:

Two features need spelling out separately:

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:

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:

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.

7. Your rights

Under GDPR, you have the right to:

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

12. Contact

All privacy and general questions: privacy@piaartech.com

Postal: Fiholmsgatan, Västerås, Sweden — see Trader details on our contact page.