Security and privacy
Focused workspace, clear data boundaries.
Harken keeps product claims grounded in the current implementation. Stronger compliance claims should only be added when the system actually supports them.
Data boundaries
| Data type | Used for | Scope |
|---|---|---|
| Audio | Transcription and meeting capture | Authenticated request/session |
| Transcript | Cleanup, summaries, and recent history | Signed-in user |
| Images and screenshots | Visual explanation, OCR-style reading, and capture history where enabled | Signed-in user or local capture flow |
| Lexicon | Learned corrections | Signed-in user |
| Meeting notes | Notes, action items, and question answering | Pro user profile |
| Trace/debug | Reliability diagnosis | Redacted event shapes, counts, timings, and keyed hashes |
| Billing | Plan and entitlement state | Account, via Lemon Squeezy when live |
No unsupported claims.
Harken should be described as a focused capture and structuring workspace, not as certified compliance infrastructure unless that certification is implemented and verified.