Transparency

Privacy — how MoveEase handles information

MoveEase is designed as downloadable, informational HTML. This policy explains what could technically be processed if you host these files online, how local-only features behave, and simple rights language in plain English.

How to use this policy page

If you open these files from disk, many sections apply only if you later publish them on a server with analytics. Use the checklist table to decide which rows matter to your situation. When in doubt, assume minimal collection.

Scenario Typical data involved MoveEase default stance
Local offline viewing None collected by MoveEase scripts beyond page-local calculator memory. No accounts; no cloud sync in these static files.
Self-hosted website Server logs (IP, timestamp) depending on host. Configure host logging minimally; refer to host privacy documentation.
Embedded third-party fonts (if added later) Font CDN may log requests. This bundle uses system font stacks only in CSS.

Cookies and similar technologies

These pages do not set first-party cookies by default. If you add analytics or a comment system, disclose those tools separately. A cookie is a small text file stored by your browser so sites can remember preferences or session IDs.

User rights — general principles

Depending on your region (for example GDPR, UK GDPR, CCPA/CPRA concepts), you may have rights to access, correct, delete, or port personal data about you, and to object to certain processing. MoveEase’s static content does not create a user database on its own. If a host processes data, contact that processor’s privacy contact listed in their policy.

Right (conceptual) Practical note for this site
Access If no personal data is collected, there may be nothing to retrieve.
Deletion Server logs retention depends on hosting provider settings.
Correction Not applicable to anonymous page views; applicable if you add forms later.

Children and sensitive information

Content targets adults seeking general movement education. It is not directed at children to collect their data. Do not submit medical records through unsecured channels tied to this static kit.

Example routine A — “Privacy hygiene” weekly
  1. Review browser extensions that read page content unnecessarily.
  2. Clear cached forms if you experiment with local notes in the same browser profile.
  3. Export tracker data you care about to paper monthly — reduces dependence on devices.

Contact and updates

If you republish MoveEase, insert a contact email or postal address appropriate for your organization. Policy updates should bump the effective date below. Pair legal reading with Terms of use for scope limits.

Example routine B — Publishing checklist

Input: domain + analytics decision. Calculation: list every script loaded. Output: privacy page subsection per script vendor with opt-out links where required by law.

Effective date

March 25, 2025 — template edition aligned with static MoveEase HTML bundle.