Trust
The questions to ask before you connect a domain.
Plain answers, no badges. If something here is unclear, that is a bug in this page.

What the domain scan reads
Public pages only: your existing posts, pricing, product, and docs pages. No logins, no analytics, no private data. Domain connection is optional and skippable.
What you can edit
Every extracted field: product, audience, tone, colors, topics, and writing instructions. Correct anything wrong before a single post is generated.
What is stored per post
The article, its source set, fact-check findings, warnings, images, and delivery records. Stored so you can audit any post later.
Credentials and keys
Publishing credentials are encrypted at rest. API tokens are hashed. Each connection gets only the permissions its job needs, and you can revoke any of them.
Publishing permissions
WordPress and Ghost connections create and update posts. GitHub commits to one configured path. Webhooks push to your endpoint. The Content API is read-only.
Ownership and deletion
Markdown is the canonical file and export is always available. Cancel and keep everything. Account deletion removes your content on request.
Model providers
Generation runs on third-party language models. Your brand context and topics are sent to them to produce your posts, and are not used by Ryterr to train models.
Fact-check limits
The fact-check pass verifies claims against live sources where it can. It is not a guarantee of accuracy. Unresolved findings stay visible, and the review gate holds those posts.
The scheduling review gate. A scheduled post with unresolved review warnings never publishes automatically. It stops and waits for a human. This rule has no override.
See how review worksQuestions this page does not answer: [email protected] · Terms · Privacy
Review the workflow on a topic you know.
Two full posts free. Inspect the sources, warnings, and files before connecting a publishing target.

