tinyfiles.tv
C-Bookings - Bookings the server can't see

Bookings.
Without the server
reading them.

C-Bookings is booking + provider setup for tinyfiles.tv. Like C-Mail + C-Talk: cryptographic buckets. Server stores ciphertext only. You decrypt locally.

What is C-Bookings?

Providers set up. Clients book. Server learns nothing.

01For Clients

Book without exposing

Pick a provider, pick a time, write your details. It is encrypted in your browser into a bucket. Server sees ciphertext only.

02For Providers

Set up your service

Create a provider bucket: name, service, price, availability. Share your provider code. Clients book you with it. You decrypt bookings locally.

03For Server

Server sees ciphertext

Like C-Mail Slot 2. Server stores buckets, never sees contents. No names, no messages, no booking details. That is the contract.

How it works - 4 steps
  1. Provider setup: Provider creates a provider bucket + PIN. Gets a provider code.
  2. Share code: Provider shares code privately. Client enters it below.
  3. Book: Client creates a booking bucket (1 booking = 1 bucket, 4 KB max). Encrypted locally.
  4. Provider decrypts: Provider logs in with code + PIN, decrypts locally, confirms.

Lose code / PIN = lose bookings. No email, no recovery. Same as saves.

Crypto Login

Log in with code + PIN.

No email. No password reset. Your code + PIN decrypts your buckets locally. Demo: Provider Code PROVIDER-DEMO + PIN 1234 — or Booking Code BOOK-1234 + PIN 1234.

Demo PIN is 1234. In real use, your PIN decrypts locally.

Your Bookings — Decrypted Locally

Log in to decrypt your bookings. Server has not seen this panel — it is decrypted in your browser.

Provider Setup

Start as a provider.

Creates a provider bucket locally. You get a provider code + PIN. Share the code, keep the PIN.

Backend  ·  Template · Proposed · Not connected

C-Bookings Backend — Template

Template-style for now. Same idea as the page: the server stores ciphertext only, it never sees the booking details. The browser encrypts / decrypts locally with the PIN. The backend below is placeholders for what the API would need — bucket, booking, message, confirm — not live code.

01 / Files to create
api/cbookings/create_bucket.php    POST /api/cbookings/create_bucket
api/cbookings/get_bucket.php       GET  /api/cbookings/get_bucket?code={{bucket_code}}
api/cbookings/create_booking.php   POST /api/cbookings/create_booking
api/cbookings/list_bookings.php    GET  /api/cbookings/list_bookings?code={{bucket_code}}
api/cbookings/get_booking.php      GET  /api/cbookings/get_booking?id={{booking_id}}
api/cbookings/confirm_booking.php  POST /api/cbookings/confirm_booking
api/cbookings/send_message.php     POST /api/cbookings/send_message
api/cbookings/list_messages.php    GET  /api/cbookings/list_messages?booking_id={{booking_id}}
sql/cbookings_tables.sql

Template pattern: each endpoint loads /api/bootstrap.php, uses json_in() / json_out(), prepared PDO statements. No plaintext booking data in logs.

02 / Database tables — template
-- sql/cbookings_tables.sql
cbookings_buckets
  id CHAR(36) PRIMARY KEY
  bucket_code VARCHAR(32) NOT NULL UNIQUE   -- e.g. PROV-1234, BOOK-1234
  bucket_type ENUM('provider','client') NOT NULL
  ciphertext TEXT NOT NULL                 -- encrypted provider profile / bucket meta
  created_at DATETIME

cbookings_bookings
  id CHAR(36) PRIMARY KEY
  bucket_code VARCHAR(32) NOT NULL
  ciphertext TEXT NOT NULL                 -- encrypted: who, when, where, service, price
  status ENUM('pending','confirmed','declined','done','cancelled') NOT NULL DEFAULT 'pending'
  created_at DATETIME
  updated_at DATETIME

cbookings_messages
  id CHAR(36) PRIMARY KEY
  booking_id CHAR(36) NOT NULL
  sender_bucket_code VARCHAR(32) NOT NULL
  ciphertext TEXT NOT NULL                 -- encrypted message body
  created_at DATETIME
Template rule: server stores ciphertext only. No columns for name, service, time, location, price, or message text. If it is in plaintext in the DB, the C-Bookings promise is broken. PIN is never sent to the server, never stored.
03 / API endpoints & request flow — template
POST /api/cbookings/create_bucket
{ "bucket_type": "provider", "ciphertext": "{{encrypted_blob}}" }
-> { "ok": true, "bucket_code": "PROV-1234", "id": "{{uuid}}" }

GET /api/cbookings/get_bucket?code=PROV-1234
-> { "ok": true, "ciphertext": "{{encrypted_blob}}" }
-- browser decrypts locally with PIN, server never sees plaintext

POST /api/cbookings/create_booking
{ "bucket_code": "PROV-1234", "ciphertext": "{{encrypted_booking}}" }
-> { "ok": true, "booking_id": "{{uuid}}", "status": "pending" }

GET /api/cbookings/list_bookings?code=PROV-1234
-> { "ok": true, "bookings": [ { "id": "{{uuid}}", "ciphertext": "...", "status": "pending" } ] }
-- browser decrypts each ciphertext locally with PIN

POST /api/cbookings/confirm_booking
{ "booking_id": "{{uuid}}", "action": "confirm" | "decline" | "done" | "cancel" }
-- status only, no plaintext. Server just flips the status column.

POST /api/cbookings/send_message
{ "booking_id": "{{uuid}}", "sender_bucket_code": "BOOK-1234", "ciphertext": "{{encrypted_message}}" }

GET /api/cbookings/list_messages?booking_id={{uuid}}
-> { "ok": true, "messages": [ { "id": "{{uuid}}", "ciphertext": "..." } ] }
04 / Crypto model — template
// Browser only, never server:
1. User types code + PIN
2. PIN -> key (e.g. PBKDF2 / Argon2, salt stored in bucket meta)
3. Key decrypts ciphertext locally -> shows booking details
4. User edits -> encrypts locally -> sends ciphertext only

// Template placeholders:
- {{salt}} - stored with bucket, not secret
- {{ciphertext}} - AES-GCM encrypted JSON, e.g. { "service": "...", "when": "..." }
- {{pin}} - never sent, never logged, never stored
- Lose PIN = lose bookings. No recovery. Same copy as the page already says.

// Server must NOT:
- log ciphertext bodies in access logs
- store decrypted data for search / admin
- accept plaintext booking fields (reject if plaintext fields present)
05 / Front-end integration contract — template
// When API exists, replace demo handlers with:
doLogin() -> GET /api/cbookings/get_bucket?code={{code}} -> decrypt locally -> render
createProvider() -> POST /api/cbookings/create_bucket { bucket_type, ciphertext }
createBooking() -> POST /api/cbookings/create_booking { bucket_code, ciphertext }
confirmBooking() -> POST /api/cbookings/confirm_booking { booking_id, action }

// Template response shape:
{ "ok": true, "mode": "live" | "simulation", "data": "{{...}}" }

// Recommended states: loading, live, simulation, wrong PIN, bucket not found, server unavailable.
// Demo PIN 1234 in this page is a placeholder - real PIN is user-chosen, never 1234 in prod.

Build order if you do this: 1) tables, 2) create_bucket + get_bucket (ciphertext round-trip), 3) create_booking + list_bookings, 4) confirm + messages, 5) rate limits + log scrubbing.