Your data

Where does ReadCastX process documents?

ReadCastX processes document text and generates narration on infrastructure operated in France. We do not send your text to a third-party narration API or use it to train models.

What happens to the uploaded file?

We extract text from the upload and do not keep the original as a library file. Upload handling can use temporary disk files. The library retains extracted text and generated audio until you delete the document.

What does deleting a document do?

Deletion removes the document from your library and feed and requests removal of its stored audio. Temporary processing copies have a separate cleanup lifecycle. If storage deletion fails, an audio object can remain until operational cleanup. Copies already downloaded by a player cannot be erased remotely.

What remains after account deletion?

Account deletion removes your library and feed records and requests deletion of audio and cover files. It does not promise instant erasure from processing storage, backups, billing records, or devices that already downloaded audio. Contact support for a data request or a storage cleanup problem.

Who can listen through my private feed?

Anyone holding the feed URL can listen. Keep it private and regenerate it if exposed. Regeneration blocks future requests to the old feed and audio addresses; it does not remove downloaded copies.

Which other services are involved?

Payments and account email use separate services. Google Analytics loads only on anonymous public marketing pages after analytics consent; it is disabled on account and private feed pages. Your chosen podcast player has its own privacy policy. These services are separate from our document narration pipeline.

Questions about your data

For access, correction, export, or deletion requests, contact support@readcastx.com. This page describes current product behavior. The legal pages remain drafts pending review; this is not a certification of compliance.