Privacy Policy

Choose the section for the service or product you use. Website & Services covers hmdia.com, directory listings, purchases, and client services; the other sections explain the relevant software. The product sections supplement the website notice for purchases and support. For data held by an independent website using our plugins, contact that website’s owner.

Website & Services

Last updated: October 19, 2026

HMDIA, using the business name HMDIA Design & Marketing in Ontario, Canada, operates hmdia.com. This section explains personal information handled for website visits, directory listings, customer accounts, purchases, support, web design, and marketing services. The other tabs explain the corresponding software products. Installing our software on an independent website does not make HMDIA the operator of that website.

This notice explains our practices; reading it or browsing the website is not, by itself, consent to every optional use of your information.

1. Information we collect and why

  • Accounts and inquiries: names, email addresses, login and account details, messages, attachments, and information you choose to provide, to manage accounts, respond, and provide requested services.
  • Directory listings: business names, descriptions, contact details, locations, categories, logos, images, and submitted links, to review and publish listings.
  • Purchases and licensing: customer and billing details, order and subscription records, transaction references, licence keys, activated site or browser identifiers, and product/version information, to deliver purchases, renew subscriptions, verify entitlements, prevent abuse, and maintain required records.
  • Website and security activity: IP addresses, browser/device details, requested pages and URLs, referrers, timestamps, approximate country, browser/session identifiers, authentication events, and relevant account or administrative activity, to understand traffic and protect the website. URLs can contain query parameters; avoid placing confidential information in a URL or support attachment.
  • Marketing measurement: campaign interactions, conversion events, cookie or similar identifiers, and browsing activity associated with our website, to measure advertising and website performance.

2. Public listings and submitted content

Information published in a directory listing is publicly accessible and may be indexed or copied by search engines and other visitors. Submit only information you are authorised to publish. Contact us to correct or remove a listing. Removing a listing here does not immediately remove independent search caches or third-party copies. HMDIA remains responsible for its own handling of personal information under applicable law.

3. Google Sign-In on hmdia.com

If you choose Google Sign-In, your browser connects to Google and provides a Google identity credential to this website. We verify it to sign you in, link your account, or help create the account you request. The information processed includes the Google account identifier, email address and verification status, and available name details; a Workspace domain may also be processed when present.

The website keeps a hashed Google-account identifier linked to the WordPress user, connection details, and relevant security events. Registration can retain the supplied name/email in the user account. The Google ID credential is not deliberately stored as a permanent credential, and this sign-in feature does not request access to Gmail or Google Drive. Temporary security challenges and a browser cookie protect the flow. You can disconnect the link using the available account controls or contact us; disconnecting does not delete your website account or records we must retain. See Google’s Privacy Policy.

4. Cookies, analytics, and advertising

WordPress and checkout functions use cookies or browser storage for sign-in, security, carts, sessions, and preferences. HMDIA Traffic & IP Security also uses the first-party hmdia_vsl_vid visitor cookie, with a configured lifetime of up to one year, and hmdia_vsl_bsid session cookie, with a 30-minute lifetime that may be renewed with activity. These distinguish browsers and visits; they do not identify a unique person with certainty. Blocking them does not necessarily prevent server-side request or security logging.

We use HMDIA Traffic & IP Security and Independent Analytics on our WordPress website for traffic reporting. We also use Google Tag Manager to manage website tags and Google Analytics/Google Ads for measurement and advertising-related functions. Google tags can send page, device, identifier, campaign, and conversion information to Google. Google’s processing is described in its Privacy Policy; Google Tag Manager is a tag-management tool, not a separate promise that no other tracking occurs.

Your choices: you can block or delete cookies through your browser, manage Google ad personalisation through My Ad Center, and use Google’s Analytics opt-out browser add-on where supported. These controls have different effects and do not remove necessary security logs or records already retained. The HMDIA browser-view tracker skips collection when it detects Do Not Track or Global Privacy Control; that does not mean every provider or server log responds to those signals. Where a separate consent or preference control is presented, use it to manage the processing it covers. Contact us about other applicable objection or opt-out rights.

5. Providers and sharing

We disclose information as needed to deliver the services you request, operate and secure the website, meet legal obligations, or respond to a lawful business transfer. Categories and examples include:

  • Payments and commerce: payment providers such as Stripe process payment details and transactions. HMDIA uses FluentCart software on its website for orders, subscriptions, and licences. We receive payment status and transaction references; do not send complete card details to our support team.
  • Hosting, delivery, and security: hosting and backup providers, Cloudflare, and website security services such as MalCare/WP Remote process requests and technical/security information.
  • Google services: Google Sign-In when selected, and Google advertising/measurement services as described above.
  • Email and support: email-delivery providers and authorised personnel or contractors process messages, requests, and relevant service information. External email or SMS services enabled on customer websites are covered in the product section and that website’s own notice.
  • Public directory users: the information you choose to publish in a listing.

We do not sell personal information for money. Website advertising or measurement tools can disclose identifiers and activity to their providers. Where applicable law treats a disclosure as a sale or sharing for targeted advertising, the corresponding legal rights still apply. This website advertising description does not change the separate restrictions on HMDIA Note extension data.

HMDIA remains accountable for personal information under its control when a provider processes it on our behalf. Independent websites and services may have their own purposes and policies; review those notices when using them.

6. Retention

As of the update date, our website’s configured retention periods are:

  • Stored submissions in the built-in contact form: 30 days, with deletion performed by the scheduled cleanup. Email copies and ongoing support correspondence are separate records.
  • Traffic & IP Security visitor logs: 365 days; its sign-in security logs: 30 days; its administrative activity logs: 7 days.
  • Deactivated-licence activation history: 90 days, after which it becomes eligible for scheduled cleanup. Active activation records remain while needed to administer the licence.

Account and listing information remains while the account, listing, or related relationship is maintained or until removal is requested and appropriate. Purchases, invoices, payment disputes, support matters, backups, and other security or analytics records have separate retention based on their purpose, applicable legal/accounting duties, and the need to resolve claims or incidents. Those records are not all deleted by the short-term cleanup settings above. Contact us for the period or criteria applicable to a particular record. We do not retain personal information indefinitely simply because it was collected.

7. Marketing and consent choices

We send promotional communications where we have the consent or other lawful basis required for them. You can unsubscribe using the message’s unsubscribe mechanism or contact us. Essential account, order, renewal, security, and service communications may still be sent. Withdrawing consent may prevent a requested optional feature from operating, but does not automatically erase information that must lawfully be retained.

8. Security and international processing

We use reasonable technical, administrative, and access safeguards. No system guarantees absolute security. HMDIA operates in Ontario, Canada, while hosting, payment, email, Google, Cloudflare, and other providers may process information in Canada, the United States, or other countries. Foreign laws and lawful government-access rules may differ. We use appropriate safeguards for information transferred under our control as required by applicable law.

9. Access, correction, deletion, and complaints

You may request access to or correction of personal information under our control, ask about retention, withdraw applicable consent, request deletion where available, or raise a privacy complaint. Additional rights, including objection, restriction, portability, or advertising choices, depend on your location and applicable law. We may verify identity and explain lawful exceptions or records that must remain. Account deletion does not necessarily erase invoices, security records, backups, or independent third-party copies immediately.

Contact our privacy contact using the details below. We will respond within the period required by applicable law and explain available review or complaint options. You can also contact the Office of the Privacy Commissioner of Canada or the regulator responsible for your jurisdiction. If the information is on an independent website using an HMDIA plugin, contact that website’s owner first.

10. Children and changes

Website accounts and purchases are subject to the eligibility requirements in our Terms. This website is not directed to children under 13. HMDIA Note has its own age-related terms and privacy section. Contact us if a child has supplied personal information without the required consent.

We update this notice when practices change and show the revision date. Material changes will be communicated where required. We obtain fresh consent where required before introducing a materially different use; continued browsing alone is not a substitute for that consent.

11. Contact

Privacy contact — HMDIA Design & Marketing
Ontario, Canada
Email: [email protected]
Contact form

HMDIA Login & Registration and Add-ons

Last updated: October 19, 2026

This policy explains how HMDIA Login & Registration (the “Plugin”), its optional Pro add-on, and related HMDIA add-ons handle personal information. It supplements the HMDIA website Privacy Policy.

The Plugin runs on websites operated by independent site owners. The owner of a website using the Plugin decides which features to enable, which information to request, how long to keep it, and which outside services to connect. If you registered, signed in, or submitted a form on such a website, contact that website’s owner about your information and read its privacy policy. HMDIA does not receive your account or form information merely because the website uses the free Plugin.

Information handled by the Plugin

Depending on the website’s settings and the information you provide, the Plugin may process:

  • Account and registration details: username, name, email address, password handled through WordPress, and optional phone number, custom fields, verification status, and records of accepting site terms.
  • Login and account security details: sign-in and password-reset requests, verification codes, session information, and technical information used to prevent abuse. With applicable Pro features, this may include two-factor authentication settings, passkey details, recovery information, authentication events, timestamps, browser information, and a masked IP address or IP-derived hash.
  • Contact form submissions: name, email address, subject, message, custom fields, submission time, and related administrative status, if the site enables the built-in Contact Form.
  • Registration documents: files submitted through an enabled registration form. Their content depends on the fields the site owner chooses to request.

The Plugin uses this information to create and manage WordPress accounts, verify registrations, process sign-ins and password resets, provide selected security features, deliver account messages, process contact submissions, and help the site owner prevent spam and unauthorized access. Anti-abuse checks may reject a form submission or sign-in attempt.

Where information is stored

Account information is stored in the website’s WordPress database. Contact submissions can be stored in a Plugin-managed table if the site owner enables the Contact Form and leaves submission storage on. Temporary verification and reset information is kept for the period needed to complete those actions. Pro features and other add-ons may store additional security or access records on the website.

Current private registration-document storage encrypts new protected uploads on the website. Older document uploads may require a separate migration by the site owner; copies previously exposed through public media URLs or external caches may remain until the owner removes them. Website owners are responsible for their hosting, backups, access permissions, and any copies held outside WordPress.

Cookies and browser storage

The Plugin relies on WordPress authentication cookies for sign-in. It can also set a temporary cookie for the password-reset process. Some interface preferences, such as the currently selected account or settings section, may be saved in the browser’s session storage. If a site enables an external CAPTCHA provider, that provider may use its own browser technologies under its privacy policy.

Optional external services and add-ons

The following connections occur only when the relevant feature is configured or used:

  • Google reCAPTCHA v3 or Cloudflare Turnstile: the visitor’s browser connects to the selected provider. The provider may receive the visitor’s IP address and browser/request information. The website also sends a challenge token, the provider’s secret key, and the visitor’s IP address to the provider’s verification API. These services help assess automated submissions. See Google’s Privacy Policy or Cloudflare’s Privacy Policy.
  • Twilio SMS through Pro: if the website administrator configures Twilio and enables SMS verification, the website sends the recipient number, configured sender, security-code message, and Twilio account credentials to Twilio. See Twilio’s Privacy Notice. Your mobile provider may also process SMS delivery information.
  • Pro licensing and updates: the separately installed Pro add-on contacts HMDIA to activate or check a license and obtain eligible updates. These requests include the website URL, license key, product and version details, and an activation identifier when available. License activation also includes WordPress and PHP versions. HMDIA processes this information to verify entitlement and deliver updates. The free Core Plugin does not send licensing or telemetry requests to HMDIA.
  • Website email and media services: account and contact messages are sent using the website’s WordPress email configuration, which may involve a separate email provider. If an administrator chooses externally hosted logos or backgrounds, a visitor’s browser or email client may request those files from the chosen host.

The sections below explain additional data handling for Google Sign-In and the related add-ons. Website owners must describe the features and providers they actually enable in their own privacy notices.

Google Sign-In

When a site enables Google Sign-In, the visitor’s browser loads Google Identity Services from Google. Google receives the browser/request information involved in that connection. If the visitor chooses to sign in, link, or register, the website receives a Google ID credential and verifies its signature using Google’s public certificates. The processed claims include the Google account identifier, email and verification status, available name details, and any Workspace domain supplied with the credential.

The website stores a hashed Google-account identifier linked to the WordPress account, a connection timestamp/revision, and relevant security events. Registration may save the provided name and email as account details. ID credentials are not deliberately saved as permanent credentials; the feature does not request Gmail or Drive access and does not send this Google identity information to HMDIA’s licensing server. It uses a secure browser-session cookie, short-lived challenges (up to five minutes), and a registration proof (up to 30 minutes). The account link remains until disconnected or the website account is deleted, subject to separate logs/backups. Website owners and users can use the available disconnect controls; disconnecting does not itself delete the WordPress account or revoke all authorisations at Google. See Google’s Privacy Policy and Google Account connections.

Traffic & IP Security

When enabled, this add-on can store full IP addresses, requested URLs (including query parameters if the owner has not enabled stripping), referrers, timestamps, approximate country, browser/device details, browser/session identifiers, user identifiers where available, and access or security outcomes in the website’s database. Optional sign-in and administrative activity logging adds records for its enabled categories. This is not necessarily anonymous information.

Browser-view tracking can set hmdia_vsl_vid for up to one year and hmdia_vsl_bsid for 30 minutes, renewed with activity. The browser tracker skips requests when it detects Do Not Track or Global Privacy Control; server-side security logging is separate. Owners configure exclusions and retention. Country lookup may use Cloudflare-provided country information or, if the owner selects ipwho.is, send a visitor IP address to that provider. Temporary Collection Diagnostics records aggregate reason counters for troubleshooting; it is separate from the ordinary visitor logs and its collection automatically stops after the selected 24-hour run. Ending a run does not itself delete all saved counters. The owner can clear them.

Post Submission

When enabled, this add-on processes submitted post titles, content, custom fields, uploaded media, author/account identifiers, status, and related submission information. Data is stored in the website’s WordPress posts, metadata, and media systems according to the configured form. Published submissions may become public and indexed. Notification messages use the website’s email provider, and media may be copied to a storage provider configured by that website. Owners control publication, permissions, retention, deletion, and any backup copies.

WooCommerce Checkout Verification

When installed and enabled, this add-on processes the checkout email address and/or phone number to send a one-time code and confirm control of that contact method before the order proceeds. Email uses the website’s mail configuration; SMS uses its configured Twilio integration. Delivery providers receive the destination and code message. The add-on’s temporary verification tables hold hashed destinations, code hashes, session-bound challenge identifiers, expiry and attempt information, and hashed rate-limit identifiers derived from the session, destination, and connecting IP address.

A private verification browser cookie can last up to two days and is used with the WooCommerce session. A successful verification proof lasts 30 minutes; code expiry is configured by the site. Expired verification and rate-limit records are removed by scheduled cleanup after a short grace period. The original billing contact details may still be retained in WooCommerce orders and provider delivery records under the merchant’s policies. Checkout verification does not sign the customer into a WordPress account or verify legal identity. HMDIA does not receive these checkout details merely because the add-on is installed.

Retention and deletion

The website owner controls WordPress user accounts and most Plugin settings. If the built-in Contact Form is enabled, its default submission-retention setting is 180 days; the owner can change this to 30, 90, or 365 days, choose to keep submissions until deleted, or turn off submission storage. Expired submissions are removed when the Plugin’s cleanup runs. Pro activity records have separate configurable retention. Temporary authentication records expire, while accounts and other records may remain until the site owner deletes them. Backups and third-party providers may have separate retention periods.

The Plugin integrates with WordPress personal-data export and erasure tools for some Plugin-managed records. Those tools do not automatically remove every WordPress user account, all security information, every backup, or copies held by external providers. Removing the Plugin also does not automatically delete WordPress users; Plugin data cleanup on uninstall is an administrator choice.

For information HMDIA receives directly through Pro licensing, purchases, or support, we retain it for the purposes described in the HMDIA website Privacy Policy and as needed for applicable legal obligations.

Your choices and requests

If your information is held on a website using the Plugin, contact that website’s owner to request access, correction, export, or deletion, or to ask which optional features and providers are active. The owner may need to verify your identity and may have legal reasons to retain certain information.

For information you have provided directly to HMDIA, including Pro license or support information, contact us through HMDIA’s contact page. Privacy rights and available choices depend on your location and the circumstances of the request.

Security and international processing

The Plugin uses WordPress authentication and access controls and includes protections for selected sensitive records. The security and location of information stored on an independent website also depend on that website’s hosting, configuration, administrators, email providers, backups, and connected services. Optional providers and HMDIA license services may process information in countries other than yours; consult their policies and the website owner’s policy for details.

Changes to this policy

We may update this policy as the Plugin or its optional services change. The latest version and its update date will be posted here. Questions about HMDIA’s handling of information can be sent through our contact page.

HMDIA Note

Effective date: August 20, 2026
Last updated: October 19, 2026

HMDIA Note is a browser extension developed and operated by HMDIA (“HMDIA,” “we,” “us,” or “our”), located in Ontario, Canada.

This Privacy Policy explains how HMDIA Note handles information when you use the Chrome, Chromium-based, or Firefox versions of the extension.

This Policy applies only to HMDIA Note. It does not cover the HMDIA business directory, other HMDIA plugins or products, or third-party websites and services.

1. Privacy summary

HMDIA Note is designed to keep your information under your control:

  • Notes are stored locally in your browser by default.

  • During ordinary use, HMDIA does not receive or store your note titles, note bodies, tags, reminders, note-associated website addresses, or exported backups.

  • Optional Google Drive synchronization stores encrypted HMDIA Note data in your own private Google Drive application-data folder.

  • Google Drive synchronization is optional and is not required to use HMDIA Note’s local features.

  • HMDIA’s servers are contacted only for Premium-license activation, validation, and deactivation.

  • HMDIA Note does not include advertising trackers, behavioural analytics, telemetry, data brokers, or third-party advertising.

  • We do not sell personal information or use it for personalized advertising, profiling, credit decisions, or training general-purpose artificial-intelligence models.

2. Information processed locally

HMDIA Note may store the following information in your browser’s extension storage:

  • Note titles, note bodies, rich-text formatting, checklists, and links;

  • Global, Domain, or Page note scope;

  • Website domains and page URLs associated with Domain and Page notes;

  • Tags, tag colours, sticky status, archive status, Trash contents, and deletion markers;

  • Creation, modification, archive, deletion, and reminder timestamps;

  • Reminder schedules, recurrence settings, time zone, snooze status, and notification status;

  • Extension settings, themes, colours, display preferences, filters, search preferences, and opening mode;

  • Autosaved drafts;

  • Protected-note encrypted content;

  • The most recently selected colour-picker value;

  • Premium-license information and installation identifiers; and

  • Google Drive connection status, connected-account display name and email address, file identifiers, synchronization status, and a locally stored unlocked synchronization key.

This information remains within your browser profile unless you:

  1. Enable Google Drive synchronization;

  2. Export a backup file;

  3. Activate, validate, or deactivate a Premium license; or

  4. Voluntarily provide information to HMDIA support.

Ordinary notes that are not password-protected are stored unencrypted in the browser’s restricted extension-storage context. Anyone who gains sufficient access to your device or browser profile may be able to access that information.

3. Website and browsing context

HMDIA Note uses website context to provide Global, Domain, and Page notes.

The extension may temporarily read URLs from open browser tabs to:

  • Determine which Domain or Page notes match a tab;

  • Display the correct notes when the extension opens;

  • Update the extension’s note-count badge; and

  • Follow the active tab when using the sidebar or movable-window interface.

HMDIA Note does not use the browser-history API, create a browsing-history profile, or transmit open-tab URLs to HMDIA.

A website domain or full page URL is stored only when you create or save a Domain or Page note. Page URLs may include paths, query parameters, document names, local file paths, or other identifiers. URL fragments are removed. You should avoid associating notes with URLs that contain passwords, access tokens, private access links, or other sensitive information.

The website context associated with a protected note remains visible in local extension storage even though its title, body, and tags are encrypted.

HMDIA Note does not run in Chrome Incognito or Firefox Private Browsing windows. Private tabs and windows are invisible to the extension, so their addresses and content cannot be added to shared extension storage.

4. Colour picker

In Chrome and compatible Chromium browsers, the colour picker uses the browser’s native eyedropper feature and retains only the selected hexadecimal colour value.

In Firefox, when you intentionally activate the colour picker, HMDIA Note may request website access, capture the visible portion of the active tab, and temporarily inject a colour-selection overlay into that page. The screenshot is processed locally for the colour-selection operation. It is not uploaded to HMDIA or Google and is not retained after the operation. Only the selected hexadecimal colour value may be stored locally and copied to your clipboard.

HMDIA Note does not continuously capture screens or webpage content.

5. Protected notes, drafts, and backups

Protected notes

When you password-protect a note, HMDIA Note encrypts its title, body, formatting, and tags locally using authenticated encryption based on AES-GCM and a key derived from your password using PBKDF2-SHA-256.

The extension does not save or transmit the protected-note password. HMDIA cannot recover a forgotten password or decrypt a protected note for you.

Note identifiers, scope, contextual URL or domain, timestamps, sticky status, archive status, and other metadata may remain unencrypted locally.

Autosaved drafts

Autosaved drafts are encrypted locally. The corresponding device key is stored in the same browser extension storage so drafts can be restored automatically. This protects draft contents from casual inspection but does not protect them against a person who has sufficient access to your browser profile or device.

Exported backups

You may export your note database as:

  • A readable JSON backup; or

  • A password-encrypted JSON backup.

Backups may include active notes, Trash contents, tags, and saved Domain or Page contexts. They do not include reminders, your Premium license, Google access token, or Google account connection details.

Exported files are controlled entirely by you after download. HMDIA does not receive them unless you voluntarily send a backup to HMDIA support. HMDIA cannot recover, replace, decrypt, or protect files that are lost, shared, corrupted, or stored insecurely.

6. Optional Google Drive synchronization

Google Drive synchronization is an optional Premium feature. It begins only after you select Connect Google Drive, review the in-extension disclosure, select the unchecked consent box, and authorize access through Google.

HMDIA Note requests only this Google OAuth scope:

https://www.googleapis.com/auth/drive.appdata

This permission allows the extension to manage only HMDIA Note’s own configuration data in Google Drive’s private application-data folder, including the technical ability to see, create, and delete its own app-data files. The current extension uses this access to create, read, and update its encrypted synchronization and key files. It does not permit HMDIA Note to access your ordinary visible Google Drive documents, folders, photos, or other files.

Google information processed

When you connect Google Drive, the extension may receive:

  • Your Google account display name;

  • Your Google account email address;

  • An OAuth access token; and

  • HMDIA Note file IDs, names, versions, and modification times.

Your display name and email address are stored locally to identify and bind the connected account in Settings. OAuth access tokens are held temporarily in browser-managed or extension session storage until they expire or are cleared.

Your Google account information and OAuth tokens are not sent to HMDIA’s licensing server.

Information synchronized

The encrypted synchronization payload can include:

  • Notes and note content;

  • Tags and the tag library;

  • Domain and Page context URLs;

  • Archived notes;

  • Notes currently in Trash;

  • Content-free deletion markers;

  • Reminders, reminder settings, and time-zone identifiers; and

  • Synchronization metadata.

HMDIA Note stores an encrypted synchronization file and a password-protected encryption-key descriptor in your private Google Drive application-data folder.

Encryption

When a new synchronization dataset is created, HMDIA Note:

  1. Generates a random 256-bit data-encryption key;

  2. Derives a wrapping key from your synchronization password using PBKDF2-SHA-256;

  3. Encrypts the data-encryption key using AES-256-GCM; and

  4. Uploads the protected key descriptor to Google Drive.

For each synchronization upload, HMDIA Note reuses that random data-encryption key to encrypt the current synchronization payload locally using AES-256-GCM, with a new encryption initialization vector, and uploads the encrypted payload to Google Drive.

Your synchronization password is not stored or transmitted to HMDIA or Google.

The unlocked synchronization key is stored locally in each connected browser so automatic synchronization can operate without repeatedly requesting the password. Anyone who compromises a connected browser profile may therefore be able to access synchronized information.

While connected, you may change the synchronization password by entering the current password. Changing the password re-encrypts the existing data-encryption key; it does not create a new synchronization account, replace your Google account, or enable HMDIA to recover a forgotten password.

HMDIA cannot recover a forgotten synchronization password. An already-connected browser that retains the unlocked key may be your only way to recover the synchronized information.

Google may see operational file and encryption-envelope metadata such as filenames, file IDs, sizes, versions, timestamps, encryption parameters, random write identifiers, and synchronization revisions. Note content and saved context URLs remain inside the encrypted payload.

7. Google API and Chrome Web Store Limited Use disclosures

HMDIA Note uses Google information only to provide the Google Drive synchronization feature requested by the user.

HMDIA Note’s use and transfer of information received from Google APIs complies with the Google API Services User Data Policy, including its Limited Use requirements.

HMDIA Note’s use and transfer of extension user data complies with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Google API information and extension user data are not:

  • Sold or provided to data brokers;

  • Used for advertising, retargeting, or marketing profiles;

  • Used for credit, insurance, employment, housing, or eligibility decisions;

  • Used for surveillance;

  • Used to train or improve general-purpose artificial-intelligence or machine-learning models.

HMDIA does not receive your encrypted Google Drive files, OAuth token, note content, synchronization password, encryption key, or Google account information. Google Drive synchronization data is not made available for HMDIA personnel to read. HMDIA personnel can access specific note or Google information only if you choose to supply it to us, for example for support. Security or legal duties concerning information already in our possession do not give HMDIA a technical ability to retrieve or decrypt notes that remain only in your browser or Google Drive.

Authorized HMDIA personnel and service providers may access limited purchase, licensing, browser-installation, security, and support records when reasonably necessary for license administration, fraud and abuse prevention, support, security, accounting, or legal compliance. These records do not include your ordinary notes or encrypted Google Drive synchronization content unless you intentionally provide specific material to HMDIA support.

8. Premium licensing

When you activate, validate, or deactivate a Premium license, HMDIA Note communicates over HTTPS with HMDIA License Manager at hmdia.com.

Depending on the requested licensing action, the extension sends:

  • The license key you enter;

  • A license activation hash for later validation or deactivation, where applicable;

  • Fixed HMDIA Note product identifiers;

  • The requested activation, validation, or deactivation action;

  • A randomly generated browser-installation identifier; and

  • A synthetic HMDIA license URL representing that browser installation.

The synthetic license URL is only an installation identifier. HMDIA Note does not connect to that synthetic address.

The Chrome and Chromium versions also include the extension version and a general browser-and-platform label in the licensing payload. The Firefox version uses a generic HMDIA Note browser-extension label and does not add the Firefox browser/platform description or extension version to the licensing payload.

The licensing service may return license status, expiration, activation limits, active-installation counts, plan or product labels, and related validation information. This information may be stored locally so the extension can determine whether Premium features are available.

HMDIA License Manager and FluentCart may associate a request with existing purchase and license records, including a customer email address, product, plan, status, and browser-installation limit.

The requesting IP address is processed for secure delivery, abuse prevention, rate limiting, and protection of the licensing service. HMDIA’s hosting provider, WordPress security systems, and Cloudflare may also process ordinary request information such as IP address, request time, browser information, and security events. If country analytics is enabled, HMDIA License Manager may retain a two-letter country code supplied by Cloudflare; this feature does not intentionally store a full IP address in the license-activation record.

License requests never include your notes, reminders, tags, saved context URLs, Google account details, synchronization password, Google token, or Google Drive files.

9. Firefox data-collection choices

The current Firefox version requires Firefox 140 or later and declares no required data collection. Local note-taking and free features operate without granting an optional Firefox data-collection permission.

Firefox separately asks for the relevant optional permissions immediately before you deliberately start a feature that transmits information outside the browser:

  • Premium licensing: Firefox may request authenticationInfo, locationInfo, and personallyIdentifyingInfo, together with access only to https://hmdia.com. These categories cover the license credentials and stable browser-installation identifier sent to HMDIA, the connection IP address necessarily received by the service, and the two-letter country code that may be retained when Cloudflare country analytics is enabled.

  • Google Drive connection and synchronization: Firefox may request authenticationInfo, browsingActivity, locationInfo, personallyIdentifyingInfo, and websiteContent, together with access only to https://www.googleapis.com. These categories cover Google authorization information, the connected Google account display name and email address, saved contextual URLs, reminder time-zone identifiers, and encrypted note and reminder content sent directly to Google for the requested synchronization.

Accepting HMDIA Note’s own privacy notice does not pre-approve Firefox’s separate optional permission prompt. Declining an optional data or host-access request leaves the related remote feature disabled; local note-taking and free features remain available. You may be asked again only when you deliberately start that optional feature later.

The Firefox locationInfo category is a data-transmission disclosure. HMDIA Note does not request Firefox’s geolocation or GPS API permission and does not collect precise GPS coordinates.

10. Browser permissions

HMDIA Note uses browser permissions only for its disclosed functions:

  • Storage: Save notes, settings, reminders, encrypted drafts, and connection information locally.

  • Tabs: Read open-tab URLs locally to match Domain and Page notes and update badges.

  • Identity: Open Google’s authorization flow for optional Google Drive synchronization.

  • Alarms: Schedule reminders, synchronization checks, and license checks.

  • Notifications: Display note reminders through the browser or operating system.

  • Side panel or sidebar: Display the HMDIA Note interface.

  • Active tab and scripting on Firefox: Run the user-initiated colour picker on the visible webpage.

  • Optional website access on Firefox: Capture the visible active tab for the user-initiated colour picker.

  • Access to hmdia.com: Activate, validate, and deactivate Premium licenses.

  • Access to Google APIs: Perform optional Google Drive synchronization.

HMDIA Note does not request cookie, web-request, browser-history, advertising-identifier, microphone, camera, or geolocation/GPS API permissions.

11. How information is used

Information is processed only as necessary to:

  • Create, display, organize, search, protect, archive, restore, and delete notes;

  • Associate notes with websites or individual pages;

  • Schedule and display reminders;

  • Apply user-selected appearance and behaviour settings;

  • Export and import user-controlled backups;

  • Connect and synchronize encrypted information with Google Drive;

  • Activate, validate, and deactivate Premium licenses;

  • Enforce legitimate browser-installation limits;

  • Prevent fraud, abuse, and excessive automated requests;

  • Diagnose a problem when you request support;

  • Maintain the security and reliability of the extension and licensing service; and

  • Comply with applicable legal obligations.

HMDIA Note does not perform automated profiling or make decisions that produce legal or similarly significant effects. Automated license validation only determines whether Premium features are available.

Where applicable, HMDIA relies on performance of a contract, your consent or requested action, legitimate security and service-operation interests, and compliance with legal obligations as the basis for processing.

12. When information may be disclosed

HMDIA may disclose information under its control only:

  • To service providers that operate HMDIA’s website, hosting, security, ecommerce, or licensing systems and are required to process information for those purposes;

  • To Cloudflare or hosting and security providers for secure delivery, abuse prevention, and protection of the licensing service;

  • Within HMDIA’s ecommerce and licensing systems, including FluentCart software, for purchase and software-license administration;

  • When reasonably necessary to investigate fraud, abuse, or a security incident;

  • When required by applicable law, court order, or lawful government request;

  • To protect the legal rights, safety, and security of HMDIA, users, or the public; or

  • In connection with a merger, acquisition, restructuring, or sale of HMDIA’s business, subject to applicable law and appropriate protections.

Because HMDIA does not receive your ordinary notes or Google Drive synchronization data, HMDIA generally cannot disclose that information in response to a request.

Google independently processes information sent directly to Google under the Google Privacy Policy. Chrome, Firefox, operating-system providers, extension stores, and websites you visit may process information independently under their own policies.

13. Data retention and deletion

Local browser data

Local extension information remains until you delete it, clear the extension’s storage, reset the browser profile, or uninstall the extension.

Deleting a note normally moves the complete note into Trash. Using Clear Notes also moves notes to Trash. Trash contents remain until restored or permanently deleted.

Permanent deletion removes the note content but may retain a content-free identifier and deletion timestamp as a synchronization marker. This marker prevents an older copy on another connected browser from restoring the deleted note.

Similar content-free deletion markers may remain for deleted tags and reminders.

Google Drive data

Disconnecting Google Drive:

  • Stops synchronization on that browser;

  • Clears the cached Google token, locally unlocked synchronization key, and most local connection information;

  • Does not revoke HMDIA Note’s authorization in your Google account;

  • Does not delete the encrypted HMDIA Note files already stored in Google Drive; and

  • Does not delete your local notes.

To remove Google authorization, visit your Google Account third-party connections and remove HMDIA Note.

To delete HMDIA Note’s hidden Google Drive data, open Google Drive settings, select Manage apps, locate HMDIA Note, and choose the option to delete its hidden application data where available.

Revoke access and delete hidden Drive data separately if you want both authorization and synchronized files removed.

Licensing information

Local license information remains until you deactivate the license, clear extension storage, or uninstall the extension.

Active server-side activation records are generally retained while the license remains active. After deactivation, activation history is ordinarily retained for the configured history period, currently 90 days, and is then eligible for scheduled deletion.

Purchase, transaction, accounting, fraud-prevention, backup, and legally required records may be retained longer where necessary.

Support information

If you voluntarily provide note content, screenshots, diagnostic information, or backup files to HMDIA support, that information will be used only to investigate and respond to your request. Remove unrelated or sensitive information before sending anything to support.

Support information is retained only as reasonably necessary to resolve the request, maintain appropriate service records, prevent abuse, and meet legal obligations.

14. Notifications

Reminder notifications may be visible on your screen, lock screen, notification centre, or to other people who can access your device.

Notification content is hidden by default. If you enable notification previews, an unprotected note’s title or part of its body may appear in a system notification. Notifications for protected notes remain generic.

You are responsible for deciding whether notification previews are appropriate for your device and environment.

15. Security

HMDIA uses reasonable technical and organizational safeguards appropriate to the information under its control. These measures include HTTPS transmission, authenticated encryption for protected notes and Google Drive synchronization, restricted browser-extension storage contexts, request validation, rate limiting, limited network endpoints, and explicit consent before optional remote features are activated.

No storage or transmission system is completely secure. Encryption cannot protect information if your device, browser profile, Google account, passwords, or unlocked local encryption key are compromised.

HMDIA cannot recover forgotten note, backup, or synchronization passwords and cannot restore local information lost through uninstallation, browser reset, storage clearing, device failure, corrupted profiles, or failure to maintain backups.

16. Your responsibilities and important limitations

HMDIA Note is a general-purpose note-taking utility. It is not designed to serve as a password manager, medical-record system, payment-card vault, legal-record repository, classified-information system, or sole backup service.

You are responsible for:

  • Deciding what information to place in a note;

  • Avoiding sensitive information in page URLs and URL query parameters;

  • Securing your device, browser profile, Google account, and passwords;

  • Choosing strong and unique encryption passwords;

  • Retaining passwords needed to decrypt protected notes or synchronized information;

  • Maintaining appropriate independent backups;

  • Permanently deleting Trash items when content should no longer be retained;

  • Revoking Google authorization and deleting hidden Google Drive data when desired;

  • Deactivating your Premium license before uninstalling if you want the activation slot released; and

  • Complying with laws and obligations that apply to information you store.

HMDIA cannot control and does not guarantee the security, availability, retention, or operation of your device, browser, operating system, Google account, Google Drive, Chrome Web Store, Firefox Add-ons, internet connection, or other third-party services.

Any liability limitations, warranty disclaimers, backup limitations, service-availability terms, indemnities, and governing-law provisions are addressed separately in the HMDIA Note Terms of Use and apply only to the maximum extent permitted by law. Nothing in this Privacy Policy limits rights or obligations that cannot legally be waived.

17. Your privacy rights

Depending on your location, you may have rights to:

  • Ask whether HMDIA holds personal information about you;

  • Request access to information under HMDIA’s control;

  • Request correction of inaccurate information;

  • Request deletion where legally applicable;

  • Withdraw consent for optional processing;

  • Object to or request restriction of certain processing;

  • Request a portable copy of qualifying information; and

  • Submit a privacy complaint.

HMDIA may need to verify your identity before responding. Some requests may be limited where retention is required for license administration, fraud prevention, accounting, legal claims, or compliance with law.

Because HMDIA does not possess your locally stored notes or encrypted Google Drive data, we cannot access, correct, export, decrypt, or delete that information for you. Use the extension and Google account controls described above.

18. International processing

HMDIA operates from Ontario, Canada. Service providers such as Google, Cloudflare, hosting providers, browser vendors, and extension stores may process information in Canada, the United States, or other countries.

Privacy laws and government-access rules may differ between jurisdictions. HMDIA uses appropriate safeguards where required for information transferred under its control.

19. Children’s privacy

HMDIA Note is a general-audience productivity tool and is not directed to children under 13 or a higher minimum age required by local law.

We do not knowingly collect personal information from children through the extension. A parent or guardian who believes a child has provided personal information to HMDIA may contact us to request appropriate action.

Google Drive synchronization is optional, and the extension’s local note-taking functions do not require a Google account.

20. No sale, advertising, or unrelated use

HMDIA does not sell or rent extension user information.

HMDIA does not “sell” or “share” extension user information for cross-context behavioural advertising as those terms are defined under applicable United States privacy laws.

Extension data is not used for:

  • Personalized advertising or retargeting;

  • Data-broker services;

  • Unrelated marketing;

  • Surveillance;

  • Credit, employment, insurance, housing, or eligibility decisions;

  • General user profiling; or

  • Training general-purpose artificial-intelligence models.

21. Changes to this Policy

We may update this Privacy Policy when HMDIA Note’s functionality, legal obligations, or privacy practices change.

The updated Policy will show a revised Last updated date. Material changes will be communicated through the extension, website, store listing, or another appropriate method where required.

If a change introduces a new use of Google user data or another materially different data practice, HMDIA will update the relevant disclosures and obtain new consent where required before beginning that use.

22. Contact and privacy complaints

For privacy questions, access or deletion requests, or complaints, contact:

Privacy Officer — HMDIA
Ontario, Canada
Email: [email protected]
Website: hmdia.com/hmdia-note/

HMDIA Admin Menu & Access Manager

Last updated: October 19, 2026

This section covers HMDIA Admin Menu & Access Manager. It supplements the Website & Services privacy notice for purchases, licensing, and support provided directly by HMDIA. The owner of an independent WordPress website controls that website’s user information and plugin settings.

1. Information handled on the website

The plugin uses existing WordPress users, roles, and capabilities to apply the administrator’s rules. It stores settings for menu and toolbar visibility, hidden plugin entries, menu names/order, role or user exceptions, permission grants, and the designated management account in the website’s WordPress database. Administration and preview controls may display existing user names and related account details to authorised administrators. It does not need visitors’ browsing histories or note content to manage menus.

2. Settings exports and local retention

A settings export may contain rules and user-specific identifiers such as usernames so rules can be matched during import. Exported files are controlled by the person downloading them and should be protected. Licence keys and activation state are excluded from settings exports.

Rules and settings remain until changed or deleted. On uninstall, plugin settings are deleted only when the administrator has enabled the delete-data option; local licence credentials and activation state are removed by the uninstall process. Uninstalling is not the same as deactivating a server-side licence activation, and it does not delete WordPress user accounts, backups, or previous exports.

3. HMDIA licensing and updates

When a licence is activated, checked, or deactivated, or eligible updates are requested, the plugin contacts HMDIA over HTTPS. Requests include the licence key, website URL, product identifiers, plugin version, WordPress and PHP versions, and an activation identifier when available. HMDIA uses these details to verify entitlement, enforce purchased activation limits, deliver updates, and prevent abuse. The service can associate them with the purchase, plan, and customer contact details.

HMDIA and its hosting/security providers also receive ordinary request information such as the connecting server IP address and timestamps. These licensing and update requests do not include the website’s user list, menu rules, submitted form content, passwords, or full website database. The plugin does not add an advertising tracker for these menu-management functions.

Active activation records remain while needed to administer the licence. Deactivated-licence history is currently retained for 90 days before becoming eligible for cleanup. Purchase, support, accounting, security, and backup records may remain longer for the purposes described in the website notice.

4. Choices, support, and privacy requests

Website administrators can change rules, export settings, deactivate the licence, and choose the uninstall cleanup setting. Disabling the commercial entitlement can stop private updates and support; existing local rules continue operating. For access, correction, or deletion of information on an independent website, contact its owner. For information HMDIA holds directly, contact [email protected] or our contact page.

Support files may reveal users or administrative settings; remove unnecessary personal information before sending them. The website notice explains HMDIA’s security safeguards, international processing, applicable rights, and complaint route. No wording in this notice removes non-waivable privacy rights.