What we correct
Anything factual. In practice that usually means one of these:
- Pricing, plan names, limits and free-tier details
- Product features that are listed incorrectly or are missing
- Product availability, including regional restrictions and waitlists
- Company ownership
- Founder and team information
- Official URLs that are wrong, redirected or dead
- Platform support, such as web, desktop, mobile or self-hosted
- Integrations that were added or removed
- Category or use-case classification
- Product status - active, beta, paused or shut down
- Launch information and dates
- Acquisitions
- Rebranding and name changes
- Discontinued services and sunset features
- Duplicate pages for the same product
How to report an error
Send it through our contact form with "Correction" at the start of the subject line. Three things make a report actionable:
- The exact TiorAI page URL.
- What is wrong, and what it should say instead.
- Where we can confirm it - ideally a link to the vendor's own pricing page, changelog, documentation or announcement.
You do not need to be connected to the product to report an error. Readers catch a great deal of this before anyone else does.
What we do with your report
- You report the issue.
- We review the page it concerns.
- We check official or otherwise reliable sources.
- We correct the content where the report holds up.
- Where the change is significant, the page's update information is refreshed to reflect it.
We do not commit to a fixed response time. A wrong URL is a minute's work; a disputed ownership claim is not.
How corrections show up on the site
Routine maintenance - a refreshed price, a new integration, a fixed link - is applied to the page directly. Where a correction changes the substance of what a page said, we update the page's modification date so the change is visible rather than silent.
Site-wide and platform-level changes are recorded separately in our changelog.
What is not a correction
Two kinds of request arrive here that this policy does not cover, and both have a better route:
- Disagreement with an editorial assessment. Where a tool ranks, how it is compared, or whether we should recommend it is judgement, not fact. We are glad to hear the argument, but it is handled as feedback rather than as a correction - see our Editorial Policy.
- Removal, logo, screenshot, trademark and copyright requests. Those go through our Content Removal & Intellectual Property Policy, which sets out the verification we need.