=== ElliePass ===
Contributors: hellowelliepass
Tags: verification, identity verification, age verification, community, privacy
Requires at least: 6.5
Tested up to: 7.1
Requires PHP: 8.1
Stable tag: 0.2.9
License: GPLv2 or later
License URI: https://www.gnu.org/licenses/gpl-2.0.html

Privacy-focused human, age, identity, and location verification for WordPress communities and sites.

== Description ==

ElliePass lets a WordPress site require verification before selected member
actions or protected content are allowed.

Supported WordPress guards include:

* New account activation
* Log in
* Create posts
* Create comments
* Access protected content

Verification requirements are configured in ElliePass Community Admin and can
include Human verification, minimum age, Verified Identity, Current location,
and ID-verified location.

Members can reuse valid ElliePass verification when it already satisfies the
site's requirements.

ElliePass handles the verification process. Your WordPress site receives the
qualification information needed to enforce its policy instead of collecting
verification documents itself.

= Protected content =

When Access protected content is guarded, ElliePass can hide the full post
body and discussion until the member qualifies. Administrators can optionally
show a plain-text preview of None, 25, 50, or 100 words.

= Documentation =

Setup guide:
https://elliepass.com/community/wordpress/setup

FAQ:
https://elliepass.com/community/wordpress/faq

== Installation ==

1. Install and activate the ElliePass plugin.
2. In ElliePass Community Admin, add your WordPress site and generate connection credentials.
3. In WordPress, open Settings → ElliePass.
4. Enter the ElliePass API URL, Community Key, and Community Secret.
5. Enable ElliePass and save.
6. Configure verification requirements and guarded actions in ElliePass Community Admin.

== Frequently Asked Questions ==

= Does every WordPress user have to verify? =

No. Verification is required only when the site's ElliePass policy applies to
the action or content the member is attempting to use.

= Does WordPress receive identity documents? =

No. ElliePass handles verification. WordPress receives the qualification
information required to enforce the configured policy.

= Does ElliePass replace WordPress permissions? =

No. WordPress continues to determine what a user is authorized to do.
ElliePass adds verification requirements to selected actions WordPress already
allows.

= Can existing verification be reused? =

Yes. Valid ElliePass verification can be reused when it satisfies the current
site requirements.

== Changelog ==

= 0.2.9 =
* Added true in-page verification prompts for guarded WordPress actions.
* Added new-account activation and guarded login flows.
* Added protected-content enforcement for post bodies and discussions.
* Added protected-content previews with configurable word limits.
* Added policy synchronization and local qualification caching.
* Added community-paid and member-paid verification handoff support.

== Upgrade Notice ==

= 0.2.9 =
Initial public ElliePass for WordPress release.
