About

The publisher of record is RTILA CORPORATION, registered in the state of Delaware, United States.

Registered name

RTILA CORPORATION

Postal address

20c Trolley Square, Wilmington, Delaware 19806

Telephone

+1 302-389-5527

Contact

support@rtila.com

These details are published identically across every property the company operates, so that a person - or an answer engine - resolving this site to an organisation finds one consistent record.

Who reviews. The editorial team is the in-house staff of RTILA CORPORATION who build and run every listing before it is published. The team is small and named collectively because the reviewers are the same people who sign the build artifacts; a listing's page records the reviewing team and the review date for the current release.

Against what. Every review works through a fixed checklist:

• The listing builds from its published project file with no hand-edited configuration.
• The bot runs to completion on every platform it declares.
• The artifact's SHA-256 digest and exact byte size are published with the listing.
• Every factual claim about third parties carries an access date or a source link.
• Third-party pricing is reported as reports, never restated as fact.
• Each page is useful to a reader who never buys anything.
• The listing's personal-data handling is stated explicitly, including when it is none.
• No listing, and no site-wide trust surface (footer, about page or structured data), carries self-published ratings or reviews, and no rating figure is attributed to a review platform it was not verified on.
• Every own-pricing statement links the product pricing page as its single source and asserts no price, billing model or licence-term detail that the page would need to change to invalidate.

How often re-reviewed. A listing is re-reviewed whenever its configuration version changes, and the whole catalogue is re-reviewed at least quarterly; the updated date on each listing reflects its latest review.

What causes a listing to be pulled. A confirmed malicious behaviour, a broken build on any declared platform, a configuration that diverges from its reviewed project file, or an unresolved responsible-use violation. Removal is by unpublishing the bot's id, which makes every distributed launcher fail closed at its next configuration fetch.