Our security starts with what we don’t collect.

Every online service carries risk. KinMap reduces unnecessary exposure by collecting less sensitive information in the first place. Data we never collect cannot be exposed from our system. What you do choose to store is still personal — which institutions you use, what you own, and who you trust — so it deserves real protection too.

What KinMap will never ask for

There are no fields for these anywhere in KinMap, and we warn you if something like them is typed into a note.

  • Banking or brokerage passwords
  • Account usernames
  • PINs or security questions
  • Full account or routing numbers
  • Debit or credit card numbers and CVVs
  • Trading credentials
  • Private keys or seed phrases

What KinMap does store

Institution names, account types, owners, optional last four digits, contact names, where records are kept, and the people you trust. It’s enough to point your family in the right direction, and treated as private information.

Sharing you control

You choose each trusted person and exactly what they can see. Nothing is shared by default, and there is no automatic release of your information.

Where this prototype stands

This is a local proof of concept. Everything you enter stays in this browser on this device, and all sample data is fictional. It does not yet include the production protections below, so please don’t enter real information. Before KinMap launches publicly, these will be in place and independently reviewed:

  • Planned Encryption in transit and at rest
  • Planned Secure sign-in with multi-factor authentication or passkeys
  • Planned Least-privilege access and audit logging
  • Planned Rate limiting and secure session handling
  • Planned Backups, dependency scanning, and vulnerability management
  • Planned Independent penetration testing
  • Planned Data export and deletion on request
  • Planned A published privacy policy and incident response plan