jonvessot

<p>VESSOT Secure Portable Data provides a secure way to store and retrieve encrypted data via the VESSOT API. All encryption happens client-side before data is transmitted, ensuring true zero-knowledge data storage.</p>
<p>You need to create an account at https://vessot.tech/ before you can use this plugin.</p>
<h3>Features</h3>
<ul>
<li>Client-side AES-256-GCM encryption</li>
<li>Store, retrieve, update, and destroy encrypted data</li>
<li>Support for nested objects and arrays</li>
<li>WordPress native HTTP API (no external dependencies)</li>
</ul>
<h3>Requirements</h3>
<ul>
<li>PHP 8.2 or higher</li>
<li>OpenSSL PHP extension</li>
</ul>
<h3>Setup</h3>
<p>Read about the simple account creation steps at https://vessot.tech/how-it-works.</p>
<p>Technical implementation is quick and easy – see the setup guide at https://vessot.tech/setup.</p>
<h3>Configuration</h3>
<p>The plugin requires two environment variables to be set at the server level. This approach ensures credentials never touch your filesystem or version control.</p>
<h3>Required Environment Variables</h3>
<h4>VESSOT_INT_TOKEN</h4>
<p>Your VESSOT API integration token for authentication.</p>
<h4>VESSOT_CRYPT_KEY</h4>
<p>A 32-byte encryption key for client-side encryption.</p>
<h3>Generating an Encryption Key</h3>
<p>You can generate a secure encryption key using the plugin’s helper function. Run this once in your WordPress environment:</p>
<pre><code>`php
</code></pre>
<p>$vessotData = vessot_secure_portable_data();<br />
$encryptionKey = $vessotData->cryptKeyGenerate(); // Copy this value to use as VESSOT_CRYPT_KEY<br />
    `</p>
<h3>Setting Environment Variables</h3>
<p>Choose the method that matches your server setup:</p>
<h4>Apache</h4>
<p>Add to your virtual host configuration or <code>.htaccess</code>:</p>
<pre><code>`apache
</code></pre>
<p>SetEnv VESSOT_INT_TOKEN “your-integration-token-here”<br />
SetEnv VESSOT_CRYPT_KEY “your-encryption-key-here”<br />
    `</p>
<h4>Nginx with PHP-FPM</h4>
<p>Add to your PHP-FPM pool configuration (usually <code>/etc/php/8.2/fpm/pool.d/www.conf</code>):</p>
<pre><code>`ini
</code></pre>
<p>env[VESSOT_INT_TOKEN] = your-integration-token-here<br />
env[VESSOT_CRYPT_KEY] = your-encryption-key-here<br />
    `</p>
<p>Then add to your Nginx server block:</p>
<pre><code>`nginx
</code></pre>
<p>location ~ .php$ {<br />
    fastcgi_param VESSOT_INT_TOKEN $VESSOT_INT_TOKEN;<br />
    fastcgi_param VESSOT_CRYPT_KEY $VESSOT_CRYPT_KEY;<br />
    # … other fastcgi_param directives<br />
}<br />
    `</p>
<h4>Docker</h4>
<p>Add to your <code>docker-compose.yml</code>:</p>
<pre><code>`yaml
</code></pre>
<p>services:<br />
  wordpress:<br />
    environment:<br />
      – VESSOT_INT_TOKEN=your-integration-token-here<br />
      – VESSOT_CRYPT_KEY=your-encryption-key-here<br />
    `</p>
<p>Or use a <code>.env</code> file (excluded from version control):</p>
<pre><code>`bash
</code></pre>
<p>VESSOT_INT_TOKEN=your-integration-token-here<br />
VESSOT_CRYPT_KEY=your-encryption-key-here<br />
    `</p>
<h4>Shared Hosting / cPanel</h4>
<p>Many hosting providers offer environment variable management through their control panel. Check your hosting provider’s documentation for “Environment Variables” or “PHP Configuration”.</p>
<h4>Local Development</h4>
<p>For local development, you can use:</p>
<p><strong>Option 1: System environment variables</strong><br />
    <code>bash<br />
export VESSOT_INT_TOKEN="your-dev-token"<br />
export VESSOT_CRYPT_KEY="your-dev-key"</code></p>
<p><strong>Option 2: PHP-FPM configuration</strong> (see Nginx section above)</p>
<h3>Security Best Practices</h3>
<ul>
<li>Use different tokens and keys for each environment (development, staging, production)</li>
<li>Never commit environment variables to version control</li>
<li>Limit access to server configuration files</li>
</ul>
<h3>Usage</h3>
<h3>Basic Example</h3>
<pre><code>`php
</code></pre>
<p>// Get an instance<br />
$vessotData = vessot_secure_portable_data();</p>
<p>// Store encrypted data<br />
$result = $vessotData->store(‘your_unique_storage_key’, [<br />
    ‘theme’ => ‘dark’,<br />
    ‘notifications’ => true,<br />
    ’email’ => ‘user@example.com’<br />
]);</p>
<p>// Retrieve and decrypt data<br />
$result = $vessotData->show(‘your_unique_storage_key’);<br />
if ($result[‘success’]) {<br />
    $settings = $result[‘value’];<br />
    echo $settings[‘theme’]; // ‘dark’<br />
}</p>
<p>// Update data<br />
$result = $vessotData->update(‘your_unique_storage_key’, [<br />
    ‘theme’ => ‘light’,<br />
    ‘notifications’ => false,<br />
    ’email’ => ‘user@example.com’<br />
]);</p>
<p>// Partial update (update specific attributes)<br />
$result = $vessotData->update(‘your_unique_storage_key’, null, [<br />
    ‘theme’ => ‘light’<br />
]);</p>
<p>// Retrieve specific attribute<br />
$result = $vessotData->show(‘your_unique_storage_key’, ‘theme’);</p>
<p>// Delete data<br />
$result = $vessotData->destroy(‘your_unique_storage_key’);<br />
    `</p>
<h3>Using in WordPress Hooks</h3>
<pre><code>`php
</code></pre>
<p>// Store user preferences on profile update<br />
add_action(‘profile_update’, function($user_id) {<br />
    $vessotData = vessot_secure_portable_data();<br />
    $preferences = get_user_meta($user_id, ‘preferences’, true);</p>
<pre><code>$result = $vessotData->store("user_preferences_{$user_id}", $preferences);

if (!$result['success']) {
    error_log('Failed to store preferences: ' . $result['error']);
}
</code></pre>
<p>});</p>
<p>// Retrieve preferences on login<br />
add_action(‘wp_login’, function($user_login, $user) {<br />
    $vessotData = vessot_secure_portable_data();<br />
    $result = $vessotData->show(“user_preferences_{$user->ID}”);</p>
<pre><code>if ($result['success']) {
    update_user_meta($user->ID, 'preferences', $result['value']);
}
</code></pre>
<p>}, 10, 2);<br />
    `</p>
<h3>API Reference</h3>
<h3>store($key, $value)</h3>
<p>Store encrypted data with a unique key.</p>
<p><strong>Parameters:</strong><br />
– <code>$key</code> (string): Unique identifier for the data<br />
– <code>$value</code> (mixed): Data to encrypt and store (can be string, or data array)</p>
<p><strong>Returns:</strong> Array with <code>success</code>, <code>error</code>, <code>code</code>, and <code>value</code> keys</p>
<h3>show($key, $attribute = null)</h3>
<p>Retrieve and decrypt stored data.</p>
<p><strong>Parameters:</strong><br />
– <code>$key</code> (string): Unique identifier for the data<br />
– <code>$attribute</code> (string|null): Optional specific attribute to retrieve</p>
<p><strong>Returns:</strong> Array with <code>success</code>, <code>error</code>, <code>code</code>, and <code>value</code> keys</p>
<h3>update($key, $value = null, $attributes = null)</h3>
<p>Update existing encrypted data.</p>
<p><strong>Parameters:</strong><br />
– <code>$key</code> (string): Unique identifier for the data<br />
– <code>$value</code> (mixed): New value (for full update)<br />
– <code>$attributes</code> (array|null): Specific attributes to update (for partial update)</p>
<p><strong>Returns:</strong> Array with <code>success</code>, <code>error</code>, <code>code</code>, and <code>value</code> keys</p>
<h3>destroy($key, $attributes = null)</h3>
<p>Delete stored data.</p>
<p><strong>Parameters:</strong><br />
– <code>$key</code> (string): Unique identifier for the data<br />
– <code>$attributes</code> (mixed|null): Optional specific attributes to delete</p>
<p><strong>Returns:</strong> Array with <code>success</code>, <code>error</code>, <code>code</code>, and <code>value</code> keys</p>
<h3>cryptKeyGenerate()</h3>
<p>Generate a new encryption key. Returns empty string if key already exists in environment.</p>
<p><strong>Returns:</strong> Encryption key or empty string</p>
<h3>External Services</h3>
<p>This plugin connects to the VESSOT API (https://vessot.tech/api) to store and retrieve encrypted data.</p>
<h3>What is VESSOT?</h3>
<p>VESSOT is a third-party encrypted data storage service that provides zero-knowledge data storage. The service is provided by VESSOT.</p>
<h3>What data is sent?</h3>
<p>The plugin sends the following data to the VESSOT API:</p>
<ul>
<li><strong>Encrypted data values</strong>: All data is encrypted client-side using AES-256-GCM encryption before transmission. The VESSOT API only receives encrypted ciphertext and never has access to your encryption keys or unencrypted data.</li>
<li><strong>Data keys</strong>: Unique identifiers you specify for each piece of data (e.g., “user_settings”, “preferences”).</li>
<li><strong>Authentication token</strong>: Your VESSOT_INT_TOKEN for API authentication.</li>
</ul>
<h3>When is data sent?</h3>
<p>Data is transmitted to the VESSOT API when you use any of these functions:</p>
<ul>
<li><code>vessot_secure_portable_data()->store()</code> – Sends encrypted data to be stored</li>
<li><code>vessot_secure_portable_data()->show()</code> – Retrieves encrypted data</li>
<li><code>vessot_secure_portable_data()->update()</code> – Sends encrypted data updates</li>
<li><code>vessot_secure_portable_data()->destroy()</code> – Requests data deletion</li>
</ul>
<h3>Service Information</h3>
<ul>
<li><strong>Service Provider</strong>: VESSOT</li>
<li><strong>Service Website</strong>: https://vessot.tech</li>
<li><strong>Terms of Service</strong>: https://vessot.tech/terms-conditions</li>
<li><strong>Privacy Policy</strong>: https://vessot.tech/privacy-policy</li>
<li><strong>API Documentation</strong>: https://vessot.tech/setup</li>
<li><strong>WordPress Setup Guide</strong>: https://vessot.tech/wordpress</li>
</ul>
<h3>Account Requirement</h3>
<p>You must create a VESSOT account at https://vessot.tech before using this plugin. See https://vessot.tech/how-it-works for account creation steps and https://vessot.tech/wordpress for WordPress-specific setup instructions.</p>
<h3>Security Notes</h3>
<ul>
<li>All encryption happens client-side before transmission</li>
<li>The VESSOT API never has access to unencrypted data or encryption keys</li>
<li>Environment variables are set at the server level and never touch the filesystem</li>
<li>Each environment should have its own unique tokens and keys</li>
<li>Server configuration changes require appropriate restart (Apache reload, PHP-FPM restart, etc.)</li>
</ul>
<h3>Support</h3>
<p>For issues and support, visit: https://vessot.tech</p>
<h3>License</h3>
<p>This plugin is licensed under the GNU General Public License v2 or later.</p>
<p>This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.</p>
<p>This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.</p>
<p>You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</p>
<h3>Author</h3>
<p>VESSOT – https://vessot.tech</p>


VESSOT Secure Portable Data

VESSOT Secure Portable Data - WordPress Plugin Zero visibility data storage with client-side encryption via the VESSOT platform.

Zestard Technologies

<p>This plugin will store data which is submitted by Contact form 7 and it will provide various features to manage it with different ways.</p>
<h3>Features</h3>
<ul>
<li>
<p>To work with this initially user needs active version of Contact form 7.</p>
</li>
<li>
<p>All submitted entries of Contact form 7 will be display.</p>
</li>
<li>
<p>User can perform various actions like bookmark, read/unread, export data into PDF, CSV and Excel format.</p>
</li>
<li>
<p>User can use datewise filter entries of Contact form 7.</p>
</li>
<li>
<p>User can display submitted entries on Frontend by using Shortcode.</p>
</li>
</ul>


Admin side data storage for Contact Form 7

This plugin will helps you to store and manage data of Submitted Contact Form 7 entries.

VESSOT Secure Portable Data vs Admin side data storage for Contact Form 7