The sources and details you explicitly select, with separate choices for session use and memory.
Choose what goes in. Decide what stays.
See what is being used, choose what is kept, and review the controls around your information.
A conversation can help you reply without becoming a permanent memory. The choices around a source, a session and a saved detail should be visible and separate.
Privacy & data
Your choices, at every step.
Clearing content does not end system sharing.
Session context, saved memory and sharing have distinct states.
Read the UI demonstration walkthrough
- Review saved memory. Open the example detail and its source.
- Choose Remove. The interface asks which detail to delete.
- Confirm removal. The example memory is removed.
- Turn selected context off. Stop using the selected text for this session.
- Clear session content. Clear the example text without claiming to end sharing.
- Session content cleared. Context is off. Sharing is still active until separately ended.
This illustrates the proposed interaction. It is not a recording of a released app. Design principles · Planned controls.
A clear input.
A considered outcome.
- 01
See which source is selected and the scope of this use.
- 02
Decide separately whether a reviewed detail belongs in memory.
- 03
Return to the detail to correct or remove it.
A clear view of the information being used, its source, and the planned controls to limit, correct or remove it.
The choice stays with you.
Per-source permissions, separate memory consent, source visibility, and planned review, correction, export and deletion controls.
What does this website actually store?
Only the waitlist and optional anonymous counts described below. Its product examples do not read messages or contacts. The private registration link lets you delete your waitlist record; it does not control a product account.
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
Are these real conversations or a finished product?
Can I use Keykind today?
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.