Trust
Premium, personal verification, page verification, and trusted voting are separate systems. The product keeps those labels distinct so people understand what each badge means.
Personal accounts can vote; publisher pages cannot cast votes.
Verification requires evidence, domain proof, or identity review.
Premium removes supported ads and unlocks product features; it is not verification.
Premium unlocks paid product tools. A verified badge means Bynesh approved a trust review. Public Premium badges are currently unavailable, so payment never appears as a public trust signal.
Regular people can vote when they meet the poll’s access rules. They may see ads and are not treated as trusted voters unless they complete the required verification.
Verified people complete identity trust checks. They can vote, may still see ads if they are not Premium, and can qualify for trusted-voter experiences.
Personal Premium removes supported ads and unlocks Premium product features. It does not buy trusted voting, identity verification, or extra vote weight.
Pages represent organizations, publishers, brands, creators, institutions, or communities. Pages can publish and manage workspaces, but pages do not vote. Voting stays with people.
A verified page has passed the organization review process and can show a verified organization badge. Verification does not remove ads or unlock Premium tools by itself.
A Premium page pays for page-level tools, dashboards, and supported ad removal. Its paid status is not currently shown as a public badge.
Verification can communicate public trust while Premium gives the team additional product tools. The two authorities remain separate.
The page starts with the website people already recognize as the organization’s home.
The verification email must use the same domain as the website, such as press@example.org for example.org.
Bynesh sends a short code from noreply@pluria.org to the official inbox. The page owner or admin enters that code in the app.
The request stays pending until a moderator approves it, rejects it, or asks the page for more information.
Domain email proof is necessary, but it is not the whole approval. A moderator can still ask for more information, check the public website, review supporting evidence, or reject requests that look misleading.
The verification code proves inbox access. Moderator review decides whether the page should receive the public verified badge. Reviewers can approve, reject, revoke, or ask for more information from the page.
This keeps the verified badge meaningful without making the first version of organization verification unnecessarily complicated.
