Privacy Policy

Note: This is a courtesy translation. In case of any discrepancy, the Spanish version prevails.

In summary: MPLock is a local-first product. Your passwords, usernames, notes, and TOTP/2FA keys are stored exclusively on your own computer and are not transmitted to any server. We do not collect usage telemetry or sell data to third parties.

1. Identity of the Data Controller

This website and the MPLock desktop application are operated by Eddie Goudet as an individual (hereinafter, "the Developer" or "MPLock"), domiciled and operating in the Republic of Chile. For any privacy-related matter, you can contact us directly at mplocksoporte@gmail.com.

2. Vault Data (Your Passwords and Secrets)

The fundamental premise of MPLock is the local-first model and strictly local storage:

Strictly Local Storage: All credentials saved in the desktop application reside locally on your device in an encrypted vault file (credentials.enc) protected by AES-256-GCM.
Zero Key Transmission: The master password you use to open your vault, the hashes derived via PBKDF2, and the decrypted data in memory are not sent over the internet or backed up to any server managed by us.
RAM Hygiene: When locking the application or closing your session, sensitive memory buffers are immediately overwritten with zeros using the native zeroize library in Rust.

3. Data Processed During Purchase

For the sale and billing of Pro Lifetime licenses, we use an external payment platform acting as our Merchant of Record (Lemon Squeezy, hereinafter the "Payment Platform"):

Payment Card Data: We do not store or process credit or debit card numbers. That data is managed directly by the Payment Platform under PCI-DSS security standards.
Billing Data: The Payment Platform collects your email address, name, and country/postal code to issue the corresponding tax invoice and handle local taxes (VAT/sales tax). Please consult the privacy policy of that platform (see checkout link).

4. Licensing Infrastructure and Service Providers

When an order is completed on Lemon Squeezy (Merchant of Record), an automated notification (webhook) is sent to our serverless function hosted on Cloudflare Workers:

Processing on Cloudflare Workers: The worker receives the webhook payload, verifying Lemon Squeezy's cryptographic signature. It processes the buyer's email address in volatile memory to sign the license key using the Ed25519 algorithm.
Cloudflare D1 Database (technical idempotency): To prevent duplicate issuances or abuse from webhook retries, Cloudflare D1 records only: order_id (transaction identifier), status (processing state: pending or sent), and updated_at (timestamp). Cloudflare D1 does not store email addresses, names, or banking details.
Email Delivery (Google Gmail API and Brevo): The activation key is sent from mplocksoporte@gmail.com via the Google Gmail API, using exclusively the restricted send scope (gmail.send). MPLock does not access, read, or store other emails in that account. Only if the Gmail API experiences a transient failure is Brevo used as a fallback transactional provider, transmitting the buyer's email address and the license text to complete delivery.
Web Hosting and Ephemeral Logs (Vercel): The static landing page and technical documentation are hosted on Vercel. Vercel generates ephemeral technical network traffic logs (IP address, user agent, and HTTP status code) solely for DDoS mitigation, perimeter security, and operational stability.
Installer Downloads (GitHub Releases): Executable binaries and installers for MPLock are distributed through GitHub Releases (GitHub / Microsoft), subject to their download and data transfer policies.

5. Data Retention Policy

Data retention is governed by data minimization principles and timeframes strictly limited to technical or legal purposes:

Lemon Squeezy (Merchant of Record): Retains billing, purchase, and tax obligation records according to the platform's privacy policy (Lemon Squeezy Privacy Policy).
Cloudflare D1: Idempotency records (order_id, status, and timestamp) are retained as long as necessary to verify activation of the purchased Pro license and prevent fraudulent re-issuances.
Server Logs (Vercel and Cloudflare): HTTP request and perimeter security logs are retained according to each provider's privacy policy (Vercel Privacy Policy and Cloudflare Privacy Policy).
Transactional Email Logs (Google and Brevo): Technical transmission and delivery logs are retained according to each provider's privacy policy (Google Privacy Policy and Brevo Privacy Policy).
Gmail Sent Folder (Support and License Delivery): Emails sent through the Gmail API remain stored in the "Sent" folder of the mplocksoporte@gmail.com account containing the buyer's email address and generated license key. These emails have a defined retention period of 12 months from the date of purchase, and are manually deleted by the controller at the end of that period.
Local Application Vault: The encrypted database and license key reside exclusively on the local storage of the user's computer indefinitely, until the user decides to delete the files or uninstall the application.

6. Cookies and Analytics on the Landing Page

In line with our privacy principles:

This website does not use Google Analytics, tracking scripts, or third-party advertising pixels.
We do not use cross-site tracking cookies. Only your browser's local storage (localStorage) is used to remember your visual preference between Dark Mode and Light Mode.

7. Managing and Inquiring About Your Data

If you wish to request access, correction, or deletion of data associated with the purchase of your license:

Payment and billing data (Lemon Squeezy): Financial, tax, and billing information is managed and retained exclusively by Lemon Squeezy as the Merchant of Record. Requests regarding such data should be directed to them under the Lemon Squeezy Privacy Policy.
Data managed by MPLock (license issuance): To request access, rectification, or deletion of your license records in our technical systems (buyer email and order number), write to mplocksoporte@gmail.com. In order to verify the holder's identity, requests received will be answered only to the email address used for the purchase.
Response timeframe: We will respond to and process your request within a maximum of 30 calendar days from receipt of your message.

8. Changes to This Policy

This text may be updated periodically to reflect technical adjustments, improvements, or service updates. Any changes will be published directly on this page indicating the date of the latest update.