Security & control

Scoped read + send OAuth. 100% human-approved replies.

Kelden drafts. You send. Nothing ever leaves your inbox without your click. Kelden connects to Gmail (gmail.readonly + gmail.send) and Microsoft Outlook (Mail.Read + Mail.Send) without deleting or modifying mailbox messages, isolates every workspace with forced PostgreSQL Row-Level Security, and keeps a durable audit trail on every issue.

Three hard operational boundaries

Kelden keeps AI inside an assistive triage and held-draft boundary, leaving Fair Housing compliance, legal interpretation, emergency response, and vendor spend under human authority.

Boundary 01 · Scope

Current-resident operational scope only

Kelden handles maintenance and unit threads for active properties and current residents. It is never used for prospective rental applicant screening, credit or eviction scoring, Emotional Support Animal (ESA) or accommodation decisions, Fair Housing eligibility, or cure-or-quit notices. Those threads flag immediately for direct human handling.

Boundary 02 · Citations

Never invent lease rules or legal opinions

Digital signed-lease PDF lookup quotes verbatim clauses with page and section citations or flags "No clause found in signed lease" (scanned image-only PDFs are rejected cleanly). Lease-policy questions always hold for human review against local law.

Boundary 03 · Escalation & Spend

Human-only emergencies and vendor spend

Every reply on Portfolio waits for an explicit click on Send reply. Messages covering life-safety or habitability emergencies (gas, fire, flooding, no heat, water loss, sewage, electrical hazards, lockouts) escalate immediately without DIY repair instructions, and Kelden never autonomously authorizes paid vendor work orders or owner commitments.

Contractual commitment: All three operational boundaries are written directly into Kelden's Terms of Service across Portfolio and every roadmap tier.

Server-enforced isolation and mailbox safeguards

Scoped read + send OAuth only

Gmail uses gmail.readonly + gmail.send and Microsoft Outlook uses Mail.Read + Mail.Send. Kelden never deletes or modifies mailbox messages, folders, or inbox filters.

Explicit manager approval before send

Every outbound reply on Portfolio stays held on Issue detail until a team member clicks Send reply. Server idempotency checks ensure concurrent edits or double-clicks never double-send.

Forced PostgreSQL tenant Row-Level Security

Properties, units, issues, threads, and attachments are isolated per workspace with forced PostgreSQL Row-Level Security (ENABLE and FORCE ROW LEVEL SECURITY). Unknown senders leave the unit blank until confirmed.

Server-verified sessions and encrypted tokens

Sessions are verified on Kelden servers before any record loads, and OAuth refresh and access tokens are encrypted at rest with AES-256-GCM.

One-click pause switch and clean disconnect

One switch in Settings pauses new inbox polling and outbound sends immediately without losing existing issues. Disconnecting revokes active polling cleanly while preserving your records.

Fail-closed sync and delivery boundaries

If an OAuth grant expires or sending fails, existing issues stay readable, draft text stays intact, status stays unchanged, and a clear reconnect or retry prompt appears.

Original messages and verified thread delivery

Original email text, CC lists, thread identifiers, and photo/PDF attachments remain attached to every issue. Replies mark sent only after provider confirmation.

Schema-bound extraction, zero model training

Extraction uses strict JSON-schema outputs rather than brittle keyword rules, while server checks enforce isolation and send gates. Mailbox data is never used for advertising or model training.

Kelden's controls are designed with SOC 2 criteria in mind. Kelden does not claim SOC 2 certification.

Operated by Clipt Videos LLC, 1908 Thomes Ave STE 12440, Cheyenne, WY 82001.

Security contact: patrick@kelden.ai