03.2 — Account· 2 min read

Security & privacy.

Your content is yours. Klyph treats every source, transcript, and render as workspace-private data and keeps only what it needs to run the service.

§ 1

Encryption in transit & at rest

All uploads and API calls use TLS 1.3 in transit. Stored sources, transcripts, and renders are encrypted at rest in our storage layer.

§ 2

Retention

  • Sources — kept until you delete them, or until the workspace is removed.
  • Transcripts & clip scores — kept for the lifetime of the source.
  • Renders — kept for 90 days after last access.
  • Deleted content — purged from primary storage within 30 days of deletion.
Note
Delete anything, any time.
Deleting a source removes every downstream clip, render, and transcript tied to it — no hidden copies.
§ 3

Ownership

You own what you upload and what Klyph generates from it. Klyph receives a limited license to process your content only for the purpose of delivering the service to you.

§ 4

Model training

Your content is never used to train foundation models. Klyph uses third-party models via API — your uploads, transcripts, and renders are not contributed to any training dataset.

§ 5

Account security

Sign in with email, Google, or GitHub. API keys can be rotated at any time from workspace settings, and scoped so a key cannot perform actions outside its role.