A goal and confirmed relationship information from sources you chose to use.
CONNECT / INTRODUCTION PATHS
See a path to the right conversation.
See a possible path through confirmed connections, then decide whether and how to ask for an introduction.
Alex once mentioned Sam, who may have relevant product experience. That creates a possible path, not a promise that either person wants an introduction.
UI DEMONSTRATION / INTRODUCTION PATHSFuture vision
9:41●●● ▰
Your network
A thoughtful way to connect.
NDYou
AAlex
MMaya
Sam
CCedar
Select a person to inspect a path.
Whether either person wants an introduction is still unknown.
01 / 11Explore confirmed connections
Start with the map, with sources behind the lines.
Automatic UI demonstration
Read the UI demonstration walkthrough
- Select Sam. Trace the possible route through Alex.
- Inspect the connection. Open Alex’s confirmed note.
- Return to the path. A recorded connection is not an agreed introduction.
- Draft the request. Open an editable introduction request.
- Keep it as a draft. No one is contacted by this demonstration.
- Draft saved. Not sent.. Alex and Sam have not agreed to an introduction.
This illustrates the proposed interaction. It is not a recording of a released app. Future vision.
HOW IT WOULD WORKA clear input.
A clear input.
A considered outcome.
- 01
Inspect how each connection in the path is known.
- 02
Check the missing information and whether asking is appropriate.
- 03
Review a low-pressure introduction request.
An explainable connection path, its source and unknowns, with a request you can review before deciding whether to send.
YOUR CONTROL
The choice stays with you.
Source review, no presumed permission, no automatic introductions, and a clear option not to approach anyone.
What if there is no confirmed path?
The product should make that limit clear. It should not invent a connection, imply a strong relationship from weak evidence, or treat a declined request as a problem to bypass.
STAY IN THE CONVERSATIONFollow the build.
Follow the build.
Hear when it’s ready.
Join for Keykind product progress and launch news. Choose the parts of the vision you care about most.
Photography sources
Reference photography: Mizuno K and Kampus Production on Pexels, used under the Pexels License. Product interfaces use synthetic example people and records.
Are these real conversations or a finished product?
The product interfaces and timeline walkthroughs use synthetic example people, messages and records. They illustrate the intended experience, with the development stage shown beside each feature. They are interactive HTML demonstrations, not recordings of a released product. No messages, contacts or relationship information are read or sent by these demos.
Can I use Keykind today?
Not yet. Keykind is in development. This page shares the intended direction, and the interactive preview uses preset examples. Joining the waitlist does not provide product access. Launch dates, supported devices and pricing are not announced.
What happens to my waitlist information?
This waitlist stores your email, optional interest (a product area or feature you choose) and phone preference, signup time, consent version, and a one-way hash of a private management code.
The records are held in this site’s Cloudflare D1 database through OpenAI Sites. They are used to manage the waitlist and understand which product areas people request.
The page does not read your messages, contacts or keyboard, and it does not send signup data to an advertising or email-marketing service. No email delivery service is configured.
Waitlist records are retained without automatic expiration, including if you never become a customer. You can withdraw from the waitlist and delete your record from the live database with the private link shown on your first successful registration. Anyone holding that link can remove the registration; do not share it.
Save a copy of your private link. No public contact details or manual recovery route are currently provided. If you lose the code or joined before private links were available, self-service access cannot currently be recovered here.
Email addresses and management codes are never displayed in the owner’s statistics.
Hosting providers may process connection metadata and retain service backups under their own policies; deleting a live record is not a claim that every provider backup is immediately erased.
Do you track visits or clicks?
Only if you choose “Allow anonymous counts”. The site then stores daily totals for approximate page visits, waitlist-button clicks and new signups from people who opted in.
A browser tab counts each visit or button-click type at most once per UTC day. These are not unique people or a complete visitor count.
Short-lived random event receipts prevent retries being counted twice; they expire after 24 hours and are removed on a later measurement request. The receipts are not linked to signup records.
Your allow/deny choice stays in this browser’s local storage; temporary per-tab deduplication uses session storage.
No tracking cookie, stored IP address, browser fingerprint, full URL query, referrer or third-party analytics is added by this application.
Recognized owner sessions, admin pages and marked QA signups are excluded.
Turning counts off stops future events; existing anonymous totals cannot be traced back to remove an individual contribution. Registration works whether you allow counts or not.
How do I leave the waitlist?
Open your saved private management link, check the code, then explicitly confirm deletion. This removes the registration and stops waitlist updates. Open the management page. Keep a copy of your private link. The site cannot email a replacement code, and there is currently no manual recovery route for lost or missing codes.
Will every feature on this page launch?
This is a product vision, not a delivery commitment. Features marked “In development” are being explored now. “Planned” and “Future vision” describe later possibilities. Scope may change based on research, platform permissions and what people actually find useful.