About Brivtex
The problem it was built for
There is no shortage of tools that will summarize a YouTube video. Paste a link, get a wall of text, copy it somewhere else — and then, in practice, never look at it again. The summary was never the hard part. Keeping it, finding it later, and connecting it to the other six things you watched on the same subject is the hard part.
Brivtex was built around that second problem. Summaries are the input; the library is the product.
How it works
You add a YouTube video or a podcast episode by URL, or pull a video straight from a channel you are subscribed to. Brivtex fetches the transcript — or transcribes the audio when there is no transcript — and writes a short summary, key points, and detailed notes.
From there it is yours: highlight what matters, save highlights into topic baskets, and write your own notes beside them. Nothing is published, shared, or shown to anyone else.
What it does not do
Brivtex organizes research you are already doing. It does not provide financial, investment, or professional advice, and its notes should not be treated as any.
Notes are generated automatically and can be wrong. They can miss a qualifier, flatten a nuance, or state something with more confidence than the speaker did. Every summary keeps a link back to the source and the full transcript, and for anything consequential the source is what counts.
Brivtex also does not publish summaries of other people's videos as public pages. Your library is private, and it stays that way.
Privacy
Summaries are private to the account that created them. Brivtex uses session cookies to keep you signed in and no tracking or advertising cookies. You can request deletion of your account and everything in it at any time, and deletion requests are actioned within 30 days.
Who builds it
Brivtex is built and run by one person. That has trade-offs — there is no support team and no enterprise sales — but it also means the free plan exists because it should, not because a growth model requires it, and questions get answered by the person who wrote the code.
The fastest way to reach me is email.