Your data, plainly.
Who we are
Minglet helps attendees of participating conferences find people with shared interests, chat, and arrange meetings. The service is provided by Sutro Software GmbH, Industriestrasse 47, 6300 Zug, Switzerland (UID CHE-144.908.537, commercial register of the Canton of Zug) (“Minglet”, “we”), the controller of your personal data. We have not appointed an EU or UK representative under Art. 27 GDPR/UK GDPR, as our processing is occasional and low-risk; if one is appointed or required, we will list them here, and you can request their details at any time. Contact: support@minglet.app.
What we collect
Account information
When you sign in with Google, GitHub, or Apple we receive your name, email address (Apple may give us a private relay address), and profile picture URL, plus the provider account ID and OAuth tokens needed to keep you signed in. Organizers sign in with email and password; we store a hashed password. We also keep the version and time of your Terms of Use acceptance, the privacy notice version presented with it, and your separate AI permission choice. Participant setup asks for these choices before you access participant features.
Profile information
Your display name, bio, interests and experience levels, conference goals and their sharing settings, and the conferences you joined. If you connect GitHub, we import public profile and repository data (for example languages, topics, starred projects, and public location). If you supply a public LinkedIn URL, we fetch public profile information about that URL through our data provider. We derive suggested interests from these sources; you can edit or hide them.
Activity in the app
- Swipes (interested / pass), mutual matches, searches you run for people, and QR networking codes you scan or show.
- Messages in match chats and your personal chat with Pip, our AI assistant, saved notes taken from those conversations, and any contact links you choose to share.
- Meeting proposals (time, place, status), and event documents or website excerpts organizers publish for attendees.
- Reports and blocks you submit, including a copy of a specific chat message if you choose to report that message to the event organizer.
Google Calendar (optional)
Only if you connect it separately, we read free/busy availability on your primary calendar and create entries for meetings both people confirmed. We don’t store your other calendar events. If you ask Pip about availability, common free slots may be sent to the AI provider; unrelated appointment titles and details are not sent.
Demo requests
When you request a demo, we use your name, email, event or organization, optional attendee range, and message to reply and arrange a conversation. Cloudflare delivers the request to our business inbox; it is not added to a mailing list. We keep demo inquiries for up to 12 months after the last contact unless we need them for an ongoing business relationship or legal obligation. Contact mail@minglet.app to ask about or delete your inquiry.
Product analytics
Our website and apps send usage events to PostHog: pages and screens viewed, taps and clicks, key actions (such as sign-in, swipe, match, message sent, meeting proposed, import completed), session information, and device and browser details (model, OS, app version, language, approximate location derived from IP address). Events are linked to your Minglet account ID once you sign in. Analytics is first-party only and never used for advertising.
What we don’t collect
We don’t collect your device location (location shown on profiles comes only from public source profiles), contacts, photos, health, or payment data. The camera is used only on-device to scan QR codes; images are not uploaded. We don’t use advertising SDKs or your device’s advertising identifier (IDFA), we don’t sell data, and we don’t track you across other companies’ apps or websites. We use PostHog for first-party product analytics (see below).
How we use it
- To run the service: show your profile to people at the same conference, recommend matches, explain shared interests, deliver chats, and schedule meetings.
- To provide Pip: relevant approved profiles, supporting project evidence, event information, messages and saved notes from the current conversation are sent to an AI model. Your personal Pip chat can also use your private event goals, people-search results, and common free slots when requested. Shared chats use only their two participants’ approved profiles and expressly shared goals. Full project excerpts from other attendees require their project-sharing opt-in.
- To keep the community safe: review reports, enforce our Terms, and prevent abuse.
- To secure and operate the service (sessions, logs, debugging).
- To understand and improve Minglet through product analytics (screens viewed, features used, events such as sign-in, swipe, match, and message sent), linked to your account ID.
We are subject to the Swiss Federal Act on Data Protection (FADP) and, where we offer the service to people in the EU/EEA or UK, the GDPR and UK GDPR. Our legal bases are: performance of our contract with you (account, profile, matching, chats, Pip, meetings); our legitimate interests in product analytics, security, abuse prevention, and handling reports; and your consent for optional sources (GitHub, LinkedIn) and Google Calendar, which you can withdraw at any time by disconnecting them.
Pip and AI people search are optional. Before using them, you choose whether to send the relevant information above to OpenRouter and its model provider, currently OpenAI. In shared match chats, both participants must allow AI first. Your account’s published profile is available to other attendees’ Pip requests only while you allow AI; public demonstration profiles remain labelled examples. You can turn permission off in You → AI privacy. This stops new AI requests and pending Pip work; data already sent cannot be recalled. GitHub and LinkedIn imports have separate, per-import permission.
Who can see your data
Other attendees of your conference see your published profile. Conference organizers see membership, published profile information, technical connections, recorded interest, and mutual matches — not your private chats or Pip notes, except for a specific message you explicitly share in a report. Personal Pip conversations are private to their owner and are not copied into match chats. We don’t sell your personal information.
Service providers
| Provider | Purpose |
|---|---|
| Cloudflare (Workers, D1, Queues) | Hosting, database, background jobs |
| Fly.io (self-hosted FalkorDB) | Graph database for interest and match relationships |
| OpenRouter and the AI model provider it routes to | Pip replies, search planning, interest extraction, and organizer document extraction |
| Bright Data | Fetching public LinkedIn profile data you request |
| PostHog (EU cloud) | Product analytics: events, pageviews and screen views, session and device data |
| Google, GitHub, Apple | Sign-in; GitHub import; Google Calendar if connected |
Some providers process data outside your country, including in the United States. Where a country isn’t recognized as providing adequate protection, we rely on the EU Standard Contractual Clauses (with the Swiss and UK addenda) and, where the recipient is certified, the EU-US Data Privacy Framework, its UK Extension, and the Swiss-US Data Privacy Framework. If we add a transactional email provider, we will list it here.
Retention
We keep your data while your account exists. Sign-in sessions expire after 7 days of inactivity; QR networking codes expire after 30 minutes. When a conference is closed by its organizer, its memberships, matches, and blocks are removed. When you delete your account, we delete your profile, imported sources, matches, chats, and saved Pip notes from our database and remove you from the graph. Specifically: account data is kept until you delete your account; backups and logs are kept for up to 30 days; reports expire after 12 months, or up to 12 months after an involved account is deleted, so we can handle repeat abuse; analytics uses a 12-month retention window, with older events removed at PostHog’s next monthly cleanup, and we request deletion of your analytics profile and events from PostHog when you delete your account.
Your choices and rights
- Edit or hide interests and goals in your profile; disconnect Google Calendar in Connected profiles. To remove stored GitHub or LinkedIn source data, contact us. You can also revoke GitHub authorization in your GitHub account settings.
- Turn off Pip and AI people search in You → AI privacy. Normal discovery, matching, chat and manual search remain available.
- Clear your personal Pip conversation and its saved notes from its conversation menu; control fuller public-project sharing in your event profile settings.
- Delete your account any time in the app (Profile → Delete account). See Support.
- Request access, correction, export, or deletion by emailing support@minglet.app. You may also complain to your data protection authority.
Children
Minglet is for adults attending professional events and is not directed to anyone under 16. You must be at least 16 to use it.
Changes
We’ll post updates here and change the date above. Material changes will be announced in the app.