Trust
Trust and verification at Pluria
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.
Payment can improve access. Verification proves trust signals.
A Premium badge means the person or page has an active paid product tier. A verified badge means Pluria approved a trust review. They can appear together, but one does not replace the other.
People, voting, and trusted voters
Regular accounts
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
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
Personal Premium removes supported ads and unlocks Premium product features. It does not buy trusted voting, identity verification, or extra vote weight.
Pages, verification, and Premium
Pages represent organizations, publishers, brands, creators, institutions, or communities. Pages can publish and manage workspaces, but pages do not vote. Voting stays with people.
Verified page
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.
Premium page
A Premium page pays for page-level tools, dashboards, and supported ad removal. It can show a Premium badge, separate from the verified badge.
Verified and Premium
The strongest public posture is usually both: verification tells people the page is legitimate, and Premium gives the team the tools to operate professionally.
How organization verification works
Add the public website
The page starts with the website people already recognize as the organization’s home.
Use a matching official email
The verification email must use the same domain as the website, such as press@example.org for example.org.
Enter the Pluria code
Pluria sends a short code from noreply@pluria.org to the official inbox. The page owner or admin enters that code in the app.
Wait for moderator review
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.
Manual review protects the badge
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.