Title: Hidefy
Author: vatom
Published: <strong>November 16, 2026</strong>
Last modified: November 16, 2026

---

Search plugins

![](https://s.w.org/plugins/geopattern-icon/hidefy.svg)

# Hidefy

 By [vatom](https://profiles.wordpress.org/vatom/)

[Download](https://downloads.wordpress.org/plugin/hidefy.1.0.0.zip)

 * [Details](https://wordpress.org/plugins/hidefy/#description)
 * [Reviews](https://wordpress.org/plugins/hidefy/#reviews)
 *  [Installation](https://wordpress.org/plugins/hidefy/#installation)
 * [Development](https://wordpress.org/plugins/hidefy/#developers)

 [Support](https://wordpress.org/support/plugin/hidefy/)

## Description

**Try Hidefy online:** [Visit the Hidefy demo site](https://demo.tempato.com). The
public demo uses a shared test environment; do not enter real passwords or sensitive
information.

Hidefy adds configurable login and content-editing security controls to single-site
WordPress installations.

Features include:

 * Custom login URL to reduce automated requests to the default WordPress login 
   address.
 * Optional Cloudflare Turnstile verification on standard WordPress login and registration
   forms.
 * Time-based one-time password (TOTP) two-factor authentication with QR enrollment
   and recovery codes.
 * Role-based content PIN controls for supported post and page editing workflows.
 * Optional public attribution widget, disabled by default and displayed only after
   an administrator explicitly enables it.

These features complement, rather than replace, secure passwords, least-privilege
user roles, WordPress updates, backups, and server-side security controls. A custom
login URL does not guarantee that the login page cannot be discovered. Content PIN
protection is not a replacement for WordPress capabilities and may not cover editing
performed through third-party integrations.

Hidefy does not support WordPress Multisite.

#### External service: Cloudflare Turnstile

Cloudflare Turnstile is optional and is not contacted by this integration until 
the administrator enables the feature. To enable it, the administrator must obtain
a Site Key and Secret Key from Cloudflare.

When enabled on the WordPress login or registration form, the visitor’s browser 
loads the Turnstile JavaScript from https://challenges.cloudflare.com/turnstile/
v0/api.js and communicates with Cloudflare to perform the challenge. The WordPress
server then sends the Turnstile response token and, when available, the visitor’s
IP address to https://challenges.cloudflare.com/turnstile/v0/siteverify for verification.
This data is processed by Cloudflare, not by Tempato. Cloudflare may process additional
browser and request information as described in its policies.

Service provider: Cloudflare, Inc.
 Service information: https://developers.cloudflare.
com/turnstile/ Terms of service: https://www.cloudflare.com/website-terms/ Privacy
policy: https://www.cloudflare.com/privacypolicy/

Cloudflare availability and a working outbound HTTPS connection are required for
verification. Use production keys for public websites. Sandbox is available only
on WordPress local, development, or staging environments (including localhost and
127.0.0.1 installations) after an explicit administrator confirmation in the plugin
settings. No manual PHP configuration is needed.

### Live Demo

Try Hidefy at [https://demo.tempato.com](https://demo.tempato.com). This is a shared
demonstration website for testing the interface and supported features. Do not submit
personal or sensitive information. Demo settings and content may be reset automatically.

### Source Code and Build Information

All custom JavaScript and CSS files shipped with Hidefy are provided in human-readable
form within the plugin ZIP. In particular, `assets/qr-enrollment.js` is the unminified
source for the TOTP QR enrollment display and is loaded directly by WordPress without
a build step. The bundled QR encoder source is `assets/qr.js`; its licensing information
is documented in `LICENSES.txt`.

No npm, webpack, or other build process is required to inspect or run these assets.

### Uninstall and Data Retention

By default, uninstalling Hidefy retains its configuration and user authentication
data, so a later reinstall can recover it. Administrators may opt in to deletion
under Hidefy > Settings > Data retention on uninstall. The choice is used only when
WordPress deletes the plugin, not when it is deactivated or updated.

If deletion is enabled, uninstall removes Hidefy-owned options, PIN hashes, TOTP
secrets, recovery hashes, and temporary challenges. WordPress user accounts, posts
and pages, and the separate Demo Manager plugin’s options and scheduled jobs are
preserved. Back up the site before enabling deletion.

## Installation

 1. Back up your WordPress files and database, and preferably test on a staging site
    first.
 2. In WordPress, open Plugins > Add New Plugin > Upload Plugin, upload the Hidefy 
    ZIP file, and activate it.
 3. Open the Hidefy settings screen in the administrator dashboard.
 4. Enable and configure only the protections you need. For Turnstile, supply your 
    own Cloudflare Site Key and Secret Key.
 5. Keep a second administrator session and hosting-level recovery access available
    when testing custom login URLs and TOTP.
 6. Test login, registration, password reset, TOTP enrollment, recovery codes, and 
    relevant post/page editing workflows before enabling the features on a live site.

## FAQ

### Is Hidefy free?

Yes. Hidefy is free software licensed under GPLv2 or later. Cloudflare Turnstile
is a separate optional third-party service subject to Cloudflare’s own terms.

### Does Hidefy support WordPress Multisite?

No. This release is intended for single-site WordPress installations only.

### Is Cloudflare Turnstile required?

No. Turnstile is optional. If enabled, it requires Cloudflare keys and communication
with Cloudflare’s servers as described above.

### Does Hidefy display a Powered by credit publicly?

Not by default. Public attribution requires an explicit administrator opt-in. The
authentication challenge does not display an unsolicited Powered by credit.

### What if the custom login URL locks me out?

Use WP-CLI, SFTP, or your hosting file manager to deactivate the plugin if necessary.
For temporary recovery, the plugin also recognizes the WP_SECURE_RECOVERY constant
in wp-config.php. Remove any temporary recovery setting after regaining access.

### Can I use Turnstile sandbox keys on a live site?

No. Sandbox mode is intended for access-restricted testing only. Select Sandbox 
and confirm its limitations in Hidefy settings on a local, development, or staging
WordPress environment. No wp-config.php edit is needed. Sandbox does not provide
production bot protection and is blocked on production environments.

### Does Content PIN protect every way to edit content?

Do not assume so. Test the editor, Quick Edit, REST API, and any third-party publishing
integrations in your own environment. WordPress user capabilities remain essential.

### What happens when upgrading from the former WP Secure plugin?

Deactivate the old plugin before activating Hidefy because the plugin directory 
changed. Back up your database and verify that your previous settings, login URL,
and 2FA enrollment work correctly after the upgrade.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“Hidefy” is open source software. The following people have contributed to this 
plugin.

Contributors

 *   [ vatom ](https://profiles.wordpress.org/vatom/)

[Translate “Hidefy” into your language.](https://translate.wordpress.org/projects/wp-plugins/hidefy)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/hidefy/), check out
the [SVN repository](https://plugins.svn.wordpress.org/hidefy/), or subscribe to
the [development log](https://plugins.trac.wordpress.org/log/hidefy/) by [RSS](https://plugins.trac.wordpress.org/log/hidefy/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.0.0

 * Initial WordPress.org submission version of Hidefy.
 * Provide custom login URL, optional Cloudflare Turnstile, TOTP authentication,
   and content PIN features.
 * Load QR enrollment JavaScript through the WordPress script API.
 * Prefix plugin identifiers and support migration of legacy WP Secure settings.
 * Provide human-readable QR enrollment JavaScript and document source availability.
 * Preserve content-list destinations after successful PIN verification for Posts
   and Pages.
 * Remove unsolicited authentication-page attribution and keep public attribution
   opt-in.
 * Document the external Cloudflare service and installation requirements.

## Meta

 *  Version **1.0.0**
 *  Last updated **5 hours ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 6.4 or higher **
 *  Tested up to **7.1.4**
 *  PHP version ** 8.1 or higher **
 * Tags
 * [authentication](https://wordpress.org/plugins/tags/authentication/)[login](https://wordpress.org/plugins/tags/login/)
   [security](https://wordpress.org/plugins/tags/security/)[turnstile](https://wordpress.org/plugins/tags/turnstile/)
   [two factor](https://wordpress.org/plugins/tags/two-factor/)
 *  [Advanced View](https://wordpress.org/plugins/hidefy/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/hidefy/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/hidefy/reviews/)

## Contributors

 *   [ vatom ](https://profiles.wordpress.org/vatom/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/hidefy/)