FAQ

Short answers to the predictable questions.

Trust, setup, billing, and private data handling — answered directly.

Roast uses private account state, a private RSS feed, and non-public user routes.

The feed URL is a bearer capability. Keep it private and rotate it if it leaks.

Forward only mail you control or are authorized to process.

Roast is not a loophole for processing private third-party mail you do not have rights to use.

Delays can happen in script generation, local TTS, or in the podcast client refresh window.

Check the inbox item first. If Roast says ready, the remaining delay is usually your podcast app refresh cadence.

Alias failures usually come from using the wrong address or from account state changes.

Confirm the exact alias shown in /my. Then confirm the account is still active.

Yes. Rotation invalidates the old feed URL immediately.

Every podcast app must then be updated to the new URL.

Yes. Use the billing portal from /my/billing.

Roast does not hide billing state inside a custom settings maze.

Yes. Roast may combine onboarding inputs with AI generation and public-web research.

User corrections remain authoritative. The profile surface makes the core state visible.