Keepr

When a user adds a link, the system validates the URL format and attempts to detect the record's title from the target page's metadata. The title is read from Open Graph, Twitter Card, or HTML title fields.

The link can be assigned to a category, and its title and description can be edited by hand. Once created, the record enters the search, favourite, pin, and reminder workflows.

Link cards present title, source, category, and record state in a dense but quiet layout. Selecting a record opens the inspector panel, where link details and the available actions get a wider surface.

From that panel a link can be opened, edited, moved between categories, favourited, pinned, given a reminder, or deleted. Some of those actions depend on package access.

Selection mode supports moving, deleting, favouriting, or pinning several links in one pass. Editing bulk actions are disabled in shared collections where the current user only holds read-only access.

Repetitive archive work can be driven from the keyboard: F toggles favourite, P toggles pinned, A opens the reminder panel, Delete or Backspace removes the link, and Escape closes the open panel.

Team users can expose a root category as a shareable collection. The shared page presents the root category's links together with the contents of its nested folders in a responsive layout, while links marked private stay out of that output. The result is a read-only presentation surface for visitors holding the link.

The same structure opens up to collaboration: an invitation is created at category level, and the invited user joins as either viewer or editor. Viewers only read; editors can add and modify links. The interface separates shared folders and read-only states through visible labels.

Registration collects username, email, password, and the required consent information, and an unverified account cannot enter the normal session flow. The six-digit OTP is not stored as plain text: an HMAC-SHA256 digest is kept instead, and the submitted value is checked with a timing-safe comparison.

Once verification succeeds, the application issues a short-lived access token of roughly fifteen minutes alongside a cryptographically generated refresh token tracked in the database. Using a refresh token revokes the old record and issues a new one; if a revoked token is presented again, the related sessions can be closed.

Failed sign-in attempts are recorded against IP and email, and temporary blocks can follow once a threshold is passed. Password updates are checked against password history, and registration, sign-in, sign-out, password changes, and bulk link operations are traceable through the audit log.