Know-N is an online bookmark library. The public privacy posture is about accounts, collections that default to private, and the session cookie that keeps you signed in on a device. This page is written for guests and agents. It is not a copy of the signed-in Settings privacy panel, which describes in-product controls for a person who already has a session.
An account is how Know-N recognizes you on later visits so you can keep a library of collections. Signing in lets you capture pages with the browser extension, organize those collections, and choose when a collection should become a public reading path. Without an account you can still read public paths that other people have shared, but you cannot write into a private library.
Know-N does not require a public telephone number or mailing address in order to use the library. Profile fields you choose to show are separate from whether a collection is private or shared.
A new collection is private. Other people cannot browse it, follow it, or treat it as a public reading path until the owner shares it. Default-private is a product rule for every new collection, not a hidden preference that only appears after sign-in. Publishing is an explicit step. Syncing bookmarks into a collection you own does not make that collection public.
Shared collections and public reading paths are visible to the audience the owner chose. Private collections remain limited to the people the owner invited. Know-N does not turn a private library into a public search index.
While you are signed in, Know-N keeps a session cookie on this device so the browser can stay authenticated without storing your password in the page. The cookie belongs to the session on this site. Signing out ends that session on the device. The session cookie is not a public profile, and it does not change a collection from private to shared.
Agents and crawlers reading this page without executing script should treat the statements above as the public policy: accounts exist, collections start private, and signed-in use relies on a session cookie.