1.Who we are
This policy applies to printport3d.com, app.printport3d.com, our mobile applications, and the 3D printing, fulfilment and design services we provide (the “Services”). It covers everyone who uses them — visitors, buyers, sellers, and people whose orders we fulfil on a seller’s behalf.
The data controller — the business that decides how and why your personal information is used — is:
PrintPort3D
Privacy enquiries: privacy@printport3d.com
General support: support@printport3d.com
Security reports: security@printport3d.com
Seller-fulfilled orders. Where you ordered from a seller’s own storefront and we manufacture and ship the item, the seller decides what happens to your data and we handle it on their instructions. For that processing the seller is the controller and we act as their processor, under the written data processing terms in the data processing section of our Terms. If you want a copy of your data, a correction or deletion, ask the seller first — they are the right place to start, and we will assist them.
We remain independently responsible, as controller, for a narrower set of things we decide ourselves: the data we hold about the seller as our own customer, our security and fraud records, our legal and tax records, and our choice of manufacturing and shipping providers.
2.What we collect
2.1Information you give us
- Account. Your name, email address and password. If you sign in with Google, we receive your name, email address and profile image from Google instead of a password.
- Business and settings. Optional details you choose to enter — business name, business address, contact details, fulfilment preferences, logo.
- Orders. Billing and delivery addresses, the contents of your order, and its history. Card details go directly to Stripe; we store only the last four digits and card type that Stripe returns to us.
- Uploads. 3D model files (STL, OBJ, 3MF, STEP), product images, thumbnails and the descriptions and prices you write.
- Studio. The prompts you write, the parameters you set, reference images you upload, and the designs, code and images generated in response.
- Support. Tickets, replies, attachments, and your conversations with our AI support assistant.
- Instant quotes without an account. If you use the public quote tool, we take the model file and the resulting quote. These are anonymous and are deleted automatically — see Section 8.
- Push notification tokens, if you use our mobile app and allow notifications. We keep them while the app is installed and you remain signed in.
What you have to give us. Your name, email and password are required to hold an account; a delivery address and payment method are required to place an order. Without those we cannot perform the contract. Everything else above is optional, and nothing follows from declining it beyond the feature not working.
2.2Information we collect automatically
- Device and log data. IP address, browser and device type, operating system, referring page, pages viewed, actions taken, and timestamps.
- Approximate location, derived from your IP address. We do not collect precise GPS location.
- Usage. Which features you use, uploads and downloads, and search terms inside the product.
- Cookies and similar technologies — see Section 11.
Where you came from, when you create an account. When you sign up we save, with your account, the page you first arrived on during that visit, the website that linked you to it (its address without any search terms or other query text), any campaign tags on the link, which kind of advertising link it was if it was one (not the ad’s click identifier), and your country as our hosting provider reports it. We read this from the visit itself and keep it only in the open page until you sign up — no cookie or other browser storage is used — so it is recorded whether or not you accept analytics cookies. We use it to understand which channels bring us sellers. If you never create an account, nothing is saved.
In our security and audit records we store a one-way hash of the IP address rather than the address itself, so we can detect abuse patterns without keeping the address. Our hosting providers’ own request logs do hold the address, for their own retention periods.
2.3Information from other people
- Stripe — payment confirmations, the card brand and last four digits, and fraud signals.
- Shippo and carriers — shipping rates, validated addresses, tracking events and delivery confirmations.
- Connected storefronts — where a seller connects a store, we receive order and customer information needed to fulfil, including the end customer’s name and delivery address. That data does not come from the person it is about, so the seller is the one who tells them how it is used; that is part of their agreement with us. If you are that customer and you have found this page, Section 1 explains our role and Section 9 explains what you can ask us for.
- Google — your basic profile if you sign in with Google, and address suggestions when you type an address.
2.4What we do not collect
- We do not collect government identity documents, biometric data, precise geolocation, or special-category data such as health, religion, ethnicity, political opinion or sexual orientation.
- We do not buy personal information from data brokers.
- We do not use identity-verification or credit-scoring vendors.
- We do not run advertising pixels, and we do not build advertising profiles.
Nothing stops you typing sensitive information into a free-text box — a support message, a Studio prompt, a product description. Do not put anything there you would mind us holding. If you tell us you have, we will delete it.
2.5Children
The Services are for adults. You must be 18 or older to hold an account, and we do not knowingly collect personal information from anyone under that age. If you believe a child has given us information, write to privacy@printport3d.com and we will delete it and close the account.
3.Why we use it
This table sets out the bases on which we process data as controller — your account with us, your own orders, and our security, legal and tax records. Where we handle a seller’s customer data on the seller’s instructions (Section 1), the legal basis is the seller’s, not ours, and we do not use that data for any purpose here beyond fulfilling and supporting the order.
| Purpose | What we use | Legal basis (EEA/UK) |
|---|---|---|
| Create and run your account | Account details, log data | Performance of a contract |
| Analyse files, quote, print, pack and ship orders | Uploads, order and address data | Performance of a contract |
| Take payment and issue refunds | Order and payment data | Performance of a contract |
| Generate designs and images in Studio | Prompts, parameters, reference images | Performance of a contract |
| Answer support requests, including with the AI assistant | Ticket and message content, account context | Performance of a contract; legitimate interests in supporting users efficiently |
| Sync orders and products with a connected store | Store connection data, order data | Performance of a contract |
| Keep the Services secure and prevent abuse and fraud | Log data, hashed IP, audit records, rate-limit counters | Legitimate interests in protecting the Services and our users |
| Improve and debug the Services | Usage data and error data; for our own Studio users, prompts and outputs. Never a seller’s customer data | Legitimate interests in improving a service people rely on |
| Send service messages you cannot opt out of (order status, security, policy changes) | Email address, order data | Performance of a contract; legal obligation |
| Meet tax, accounting and legal obligations, and defend claims | Transaction records, correspondence | Legal obligation; legitimate interests in establishing and defending legal claims |
We do not use your personal information to make decisions about you that produce legal or similarly significant effects without a human involved. A person makes any decision that affects your account or your money. Some purely operational steps are automatic — for example, we hold an order that arrives with an incomplete delivery address until someone fixes it, and we advance an order’s status as it moves through production.
4.Who we share it with
4.1Service providers
We use other companies to run parts of the Services. They may only use your information to do the job we have engaged them for, under their standard data processing terms, which require them to keep it secure and to act on our instructions. Every one of them is named — with what it receives and where it is — on our sub-processor page, which we keep current. There are currently 16 of them.
4.2Connected storefronts
If you connect a store (Shopify, Etsy, Amazon, eBay, Walmart, TikTok Shop, WooCommerce, BigCommerce, Squarespace, Wix, Magento), information flows both ways so we can fulfil orders. Connections are held in your own Shippo account rather than through a direct integration. Each platform decides independently what to do with the data it holds, under its own privacy policy — for that, it is a controller and not our processor.
4.3Other sellers and buyers
If you ordered directly from us, no other seller is involved — we are the seller, and your details go only to the providers in Section 4.1 who help us make and ship your item.
If you ordered from a seller’s own storefront, that seller sends us your name and delivery address so we can make and ship the item, and we send them back the tracking information and order status. That is the whole of the exchange. We do not put buyers and sellers in touch with each other, we do not host a marketplace, and we do not give other users your email address.
4.4Legal and safety
We disclose information where we are legally required to — a court order, a subpoena, a lawful request from a public authority — and where we reasonably believe it is necessary to investigate fraud or a security incident, to enforce our Terms, or to protect the rights, property or safety of anyone. We assess every request, we do not hand over more than is asked for, and where the law allows it we tell you first. Where a request reaches data we hold for a seller, we notify the seller before responding unless the law forbids it, and we point the requester to them where we can.
4.5If the business changes hands
In a merger, acquisition, financing, reorganisation or sale of assets, your information may transfer with the business. We will give you notice by email or a prominent notice in the product, and the buyer remains bound by this policy until they give you notice of a new one. Where we hold data as a seller’s processor, we treat such a transfer as a change of sub-processor: we notify the seller in advance and they may object under the data processing section of our Terms.
4.6Aggregated and de-identified information
We may create and share statistics that cannot reasonably be used to identify you, from data we hold as controller only. We do not aggregate or combine a seller’s customer data with anyone else’s. We do not attempt to re-identify these statistics and we require the same of anyone we share them with.
5.Artificial intelligence
Several parts of the Services use AI models run by other companies. Studio generates designs and product images. The support assistant answers questions in our help widget. And our staff use AI tools to draft support replies and to triage orders. All of them send some of what you type outside our systems.
5.1What leaves our systems
| Feature | What we send | Who receives it |
|---|---|---|
| Studio — design generation | Your prompt, design parameters, the current design code, and the reference images you attach | Microsoft (Azure AI Foundry), Amazon Web Services (Bedrock), OpenRouter |
| Studio — look-ups | A short extract of your request (up to 600 characters) sent to a web search tool | Microsoft (Azure AI Foundry), OpenRouter |
| Studio — product images | Your image prompt and the reference images you attach, including photos of your own products | Microsoft (Azure, running FLUX), OpenAI, OpenRouter |
| Studio — image to 3D | A reference image | fal.ai |
| Support assistant | Your message and the recent conversation, plus the content of any of your own support tickets the assistant looks up for you | Microsoft (Azure AI Foundry) |
| Support tickets you send by email or the ticket form | The text of your ticket and our replies, with personal identifiers stripped, so a member of our team can draft a response | Microsoft (Azure AI Foundry), OpenRouter |
| Order triage and customer messages | Order status and evidence, with personal identifiers stripped | Microsoft (Azure AI Foundry), OpenRouter |
On the last two: a person reads, edits and sends every reply. The model never contacts you and never changes anything on your account. We strip the identifiers listed in Section 5.2 from what we send it — but that stripping is pattern-based, it does not detect names, and it will not catch every address format. Assume anything you write in a ticket may reach the model.
5.2What we strip out first
Before your text leaves our infrastructure it passes through an automatic redaction step that removes email addresses, telephone numbers, payment identifiers and US-format street addresses. It does not detect names, and it does not recognise every address format.
It is a safeguard, not a guarantee
Redaction is pattern-based. It will not catch everything, and it cannot recognise information that only you know is sensitive. Please do not type personal, confidential or commercially sensitive information into a prompt or a chat message.
5.3What the providers may do with it
Our agreements with Microsoft Azure AI Foundry and Amazon Bedrock provide that your inputs and the generated output are not used to train their models, and are not kept by them beyond returning a result and running abuse monitoring.
For every other provider we may route to — OpenRouter, which passes your request on to a model run by a further company, OpenAI and fal.ai — we cannot give you that assurance for every model.
5.4What we keep
- Studio projects — your prompts, the conversation, the generated code and parameters — stay in your account until you delete the project, and in any event no longer than 24 months after you last opened it — whichever comes first (see Section 8 for how that is enforced today).
- Generated images are stored in your account with the style prompt that produced them.
- Support conversations are stored in full — including the original, unredacted text of what you typed — so you and our team can refer back to them and so we can investigate abuse. The redaction in Section 5.2 applies to the copy we send to the AI provider, not to the copy we keep. If you have typed something into the chat you would rather we did not hold, tell us and we will remove that message.
- Look-up results. When Studio needs a real-world measurement, we cache the answer so the same question does not cost another search. The cache is keyed by a fingerprint of the request and is shared across all users: if someone else asks a materially identical question, they get the cached answer. It stores up to the first 300 characters of the request text after personal identifiers have been stripped — it holds no account, name or identifier of yours, but free text can still describe you, so do not put anything identifying or confidential in a Studio prompt. Cached entries expire after 30 days; Section 8 explains how that is enforced today.
5.5Human review
A small number of prompts and outputs are reviewed by our staff where we are investigating a safety, abuse or quality problem, or where you ask us to look at a specific result. Access is limited to the people who need it and is logged.
5.6Automated decisions
The AI features generate content. They do not decide anything about you — not your pricing, not your account standing, not whether an order is accepted. Where the model declines a request, you can ask a person to review it at support@printport3d.com.
6.How we protect it
- In transit, everything is encrypted with TLS.
- At rest, your data is encrypted by our infrastructure providers (Google Cloud and Firebase) using their platform encryption.
- Passwords are never stored by us — authentication is handled by Firebase Authentication, which stores a salted hash. Email verification is required before an account can be used.
- Access control. Staff access is limited to those who need it. Administrative actions require a recent sign-in, and the most sensitive ones additionally require a hardware passkey.
- Audit logging. Sensitive administrative actions are written to an audit log with the actor, the target and a hashed IP address.
- Rate limiting on authentication, support, AI and administrative endpoints.
- Uploads are validated by inspecting file contents, not by trusting the file extension, and are stored in access-controlled buckets.
- Redaction of personal identifiers before text is sent to any external AI provider.
No system is perfectly secure, and we cannot guarantee absolute security. If we discover a breach affecting your personal information, we will notify you without undue delay where the law requires it, and tell you what happened, what was affected and what to do about it. We notify the relevant supervisory authority in the EEA or UK within 72 hours of becoming aware, as Article 33 GDPR requires, and we notify US state authorities and affected residents on the timetables their breach-notification laws set, including Cal. Civ. Code §1798.82.
If you find a vulnerability, please tell us at security@printport3d.com. Our Terms contain a safe harbour for good-faith security research.
7.Staff access to your account
To investigate a problem you have reported, an administrator may need to view the Services as you see them — signed in as you, seeing your workspace, your orders and your connected stores.
- It can only be done by a named administrator, who must have signed in within the last ten minutes and hold an active hardware-key session.
- It is rate-limited, and each use expires automatically after two hours.
- Every use is written to our audit log with who did it, whose account, and when.
- It is used for support and abuse investigations. It is not used to browse accounts.
We do not notify you automatically when this happens today. You can ask us and we will tell you from the audit log, which we keep for 24 months — write to privacy@printport3d.com. Notifying you at the time is the right default, and it is not built yet.
8.How long we keep it
We keep personal information only as long as we need it for the purpose we collected it for, plus any period the law requires. These are our retention periods by category:
| Category | How long | Why |
|---|---|---|
| Account records (identifiers, credentials, profile) | Life of the account, then 7 years | Tax, accounting and limitation-period requirements |
| Order and transaction records | 7 years from the transaction | IRC §6001 / state tax record-keeping; chargeback and dispute windows |
| Payment card data | Full card numbers: never held by us. Card brand and last four digits: for the life of the order record (7 years) | PCI-DSS scope minimisation; the order record needs to identify the tender |
| Uploaded 3D model files and designs | Life of the associated product, then 90 days | Fulfilment, reprints and dispute resolution |
| AI Studio prompts and generated output | Until you delete the project, and no more than 24 months after you last opened it | Abuse prevention, safety review and service improvement |
| Support tickets and correspondence (incl. AI chat) | 3 years from resolution | Service quality and defence of claims |
| Server and security logs | 12 months | Security monitoring and incident investigation |
| Cookie and consent records | 24 months from the choice | Proving the consent state we acted on |
| Studio look-up cache (extract of the request text) | 30 days | Avoiding a repeated search for the same question |
| Studio-generated images | 24 months, or until you delete the project | Showing you your own work; abuse and safety review |
| Instant quotes without an account | 6 hours once produced or failed; 7 days in every case | Producing the quote you asked for, and nothing beyond it |
| Staff access and audit records | 24 months (impersonation session records: 12 months) | Answering who accessed an account, and when |
Anonymous instant quotes are deleted automatically: within six hours once the quote has been produced or has failed, and within seven days in every case.
What is enforced automatically today
The periods above are the maximum we will apply. This is how much of that runs by machine. One category is enforced by a live job today — anonymous instant quotes. For every other category a sweep runs nightly in review mode and does not yet delete; account records, order records, uploaded model files, generated images and server logs are not yet covered by it at all. Until that work is finished we delete on request and on a manual review cycle.
If you want something deleted before its period expires, ask us at privacy@printport3d.com — that route works today for everything in the table.
When a period ends we delete or irreversibly anonymise the information, by the mechanism described above. Copies may persist in encrypted backups for up to 98 days (daily snapshots rotate at 30 days, weekly snapshots at 14 weeks) before those rotate out. If information is subject to a legal hold — an active dispute, an investigation, a regulatory requirement — we keep it until the hold lifts, and no longer.
9.Your rights and choices
9.1Rights everyone has here
We honour these wherever you live, for the data we hold as controller. If your data reached us because you ordered from a seller’s own store, ask the seller first (Section 1): we act on their instruction and assist them, and we will tell you if we cannot act ourselves.
- Access and portability
- Get a copy of the personal information we hold about you, in a structured, machine-readable format.
- Correction
- Have inaccurate or incomplete information corrected. Most of it you can edit yourself in settings.
- Deletion
- Have your personal information deleted, subject to the exceptions in Section 9.4.
- Objection and restriction
- Object to processing we base on legitimate interests, or ask us to restrict it while a dispute is resolved.
- Withdraw consent
- Withdraw consent at any time where we rely on it — today that means non-essential cookies. Withdrawing does not undo processing already carried out.
- Email you receive from us
- We send three kinds of email. Service email — order status, security notices and policy changes — cannot be switched off while you hold an account, because it is how we perform the contract and how we tell you what is happening to your money and your prints. Setup email is about finishing the account you created: at most three messages, and none at all once you have started or if you tell us to stop. Every one carries a one-click unsubscribe that needs no login, and you can also switch it off in Settings. The weekly email is our newsletter: one message a week, and each one is a piece we have actually published — a guide to pricing, materials, selling, or the economics of a print business. Never the same piece twice; when we run out, the sequence stops. If you hold an account you are on it by default and can leave in one click; if you are on it and never held an account, it is because you or someone acting for you gave us the address, and we record where every address came from. Every message carries a one-click unsubscribe that needs no login and works from the message itself. Unsubscribing is permanent: we keep the record so that later imports cannot put you back on.
- What we do not do
- We do not sell or rent your address, we do not run advertising pixels in email, and we do not buy lists. An address with no recorded reason for us to hold it is never mailed.
- Where to write to us
- Every marketing email carries our postal address, as the law requires. It is [postal address pending].
- Close your account
- Ask us to close your account and delete what we are not required to keep. Either address works — the Terms use support@, this policy uses privacy@, and both reach us.
9.2How to exercise them
Email privacy@printport3d.com from the address on your account, telling us what you want. You do not need to use a particular form of words, and you do not need an account to make a request. Much of your information you can also correct yourself in settings.
- We will acknowledge within 10 days and respond within 45 days. If a request is complex we may take a further 45 days, and we will tell you why before we do. For people in the EEA and UK the response time is one month, extendable by two.
- A request to opt out of sale or sharing, or to limit the use of sensitive personal information, we act on within 15 business days — faster than the 45 days above, because California requires it (11 CCR §7026(f)(2)).
- We will verify your identity in proportion to the sensitivity of the request — usually by confirming control of the account email, and for a full export by also asking you one or two questions about recent account activity.
- You may use an authorised agent. We will ask for written authority signed by you, and we may still ask you to confirm directly.
- These rights are free. We will only charge, or refuse, where a request is manifestly unfounded or repetitive — and we will explain why.
- We will not discriminate against you for exercising any of them. No price change, no service reduction, no account closure.
9.3If we say no — your right to appeal
You can appeal a refusal
If we decline a request, we will tell you why and how to appeal. To appeal, reply to our decision or write to privacy@printport3d.com with “Appeal” in the subject line. Someone who was not involved in the original decision will review it and respond within 45 days, in writing, with our reasoning.
If we refuse the appeal, we will give you a link to lodge a complaint with your state Attorney General or data protection authority.
9.4When we may keep something anyway
Deletion is not always absolute. We may keep specific records where we must:
- Transaction and tax records, for the periods in Section 8. We cannot delete an invoice on request.
- Records needed for an active order until it is complete.
- Information under a legal hold, or needed to establish, exercise or defend a legal claim.
- Security and abuse records, including records of accounts we have restricted.
- Content another person has rights in, such as an order a seller must be able to evidence.
Where we keep something, we keep only what is necessary and we restrict it to that purpose. We will tell you what we have kept and why.
10.United States state privacy rights
10.1We do not sell or share your personal information
No sale. No sharing for advertising.
We have never disclosed personal information in exchange for money or for any other valuable consideration, and we do not disclose it for cross-context behavioural advertising — the two things California law calls “selling” and “sharing”. We run no advertising pixels and build no advertising profiles. Nearly every company we disclose your information to is one we pay to perform a service for us, under a contract that forbids them using it for anything else. Three do not fit that description: the carrier who delivers your parcel and any storefront you connect are independent controllers; and the AI providers in Section 5.3 (OpenRouter, OpenAI and fal.ai) may use inputs for their own purposes — which is exactly why we send them only redacted design content and reference images, never a seller’s customer data, billing data, delivery address or account identifier. None of this is a sale.
We also do not sell or share the personal information of anyone under 16, because we do not knowingly collect it at all.
Because we do neither, there is nothing to opt out of. We publish Your privacy choices anyway, so that the control exists if our practices ever change, and so you can record a preference in advance.
10.2Global Privacy Control
We honour the Global Privacy Control (GPC) browser signal as a valid opt-out request. If your browser or extension sends it, we treat it as an instruction to opt out of any sale or sharing and to disable non-essential cookies, without you needing to do anything else.
We honour it wherever you live, not only in California — Colorado, Connecticut, Texas, Montana, Oregon, Delaware and New Jersey all require recognition of a universal opt-out signal, and applying it to everyone is simpler than checking who is entitled to it.
We do not respond to the older “Do Not Track” header: it has no agreed meaning and was never finished as a standard.
10.3California — categories collected in the last 12 months
| CCPA category | What that means here | Where it comes from | Who we disclose it to |
|---|---|---|---|
| Identifiers | Name, email, postal address, IP address, account ID | You; automatically | Payment, shipping, hosting and email providers |
| Customer records | Billing and delivery address, card brand and last four digits, purchase history | You; Stripe | Payment, shipping and hosting providers |
| Commercial information | Orders, products, quotes, transaction history | You; connected stores | Payment, shipping, manufacturing and hosting providers |
| Internet or network activity | Pages viewed, features used, searches, uploads, interactions | Automatically | Hosting and (with consent) analytics providers |
| Geolocation data | Approximate location from IP address. Not precise location | Automatically | Hosting providers |
| Professional information | Business name and details for seller accounts | You | Payment and hosting providers |
| Visual information | Product photos, model renders, reference images you upload | You | Hosting and AI providers |
| Inferences | Product and feature preferences derived from your use | Derived by us | Hosting providers |
Sensitive personal information. One category applies to us: your account log-in credentials (§1798.140(ae)(1)(D)), which we collect so you can sign in and so we can keep your account secure. We hold them for the life of your account — the password itself is held by Firebase Authentication as a salted hash, see Section 6. We do not use or disclose them beyond authenticating you, securing the Services and preventing fraud, which are purposes §1798.121(a) and 11 CCR §7027(m) permit without a limitation right, so the right to limit does not arise. If you would like us to confirm what we hold and restrict it anyway, write to privacy@printport3d.com.
We collect no other category of sensitive personal information: no government identifiers, no financial account numbers, no precise geolocation, no biometrics, no racial or ethnic origin, religion, health, sex life or sexual orientation, and no contents of your private communications with anyone other than us.
Shine the Light. Under Cal. Civ. Code §1798.83 you may ask about disclosures to third parties for their own direct marketing. We make none.
10.4Other states
If you live in Virginia, Colorado, Connecticut, Utah, Texas, Oregon, Montana, Delaware, Iowa, Nebraska, New Hampshire, New Jersey, Tennessee, Minnesota, Maryland or another state with a comprehensive privacy law, you have rights to access, correct, delete and port your information, to opt out of targeted advertising, sale and profiling, and — in most of those states — to appeal a refusal. Section 9 tells you how to exercise all of them, and we apply it to everyone rather than checking which state you are in.
Two states go further and we follow them: if you live in Oregon or Minnesota you may also ask for a list of the specific third parties we have disclosed your data to, and Minnesota residents may ask us to explain the result of any profiling and to review the data behind it.
Nevada residents may direct us not to sell covered information. We do not sell it, and we will record your direction on request.
11.Cookies and similar technologies
Non-essential cookies are off until you switch them on. When you first visit, we show a banner with equally prominent “Accept all” and “Decline all” options and a per-category chooser. Nothing but strictly necessary cookies runs before you choose, and declining is one click.
| Category | What it does | Runs by default? |
|---|---|---|
| Strictly necessary | Signing you in, keeping your session, security, remembering your cookie choice | Yes — the Services cannot work without these, and they need no consent |
| Analytics | Google Analytics 4, to understand how the product is used and where people get stuck | No — only if you accept analytics cookies |
| Marketing | None in use today. If we ever add any, they will require consent first | No |
Analytics runs only if you accept it. We use Google Analytics 4 to see which pages people arrive on and where they stop during setup. It loads only after you accept analytics cookies — decline, or send a Global Privacy Control signal, and no Google tag is loaded at all and nothing is sent. That applies to measurements we send from our own servers too: before recording anything about an order, we check the consent choice you actually made. We send your account ID but never your name, email address or store address.
We also use Cloudflare Web Analytics, and it is not part of that choice — because it does not set a cookie, does not store any cross-site identifier and does not build a profile of you. It counts page views and how fast pages loaded. We use it because it measures without asking anything of you, and it is listed on our sub-processor list alongside everyone else.
You can change your mind at any time from “Cookie settings” in the footer. If you decline or withdraw consent, we clear the non-essential cookies we can reach from your browser. Your choice is recorded with a timestamp and a version, kept for 24 months, and refreshed after that so you are asked again rather than assumed to agree forever.
Browsers also let you view, block and delete cookies directly. Blocking strictly necessary cookies will stop you signing in.
12.International transfers
We are based in the United States and our providers are principally in the United States. If you use the Services from elsewhere, your information will be transferred to and processed there, under laws that may differ from your own.
For transfers out of the EEA, the UK and Switzerland we rely on:
- Standard Contractual Clauses approved by the European Commission, with the UK International Data Transfer Addendum where the UK GDPR applies, with every provider that offers them — which includes Stripe, Google, Microsoft, Amazon Web Services, Cloudflare, OpenAI, OpenRouter, Shippo, Resend and Printago, whose data processing terms incorporate them. You can request a copy from privacy@printport3d.com. The full recipient list, with what each receives, is on our sub-processor page.
- Data minimisation. To fal.ai we send only a reference image. Delivery to carriers relies on the transfer being necessary to perform your contract (Article 49(1)(b)).
Wherever you are, you can reach us directly. For anything in this policy, or to exercise any of your rights, contact us at privacy@printport3d.com — we handle every request ourselves and will not treat your location as a reason to decline or delay one.
13.Other sites and services
The Services link to and integrate with services we do not run — marketplaces, carriers, payment pages. This policy does not cover them. When you follow a link or connect an account, that company’s own privacy policy applies to what it does with your information.
14.Changes to this policy
We will update this policy as the Services change. When a change is material — a new category of data, a new purpose, a new kind of recipient — we will give you at least 30 days’ notice by email and in the product before it takes effect, and we will obtain your consent where the law requires it. Other changes take effect when posted.
The change still to come. This policy used to say we ran no marketing list. We do now — the weekly email described in Section 9.1 — and we have not started sending it. Commercial email is blocked in our systems until we publish a verified postal address, and we will not start before the 30 days’ notice described above has run.
Every version carries a version number and an effective date. We keep superseded versions — ask privacy@printport3d.com for the one that applied on a particular date.
15.Contact us and complaints
PrintPort3D
Privacy and data rights: privacy@printport3d.com
General support: support@printport3d.com
Legal: legal@printport3d.com
Security: security@printport3d.com
We are not required to appoint a Data Protection Officer and have not appointed one; privacy@printport3d.com reaches the person responsible for privacy here.
If you are not satisfied with how we have handled something, tell us first. You can also complain to a regulator:
- EEA: your national data protection authority. A list is at edpb.europa.eu.
- UK: the Information Commissioner’s Office, ico.org.uk.
- California: the California Privacy Protection Agency, cppa.ca.gov, or the Attorney General at oag.ca.gov.
- Other US states: your state Attorney General.
Version 2026-09-24 · Effective September 24, 2026 · Supersedes the version of September 11, 2026.