Privacy Policy

Effective date: 19 September 2026
Last updated: 28 September 2026

This Privacy Policy explains how Easeare (“Easeare”, “we”, “us”, or “our”) collects, uses, shares, and protects information when you use our websites, purchase or manage licenses, contact us, or when optional features in Easeare WordPress products communicate with our API.

It is written for Easeare as a whole and is intended to cover multiple WordPress.org plugins and commercial add-ons that share the same inbound and outbound patterns—not only a single product.

Primary website: https://easeare.com/
Related properties: Easeare product sites under *.easeare.com, the shared API at https://api.easeare.com/, and Easeare WordPress software (free plugins, commercial add-ons, and related services).

Our Terms of Service describe contractual rules for using the Services.

Privacy and data requests: support@easeare.com.

1. Scope — what this Policy covers

This Policy applies to personal data and related technical information processed by Easeare in connection with:

1. easeare.com and other Easeare-operated websites (marketing, documentation, support, checkout, account areas);
2. communications you send us by email;
3. orders, licenses, and customer records for Easeare products;
4. the Easeare API at api.easeare.com, including optional license and catalog requests from WordPress sites; and
5. security, fraud prevention, and service logs related to the above.

1.1 What this Policy does not cover by default

Easeare WordPress plugins typically store visitor submissions (leads, quotes, form answers, bookings, and similar) in your WordPress database on your hosting. In that case:

• you (the site owner) are the controller for that visitor data;
• your own privacy policy and cookie notices apply to your visitors;
• Easeare does not automatically receive those visitor records for ordinary free plugin use.

If a specific Easeare cloud feature later sends visitor content to Easeare, we will disclose it in that product’s WordPress.org “External services” section and update this Policy.

2. Roles in plain language

3. Categories of information we collect

3.1 Information you provide directly

Depending on how you interact with us, this may include:

• Identity and contact data — name, email address, and message contents when you email support or create an account;
• Account data — login identifiers, password hashes (if we operate accounts), profile preferences;
• Order and billing data — products purchased, license keys issued to you, plan limits, invoices, billing address, tax identifiers where required; payment card data is typically processed by our payment provider and not stored in full by Easeare;
• Support data — ticket history, diagnostics you choose to share (site URL, plugin versions, screenshots, error logs);
• Marketing preferences — newsletter opt-in or opt-out where offered.

3.2 Information collected automatically on Easeare websites

When you visit easeare.com or related Easeare sites, we and/or our processors may collect:

• Technical and usage data — IP address, approximate location derived from IP, browser type, device type, operating system, referring URL, pages viewed, timestamps, and diagnostic logs;
• Cookie and similar technology data — session cookies necessary for security and forms; optional analytics or preference cookies if enabled (see Section 8).

3.3 Information from optional WordPress plugin → API communications

Official Easeare plugins may send limited technical data to api.easeare.com only when optional features are used. Across Easeare products, the shared pattern is:

A. License activation, deactivation, and validation (optional)

When it happens: after you enter a license key in a plugin’s settings (or equivalent), and on activate, deactivate, or periodic or admin-triggered re-check.

What is typically sent:

• license key;
• site home URL (home_url / site URL);
• product / plugin identifier (which Easeare product the key belongs to);
• standard HTTP metadata (IP address of the requesting server, User-Agent, timestamps).

What is typically not sent for this purpose: visitor lead fields, quote line items, calculator answers, or other end-customer personal content stored in your WordPress database.

Why we process it: to verify the key, bind or unbind sites within plan limits, return entitlement lists (which packages the key may use), prevent abuse, and provide customer support related to licensing.

B. Official add-on / package catalog (optional)

When it happens: when an administrator clicks a catalog refresh control, or when daily catalog updates are explicitly enabled (WordPress Cron approximately once per 24 hours). If those options stay off, official plugins should not schedule catalog requests.

What is typically sent:

• HTTPS GET to a product-scoped catalog endpoint (for example /v1/{product}/catalog);
• product identifier header (for example X-Easeare-Plugin);
• User-Agent that may include plugin version and site home URL;
• standard server request metadata (IP, time).

What is typically received:

• public package metadata: names, descriptions, types (free/pro), versions, feature lists, availability (available / coming soon), HTTPS preview image URLs, and optional product page links.

What is typically not sent: license keys (for catalog GET), visitor personal data, or executable plugin code via the catalog response. Catalog responses are informational metadata; they do not install or execute remote code by themselves.

Why we process it: to keep Add-ons / opportunities screens current without embedding remote marketing assets inside WordPress.org plugin packages; to operate and secure the API; and to understand aggregate demand for catalog endpoints (for reliability).

3.4 Information we generate

We may create:

• license entitlement records and site activation history;
• security logs and rate-limit events;
• aggregated, de-identified statistics about API usage and website traffic.

3.5 Information from third parties

We may receive limited data from:

• payment processors (payment confirmation, last four digits, card brand, billing country);
• WordPress.org (public plugin listing metadata—not your private site data);
• email or support tools (delivery status);
• fraud or security providers if used.

4. How we use information (purposes)

We use information to:

1. operate websites and the API — serve pages, authenticate requests, return license and catalog responses;
2. provide products you request — fulfill purchases, issue and manage license keys, deliver downloads and documentation;
3. customer support — respond to questions and troubleshoot issues you report;
4. security and abuse prevention — detect fraud, piracy attempts, credential stuffing, and API misuse;
5. improve Services — understand which documentation and catalog items are needed; fix bugs; plan capacity;
6. communications — send transactional messages (receipts, license notices, security alerts); send marketing only where allowed and with an opt-out;
7. legal compliance — tax, accounting, respond to lawful requests, enforce our Terms;
8. business operations — audits and corporate transactions under appropriate safeguards.

5. Legal bases (where GDPR / UK GDPR applies)

If European or UK data protection law applies, we rely on one or more of:

• Contract — processing needed to provide Services you request (accounts, purchases, license API);
• Legitimate interests — securing the API, preventing abuse, improving reliability, and limited product analytics that do not override your rights;
• Consent — where required (optional cookies, certain marketing);
• Legal obligation — tax and bookkeeping requirements.

You may withdraw consent where processing is consent-based, without affecting prior lawful processing.

6. How we share information

We do not sell your personal information for money. We may share information with:

1. Service providers / processors who help us host sites, run the API, process payments, send email, provide support desks, or security monitoring—under contractual obligations to use data only for our instructions;
2. Professional advisors (legal, accounting) under confidentiality;
3. Authorities when required by law or to protect rights, safety, and security;
4. Business transfers — if Easeare is involved in a merger, acquisition, or asset sale, information may transfer under continued confidentiality commitments where required;
5. With your direction — for example if you ask us to coordinate with your developer or host.

We do not share your WordPress visitors’ lead or quote databases with third parties via the license or catalog API, because those records are not part of that data flow.

7. International transfers

Easeare may process data on servers or with providers located outside your country (including outside the EEA/UK). Where required, we use appropriate safeguards such as Standard Contractual Clauses or equivalent mechanisms offered by our providers.

For more information about transfers that apply to your request, contact support@easeare.com.

8. Cookies and similar technologies

Easeare websites may use:

• Strictly necessary cookies — security, load balancing, form submissions, consent storage;
• Preferences — remembering UI choices;
• Analytics (if enabled) — understanding aggregate traffic;
• Marketing (if enabled) — measuring campaigns, only with consent where required.

You can control cookies through your browser and, where provided, our cookie banner. Blocking some cookies may affect site functionality.

WordPress admin screens on your site may set their own cookies controlled by WordPress and other plugins you install—not by this Policy alone.

9. Data retention

We retain information only as long as needed for the purposes above, including:

• license and order records — for the life of the customer relationship and for tax/legal retention periods afterward;
• support tickets — for a reasonable period to maintain service history;
• API and security logs — for shorter operational windows unless needed for investigations;
• website analytics — according to tool settings;
• marketing contacts — until you unsubscribe or we purge inactive lists.

When data is no longer needed, we delete or de-identify it, subject to backup cycles.

10. Security

We implement technical and organizational measures appropriate to the risk, which may include HTTPS/TLS for the API and websites, access controls, least-privilege administration, logging, and protected storage of sensitive secrets where applicable.

No method of transmission or storage is 100% secure. You must also secure your WordPress site, admin accounts, and hosting.

11. Children

The Services are directed to businesses and adult professionals. We do not knowingly collect personal data from children under 16 (or the lower age required by local law). If you believe a child provided data, contact support@easeare.com so we can delete it.

12. Your rights and choices

Depending on your location, you may have rights to:

• access personal data we hold about you;
• correct inaccurate data;
• delete data (subject to legal exceptions);
• restrict or object to certain processing;
• portability of data you provided;
• withdraw consent where processing is consent-based;
• opt out of marketing emails (transactional mail may continue);
• lodge a complaint with a supervisory authority.

California and similar US state laws: you may have rights to know, delete, correct, and opt out of certain sharing. We do not sell personal information for money. If we use cookies or advertising technologies that constitute “sharing” or “targeted advertising” under applicable state law, we will provide required opt-outs.

To exercise rights, email support@easeare.com with enough detail to verify your request. We may need to confirm identity before acting.

13. Your responsibilities as a WordPress site owner

If you install Easeare Software on a site that collects visitor personal data, you should:

1. publish a clear privacy policy for your visitors;
2. obtain any consents required for your forms, cookies, and marketing;
3. configure retention and deletion practices for leads, quotes, or similar records on your site;
4. understand that optional Easeare API features may send site URL and license technical data to Easeare as described above;
5. leave catalog daily updates disabled if you do not want scheduled outbound catalog requests.

Where Easeare Software includes on-site privacy helpers (for example WordPress privacy exporters and erasers), those tools help you respond to your visitors’ requests for data stored in your database—they do not move that data to Easeare.

14. WordPress.org plugin disclosures

Each Easeare plugin hosted on WordPress.org includes an External services section in its readme.txt describing optional connections to api.easeare.com. That product-level disclosure works together with this company-wide Policy. If there is a conflict about a specific plugin’s optional calls, the plugin readme’s External services text and this Policy should be read together; we will correct inconsistencies when found.

15. Automated decision-making

We do not use automated decision-making that produces legal or similarly significant effects about individuals solely by automated means without human involvement, except routine fraud and security controls (for example rate-limiting abusive API traffic).

16. Third-party links

Our websites may link to WordPress.org, payment pages, social networks, or documentation hosts. Their privacy practices are their own. Review their policies before providing data to them.

17. Changes to this Policy

We may update this Policy to reflect product, legal, or operational changes. We will post the updated version at https://easeare.com/privacy and revise the “Last updated” date. Material changes may also be highlighted on easeare.com or by email where appropriate.

18. Contact

Privacy and data requests
Email: support@easeare.com
Web: https://easeare.com/

19. Detailed reference — shared API data map (Easeare WordPress products)

This table is the company-wide description of optional outbound plugin traffic. Individual plugins may enable a subset of these features.

Core free features that are designed to work offline do not require these calls.

20. Product coverage

Without limiting this Policy to a single plugin, the same framework covers Easeare products such as:

• Easeare Quote Calculator (WordPress.org free plugin and optional Pro add-ons);
• future Easeare WordPress.org plugins that use api.easeare.com for license and/or catalog services;
• related documentation and marketing sites under easeare.com domains.

New products will reuse this Policy where the inbound and outbound model matches. Materially different cloud features will receive an explicit update here.

If anything in this Policy is unclear, contact support@easeare.com before enabling optional API features on production sites.