Local-First and Privacy

Caption is positioned around a local-first workflow because subtitle work often touches sensitive material:

internal meetings,
research interviews,
training content,
product demos,
and media that should stay inside your own boundary.

Why local-first matters here

A subtitle workflow usually touches more than text. It may include raw audio, screen activity, app output, and camera footage.

That makes the capture layer as important as the transcript layer.

Practical implication

When the core path stays local, you have a clearer boundary for:

what was captured,
where it was processed,
and where it remains searchable later.

What local-first does not mean

It does not mean every feature must avoid integration forever. It means the critical workflow should remain understandable and stable without forcing sensitive media through unnecessary external steps.