Kept
Adults only · Consent requiredPrivate keyholding platform

Session terms — Kept

Set the terms.
Lock the session.
Track every decision.

Kept helps consenting adults create timed-release sessions, secure a Release Vault code, assign trusted keyholders, and manage release rules with clear logs and safety controls.

Create a lock Sign inLearn how Kept worksView safety principles

Kept coordinates timers, codes, logs, and communication. It does not physically control any device.

Dossier № KP-4417

Private session

Locked
02days:14hrs:37min
Release
window left
Release window
Mar 14 — Mar 21
Minimum release
24 h
Maximum limit
7 d 00 h
Keyholder
Assigned · reviewing
Unlock vault
1 code · sealed
Safety release
Available
Last recorded action
+6 h · keyholder · 14:02

Keyholder permissions

Add timeReduce timeReveal codeExtend past max
Contract accepted · both partiesSealed
Clause I

Consent defines the session

Clause II

Release limits are visible

Clause III

Keyholder permissions are explicit

Clause IV

Safety release remains available

The terms

The terms are set before the session starts.

Every session opens as a written agreement. The rules are visible to both people before anything locks.

Agreement · Kept
  1. 01

    Release limits are defined

    A minimum and maximum release window is agreed before the clock starts. Nothing runs past the maximum you set.

  2. 02

    Keyholder permissions are explicit

    Every keyholder action — add time, reduce time, reveal a code — is granted on the record, and only what you allow is possible.

  3. 03

    Automation stays within approved limits

    Bots and Deck Mode act only inside the bounds you approved. No effect exists outside the terms already written down.

  4. 04

    Emergency unlock, your call

    Emergency unlock is on by default so the owner can end a lock early. It can be disabled per lock, and the maximum lock time always remains the hard limit.

How Kept works

A session moves in five deliberate steps.

  1. 01

    Set the terms

    Define the minimum and maximum release window, then agree the rules that govern the session.

  2. 02

    Choose a control mode

    Self-managed, keyholder, automation, Deck Mode, or Trusted Mode — each with its own boundaries.

  3. 03

    Assign a keyholder or automation

    Hand review to a trusted person, or let bounded automation adjust time on a schedule you approve.

  4. 04

    Track every change

    Every adjustment, request, and code event is written to a private, timestamped log.

  5. 05

    Release through rules, codes, or safety release

    The clock resolves within the window — or you use an unlock code, or the always-available safety release.

Control modes

Choose how control is held.

Switch the arrangement to match the trust you've agreed. Every mode keeps safety release intact.

Self-managed

01

You hold your own terms. The clock runs within limits you set for yourself.

Keyholder

02

A trusted person reviews requests, adjusts time, and approves release within permissions.

Automation

03

Configurable profiles move release time on a schedule — always bounded by your limits.

Deck Mode

04

Draw cards at set intervals to progress toward release or trigger agreed effects.

Trusted Mode

05

A higher-trust arrangement with a keyholder, still bounded by safety release.

Unlock codeSingle use

K7Q9·P2X4

Revealed once · expires in 10:00

Hashed at rest Revocable

Unlock Vault

Codes you control, stored as hashes.

Generate secure release codes with the exact format you agree on. Nothing is stored in plain text — not for you, not for a keyholder, not for us.

  • Configurable unlock codes, from 3 to 32 characters
  • Reveal confirmation — the plain code is shown once, to you alone
  • Optional code scramble to obscure over-the-shoulder viewing
  • Expiration and revocation on your terms
  • Hashed storage — the plain code is never saved

Keyholder Control Room

A command surface for the keyholder.

Everything a keyholder can do lives in one dark console — with clear permissions, counteroffers, and a safety line that never disappears.

Enter as a keyholder

Requests

Review and approve time changes on the record.

Counteroffers

Propose alternative terms instead of a flat no.

Check-ins

Schedule required confirmations and reviews.

Scheduled actions

Queue bounded automation ahead of time.

Safety controls

Freeze the clock or step back at any point.

Private messaging

Talk within the session, kept in the log.

Deck Mode

Chance, dealt from a table you control.

Draw cards at scheduled intervals. Every card is defined up front and bounded by your limits — nothing outside the deck can happen.

01

Release

Advance toward the release window.

02

Delay

Add time inside the agreed maximum.

03

Mercy

Cut time back toward the minimum.

04

Automation

Hand the next draw to a bot.

Draw history — every card drawn is logged with its effect and timestamp.

Safety & consent

You are always in control.

Kept does not physically control any device. It provides timers, unlock-code workflows, request handling, logs, and communication tools for consenting adults. Every session begins with explicit consent and an 18+ confirmation, and safety release remains available at all times.

View safety principles
  • Explicit 18+ age confirmation for every account
  • Emergency safety release available to the owner at all times
  • Automation can never exceed your configured maximum release time
  • Permanently end automated or keyholder control at any moment
  • Row-level security on every table — your sessions stay yours
  • Delete your account and full session history on demand

Start a private session.

Set the terms, invite a keyholder when you're ready, and keep every detail behind security you control.

Create a lock View safety principles