Account member
Confirmed email + safety agreementThe person has an authenticated Y account, confirmed their email, self-attested that they are 18 or older, and acknowledged the current Terms, Privacy Policy, Community Guidelines, and safety rules.
Y uses layers instead of one giant “verified” stamp. Each layer answers one narrow question. That prevents a profile badge from accidentally becoming a promise that someone is safe, qualified, honest, compatible, or trustworthy.
The person has an authenticated Y account, confirmed their email, self-attested that they are 18 or older, and acknowledged the current Terms, Privacy Policy, Community Guidelines, and safety rules.
A public profile, community, opportunity, or resource was checked for platform fit, basic completeness, privacy/safety problems, and required disclosures before becoming visible.
The member chose to upload a government-issued photo ID through private storage. An authorized admin reviewed the document and the profile's identity details. Other members never see the document.
This is a narrow participation/tenure signal that can be used as a contact filter. It gives members a little more friction against brand-new throwaway accounts.
The recipient decides whether to accept, decline, block, or report a contact request. Personal contact details stay hidden until the recipient accepts. Members can also stop new requests or limit them to established accounts.
A real person can still behave badly. A credentialed person can still make a poor offer. A long-time account can still be wrong. That is why Y treats control over access as a stronger safety mechanism than a status badge.
You do not need to wait until you can “prove” a concern to use your own safety controls. Decline or block contact whenever you want. Use Report when conduct may violate Y's rules. For immediate danger or possible crime, use the appropriate emergency service or authority rather than waiting on Y moderation.