Notes and selected conversations you allow to be considered for memory.
REMEMBER / PEOPLE & MEMORY
Remember what matters about the people who matter.
Review the details that matter about a person, see where they came from, and decide what belongs in memory.
Alex says a short summary would be ideal. It may be a useful preference to remember, but you should be able to inspect the source before making it part of his profile.
UI DEMONSTRATION / PEOPLE & MEMORYPlanned
9:41●●● ▰
Review a memory
Your private relationship memory.
AC
Alex ChenProject contact · Business
POSSIBLE MEMORY · REVIEW FIRST
Alex prefers a short summary before the details.
Discard is always available.
01 / 11Review a possible memory
A suggestion is not a saved fact.
Automatic UI demonstration
Read the UI demonstration walkthrough
- Inspect its source. Open the selected message behind the suggestion.
- Return to review. The source stays attached to the candidate.
- Edit the memory. Narrow the wording to this project.
- Save the edit. The revised candidate still needs your confirmation.
- Confirm this memory. Only an explicit confirmation saves it.
- Memory confirmed. The saved detail keeps its source and can be reviewed.
This illustrates the proposed interaction. It is not a recording of a released app. Planned.
HOW IT WOULD WORKA clear input.
A clear input.
A considered outcome.
- 01
Inspect a possible memory alongside its source and date.
- 02
Confirm, edit or discard it; keep uncertain facts unresolved.
- 03
Return to the person’s page when preparing the next conversation.
An editable, source-linked detail on a person’s page, only after your review. Recorded timelines and circles keep the wider context nearby.
YOUR CONTROL
The choice stays with you.
Separate permission for memory, review before saving, and the ability to correct or remove a detail.
What happens if two notes disagree?
Both should remain visible as unresolved information until you choose what is current. A suggested interpretation should not silently replace a confirmed detail.
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.