Credentials and keys
Publishing credentials and API keys are encrypted at rest. A new API key is shown once, and after that only a masked form appears. Each connection gets the permissions its job needs, and you can revoke any of them.
Trust center
What happens to your site, your posts and your keys.
Plain answers on what Ryterr reads from your site, what it stores, who receives your content and what it will not publish without you.
Ryterr reads public pages and you edit what it saves.
Adding your website is optional. Ryterr reads public pages on your own site, such as your homepage, pricing, product, docs and blog. It follows your robots.txt, stays on your domain and never logs in or reads private data.
Each fact it saves shows the quote it came from. You can edit the product, audience, tone, colors, topics and writing instructions before a single post is written.
How your data and keys are handled.
Six points, each with what Ryterr does.
Requests to your site
When Ryterr reads or publishes to a web address, it connects only to public addresses and refuses private network ones. Webhooks are signed, so your site can check that a request came from Ryterr.
Publishing permissions
WordPress and Ghost connections create and update posts. GitHub commits to one configured path. A webhook sends the post to your endpoint. The Content API is read-only.
Model providers
Language models write and check your posts, so your brand context and topics go to them for that task. Ryterr does not use your content to train models. The privacy policy lists each provider and what it receives.
See the provider listGoogle Search Console
Optional, and read-only. It uses its own consent screen, separate from signing in. Disconnecting revokes Ryterr's access at Google and deletes the search data it imported.
Ownership and deletion
Your posts are yours, and Markdown and HTML export is always available. If you cancel, you keep everything. Deleting your account removes your posts, images, connections and API keys, and cancels an active subscription at once.
A scheduled post with open warnings waits for you.
Scheduled publishing always stops when a post has unresolved review findings. The post stays in your account until you read the report.
A post you publish by hand asks you to acknowledge the warning first, so nothing flagged goes live by accident.
What the fact check can and cannot do.
It is a check against live sources with a report you can read.
Checked against live sources
Each statistic, price, name and date is compared with a page Ryterr retrieved.
Unresolved claims stay visible
A claim Ryterr cannot confirm is listed on the post with its status.
Not a guarantee of accuracy
The fact check reduces risk. You read the report and decide what to publish.
Corrections on every post
Ryterr corrects what the source contradicts and checks the claim again, on your free posts and on Solo. Anything it cannot confirm stays flagged for you.
A question this page does not answer? Write to [email protected], or read the terms and the privacy policy.
Review the workflow on a topic you know.
Two posts free, no card needed. Read the sources, the warnings and the files before you connect a publishing target.