# Store generated content in the user's browser, not on your servers

- Category: business
- Author: Andrei Statescu (https://indie.md/people/andrei-statescu/)
- Source: https://indie.md/journeys/andrei-naramine/
- Canonical URL: https://indie.md/advice/let-the-browser-hold-the-bytes/

Every minute of audio Naramine generates is cached in IndexedDB on the listener's own machine, sometimes tens or hundreds of megabytes of it, with a clear-data control and a download option for the user. Andrei's servers never store the stories or the audio derived from them, and that decision does double duty. Economically, his storage bill is zero and stays zero as usage grows, which matters enormously for a solo founder with an 80 percent margin target. Legally, it keeps him a tool rather than a distributor: a service that hosts copies of authors' copyrighted stories, or audio derived from them, has built a library it must defend, while audio generated on demand and held only on the reader's device looks like the reader's own personal-use copy. When your product transforms content you do not own, ask where the transformed bytes live, because that answer decides both your infrastructure costs and which side of a copyright argument you are standing on.