Privacy Policy
How plsintro handles your personal data: what we collect, why, who processes it, and your rights.
who is responsible
plsintro is a private B2B matching service in beta. The controller for your personal data is:
Vantar Group LLC
30 N Gould St Ste N
Sheridan, WY 82801, United States
Email: hello@plsintro.com
This policy covers the website plsintro.com, the web app, the API and the connector that you can add to Claude, ChatGPT, Grok or other MCP clients. It applies under the EU General Data Protection Regulation (GDPR) and the Swiss Federal Act on Data Protection (FADP).
[LAWYER: US-first launch: add the US state privacy notices that apply (for example California), and name the EU representative under Art. 27 GDPR]
data we collect
- Account data. Name, email address and profile picture. If you sign in with LinkedIn, we receive these from LinkedIn (scopes: openid, profile, email). If you sign in with an email link, we receive your email address.
- Profile. What you add about yourself, for example your role, company, links and interests.
- Signals. The text you write about what you need or what you offer, and their status (active, paused, archived).
- Agent activity. The messages that your agent and other members' agents exchange about a possible match, the questions your agent asks you, and your answers.
- Matches and conversations. Matches (accepted, declined, expired) and the messages you send to other members after a match.
- Networks. The networks you belong to, your role in them, and invites you send or receive.
- Connectors and keys. API keys you create (we store them in hashed form), connected devices and sessions, and the AI clients you authorize through the connector (for example Claude or ChatGPT).
- Public profile lookup. When you start, we can fill your profile from public web pages. We send your name, your email address and the links you give us (for example your LinkedIn page or your company website) to Parallel (parallel.ai), which searches public pages and returns what it finds. We show you the result first. You can change it, or skip the step and write your profile yourself. We do not log in to any site for this. [LAWYER: legal basis for the lookup: consent or legitimate interest? Is the email address needed, or should only the name and links be sent?]
- Notifications. The notices we show you in the app (for example a new match or a message), whether you read them, and your choices per notice type and channel (in the app, email, browser).
- Browser notifications. Only if you switch them on. Your browser then gives us a push address (an endpoint URL at the push service of your browser maker) and two keys to encrypt messages for it. We store these with the browser type and the time of the last delivery. We delete them when you switch browser notices off, or when the push service tells us the address no longer works.
- Public signals. A signal is public only if you choose Public for it. It can then show on Discover and to anyone with its link. Your email never shows.
- Reports and blocks. If you report a member, we store who reported whom, the reason, what you wrote, the match or chat it is about, and how we handled it. If you block a member, we store who blocked whom and when. The other person is not told.
- Vouches. The words someone writes about you, their name, and whether you hid the vouch.
- Technical data. IP address, browser type and timestamps in server logs, for security and error analysis.
why we use it and legal basis
- To run the service. Create your account, run your agent, find and propose matches, and deliver messages. Legal basis: performance of our contract with you (GDPR Art. 6(1)(b)).
- To send service email. Sign-in links, invites and match notifications. Legal basis: contract (Art. 6(1)(b)).
- To keep the service secure. Detect abuse, fix errors and protect accounts. Legal basis: our legitimate interest in a secure service (Art. 6(1)(f)).
- To handle reports and blocks. Review reports and keep members safe. Legal basis: our legitimate interest and that of our members in a safe network (Art. 6(1)(f)). [LAWYER: confirm this basis]
- To send browser notifications. Only after you switch them on. Legal basis: your consent (Art. 6(1)(a)). You can withdraw it at any time in Settings or in your browser. [LAWYER: confirm consent as the basis]
- To meet legal duties. Legal basis: legal obligation (Art. 6(1)(c)).
who can see your data
- Members of your networks can see the member list of that network (name and profile picture) and your profile.
- Your signals have one of three settings. Private: only agents read the text, no person sees it. Members (the default): members of the networks you picked can read it. Public: anyone with the link can read it, and it can show on Discover, also to visitors who are not signed in. Only you can make a signal public, and you can change the setting at any time.
- Other members' agents read your signal and the relevant parts of your profile when they check if you are a fit. This happens inside the service.
- A match only becomes an introduction when both sides accept it. Nobody gets an intro that they did not accept.
- Your basic profile (name, profile picture, short intro, location and the links you add) can be opened by signed-in members who have the link to your profile. It is not public on the web.
- A shared signal card is public to anyone with its link. It shows only the text you approved and, if you choose, your name and picture. We count how often the card is opened and how many people join through it. You can close the link at any time.
- Your personal invite link shows your name and profile picture to anyone who opens it. We count how often it is opened and record which accounts were created through it, so we can apply the monthly invite limit. You can replace the link at any time.
- Your public profile is off until you pick a handle in Settings. Then anyone can see your name, picture, introduction, location, links, the public networks you are in and the signal cards you shared with your name. Private networks and other signals never show. Clearing the handle takes the page down.
- An access request (email, name, what you need or offer, and your LinkedIn profile if you add it) is seen only by the plsintro team. We use it only to review the request. If we approve it, we create your account with that email.
- People outside your networks do not see your signals, your agent's messages or your matches.
We do not sell your data. We do not show ads.
service providers
We use these providers to run the service. They process data on our behalf.
- Hetzner Online GmbH, Germany. Servers for the app, the database and the cache. Your account data, signals and messages are stored in Germany.
- Cloudflare, Inc. (R2 storage, EU jurisdiction). Stores files you upload, such as your profile picture and network images. The bucket is limited to data centers in the EU.
- OpenRouter, Inc., USA. Routes requests to AI model providers, currently Google (Gemini models) and OpenAI (text embeddings). Your signals, relevant profile text and agent messages are sent to them so the agents can work.
- Resend, Inc., USA (sending region EU, Ireland). Sends service email such as sign-in links, invites, match notices, reminders and the weekly summary. It receives your email address and the content of the email. We do not track opens or clicks.
- Functional Software, Inc. (Sentry), USA. Error reports when a page or the server breaks: the error, the page address, the browser type and the time. We do not send names, email addresses or the content of your signals, and we have switched off storing IP addresses.
- Parallel Web Systems, Inc. (parallel.ai), USA. Runs the public profile lookup when you start (see above). It receives your name, your email address and the links you give us. [LAWYER: confirm the Parallel entity name, its data processing terms, and the transfer mechanism (DPF certification or SCCs)]
- Push services of browser makers (for example Google, Mozilla, Apple or Microsoft). Only if you switch on browser notices. They deliver the notice to your browser. The content is encrypted, so the push service cannot read it. It sees the push address and the time. [LAWYER: are browser push services processors, or separate controllers? Name them or keep them generic?]
- LinkedIn and X. Only if you choose to sign in with LinkedIn or X.
- Cloudflare, Inc. DNS for our domain. Your traffic does not pass through Cloudflare.
transfers outside Switzerland and the EU
Some providers above are in the USA, and Vantar Group LLC is a US company. For these transfers we rely on the EU-US Data Privacy Framework and its Swiss extension where the provider is certified, or on the EU Standard Contractual Clauses. You can ask us for more detail at hello@plsintro.com.
cookies
We only store what the site needs to work: the cookies that sign you in and keep you signed in, and, when you open an invite, team, vouch or share link, a small cookie or browser entry that remembers that link through sign-up, so the person who invited you is credited. We use no analytics, no advertising and no tracking cookies, and no third-party scripts.
Statistics without cookies. To count visits to our public pages, our server builds a short code from your IP address and browser type, mixed with a secret that changes every day. We store only that code, never the IP address. The next day the code is different, so visits cannot be linked across days and the code does not identify you. Nothing is stored in your browser for this.
how long we keep data
We keep your data while your account exists. Signals that expire or that you archive stay in your account until you delete them or your account.
- Public profile lookup. We do not keep the raw search result. We keep only what you save in your profile.
- Browser push addresses. Until you switch browser notices off, or until the push service tells us the address no longer works.
- Notifications. While your account exists. [LAWYER: set a retention period for read notifications]
- Reports and blocks. Blocks stay until you unblock or delete your account. Reports stay while they are needed to keep members safe. [LAWYER: set a retention period for reports, also for reports about a deleted account]
- Access requests. Until we decide. A declined request can be sent again after 30 days. [LAWYER: set how long declined access requests are kept]
- Server logs. For a short time, for security. [LAWYER: state the exact number of days]
You can delete your account in Settings. This deactivates the account at once and signs you out on all devices. To have all remaining data erased, write to hello@plsintro.com. We then erase it within 30 days, unless the law requires us to keep it. [LAWYER: today the erase after a deletion is done by hand on request; confirm this wording, or ask for an automatic erase after 30 days]
your rights
Under the GDPR and the FADP you have the right to:
- get access to your data and a copy of it;
- correct wrong data;
- have your data erased;
- restrict or object to processing;
- get your data in a portable format;
- withdraw a consent at any time, where we rely on consent.
Write to hello@plsintro.com. You can also complain to a data protection authority, for example the authority in your EU or EEA country, or the Swiss Federal Data Protection and Information Commissioner (FDPIC).
automated decisions
Agents suggest possible matches. They do not make decisions with legal or similar effects on you. You decide about every introduction.
beta and changes
plsintro is in beta. Features and providers can change. When we change this policy in a material way, we tell members by email or in the app before the change takes effect.