Privacy
This page describes ForgeBridge from November 18, 2026, when it moves to a subscription. Until that day there are no accounts and no payments; the file, the metrics and the server log already work as explained here.
Your file
Your file is used only to convert it. While it uploads it may pass through a temporary file on the server, which is deleted when the request ends; anything a crash leaves behind is wiped when the service starts. The conversion runs in memory and the original is not kept.
The converted result lives only in memory: it can be downloaded for one hour or up to 3 times; after that it is no longer reachable and is removed from the server's memory. The result is not written to disk.
To avoid counting the same file twice, a fingerprint is computed when it is converted: a 64-character code that comes from its contents and can't be used to rebuild the file. If you download it with your account, that fingerprint is recorded in your account, in the month you downloaded it.
If you have Pro and upload a file over 300 MB, that file does not go through my server: your browser sends it straight to a private Cloudflare R2 space (North America), with a temporary address that only a person with Pro receives. From that order I keep in your account the file's name and size, the printer it is for, a small image of the model if the file has one, its status and the dates. I download the file, convert it by hand and upload the result to the same space. Both files are deleted automatically after 7 days, and if you delete your account I delete them right away, along with the record of the order. For each order I also keep, for 7 days, a fingerprint of your email that cannot be reversed and the date you requested it. That fingerprint stays even if you delete your account, and its only purpose is to stop anyone from getting around the limit of 4 per week by deleting their account and signing in again. It is the only case in which a file of yours is kept for more than an hour.
Your account
You need an account to download. You sign in with Google or with a 6-digit code I email you, and if you use the same email, both ways lead to the same account.
From your account I keep your email; if you sign in with Google, your Google account's identifier (from Google I receive only that and your verified email: not your name or your photo); when you created it and the last time you signed in; your browser's language when you created it, so I can write to you in your language; whether you want news by email (off by default; I don't send any news today); the fox you picked as your avatar (I don't keep photos); the printers you ticked in “My printers”; if you have Pro, what you loaded in “My filaments” (per printer, the color and material of each slot), your slicer profiles and your spools (see below); the printers you asked me to add, with their date; and how many different files you downloaded each month, with each one's fingerprint and the time of its first download.
If you leave it on, I also keep your history: one line for each different file you download in the month and for each printer you download it for (if you convert the same file for another printer from the result, that adds another line, even though it does not count as another file in your month). Each line has the date and time, the file name (up to 120 characters), the file's fingerprint, the printer, the title, the designer and the model number if the file carries them, the codes of the report's notices and the link to download it again while the result exists. Never the file. You can delete it whenever you like, and turning it off deletes it.
If you upload your slicer profiles, the bundle you exported from OrcaSlicer or from Flash Studio is read in memory. While it uploads it may pass through a temporary file on the server, which is deleted when the request ends, and the bundle itself is not kept. For each preset I keep its name, the factory preset it comes from, the material if it is a filament, and the settings you changed. For each profile I keep the name you gave it, which one is the default, when you uploaded it and which program it came from. I never keep the connection to your printer (the address, the API key, the user and the password, if the profile carries them) or the paths on your computer to the bed image or model. I discard them before saving, and “My account” tells you if I removed the connection. If the profile carries a post-processing command (Z-Mod uses one), I keep it as it is, with whatever path it has, because it is part of your profile. You see it in “My account” and it reaches every file you convert with that profile. You can remove a profile whenever you like, even if you have left Pro, and it is deleted right away.
If you have Pro and add spools to “My filaments”, for each spool I keep the brand, the line, the material, the color and its name, the net weight, how much is left, the weight of the empty spool if you know it, how you measured it (new, weighed or by eye) and when, the price if you enter it, when you added it, and which slot of each printer it sits in.
When I tell you whether each spool is enough, I keep the date of that conversion, the printer, the download identifier and, if your history is on, the file name (up to 200 characters) and its fingerprint. When you clear your history or turn it off, the name and the fingerprint are deleted from those conversions. Anything with no active deduction is deleted after 12 months. For each filament I keep the slot, the spool, the range of grams I estimated, how much of that I estimate is purge, and whether it is enough, tight or not enough. When you press “I printed it”, I keep how much was deducted from each spool, when, where the grams came from (my estimate or the number you typed) and whether you undid it. I never keep the file.
If you remove a spool from your shelf it stops showing, but I keep it until you delete your account, because your deduction history names it. Your spools, the measured conversions and the deductions come out in “Download my data” and are deleted with your account.
For each open session I keep when it started, when it expires and the last time it was used; not your IP or your browser. For each code you request, your email, when it expires and how many attempts you've made; a code expires after 15 minutes and works only once. Session tokens and codes are not stored as they are: only their fingerprint, which can't be reversed.
I use it to let you download, count the files in your plan, remember your printers and your avatar, show you your history, choose which printers to add and know whether you have Pro. The emails I send you are these: the sign-in code, when you ask for it; if you ask to join the creator program and I approve you, the notice that you are in; if you have Pro and upload a file over 300 MB, the notice that it has been converted; and, if you have Pro as a gift for donating, one the week before it ends. Invoices and receipts for a payment are sent to you by Paddle, not by me (see “Payments and subscription”).
Only I see account data, except what you publish as a creator (see “Creators and referrals”). My metrics dashboard shows only totals: how many accounts are created per day and how many there are, how many downloaded 1, 2, 3 or more files in the month, and which printers are requested; never a list of emails.
Your account stays until you delete it. Your history is deleted on its own after 12 months. A session lasts 90 days from when you sign in; signing out deletes it, and expired ones are deleted every day. The codes you request are deleted once a day has passed, even if you never signed in, and of the file count I keep the current month and the 12 before it.
The accounts database has its own backups: a daily one on the same server, which only the service can read, and another one, encrypted before it leaves, at Cloudflare R2 (North America), which that provider cannot read. The server keeps the last 14 daily copies, and R2 deletes each copy after 14 days; so something you delete may remain in them for about two more weeks, or a little longer if a daily copy is ever missed.
In “My account”, “Download my data” gives you a file with your email, whether you sign in with Google, when you created the account and last signed in, your preferences, your printers, your filaments, your spools with their deductions, your slicer profiles with their settings, your avatar, your open sessions, how many files you downloaded each month, your history, your printer requests and, if you take part in the creator program, what I keep about you as a creator and, if you came through a creator's link, which one and when. “Delete my account” deletes it right away, along with your sessions, your printers, your filaments, your spools and their deductions, your profiles, the file count, your history, your requests, everything about the creator program (photos included) and the codes requested with your email.
My metrics don't keep your email or your account number, but they can be associated with your account. When you download a file with your account, your account records, to the second, the moment you asked for it, and the metrics record that same download, also to the second, when it finishes, next to the daily pseudonym explained under “What I measure”. The two times match or are apart by how long the download took, and by matching them, what I measure of your use (your visits, conversions and downloads that day, and the times you sign in) can be tied to your account. If you want to see it or have me delete it, write to hola@forgebridge.app from your account's email: I handle it by hand. “Download my data” and “Delete my account” don't reach that part.
If you sign in with Google, you go to Google's page and come back: I load no Google script on my pages. Google learns that you signed in to ForgeBridge, as with any site that offers sign-in with Google, and what it does with that is in its own privacy policy. If you don't choose Google, Google isn't involved.
The emails I send you (the ones above) go out through ZeptoMail, Zoho's email delivery service, which works for me as a processor: it receives only your address and the text of the email. I use its United States server.
Payments and subscription
Pro is charged by Paddle (Paddle.com Market Limited), which sells as the “Merchant of Record”: the payment, the invoice, the taxes and the refunds go through Paddle. Paddle receives your card and payment details, not me: I never see or store your card number. What Paddle does with them is in its own privacy policy.
From Paddle I receive your customer and subscription identifiers, the plan (yearly or monthly), its status and its dates, and, for each charge or refund, the amount, the tax, Paddle's fee, what is left to me and the country of the charge. They let me know whether you have Pro and keep the books; my dashboard shows only totals. The amounts of a charge are kept without your email even if you delete your account; the rest is deleted with it, and deleting the account cancels the subscription at Paddle.
If you donated through Ko-fi or Buy Me a Coffee before the launch, I keep the email you donated with, the platform and the dates of your gift year of Pro; I load them by hand from the list those platforms provide. If you sign in with that email, your account has Pro until that date. This data stays even if you delete your account; if you want me to delete it, write to me at hola@forgebridge.app.
Cookies and what your browser keeps
If you don't sign in to an account or open a creator's link, ForgeBridge uses no cookies. If you do sign in, it uses your session's: it's called __Host-fb_sesion, it is strictly necessary (without it the site doesn't know you signed in), it only travels to this site, no script on the page can read it, and it lasts 90 days; signing out deletes it. While you sign in with Google, another one, __Host-fb_oauth, is added for 10 minutes and deleted when you come back. If you open a creator's referral link, __Host-fb_ref is saved: it is not needed to use the site, it carries only that creator's code, it only travels to this site, no script on the page can read it, and it lasts 30 days; it is deleted when you sign in to an account (more under “Creators and referrals”). There are no third-party or advertising cookies.
Your own browser also keeps the language you chose; whether you were signed in last time, so the header doesn't jump while it loads; the files you drop on the home page, until the app picks them up when it opens; and, if you sign in with Google, a mark of how it ended (signed in, cancelled or failed) and when, with no session data. If Google opens in the same tab, the page also keeps what you had on screen (the files, the downloads that were waiting, the printer and your settings) so you can pick up where you left off, which is deleted when it's read and useless after 30 minutes, and that tab notes that you went to Google until you come back. None of that is sent anywhere on its own: files are uploaded only when you convert them.
On the payment page, Paddle may keep in your browser what it needs to complete the payment; its privacy policy explains it.
No third-party trackers
There is no third-party analytics or pixels: this page makes no request to any other domain, not even for fonts. The only exception is the payment page (/pagar), which loads Paddle's script to show the payment; no other page loads it.
What I measure
I measure visits with my own script, without cookies or third-party services (your session cookie is not used for measuring). For each visit I keep the page, the language, the device type (computer, phone or tablet), the country you connected from and only the domain of the site you came from (never the full page; empty if you came directly or from ForgeBridge), for 180 days.
The country comes from matching your IP address against a database that lives on my own server: no external service is queried, so your IP never leaves it. I keep only the two-letter country code (AR, ES, US…), never the city, the region or any coordinates (that database does not even carry them), and for an IPv6 address the prefix is looked up, not the full address. If your IP is not in the database, or you use a VPN, the country stays empty.
Your IP address and your browser's identifier are combined into a code of 16 characters using a secret key that changes every day and exists only in the server's memory: during that day the code is a pseudonym; afterwards nobody, not even me, can link it back to you.
If your browser sends the Global Privacy Control or Do Not Track signal, I count the visit without that code.
After 180 days the code is erased from the database along with the rest of the record; after that only daily totals remain, with no per-visitor data at all: how many visits and how many people there were each day, and from which countries, with nothing pointing at anyone in particular.
For each conversion I record the target printer, the brand of the printer the file had been prepared for (for example, Bambu Lab or Creality), whether it succeeded or what kind of error it gave (for example, that the file was already sliced), the approximate file size, the layer height, the chosen profile, how many filaments it had and how many were kept, whether anything was trimmed, whether the model came split or with painted supports, how long it took and from what device type it was done; never the file name, its contents or its colors. If you installed ForgeBridge as an app from your browser, the conversion carries that mark, so I know how many people installed it. If the file is rejected for not coming from Bambu Studio, I also keep the name of the program that made it, as declared by the file itself (for example “tinkercad”), without its version; never the file name. If you convert with your slicer profile, the conversion also carries that mark and whether your profile carries a post-processing command, never its settings, its names or the command. And if you convert it again from the result, it carries whether you picked another profile or none.
When you upload a file, the app gives it a random number that comes neither from its name nor from its contents and sends it with every attempt, to know how many times the same file was tried. Your browser keeps it only while the tab stays open, and it is erased from the server database after 180 days.
If the file carries a MakerWorld model number or its designer's number, I add the conversion to a weekly total: the model, its title, the designer and the license as the file declares them, the target printer, the country and how many times it was converted. That total carries neither the pseudonym nor your account, and it is kept with no time limit. It tells me which models get converted the most for Flashforge. Those totals also feed what each creator sees and, if I publish it, a weekly ranking (see “Creators and referrals”).
Until I removed them, I recorded each click on a donation button (only the destination domain, never the full URL); those records follow the same time limits. I record each download of the result: whether it succeeded, whether it asked to sign in to an account, whether the month's files had already been used, whether it came from an older version of the extension during its days without an account, or what error it gave, and from what device type. And I count, without uploading anything, the times the app rejects a file in your browser for exceeding the size limit or for not being a .3mf; when it is about size I also keep which range it fell into (say, between 150 and 200 MB), never the exact size nor the file name. And I count, without the daily pseudonym or the page you came from, the times the window to sign in to an account is opened (and from where), which method is used to sign in and why it fails when it does. And I count, also without the daily pseudonym or the page you came from, the times the screen for the monthly file limit is shown and the times the payment is opened from that screen. And I count, without the daily pseudonym or your account, the profile uploads I reject and why (for example, because it could not be read or because it is for a nozzle I do not accept yet), with the nozzle when it is one I know and with the printer when the bundle declares it and it is one I convert or another Flashforge model; for any other I only note that it is from another brand; never the file name, the preset names or their content. And I count, also without the daily pseudonym or the page you came from, the times you convert a file for another printer from the result, with the printer you picked. And I count, also without the daily pseudonym or your account, the conversions where I tell you whether each spool is enough, with the worst result (enough, tight or not enough), and the times you press “I printed it”, and whether the grams were my estimate or the number you typed. I never record the grams, the spools, the printer or the file name here.
A backup of this database is saved daily on the same server and kept for 14 days. Another copy, encrypted before it leaves the server, is stored with a different provider (Cloudflare R2, in North America) so it is not lost if the server fails: that provider cannot read it and deletes it on its own after 14 days. So a deleted record can survive in the backups for up to two more weeks; any visitor code left there can no longer be linked to anyone, because the daily key it was made with no longer exists.
The home page shows two of these to anyone who visits: how many files have been converted in total and, for the most recent conversion, how long ago it was, which printer it was for and which country it came from. Never the file or its name, and if your browser sends Global Privacy Control or Do Not Track, your conversion never shows up there.
Only I see the rest of this data, behind a password, and it is used to know how many people use ForgeBridge and what fails.
What the server logs
That access log does not keep your IP address, cookies, your browser language or the page you came from; what the visit script measures is described in the previous section. The log keeps the method and path of each request (never your file name), the response code, the time, the duration, the response size and your browser's identifier (User-Agent), among other technical request data.
Your IP address is used in memory to limit abusive use: one counter per address and path, which is discarded on its own at most one hour after your last request (the sweep runs with the next request the server handles), and another one of the requests you have in progress, which is cleared when they finish. Neither is written to disk or to the log, and both disappear when the service restarts. The basis for that use is my legitimate interest in keeping the service available. For profile uploads there is also a counter per account, also in memory, which is discarded after an hour.
The server's operating system logs, like any server, administrative connection attempts (SSH) with their IP address. That does not go through the application or through this filter.
The application log records an account's internal number, never its email, when the account is deleted or when recording a download fails.
If you write to me
The site has a contact form and the app offers to leave a message after a conversion or an error. For each message I keep the text you write, your email (required: it is the only way to reply to you), the link to the model if you paste it, the language, which page you sent it from, the country of your connection (from the same local country database I use for visits, just the two-letter code) and, if you send it from the app, the name and size of the file you uploaded, which printer you picked, which ForgeBridge version converted, the profile and the choices (purge, extruders, materials) and which notices or error it showed, with their values. Never the file.
I use it to read your message and reply to you. A message is kept until I archive it; once archived it is deleted after 180 days. Nobody else receives it: there are no third parties in between, neither to send it nor to store it.
Creators and referrals
The creator program is for people who publish models on MakerWorld. When you ask to join, I keep the link to your MakerWorld profile, the code I give you to put in your profile, when you made the request, whether you pressed “I put it there”, and, if I reject it, the reason, which you see in your account.
When I approve you I also keep the name you display, your bio of up to 280 characters, up to 6 links to your channels, your photo, the link and the photo you give each model, the models you add by hand, which ones you hide, the code of your referral link and the MakerWorld designer number that I tie to your account.
I review each request by hand. I open your profile, check the code and choose which designer number, among those the converted files carry, to tie it to. You can join even if nobody has converted a model of yours yet; in that case the number is tied when one shows up. When I approve you I email you in your language, through ZeptoMail (see “Your account”). If I reject your request, I send nothing.
With that number, your dashboard shows the weekly totals of your models: how many times each one was converted, for which printers and from which countries. A country with fewer than 3 conversions is added to “Other countries”. They are the same totals as in “What I measure”: they carry neither the pseudonym nor anyone's account, so you will never know who converted a model of yours. The dashboard also shows how many visits came through your referral link in the last 30 days, only the number.
What you publish is public. Your page shows the name you chose, your approved photo, your bio, your links, the “Creator” badge and your models with how many times each one was converted for each printer. It shows neither countries nor accounts, and a model with fewer than 3 conversions in total does not appear. Anyone can see it, and what gets copied outside ForgeBridge I cannot delete.
The photos you upload (yours and one per model) are converted to my own format, without the hidden camera and location data, and are stored under a name that comes from their content. Until I approve them by hand they wait in a private folder that no page serves, and your page keeps showing the previous photo, if there was one. A rejected photo is deleted. A photo is also deleted when you replace it, when you withdraw and when you delete your account. Published photos also go into the encrypted Cloudflare R2 copy, which is deleted after 14 days, so a deleted photo may stay there for about two more weeks.
Your referral link is forgebridge.app/r/ followed by a code of yours, different from your page's. Whoever opens it gets a cookie, __Host-fb_ref, which keeps only that code, only travels to this site, no script on the page can read it, and lasts 30 days. It does one thing: if within those 30 days that person creates a new account, signing in with Google or with a code, a row in their account records which creator they came from and when. The cookie is deleted as soon as they sign in to an account, new or not; if the account already existed, nothing is noted. The creator does not see that row. If the code does not exist or the creator withdrew, no cookie is saved. The code also stays in the access log, as part of the path, without your IP. Also, every time someone opens the link I add one visit to that creator's day, and that is all the creator sees: how many visits they had in the last 30 days. Only the creator, the day and the count are stored, nothing about who comes in; visits from automated programs do not count, and days older than 30 are deleted.
I may publish a page with the most converted models of the last week. For each one it shows the title, the designer as the file declares them, how many times it was converted and for which printers. Only models with at least 3 conversions in the week get in, and it shows neither countries nor accounts. The designer appears even if they are not in the program. If you want your name or one of your models not to appear there, write to hola@forgebridge.app and I will take it out, whether or not you are in the program; if you are, you can also hide a model from your section.
You can withdraw whenever you like from “Creator”, in “My account”. When you withdraw, your page, your referral link and the program's Pro stop right away, and your photos are deleted. The accounts that already came through your link stay noted. The rest of what you wrote, such as your name, your bio and your links, and the request data, is not shown anywhere and stays in your account until you delete it. “Delete my account” deletes everything about the creator, including the notes about whoever came through your link. If you want me to delete something sooner, write to hola@forgebridge.app.
The browser extension
The Chrome extension, the same one you install in Edge, Brave and Opera, does the same as the website, on its own. A .3mf finishes downloading, it reads it from disk, sends it to my server to be converted for the printer you chose and saves the converted file next to the original. Everything above still applies: your file is converted in memory and not kept, and the result lives for one hour or 3 downloads.
It does not look at the pages you browse. It asks for no permission on MakerWorld, Printables or any other site. It reads a single file, the .3mf the browser has just reported as a finished download, at the path the browser gives it. It never looks through your folders or reads other files. To read that file, the browser asks you to turn on “Allow access to file URLs” on the extension's page.
In your browser it stores only your settings (the printer, whether you want the report, whether it is on), a short list of recent activity with file names, which you can clear whenever you like, and, while it works, the name of the file it is converting or that is waiting for you to sign in, which it deletes when done (if the browser shuts it down halfway, when it starts again). None of that leaves your browser. Each conversion made from the extension counts as one more conversion, with the same data described under “What I measure” plus the extension's version, to know how many people use it. If you convert several files at once (batches are a Pro feature), each conversion is counted as part of a batch.
Since version 0.3.0, the Chrome extension (the same one for Edge, Brave and Opera), before uploading each file, asks my server whether an account is needed to download and whether you're signed in. That check and the upload carry your session cookie, if you have one, which your browser already keeps for the site; the extension doesn't read it. If an account is needed and you aren't signed in, it tells you, opens the sign-in page and asks again every 3 seconds, for up to 10 minutes. What you convert with the extension while signed in is recorded in your account when it downloads and, if you have it on, shows up in your history. The Firefox extension does none of this: you do the conversion yourself on the page.
The Firefox extension reads no file at all: Firefox only tells it that a download finished and what the file is called. It shows you a notice and, if you click it, opens the file's folder and ForgeBridge in a tab; you upload the file yourself by dragging it in, like on the website. It has no permission on any site, stores only your settings and recent activity in your browser, and the conversion you make from that tab is counted with the extension's version, like the others.
The plugin for OrcaSlicer shows ForgeBridge in a panel inside OrcaSlicer. You do the conversion on that page, with your account, just like on the web, and it is counted with the plugin’s version. The plugin does not read your files or your projects: it only receives the converted file from the page, saves it in its own folder inside OrcaSlicer’s data and asks OrcaSlicer to open it. The last 10 converted files stay there; it deletes older ones, except any you have saved over. When OrcaSlicer opens, the panel loads the ForgeBridge page, just as if you opened it in your browser. The plugin itself does not connect to the Internet or send your files anywhere. If you click “Open the full ForgeBridge” or “Upgrade to Pro”, it opens that page in your browser; OrcaSlicer asks for your permission the first time.
Where the server is
At OVHcloud in Beauharnois, Canada. The accounts database lives on that same server. I use no content delivery networks or third-party proxies: the encrypted connection ends on my own server. For your account, outside it only Google is involved, if you sign in with Google; ZeptoMail, for the emails I send you; Paddle, if you pay for Pro; and Cloudflare R2, which stores the encrypted backups without being able to read them and, if you upload a file over 300 MB, that file for 7 days.
Contact
For any question about this page: hola@forgebridge.app.
Countries come from the DB-IP IP to Country Lite database, licensed under Creative Commons Attribution 4.0.
Last updated: