Question 1

How Kept works

Accepted Answer

Kept is a private coordination layer for consensual keyholding between adults. You create a session with agreed release rules, optionally assign a keyholder or bounded automation, and Kept keeps a clear, timestamped record of every change. Kept coordinates timers, unlock codes, logs, and communication — it does not physically control any device.

Question 2

What is keyholding?

Accepted Answer

Keyholding is a consensual dynamic where one person (the keyholder) helps manage when another person's session resolves. In Kept this is entirely tracking and communication: the keyholder can adjust time or reveal codes only within the permissions that were explicitly agreed before the session started.

Question 3

What is a timed-release session?

Accepted Answer

A session with a minimum and maximum release window. The clock resolves within that window based on your rules, keyholder decisions, or automation. Nothing can run past the maximum you set, and the session owner always keeps an emergency safety release.

Question 4

How safety release works

Accepted Answer

The session owner always has an emergency safety release available. It cannot be removed, delayed, or overridden by a keyholder, a bot, Blind Mode, or any module. If you ever feel unsafe or unwell, use it — no code, approval, or waiting period is required.

Question 5

Safety principles

Accepted Answer

Consent is required and can be withdrawn at any time. Everything is opt-in. Limits are visible before a session locks. Automation and keyholders act only inside approved bounds. Your emergency release is always one tap away, everywhere in the app.

Question 6

How keyholders work

Accepted Answer

You can invite a keyholder by email, by username, or with a private invite link. They review the session terms before accepting, and can only take the specific actions you granted (for example: add time, reduce time, reveal a code). You can also set up a backup or temporary keyholder and hand off control.

Question 7

How unlock codes work

Accepted Answer

An unlock code is a sealed secret tied to a session. Kept stores only a secure hash — the plain code is shown to you once and never stored or exposed again, not in logs, notifications, or admin views. You reveal, redeem, or revoke codes according to the session's rules.

Question 8

How Code Scramble works

Accepted Answer

Code Scramble lets a session obscure or shuffle how a code is presented so it isn't casually readable until the agreed conditions are met. The underlying code is still stored only as a hash.

Question 9

How Blind Mode works

Accepted Answer

Blind Mode hides or masks selected session details from the locked user — such as exact timer amounts, direction, or recent changes — while keeping the keyholder's full view. Masked events can be revealed later based on the reveal policy you agreed. Your emergency safety release always stays visible.

Question 10

How Deck Mode works

Accepted Answer

Deck Mode introduces a deck of cards that apply agreed effects (like adding or removing time) when drawn. Every possible effect stays inside the session's approved limits.

Question 11

How bots and automation work

Accepted Answer

Bots make bounded, scheduled adjustments you approve in advance — respecting each bot's cooldown, daily limit, and the session's release boundaries. Automation can be paused, and it can never exceed the maximum limit or bypass safety release.

Question 12

How Temporary Openings work

Accepted Answer

A temporary opening (hygiene window) is a scheduled, time-boxed pause you or your keyholder can request, with optional cooldowns and daily limits. Relock happens automatically or on confirmation, and the whole cycle is logged.

Question 13

How Tasks and Verification work

Accepted Answer

Tasks are assignments a keyholder sets; verification lets a locked user submit proof of a state or task. Verification media is handled privately and is never attached to notifications or exposed in general admin views.

Question 14

How Shared Links work

Accepted Answer

Shared control links let you delegate specific, limited actions to someone without giving them full account access. Links carry only the permissions you choose and can be revoked at any time; sensitive session data is not exposed through them.

Question 15

How data privacy works

Accepted Answer

Kept is private by design. Your sessions are visible only to their participants under strict row-level security. Unlock codes are stored as hashes, verification media is access-controlled, and hidden Blind Mode details are never leaked through notifications or logs.

Question 16

How to delete your account or history

Accepted Answer

You can end and remove sessions from your history, and request account deletion from Settings. Deleting your account removes your profile and cascades to your sessions and related records. If you need help, use the in-app feedback tool.

Question 17

Beta tester guide

Accepted Answer

Kept is in private beta. Expect occasional rough edges and please report anything confusing or broken with the Report an issue button — it attaches the page you're on (never your codes or private media). Your feedback directly shapes the release.

How Kept works

Getting started

Safety first

Keyholders & control

Modules

Privacy & account

Still need help?