Skip to main content
MeshLib
  • Features
      • Mesh Boolean
      • Collision Detection
      • Mesh Healing
      • Mesh Simplification
      • Mesh Offsetting
      • Mesh Smoothing
      • Mesh Intersection
      • Fill Holes
      • Point Cloud to Mesh
      • Mesh Triangulation
      • Iterative Closest Point
      • Mesh to SDF
      • 3D Volume Rendering
      • CT Reconstruction
    • File Formats
    • Viewer
    • Show All Features
  • Applications
  • Documentation
    • Getting Started Guides
    • Code Samples
    • Tutorials
  • License
    • Team Augmentation
    • Blog
      • Mesh Boolean Libraries Comparison
      • Mesh Simplification Libraries Comparison
      • 3D Python Libraries Comparison
      • Show All Articles
    • News
    • About us
    • MeshLib in Research
Get a QuoteTry Meshlib
  • Features
      • Mesh Boolean
      • Collision Detection
      • Mesh Healing
      • Mesh Simplification
      • Mesh Offsetting
      • Mesh Smoothing
      • Mesh Intersection
      • Fill Holes
      • Point Cloud to Mesh
      • Mesh Triangulation
      • Iterative Closest Point
      • Mesh to SDF
      • 3D Volume Rendering
      • CT Reconstruction
    • File Formats
    • Viewer
    • Show All Features
  • Applications
  • Documentation
    • Getting Started Guides
    • Code Samples
    • Tutorials
  • License
    • Team Augmentation
  • Blog
    • Mesh Boolean Libraries Comparison
    • Mesh Simplification Libraries Comparison
    • 3D Python Libraries Comparison
    • Show All Articles
    • News
    • About us
    • MeshLib in Research
Get a Quote

Privacy Policy

Effective Date: September 30, 2026

AMV Consulting LLC, (“AMV,” “we,” “us,” or “our”), the developer and provider of the MeshLib software library (“MeshLib”) and operator of the MeshLib website at meshlib.io, respects your privacy.

This Privacy Policy explains how we collect, use, disclose, retain, and protect personal information when you visit MeshLib website at meshlib.io, communicate with us, request a demonstration or commercial license, obtain support, participate in MeshLib-related services operated by AMV, or otherwise interact directly with AMV in connection with MeshLib.

MeshLib is a general-purpose software development library for processing 3D data. MeshLib source code and software are available for evaluation, educational, research, and other permitted non-commercial uses under the applicable license terms. Commercial use requires an appropriate commercial license from AMV.

This Privacy Policy concerns privacy and data processing. It does not modify or grant any rights under the MeshLib software license. Your right to use, modify, distribute, or commercially exploit MeshLib is determined by the applicable MeshLib license agreement.

1. Who We Are

MeshLib is provided by:

AMV Consulting LLC
19125 North Creek Parkway, Suite 120
Bothell, WA 98011
United States

MeshLib website: meshlib.io
Privacy inquiries: privacy@meshlib.io
General inquiries: contact@meshlib.io

2. A Key Privacy Principle: MeshLib Runs in Your Environment

MeshLib is principally a software development library that runs within software environments controlled by its users.

The MeshLib SDK does not contain AMV product telemetry that transmits your application data, project files, geometry, or end-user data to AMV simply because you use MeshLib.

Using the MeshLib SDK locally does not, by itself, establish a data-processing relationship under which AMV receives the data processed by your application.

For example, when your application uses MeshLib to process:

  • meshes;
  • point clouds;
  • voxel data;
  • CT or other volumetric data;
  • STL, OBJ, PLY, DICOM, or other supported file formats;
  • measurements;
  • geometry;
  • images; or
  • other application data,

that information remains within the environment in which you deploy MeshLib unless you or your application independently transmit it somewhere else.

AMV does not automatically receive that information.

Organizations that incorporate MeshLib into their own products are responsible for determining what personal information their applications collect or process and for complying with privacy laws applicable to those applications.

3. Information We Collect Directly

Although use of the SDK itself does not transmit customer data to AMV, we collect personal information when you interact directly with us.

A. Contact and Business Information

When you contact AMV, submit a website form, request a demo, inquire about licensing, or otherwise communicate with us, we may collect:

  • name;
  • work email address;
  • telephone number where provided;
  • company or organization;
  • job title;
  • country or region;
  • information about your project or intended use of MeshLib; and
  • the contents of your communications.

B. Licensing and Commercial Customer Information

If you obtain or evaluate a commercial MeshLib license, we may collect information necessary to administer the relationship, including:

  • customer and company name;
  • business contact information;
  • developer or license-user information where applicable;
  • license type;
  • number of licensed developer seats;
  • license term;
  • license and activation identifiers;
  • commercial and contractual information;
  • support entitlement;
  • invoice and transaction records; and
  • communications concerning the commercial relationship.

We use this information to evaluate licensing requests, provide quotations, enter into and administer agreements, provide licenses and support, and maintain appropriate business records.

C. Payment Information

If a transaction requires payment, our payment or financial service providers may process payment information.

AMV may receive transaction information such as:

  • customer name;
  • company;
  • billing address;
  • invoice information;
  • transaction amount;
  • transaction status; and
  • payment identifiers.

Complete payment-card details may be collected directly by the applicable payment provider rather than AMV.

D. Technical Support

If you request support, we may collect:

  • contact information;
  • description of the technical problem;
  • MeshLib version;
  • operating system and development environment;
  • logs;
  • crash information;
  • sample code;
  • screenshots;
  • test data; and
  • other information you voluntarily provide to diagnose the issue.

You control what information you provide to AMV for support.

Please avoid providing confidential, personal, regulated, or proprietary information that is not necessary to address your support request.

If you voluntarily provide project files, datasets, source code, or other materials to AMV for support or development services, we will process them for the purposes for which they were provided and subject to any applicable contractual confidentiality obligations.

4. Website Information

When you visit meshlib.io and related websites operated by AMV, we may automatically collect technical information such as:

  • IP address;
  • browser type;
  • operating system;
  • device information;
  • referring website;
  • pages visited;
  • dates and times of access;
  • session activity;
  • cookie or advertising identifiers;
  • server logs; and
  • security information.

We use this information for website operation, analytics, performance, security, fraud prevention, understanding interest in MeshLib, and marketing where permitted.

5. MeshLib Live Demos and WebAssembly

AMV may provide browser-based demonstrations of MeshLib, including demonstrations implemented using JavaScript or WebAssembly.

Where a demonstration performs processing directly in your browser, the underlying MeshLib computation occurs within the browser environment.

The demo website may separately collect ordinary website technical and analytics information as described in this Privacy Policy and our Cookie Policy.

If a particular demonstration or service requires information to be uploaded to AMV infrastructure, we will describe that functionality where appropriate and process the information in accordance with this Privacy Policy or an applicable agreement.

6. GitHub and Open-Source Community Activity

MeshLib source code, issues, discussions, documentation, examples, and other materials may be made available through GitHub or other third-party developer platforms.

AMV does not control the personal-information practices of GitHub or other independent third-party platforms.

Information that you post publicly in a GitHub issue, discussion, pull request, commit, profile, or other public forum may become publicly available.

AMV may receive or use information you intentionally provide through these channels for purposes such as:

  • answering questions;
  • investigating bugs;
  • reviewing contributions;
  • improving documentation;
  • communicating with contributors; and
  • developing MeshLib.

Your use of GitHub is also governed by GitHub’s own privacy policy and terms.

7. Open Source, Non-Commercial Use, and Commercial Licensing

The public availability of MeshLib source code does not mean that all uses are unrestricted.

MeshLib is made available subject to its applicable license terms.

Certain evaluation, educational, research, and non-commercial use may be permitted without a paid commercial license.

Commercial or business use requires an appropriate commercial license from AMV unless AMV expressly agrees otherwise in writing.

AMV may process business and contact information in order to determine the appropriate licensing arrangement, provide commercial quotations, issue licenses, administer license agreements, and communicate with prospective or existing commercial customers.

The processing of licensing information does not cause AMV to receive data that your application processes through the MeshLib SDK.

8. How We Use Personal Information

We may use personal information to:

  • operate and improve the MeshLib website;
  • respond to inquiries;
  • provide demonstrations;
  • evaluate licensing requests;
  • prepare commercial proposals;
  • administer software licenses;
  • maintain customer and developer relationships;
  • provide technical support;
  • process transactions;
  • provide product updates and release information;
  • understand interest in MeshLib;
  • improve documentation, examples, and developer resources;
  • maintain security and prevent abuse;
  • conduct marketing where permitted;
  • comply with legal obligations; and
  • establish, exercise, or defend legal rights.

We may also create aggregated or de-identified business or website statistics for analytics, product development, and other lawful purposes.

9. Cookies and Similar Technologies

Our websites may use cookies, pixels, local storage, analytics technologies, and similar tools.

We may use these technologies for:

  • necessary website functionality;
  • security;
  • analytics;
  • measuring site performance;
  • understanding how visitors interact with documentation and content;
  • remembering user preferences;
  • marketing measurement; and
  • advertising where permitted.

Non-essential cookies are subject to consent where required by law.

These technologies are provided by service providers that process the resulting data on our behalf: Google (Google Analytics and Google Ads), Microsoft (Clarity), Mixpanel, HubSpot, Meta Platforms (Meta Pixel), LinkedIn (Insight Tag) and Apollo.io (website visitor tracker). They receive website technical and interaction data, such as pages visited and cookie or advertising identifiers, only after you consent to the relevant category.

For additional information, see the MeshLib Cookie Policy.

10. How We Disclose Information

We may disclose personal information to service providers that assist us with:

  • website and cloud infrastructure;
  • customer relationship management;
  • communications;
  • analytics;
  • marketing;
  • payment processing;
  • security;
  • technical support; and
  • other business operations.

Service providers may process personal information only for authorized purposes and subject to applicable contractual and legal obligations.

We may also disclose information if reasonably necessary to comply with law or legal process; respond to lawful governmental requests; investigate fraud, misuse, or security incidents; enforce agreements, including software licenses; protect the security of MeshLib systems; protect our rights or the rights and safety of others; or establish or defend legal claims.

Information may also be transferred as part of a merger, acquisition, financing, restructuring, sale of assets, or similar corporate transaction.

11. We Do Not Sell SDK Data

Because the MeshLib SDK does not automatically transmit the data processed by your application to AMV, AMV ordinarily does not possess your application data merely as a result of your use of MeshLib.

AMV does not sell project data, geometry data, source code, or end-user data voluntarily provided to us for technical support or commercial development purposes.

Our public website may use advertising or analytics services. Certain privacy laws may treat some disclosures of website identifiers or browsing activity as “sale,” “sharing,” or “targeted advertising.”

Where applicable law provides an opt-out right, you may exercise that right through our cookie controls, recognized browser signals, or by contacting us.

12. Marketing Communications

We may send business contacts information about MeshLib products, releases, features, documentation, events, commercial licensing, and related AMV services where permitted by law.

You may unsubscribe from promotional email messages through the unsubscribe mechanism in those messages.

We may continue to send non-promotional communications necessary for licensing, support, transactions, security, or administration of an existing business relationship.

13. Data Retention

We retain personal information for as long as reasonably necessary to fulfill the purposes described in this Privacy Policy and to satisfy legal, contractual, accounting, security, and business-record requirements.

For example:

  • business inquiries may be retained while an opportunity remains active and for a reasonable period afterward;
  • commercial-license records may be retained for the duration of the relationship and an appropriate period after expiration;
  • accounting and transaction records may be retained as required by tax and financial laws;
  • support records may be retained as reasonably necessary for technical support and product improvement; and
  • website and security logs may be retained for reasonable operational and security periods.

Deleted information may remain temporarily in backups or disaster-recovery systems until those copies expire or are overwritten according to normal procedures.

14. Security

We maintain administrative, technical, and organizational safeguards designed to protect personal information under AMV’s control against unauthorized access, use, disclosure, alteration, loss, or destruction.

Safeguards may include encryption, authentication, access controls, network security, monitoring, backups, vulnerability management, confidentiality requirements, and security policies and procedures.

No system can guarantee absolute security.

Users integrating MeshLib into their own systems are responsible for securing those systems and the data processed by them.

15. International Users and Data Transfers

MeshLib is used by developers and organizations throughout the world.

Information collected directly by AMV may be processed in the United States and other countries where AMV’s service providers operate.

Where applicable law requires additional safeguards for international transfers, we use appropriate legal mechanisms, which may include adequacy decisions, Standard Contractual Clauses, approved data-transfer addenda, or other lawful transfer mechanisms.

16. EEA and United Kingdom Privacy Rights

Where the GDPR, UK GDPR, or similar privacy laws apply, AMV generally acts as controller for personal information that individuals provide directly to AMV through our Website, licensing activities, sales, support, marketing, or other business communications.

Our legal bases for processing may include:

  • performance of a contract;
  • steps requested before entering into a contract;
  • legitimate interests in operating, protecting, improving, and commercializing MeshLib;
  • compliance with legal obligations; and
  • consent where applicable.

Depending on applicable law, individuals may have rights to:

  • access personal data;
  • correct inaccurate information;
  • request deletion;
  • restrict processing;
  • object to certain processing;
  • receive certain personal data in portable form;
  • withdraw consent where processing relies on consent; and
  • lodge a complaint with an applicable data-protection authority.

Requests may be submitted to privacy@meshlib.io.

17. U.S. State Privacy Rights

Residents of certain U.S. states may have additional rights under applicable privacy laws, including rights to access, correct, delete, or obtain certain personal information and to opt out of certain sales, sharing, or targeted advertising.

Applicable rights vary by jurisdiction and are subject to statutory exemptions and limitations.

AMV does not unlawfully discriminate against individuals for exercising applicable privacy rights.

Requests may be submitted to privacy@meshlib.io.

18. Global Privacy Control

Where required by applicable law, we recognize legally valid browser-based opt-out signals, including Global Privacy Control, for processing activities within the scope of those signals.

19. Children

MeshLib is a professional software-development product and is not directed to children.

Our commercial licensing and account relationships are intended for adults and organizations capable of entering into binding agreements.

If you believe a child has submitted personal information directly to AMV without appropriate authorization, contact privacy@meshlib.io.

20. Third-Party Websites and Services

Our Website and documentation may link to third-party resources including GitHub, YouTube, package repositories, developer tools, documentation services, social-media platforms, and other websites.

Those services are operated independently and subject to their own privacy policies and terms.

AMV is not responsible for the privacy or security practices of independent third parties.

21. Changes to This Privacy Policy

We may update this Privacy Policy as MeshLib, our business practices, or applicable laws change.

We will revise the Effective Date when changes are made.

Material changes may be communicated through the Website, email, or another appropriate method.

22. Contact Us

Questions, privacy requests, or complaints may be directed to:

AMV Consulting LLC
19125 North Creek Parkway, Suite 120
Bothell, WA 98011
United States

Privacy: privacy@meshlib.io
General inquiries: contact@meshlib.io

MeshLib logo – 3D mesh processing library

Try MeshLib Now

Launch Live Demo

Product

  • Features
  • Use Cases
  • Documentation
  • License
  • Services

Resources

  • News
  • Blog
  • MeshLib in Research
  • About us
  • Careers
  • Contact us
  • Try MeshLib SDK

Compare

  • Comparing 3D Boolean Libs
  • Comparing 3D Simplification Libraries
  • MeshLib vs VTK
  • MeshLib vs CGAL
  • MeshLib vs Geogram
  • MeshLib vs Rhino
  • MeshLib vs MeshLab
contact@meshlib.io
●

AMV Consulting LLC • 19125 North Creek Parkway Suite 120 • Bothell, WA 98011 • USA

  • Terms of use
  • Privacy policy
  • Cookie policy

© Copyright MeshLib 2026

We value your privacy

We use cookies to enhance your experience, analyze traffic, and personalize content and ads. By clicking “Accept All,” you consent to our use of cookies.

Your browser is sending a Global Privacy Control signal, so we treat it as an opt-out of advertising: “Accept All” leaves the Advertisement category off. You can still turn it on yourself under Customize.

Cookie Policy |Privacy Policy |Terms of Use

Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site.

We also use third-party cookies that help us analyze how you use this website, store your preferences, and provide the content and advertisements that are relevant to you. These cookies will only be stored in your browser with your prior consent.

You can choose to enable or disable some or all of these cookies but disabling some of them may affect your browsing experience.

Your browser is sending a Global Privacy Control signal, so we treat it as an opt-out of advertising: “Accept All” leaves the Advertisement category off. You can still turn it on yourself under Customize.

To learn more about how Google processes personal information, visit: Google privacy policy

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

CookieDurationDescription
meshlib_cookie_consent1 yearStores your cookie consent choice for this site (policy version, timestamp and categories).
doxygen_* (local storage or cookie)Session to 10 yearsDocumentation pages only: remember the position, width and state of the navigation sidebar. Set by the documentation generator and never sent anywhere.
prefers-dark-mode-in-light-mode, prefers-light-mode-in-dark-mode (local storage)PersistentDocumentation pages only: remember the theme you picked with the light and dark switch.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

CookieDurationDescription
_ga2 yearsGoogle Analytics: registers a unique ID used to generate statistical data on how you use the website.
_ga_*2 yearsGoogle Analytics 4: persists session state for the property.
_clck1 yearMicrosoft Clarity: persists the Clarity user ID and preferences, unique to this site.
_clsk1 dayMicrosoft Clarity: connects multiple page views by a user into a single session recording.
CLID1 yearMicrosoft Clarity (clarity.ms): identifies the first time Clarity saw this user on any site using Clarity.
MUID13 monthsMicrosoft (bing.com, clarity.ms): identifies unique web browsers visiting Microsoft sites; used for advertising, site analytics and operational purposes.
ANONCHK10 minutesMicrosoft Clarity (clarity.ms): indicates whether MUID is transferred to ANID; Clarity does not use ANID, so this is always 0.
MR7 daysMicrosoft (bing.com, clarity.ms): indicates whether to refresh MUID.
SMSessionMicrosoft Clarity (clarity.ms): used in synchronizing MUID across Microsoft domains.
mp_51875322b58ddf1523d499cc7d1c80a2_mixpanel1 yearMixpanel: stores the anonymous distinct ID and super properties used for product analytics events.
hubspotutk6 monthsHubSpot: keeps track of a visitor's identity; passed to HubSpot on form submissions and used when deduplicating contacts.
__hstc6 monthsHubSpot: main cookie for tracking visitors; contains the domain, initial and last visit timestamps and the session count.
__hssc30 minutesHubSpot: keeps track of sessions to determine whether the session number should be incremented.
__hssrcSessionHubSpot: set whenever the session cookie changes, to determine whether the visitor has restarted their browser.
__cf_bm30 minutesCloudflare, on behalf of HubSpot (hubspot.com, hs-scripts.com, hs-analytics.net, hs-banner.com): bot management, telling people from automated traffic.
SRM_B13 monthsMicrosoft (bing.com): browser identifier paired with MUID, set during Microsoft Clarity's cross-domain sync.
__mpq_51875322b58ddf1523d499cc7d1c80a2_ev (local storage)PersistentMixpanel: queue of analytics events waiting to be sent.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

CookieDurationDescription
_fbp90 daysMeta Pixel: first-party browser identifier used to attribute and measure Facebook and Instagram ads.
_fbc90 daysMeta Pixel: stores the click identifier (fbclid) from a Meta ad that led to this site.
fr90 daysMeta (facebook.com): used to deliver, measure and improve the relevance of ads.
_gcl_au90 daysGoogle Ads: conversion linker; stores ad-click information for conversion attribution.
_gcl_aw90 daysGoogle Ads: stores the Google Ads click identifier (gclid) for conversion attribution.
_gcl_dc90 daysGoogle Ads: stores the DoubleClick click identifier (dclid) for conversion attribution.
IDE13 monthsGoogle DoubleClick (doubleclick.net): used for ad delivery, measurement and retargeting.
test_cookie15 minutesGoogle DoubleClick (doubleclick.net): checks whether the browser supports cookies.
NID6 monthsGoogle (google.com): contains a unique ID used by Google to remember preferences and for ad personalization.
bcookie1 yearLinkedIn (linkedin.com): browser identifier cookie to uniquely identify devices accessing LinkedIn and detect abuse.
bscookie1 yearLinkedIn (linkedin.com): remembers that a logged-in LinkedIn member is verified by two-factor authentication.
lidc24 hoursLinkedIn (linkedin.com): facilitates data center selection.
li_gc6 monthsLinkedIn (linkedin.com): stores guests' consent regarding the use of cookies for non-essential purposes.
li_sugr90 daysLinkedIn (linkedin.com): used to make a probabilistic match of a user's identity.
li_fat_id30 daysLinkedIn: member indirect identifier used for conversion tracking, retargeting and analytics.
UserMatchHistory30 daysLinkedIn (linkedin.com): used for the ID sync process; stores the last sync time to avoid repeating it.
AnalyticsSyncHistory30 daysLinkedIn (linkedin.com): stores the time a sync took place with the lms_analytics cookie.
ln_or1 dayLinkedIn: determines whether Oribi analytics can be carried out on this domain.
apolloAnonId (local storage)PersistentApollo website tracker: anonymous visitor identifier and event queue kept in browser local storage, not in a cookie.
__cf_bm30 minutesCloudflare, on behalf of LinkedIn, Apollo.io and HubSpot Ads (linkedin.com, apollo.io, hsadspixel.net): bot management, telling people from automated traffic.
68c4578a29a1ad0011d47ef7_eventQueue, 68c4578a29a1ad0011d47ef7_canTrack (local storage)PersistentApollo.io: queue of visitor events waiting to be sent, and whether tracking is allowed.
lastExternalReferrer, lastExternalReferrerTime (local storage)PersistentMeta Pixel: the last external site that referred you here and when, used for ad attribution.

Other cookies are those that are being identified and have not been classified into any category as yet.

No cookies to display.

Formnext

Join us at Formnext 2026, Frankfurt!

November 17–20, 2026 · Frankfurt, Germany
Hall 12.1, Booth A129

Formnext 2026 details