Everything you need to make the case.
The honest version. What a host can see, what a host can't, what we do with data, and what happens when a round doesn't fill. Written to be forwarded.
What a host can see. What they can't.
A host can see
- Who is a member, their role, and whether they're invited, active, paused, or gone
- How many introductions someone has had, and when they were last active
- How the program is going overall: participation, which departments are connecting, feedback ratings as a distribution
- The round itself: who's included, how often it runs, what it's for
- Member email addresses are hidden by default. Revealing one is a separate, logged action
A host can't see
- What you talked about. We don't store conversation content anywhere
- Your notes. They are yours, and there is no setting that shares them
- What you wrote in feedback after a coffee
- Your personal network, and anyone in it
- Passport fields you haven't chosen to share
- Who you were introduced to in a coffee round
- Your coach and relationship history
Your relationships are yours. Running the program never means reading people's conversations.
Three things we won't pretend about
- Live events are different. If you run a live event, whoever organizes it sees that event's pairings by name, and whether each pair met. Seating a room needs it. Coffee rounds are not like this, and never have been.
- Host activity isn't fully logged yet. Today, one host action is recorded: revealing a member's email address. Making all host access to member data least-privilege and auditable is work we haven't finished, and we'd rather say that than imply otherwise.
- This describes our tools, not a vault. The boundaries above are what our host tools show and don't show. We're telling you how the product behaves, not claiming a database that makes misuse impossible.
See whether connections are forming.
Social capital is richer than a single score. But the activity that builds it doesn't have to stay invisible. See introductions made, conversations completed, participation over time, connections across teams or cohorts, and where people may be getting left out.
Counts and patterns, never who met whom, and never what anyone said. The full list is above.
48
members opted in
6
teams represented
84%
met for coffee
New introductions, every round.
Onboarding that becomes belonging
New hires meet people beyond their team early. They know who to ask, and feel known sooner.
Silos that begin to open
Connections form across functions, levels, and locations, so two departments understand one another before a problem escalates.
Knowledge that travels further
Know-how travels through people, from a mentor a level up to a peer in another office, not only through documents.
Connection you can see
See where introductions are forming and who is taking part, so support reaches the groups that need it and no one is quietly left out.
Not every coffee changes a career. But one trusted relationship can strengthen the network around it.
Almost nothing, and never a demand.
Two minutes, once
A few interests and what they're hoping for. That's the whole profile.
One introduction
One each round. Never a queue of strangers.
Out whenever
Pause or leave without explaining themselves to anyone.
One afternoon.
Pick who's included, invite them by email or a single shared link, and start a round when you're ready. Introductions and reminders go out on their own after that. There is no rollout project, no integration to schedule, and nothing for you to chase.
A buddy for anyone new, without a reporting channel.
Pair each new colleague with someone who's offered to help, for about 90 days: a first coffee in week one, three introductions in the first month, and a thank-you at the end. Buddies are asked before every pairing, and you choose every pair yourself, so you can keep buddies outside the reporting line. Existing members can ask for one too, after a move or a return from leave.
The program lead sees
- Who is paired with whom, because you chose the pair
- Where each pair is: waiting for a yes, met for a first coffee, needs a hand, wrapped up
- How settled people feel, as a distribution, and only once at least five people have answered
The program lead doesn't see
- What a buddy and their new colleague talk about
- How often they meet or message
- Any one person's answer to the settling-in question
- Why someone stepped out of a pairing
Off until you choose it. We make the buddy program available to your organization when you ask, and then your admin switches it on. Before it goes on, you name who people should contact for anything serious. That contact is shown on buddy screens, and the app never collects incident details itself. How the buddy program works
What if people don't show up?
Then the program has told you something, and it isn't that your people failed. Low participation is a design signal: the cohort may be too small, the timing wrong, or the reason to meet unclear. We will never shame anyone for not taking part, never name them to a host, and never manufacture a bad introduction to keep a schedule looking healthy.
We'd rather make no introduction than a bad one.
The rest of the diligence
Security & your data
Sign-in, access, deletion, and how member data is handled.
Read itWhat it costs
Free for communities. No card to start, and no contract to leave.
See pricingWhat it works with
Sign-in, calendars, and where introductions arrive, honest gaps included.
See integrationsOn keeping data. We keep information only as long as we need it to run the service and meet our security, contractual, and legal obligations. Members can ask us to delete their data, and an organization can close its space. We may keep de-identified, aggregate information. What we will not do is treat someone's private relationships as organizational property.
Still have a question?
Ask us anything you'd need to answer for the person above you. A human reads it.