Loading...
Searching...
No Matches
Privacy Statement — MeshKit

Version 1.0 — last updated November 13, 2026

This statement explains what personal information the MeshKit software handles, and what personal information the project keeps about the people who contribute to it. In short:

  • The software collects no personal information for us. It has no accounts, telemetry, analytics, crash reporting, advertising, or update checks, and it never contacts a project-run server. It runs on your own machine and makes no network connections (Section 3).
  • We keep a small amount of information about contributors, mainly GitHub identities and contributor-agreement records. Most of it is public by nature, because it lives in a public Git repository.
  • We never sell personal information or share it for advertising.

1. Who is responsible

This project is maintained under the HydroCouple GitHub organization (https://github.com/HydroCouple). It is to be stewarded by the HydroCouple Foundation, a nonprofit that has not yet been formed. Until the Foundation is incorporated, the person responsible for personal information handled by the project is Caleb Buahin (GitHub: @cbuahin), its founding Executive Director. Where data protection law uses the term, he is the controller. When the Foundation is incorporated, that responsibility will pass to it and we will update this statement.

The project does not process personal information on behalf of anyone else. In particular, it does not receive, host, or run your models or data.

Contact: support@hydrocouple.org for any privacy question or request.

This statement covers the software in this repository and the project's own handling of contributor information. It does not cover:

  • GitHub's own processing. GitHub hosts the code and the contribution tools; see the GitHub General Privacy Statement.
  • Software built by others on top of this project.

2. What the software collects

Nothing, for us. Using the software sends no information to the project, and the project receives no information about who uses it or how. Anything the software stores stays on your device, and it transmits nothing. The details for this package follow.


3. This package: MeshKit

MeshKit is a C++ meshing library, a command-line program (meshkit), and the meshkit Python package (distributed as hydrocouple.meshkit). It has no accounts, telemetry, analytics, crash reporting, or update checks, and it never contacts a project-run server.

Network connections: none. The library, the command-line program, and the Python package make no network connections and read no environment variables. The Python package needs nothing else at run time; NumPy is used only if you have installed it. Nothing is downloaded at run time.

Files on your device.

  • MeshKit reads and writes only the files you name: MeshKit binary meshes (.mkb), SMS 2DM meshes (.2dm) and, through the optional Qt targets, the mesh sections of model input (.inp) files and infiltration lookup tables (.csv).
  • A write goes first to a temporary file in the destination folder (.meshkit-<number>.tmp), which on Linux and macOS only your user account can read or write. It replaces the target when complete and is deleted if the write fails or is cancelled. The Qt targets write through Qt's QSaveFile, which also uses a temporary file beside the target.
  • Output files can contain information from your inputs. MKB files keep the metadata, region labels, and source aliases of the mesh you write, including any your own program adds, and an input file written by the Qt targets records the path of its mesh file, which can include folder names. Check outputs before sharing them.
  • MeshKit does not record your user name, computer name, or location.

When building from source. pip install from a source checkout downloads the build tools it needs (setuptools, wheel, and CMake) from PyPI, and projects that build MeshKit through CMake's FetchContent download it from GitHub. That happens on the build machine, not when the software runs.


4. Information about contributors

When you contribute to any HydroCouple repository, the project handles the following.

Your contributions, on GitHub, in public. This means commits (including the author name and email address your Git client records — you can use a GitHub-provided no-reply address), pull requests, issues, discussions, and comments, together with your GitHub username and public profile. GitHub collects and stores this; we use it to review, accept, and credit contributions.

Contributor License Agreement records. Before a contribution can be merged, its author signs the Individual CLA (CLA.md). An organization may also sign the Corporate CLA (CCLA.md).

  • Signing on GitHub. Repositories that run the CLA Assistant GitHub Action (contributor-assistant/github-action) record your GitHub username, GitHub user ID, the pull request number, and the date and time you signed. The record goes in a file inside that repository (.github/cla-signatures.json), so it is public. The action runs on GitHub; no other service receives the record. The comment you post to sign is also public on the pull request.
  • Signing by email. We keep your email, which includes your name, email address, GitHub username, the repository, and the CLA version. We also keep the date we received it and the name of the maintainer who recorded it. The email itself is not published. The public log, CLA-SIGNATORIES.md, lists your GitHub username, the CLA version, the date, and the signing method. It shows your name only if you agree.
  • Corporate CLA. We keep the signed agreement, which includes the organization's name and address, the signatory's name and title, and the names, GitHub usernames, and contact email addresses of the employees it designates. The agreement is not published. Whether an organization has a CCLA on file, and which GitHub accounts it covers, may be disclosed where needed to explain why a contribution was accepted.

Attribution. If you want to be credited, your name, GitHub username, and any affiliation or ORCID iD you provide may appear in AUTHORS.md, CITATION.cff, release notes, or documentation.

Correspondence. If you email us, we keep the message for as long as needed to deal with it and, where it is a CLA signature or a request under this statement, as a record.

Why we keep this information, and our legal basis.

Information Purpose Legal basis (where GDPR / UK GDPR applies)
Contributions and GitHub identity Reviewing, accepting, and distributing contributions Our legitimate interest in running an open-source project, and the contract formed by the CLA
CLA and CCLA records Proving the project has the right to distribute each contribution Performance of the CLA/CCLA, and our legitimate interest in establishing and defending legal claims
Attribution Crediting your work Your request, and our legitimate interest in accurate credit
Correspondence and requests Answering you and keeping a record of what was decided Legitimate interest, and compliance with legal obligations

We do not use contributor information for marketing, profiling, or automated decision-making.

How long we keep it. CLA and CCLA records are kept for as long as any contribution they cover remains part of the project, plus a reasonable period afterwards for limitation purposes. Correspondence that is not a record is deleted when it is no longer needed. Contributions themselves remain in the project's Git history.

Public means permanent. Git history, signature files, issues, and pull requests are public and are copied by everyone who clones or forks the repository, and by public archives such as Software Heritage. We can change what the project publishes from now on, but we cannot recall copies that others already hold.


5. Who receives personal information

  • GitHub, Inc. hosts the repositories, issues, discussions, the CLA Assistant workflow, and (for the project website) GitHub Pages. GitHub acts under its own privacy statement and is based in the United States.
  • Our email provider delivers and stores mail sent to the project address.
  • Authorities, only where we are legally required to disclose information.
  • A successor steward. When the HydroCouple Foundation is incorporated, contributor records will be transferred to it. Records may also be transferred to any later successor that takes over stewardship of the project.

We do not sell personal information, share it for cross-context behavioral advertising, or give it to data brokers.

International transfers. The project is run from the United States, and GitHub stores data in the United States. If you are outside the United States, your information is transferred there. For information that GitHub holds, GitHub's transfer mechanisms apply, as described in its privacy statement. For information we hold ourselves, the transfer happens because you chose to contribute to or contact a project based in the United States.


6. Your rights

Wherever you live, you can ask us to:

  • access the personal information we hold about you, including a copy in a portable format;
  • correct it;
  • delete it;
  • restrict or object to how we use it; and
  • withdraw consent where we relied on it, for example to display your name in CLA-SIGNATORIES.md.

Email support@hydrocouple.org. We respond within one month of receiving your request. If a request is complex, we may extend that, as the law allows, and will tell you why. Requests are free.

Verification. Before acting, we confirm that you control the GitHub account or email address the request is about. We ask for nothing beyond that.

Limits we will explain if they apply:

  • We cannot remove information from copies of public Git history held by others (Section 4).
  • We may decline to delete a CLA or CCLA record while the contribution it covers remains in the project, because the record is what allows the project to distribute that contribution. In that case, we can instead remove your name from public display and, at your request, remove or rewrite your contribution going forward.
  • Information that GitHub controls, such as your account and profile, is handled through GitHub's own privacy controls.

Complaints. You can also complain to a data protection authority, for example the supervisory authority where you live in the EU/EEA or the Information Commissioner's Office in the UK. We would appreciate the chance to resolve your concern first.


7. Security and incidents

Project records are kept in access-controlled accounts, and access is limited to the people who need it to run the project. If we learn of a security incident affecting personal information we hold, we will assess it promptly. We will notify the people affected, and any authority we are required to notify, within the time the law requires.

To report a security vulnerability in the software itself, follow SECURITY.md or email support@hydrocouple.org instead of opening a public issue.


8. Children

The software and the project are not directed at children. We do not knowingly collect personal information from anyone under 16. Signing the CLA requires legal capacity to enter into the agreement.


9. Changes to this statement

We will update this statement when the software's behavior or the project's practices change, and when the HydroCouple Foundation is incorporated. The version and date at the top tell you when it last changed, and the repository's Git history records every change. If we make a material change that affects contributor information we already hold, we will announce it in the repository before it takes effect.


Copyright © 2026 HydroCouple Foundation. The HydroCouple Foundation has not yet been formed. Until it is incorporated and the rights are formally assigned to it, the copyright and other intellectual property the Foundation will hold in this project are held by Caleb Buahin (GitHub: @cbuahin), its Executive Director, who holds them on the Foundation's behalf. Contributions from other contributors stay owned by their authors and are licensed to the project under CLA.md and CCLA.md.