Storyloom

Legal

Privacy

Controller

The data controller is Emanuele Pavanello, independent operator of Storyloom. Privacy requests may be sent to hi@emadev.co.

Data processed

Storyloom processes account and session data, books and prompts you provide, generated artifacts, encrypted provider credentials, job records, favorites, listening progress, rights declarations and content reports.

Purposes and legal bases

Data is processed to provide the requested service and manage accounts, to publish content at your request, to comply with legal obligations, and for the legitimate interests of securing the service, preventing abuse and handling reports. Listening is associated with an account so the same person is counted once per book.

Providers and recipients

Infrastructure, authentication, email, database and storage providers process data where configured. When you request cloud generation, relevant prompts or book passages are sent to OpenRouter and the selected model provider. Your API key is encrypted at rest and is never returned to the browser after storage.

Public information

A public story exposes its title, creator display name, summary, language, category, selected chapters and published media. Email addresses, provider keys, jobs, private registries and internal provenance are not public.

Retention and control

Account and project data are retained while the account or project remains active. You can unpublish, remove a key, move a book to recoverable trash and permanently delete it. Security, rights and moderation records may be retained for as long as reasonably needed for legal claims, abuse prevention or compliance.

Your rights

Depending on jurisdiction, you may request access, correction, deletion, restriction, portability or objection, and lodge a complaint with your supervisory authority. Send requests to hi@emadev.co. Private routes use authentication; robots.txt is not treated as a privacy control.

Cookies

Storyloom uses authentication and security storage necessary to operate the service. If optional analytics or advertising technologies are introduced, this notice and the consent interface will be updated before they are enabled.