Legal

Privacy Policy

Last updated: November 15, 2026

Meshory is a local-first desktop app: the product itself never uploads your files anywhere. This policy covers the personal data this website handles: your email address if you join the early-access list, your purchase details if you buy a license or renew your updates, limited data used for our advertising, and what you send if you report a problem with the free 3MF converter. It also covers what the desktop app sends: anonymous crash reports and usage statistics, plus library figures stored with your license, all of which you can turn off; the details it needs to activate your license; a MakerWorld account name lookup, which you can turn off; the OrcaSlicer download for print estimates, only if you ask for it; a problem report or suggestion, only when you send one; and, only if you set them up, what its optional AI features send. The optional browser extension is covered too: it sends us nothing you do or read. So is Etsy order import, which is still in development.

Who we are

Meshory and meshory.com are operated by Onemind LTD, a company registered in Cyprus under number HE 432027, with its registered office at Faneromenis 12, 3076 Limassol, Cyprus.

What we collect

If you join the early-access list, we store the email address you entered. No names, no passwords.

If you report a problem from the free 3MF converter, we receive the reason you chose, your message if you wrote one, and what the converter knew about the conversion: the result, the slicer, printer, plate and color count of your project, its file size, the slicer, printer and profile you picked, and your browser. Never your file or its name. You can add your email address so we can reply, and we use it only to answer that report. To keep out spam, the form uses Cloudflare Turnstile, and we count reports from each IP address for ten minutes.

If you buy a license, payment is handled by Stripe, our payment processor. Stripe collects your name, email, payment details, and billing country (used for tax calculation). Your card number never touches our servers. We receive and store your email, the license key issued to you, and a record of the purchase so we can look your license up for support and refunds.

If you renew your updates, payment is handled by Stripe in the same way. We store a record of each renewal with your license: the Stripe checkout session and payment, the amount and currency, when you paid, your updates end date before and after it, and whether it was refunded. We use it to extend your updates, send your receipt, and handle refunds and support.

To renew without your license key, you can enter the email address you bought with on the renewal page: we look that address up in our license database and, if it has a license that can be renewed, email a renewal link to it, and the page answers the same either way. To keep out abuse, that form uses Cloudflare Turnstile, and the renewal page passes your IP address to our license server, which counts requests for a minute for each IP address and each email address (or license key, if you enter one). A renewal link carries a token that identifies your license. The renewal page keeps it in a cookie, mshy_renew, for three hours, so it never appears in a page address.

If you open a friend's referral link, a first-party mshy_friend cookie keeps their code for 60 days so the discount applies at checkout. It holds only the code and the discount. If you then buy, we record which link the purchase came from so its owner can earn their reward; we never tell the owner who bought. If you share your own link, we store the PayPal address your rewards are paid to (your license email unless you set and confirm another) and a record of each payout.

What it's used for

Your email is used to send a signup confirmation and occasional updates about Meshory: early-access invites, launch news, and roadmap votes. We never sell your address, and share it only as described in this policy.

If you buy a license, we also send your email address and order number to Trustpilot, which emails you an invitation to review your purchase. Nothing else about your purchase goes with them: not your license key, not your payment details. Data shared with Trustpilot is also governed by Trustpilot's Privacy Policy.

Where it's stored

Emails are stored in our subscriber database and with Resend, the email service we use to send messages. Purchase, renewal and license records live in our license database and with Stripe. Reports from the 3MF converter, and problem reports and suggestions sent from the desktop app, reach our support inbox as emails sent through Resend, and are kept there.

Analytics

We use PostHog (EU-hosted) to understand how the site is used: pages visited, referral source, and anonymous usage events. For visitors in the EU/EEA/UK/Switzerland, PostHog runs in a cookieless mode that stores no analytics identifiers on your device; elsewhere, PostHog uses cookies and local storage to recognize repeat visits. A single first-party cookie remembering your country code selects the right mode. We never sell your data. How we measure advertising is covered below.

If you open a feedback questionnaire we emailed you, PostHog (EU-hosted) records with your email address that you opened it, and if you answer, your answers too, so we can read them in context and, if you ticked the box, write back to you. We use them only to improve Meshory.

We also use DataFast to see which pages and which marketing channels bring visitors, and which of them lead to a purchase. It stores two first-party cookies on your device: datafast_visitor_id for a year, and datafast_session_id for thirty minutes. Those two identifiers are attached to the Stripe checkout if you buy, which is what lets a purchase be credited to the visit that led to it; they carry nothing about you beyond the visit itself. For visitors in the EU/EEA, UK, and Switzerland it loads only after you accept cookies on the banner shown on your first visit, and decline means nothing is stored at all. Elsewhere it is active by default. Clearing the mshy_ads_consent cookie resets that choice, and setting datafast_ignore to true in your browser's local storage opts you out everywhere.

Advertising

We advertise Meshory on Meta platforms (Facebook and Instagram). To measure whether those ads work, we use the Meta Pixel, which reports events such as page views, checkout starts, and purchases back to Meta, along with technical data (IP address, browser) and, where available, a hashed version of your email used to match the event to a Meta account. This lets us see which ads lead to purchases and reach similar people. We use it only to measure and improve our advertising, and we never sell your personal data.

Some of these events are sent from our server rather than your browser, so that ad measurement still works when a browser extension blocks the Pixel. They carry the same information described above, plus a random identifier we generate for your visit, and they are matched with the browser event so a single action is never counted twice. If you arrive from a Meta ad we also store that ad's click identifier in a mshy_fbc cookie so the purchase can be attributed to it. Both are subject to the same consent choice below: decline and neither the server events nor that cookie happen.

For visitors in the EU/EEA, UK, and Switzerland, the Meta Pixel loads only after you accept advertising cookies on the banner shown on your first visit. Decline and it never loads. Elsewhere it is active by default. You can change your choice at any time by clearing the mshy_ads_consent cookie, and you can control ad personalization in your Facebook and Instagram settings. Data shared with Meta is also governed by Meta's Privacy Policy.

If you buy a license, we may also share your contact details with our advertising partners for advertising purposes. If you declined advertising cookies, they are never shared. To have your details left out, email us.

We also use Google Tag Manager to load our measurement tags, and Google Analytics to report on how the site is used alongside our advertising. These receive page views and conversion events such as checkout starts and purchases, along with technical data (IP address, browser), and Google Analytics sets cookies on your device to recognize repeat visits. We use them only to measure and improve our advertising, and we never sell your personal data.

Google is governed by the same consent choice as Meta. Google's tag loads in a consent-aware mode: for visitors in the EU/EEA, UK, and Switzerland it stores nothing on your device (no cookies, no identifiers) until you accept advertising cookies on the banner, and declining keeps it that way; before consent it can send Google at most cookieless, aggregate signals. Accepting enables the cookies and measurement described above. Elsewhere it is active by default. Clearing the mshy_ads_consent cookie resets the choice. Data shared with Google is also governed by Google's Privacy Policy.

The desktop app

Your model files stay on your computer. The app has no account and never uploads them. It does send some information, depending on what you use: crash reports and usage statistics, the details it needs to activate your license, a name lookup for MakerWorld accounts that you can turn off, the OrcaSlicer download for print estimates if you ask for it, a problem report or suggestion if you send one, and, only if you set them up, what the optional AI features need.

Crash reports and usage statistics. These are anonymous: they're tied only to a random identifier generated on install, which isn't linked to your email, your license, or your purchase.

Crash reports go to Sentry (EU-hosted) and contain the error and the stack trace that produced it. Before a report is sent, the paths in it are stripped: your watched folders, your home directory, and the name of any model, image, archive, or document file are replaced with placeholders. Native crash dumps, which can contain arbitrary memory, are disabled entirely.

Usage statistics go to PostHog (EU-hosted) and are limited to a fixed list of events defined in the app: which version, operating system, and architecture you run; that a feature was used, such as starting a search, sending a model to a slicer, or creating a collection; and how big your library is. Library size is reported only as a range, for example “1,000–5,000 models” or “10–50 GB”, never as an exact figure, and no more than once a day. We use it to know which library sizes to make the app fast for. If you use the Meshory Capture extension, they also describe how each import from it went: which site it came from, whether it finished or was cancelled, how many files it had and how many failed (as ranges) and the most common reason, whether its pictures, description and archive unpacking worked, and the extension's version and browser. An “Import all” run is reported the same way, with how many releases it had and why it paused or stopped.

Crash reports and usage statistics never include file names, folder names, file paths, tags, notes, or search terms. You can turn them off from the banner shown when you first open the app, or at any time in Settings. With them off, the app sends no crash reports or usage statistics, and no library figures with your license.

Your license. To activate your license, to refresh it (about once a week, or each time you open the app during a trial), and to check whether an update is covered by it, the app sends our license server your license key, an identifier for this computer, and the computer's name, and the server records when this computer last checked in. We use these to confirm your license is valid, to count the computers it's active on against its limit (see the Terms of Use), and to stop counting a computer once you deactivate it in Settings. Deactivating sends the same key and identifier. This happens whether or not crash reports and usage statistics are on. The app also checks our download server for new versions; that request carries no license or library details.

If crash reports and usage statistics are on, activating or refreshing your license also sends the app version you're running and the size of your library: how many models and files it holds, its total size, and how many folders you watch. If you use Meshory Capture, they also include the extension's version, the browser it runs in, and when it last reached the app. Unlike the usage statistics above, these figures are exact and stored against your license: one set per computer, replaced each time new figures arrive. We use them to help when you contact support and to see how Meshory is used, such as which versions are still running. They never include file names, folder names, file paths, tags, notes, or search terms. Turning crash reports and usage statistics off stops them being sent; to have figures already stored deleted, email us.

Optional AI features. AI tagging and semantic search send nothing about your library until you choose a provider in Settings and run them. AI tagging can use your own API key for OpenRouter, OpenAI, Anthropic or Google Gemini, an Ollama model running on your own computer, or the Codex CLI signed in with your ChatGPT account. The app sends requests directly from your computer to the provider you chose, using your key or your account. They don't pass through Meshory's servers, and that provider's privacy policy applies; OpenRouter forwards each request to the AI model that handles it, so that model provider's policy applies too. With Ollama, the requests stay on your computer. Meshory never sees your ChatGPT sign-in.

AI tagging sends each model's file name, folder path, and existing tags. If you turn on image tagging, it also sends a rendered picture of the model. If you write custom tagging instructions, they go with each tagging request too.

Semantic search sends each model's file name, folder path, tags, and AI description, plus the names of files inside archives, to build its index, and sends your search terms each time you search. It goes through your OpenRouter key and uses OpenAI's text-embedding-3-small model.

MakerWorld account names. A 3MF file saved from MakerWorld can carry the number of the MakerWorld account that saved it. When you open the details of such a file and haven't named that account yourself, the app asks Bambu Lab's public profile service (api.bambulab.com) for the account's public name and offers it as a suggestion. The request carries only that account number, and like any web request it shows Bambu Lab your IP address. No file or file name is sent, the answer is kept on your computer for 30 days, and Bambu Lab's privacy policy applies to the request. You can turn this off in Settings → Privacy with “Look up MakerWorld account names”.

Print estimates. The app works out print time and filament by handing a file to OrcaSlicer on your computer; Meshory sends the file nowhere. If you choose to have Meshory download its own copy of OrcaSlicer rather than use one you installed, the app fetches that release from OrcaSlicer's page on GitHub (github.com), and on a Linux computer with older system libraries it also fetches a few Ubuntu libraries from Launchpad (launchpad.net). Nothing is downloaded until you ask for it. The requests carry no license, file, or library details, and like any web request they show GitHub or Launchpad your IP address; their privacy policies apply to them.

Reports and suggestions. Send feedback, in the app's header and its Help menu, sends nothing until you press Send report or Send idea. Then the app sends our license server your message; the email address in Reply to, which starts as your license email and which you can clear, though then we can't reply; the app's version, language and theme, your operating system with its version and architecture, and which part of the app you were in. It also sends your license key, which the server uses to add whether your license is a trial or paid, and its email if you left Reply to filled in. A problem report can also carry, each only if its box is ticked: the app's diagnostics, ticked to start with, which are its recent logs and details about your computer and library, such as its size, its sources and recent scan problems; a screenshot of the Meshory window as it was when you opened Send feedback, which is off until you tick it; and, when you report a failed conversion, the error details shown in the form. While “Hide file and folder names in diagnostics” is on in Settings → Privacy, as it is unless you turn it off, file and folder names are removed from the diagnostics and the error details. The server emails it all to our support inbox through Resend, where it is kept, and we use it only to answer you and to fix Meshory. To keep out abuse, the server counts reports from each IP address for a minute, and keeps a daily count of the reports from each license.

The browser extension

Meshory Capture is an optional browser extension for Chrome, Edge, Brave and Firefox, installed separately, that brings a release or model from Patreon, MakerWorld, Printables, MyMiniFactory, Thingiverse, Thangs, Cults3D, Creality Cloud or Snapmaker Space into the desktop app. It sends Meshory no copy of anything it reads. It tells the Meshory desktop app on the same computer its version, the browser it runs in, and, when something goes wrong, what kind of failure happened on which site, on which day and how many times, such as a page it could not read or a download link that had expired. It also tells the app how many MakerWorld download links it asked for in the last hour and day, which the app keeps only in the diagnostics a problem report can carry. In Firefox it tells the app all this only while you allow technical and interaction data for it in Firefox's add-on settings. The app passes the failures on only if crash reports and usage statistics are on, as described above, and none of it includes page addresses, creators, titles or file names. In Chrome, Edge and Brave, while you use it on MakerWorld, Printables, MyMiniFactory, Thingiverse or Thangs, it downloads one public file from meshory.com every few hours that says where its buttons go on those sites; like any download, that request shows our host your IP address and that the extension is installed.

When you press its button on a release or model, it reads it from the page you are on or from the site's own API: the title, the description, the pictures, the creator's name, and the names and sizes of its files. That capture is kept in the extension's storage in your browser, where it stays until the next one replaces it. While an import is unfinished, or has files that failed and can be retried, the extension also keeps its capture and the addresses of its files on the site there, until the import is finished or cancelled; the download links it is given are never stored. “Import all” on a creator's page or a collection reads the list from the site's API, and then each model in it the same way. What it reads is handed to the Meshory desktop app on the same computer through the browser's native messaging, and does not leave your computer. On those sites it also asks the desktop app which of the releases on the page are already in your library, by their numbers on the site and sometimes their addresses, so their buttons can say so.

To fetch a file, the extension asks the site for that file's download link using the session your browser already has with it, and passes the desktop app that link; the app downloads the file. Patreon's and MakerWorld's links are short-lived. On Patreon, MyMiniFactory and Thingiverse it asks for the file's first byte to learn where the link leads, then stops. Most of these sites accept your browser's session as it is, and the extension never sees those cookies. Three sites' APIs want a sign-in token instead, so when you use the extension on one of them, it reads that site's own sign-in cookie and sends it only to that site's own API: accessToken on Thangs, login_access_token on Snapmaker Space, and model_token, model_user_id and model_device_id on Creality Cloud. It reads no other cookies and never stores these. On Thingiverse it asks the site for an API token for your session and uses it only with Thingiverse's own API. Your passwords never pass through the extension. It reaches only what you can already open while signed in, and does not bypass paywalls, membership tiers, or creator settings.

On two sites it does one more thing. On Thangs, it tells Thangs about each download, as Thangs' own Download button does. On Cults3D, if you have no order for a free model, it first places a free order for it on your Cults3D account. Cults3D's bot check turns away the extension's own requests, so it asks for a Cults3D download link from your open Cults3D tab and reads only where that link leads; it never blocks or changes a request.

On MakerWorld, Printables and Thingiverse, a See real prints button shows the photos people posted of their own prints of a model. To decide whether to show the button, the extension asks the site whether a model has any. The photos are read from the site's own API only when you press it, are shown over the page, and are neither stored nor sent anywhere.

The Chrome, Edge and Brave version is allowed to read some sites it does not support yet, such as GrabCAD and CGTrader, because adding a site in an update would otherwise switch the extension off until you accept it. It reads nothing from those sites until it supports them.

Etsy orders

Meshory is adding a way for sellers who print what they sell to turn their Etsy orders into prints. It is not available yet. When it is, you download your orders from Etsy as a CSV file and open it in Meshory. The file is read on your computer and its contents are never sent to us. Meshory drops the buyer's details, such as their name and address, as it reads the file, and keeps the rest only on your computer.

Meshory for Etsy sellers explains exactly what is read and what is kept.

Unsubscribing & deletion

Every email we send includes an unsubscribe link. If you'd like your address removed from the list entirely, email us and we'll delete it.

Contact

Questions about this policy or your data: support@meshory.com.