Workplace transparency with privacy built into the architecture.

Travaix requires an account to submit a review, but published reviews are intentionally detached from user accounts after submission. A review does not store a user ID, author ID, account ID, or public profile link.

This means Travaix can enforce basic rules, such as one review per company, without displaying or storing direct published-review ownership.

In the future, Travaix will support Verified Employee reviews. A person may verify that they work, or worked, at a company. Future reviews for that company can then carry a Verified Employee signal.

Verification is attached to the person-company relationship, not to a public author profile. The published review still does not show who wrote it.

There is an important practical limitation: if only a small number of people are verified at a company, the possible group of authors can be narrowed. For example, if five people are verified and five verified reviews exist, someone may understand that the reviews came from that verified group, but they still would not know which person wrote which specific review from the public product.

Travaix is designed so reviewer identity is not visible in the product. Public users, companies, and admins should not be able to see who wrote a specific published review.

Like any online service, Travaix may be required to respond to valid legal processes, court orders, or abuse investigations. Depending on the request and applicable law, account data, report metadata, or participation records may need to be reviewed or disclosed.

The important distinction is that Travaix does not make reviewer identity visible in the normal product, and the review architecture avoids storing direct published-review ownership.