Privacy Policy

This policy explains what Pack3D collects when you use the packing workspace, why, and what control you have over it. We have deliberately kept the service narrow: we run no third-party analytics, no tracking and no advertising, and we never sell your data. We count visits to our pages as anonymous daily totals, with no cookie and no identifier. The few outside providers involved are listed by name below.

Who is responsible

Pack3D ApS (CVR 46787404) operates this service and is the data controller. For any privacy question or data request, contact privacy@pack3d.net.

Pack3D is operated by Pack3D ApS, Brandsbjergvej 88, 2600 Glostrup, Denmark (CVR 46787404). Contact: contact@pack3d.net.

What we collect

Account details: the username you choose, your email address, and your password. Passwords are stored only as a salted Argon2 hash; we cannot read them. Your address is kept so we can recover your account and reach you about the service; we do not send marketing to it.
Service email: we send transactional messages only, and only to your own address: a link to confirm the address, a password reset link if you ask for one, a notice when your password changes, a notice when a sign-in method such as Google or Microsoft is connected to your account, a notice when these terms or this policy change, and, only if you turn it on in your account, an email when your jobs finish. These go through Postmark, a transactional email provider acting as our processor. There are no tracking pixels and no marketing.
Signing in with Google (optional): if you choose "Continue with Google", Google tells us your Google account identifier, your email address and whether Google has verified it. We ask for nothing else (no contacts, no files, no calendar) and we never write anything back to your Google account. The identifier is kept with your account so Google can sign you in next time; it is removed when you disconnect Google or delete the account.
Signing in with Microsoft (optional): if you choose "Continue with Microsoft", Microsoft tells us an account identifier it issues for this service and the identifier of the organisation your account belongs to (for a personal account, one value Microsoft uses for all personal accounts). We do not ask for your email address, your name or anything else, and we never write anything back to your Microsoft account. The identifier is kept with your account so Microsoft can sign you in next time; it is removed when you disconnect Microsoft or delete the account.
Terms acceptance: which version of these terms you agreed to when you registered, and when. We deliberately do not store an IP address with it.
Uploaded models: the 3MF or STL files you submit, kept only to produce your packed result.
Job data: filenames, settings (printer, clearance, scale), timestamps, and the resulting layout.
Contact messages: if you write to us through the contact form, we keep your message and the details you include with it (name, email address, printer count) so we can reply.
Feedback: if you report a bug or send an idea from the workspace, we keep the conversation (your messages and our replies), the plate image if you choose to attach it, and a copy of the job details it is about (filename, printer, settings and outcome). That copy is kept with the report even after the job itself is deleted, so the report still makes sense later.
Cookies: one strictly-necessary session cookie (HttpOnly, SameSite=Strict) that keeps you signed in. It expires after 24 hours at most (sooner after 8 hours of inactivity) and carries no tracking identifier. If you sign in with Google or Microsoft, two more strictly-necessary cookies exist for at most 30 minutes, only while that sign-in is in progress: one ties the provider's answer to the browser that asked, the other holds your place until you finish creating an account. In addition, our network provider Cloudflare sets a short-lived security cookie (such as __cf_bm) as part of the bot protection that shields the service from automated abuse. None of these is used for advertising or cross-site tracking.
Page counts: when a page of this site opens, your browser tells our server which page it was, and the server adds one to that page's total for the day. Nothing else is sent or kept with it: no cookie, no identifier and no browser details, and no IP address is stored with it. A contact message sent and an account created are counted the same way. The totals cannot tell one visitor from another, and no outside analytics service is involved.
Plan and payment: if you buy a paid plan, checkout happens on a page hosted by Stripe, our payment provider, and your card details go to Stripe and never to our server. We keep only what we need to run your plan: which plan you are on, whether the subscription is active, when the paid period ends, whether you have asked to cancel, how many jobs you have used this month, and the reference numbers Stripe gives your customer record and subscription. Stripe sends us a notice when a payment succeeds or fails or a subscription changes; those notices hold no card details.
Storage in your browser: the workspace keeps your light or dark theme choice, your choice of price currency and cached preview images of your plates in your own browser, so pages load faster. Any page may also note the time it last reloaded itself after a site update, so it never reloads twice in a row; that note is gone when you close the tab. They never leave your device and are not used to track you; clearing your browser data removes them.
Network address: your IP address is used briefly to rate-limit sign-in and registration attempts. It is not used to build a profile. The country Cloudflare says a request comes from is read when you open the pricing or upgrade pages, only to show prices in euros or dollars; it is not stored.
Error reports: if a page fails to load or crashes in your browser, the page sends us a short report so we can fix it: the page address without anything after the ?, the error message and where in our code it happened, which version of the site you had, and your browser family (for example "Safari (mobile)"). It carries no name, email address, account or IP address.
Server logs: the server keeps a technical log of account events (for example a registration, an email confirmation or a password reset) that names the account involved, so we can investigate faults and misuse.

Why we may process it (legal bases)

To provide the service you asked for: packing your files and showing your results, running your account, signing you in (including with Google or Microsoft if you choose it), and sending the service messages listed above (performance of a contract).
To take payment and keep the books: charging for a paid plan, sending receipts, and keeping the accounting records that Danish law requires of a company (performance of a contract, and legal obligation).
To keep the service secure and working: rate limiting, abuse prevention, server logs, error reports, and backups that let us restore the service after a failure (legitimate interest).
To answer you: replying to messages you send through the contact form (legitimate interest, or steps taken at your request prior to a contract).
To fix what you report: handling bug reports and ideas you send from the workspace (performance of a contract, and our legitimate interest in improving the service).
To show what you agreed to: keeping the version and date of the terms you accepted, including a later version you accept when the terms change (legal obligation and legitimate interest).
To know which pages are used: the anonymous page counts described above. They hold no personal data, so they need no legal basis; we list them so that nothing is left out.

How long we keep it

Your uploaded input file is deleted automatically once its job finishes.
Packed results and job metadata stay until you delete the job, and the oldest entries are removed automatically once your history grows beyond a fixed limit.
Account details are kept until you delete your account, which you can do yourself at any time from the account page. Deleting your account removes your jobs, uploaded files, results, and feedback conversations from the server immediately.
Plan and payment references are removed with your account. Invoices and payment records are not: the accounting law that applies to us requires them to be kept for five years, and Stripe keeps its own records of payments under its own legal obligations. Deleting your account also cancels any subscription so that you are not charged again.
Feedback conversations are kept until you delete your account. You can mark a conversation resolved yourself; to have one erased sooner, write to privacy@pack3d.net.
Contact messages are kept while we handle your inquiry and deleted automatically after 12 months at the latest.
Server logs and error reports are deleted automatically after 90 days at the latest. The records that let an email confirmation or password reset link work once are kept for 30 days.
Page counts are daily totals with nothing personal in them; each day's totals are deleted after about 13 months.
Backups: the server's data is backed up every night, and each backup expires after about six months at the latest. Something you delete therefore disappears from the backups as the older copies expire. Backups are used only to restore the service after a failure; if one is ever restored, we repeat the deletions and account deletions made since it was taken, as far as our records of them allow.

Who else is involved

The service is self-hosted on a server located in Denmark (EU). Your files, results, and account data are stored on that server, and an encrypted backup copy is kept by our backup provider. The complete list of processors acting on our behalf is:

Cloudflare, Inc. (United States): network and security provider. Cloudflare terminates the secure connection at its edge, so requests (including files you upload) pass through its systems on the way to our server; it also applies bot protection and sets the security cookie described above. If a page fails to load, your browser may also send Cloudflare a short network error report (the address it tried and the kind of failure), which Cloudflare uses to keep its network working. How long Cloudflare keeps its own network logs is set by Cloudflare's privacy policy, not by us.
Postmark, operated by ActiveCampaign, LLC (United States): transactional email provider. It delivers the service messages described above, so it handles your email address and the contents of those messages. It is never used for marketing, and no uploaded file, packed result, or job data is ever sent to it.
Backblaze, Inc. (United States company, storing in its EU data centre in the Netherlands): backup storage. It stores the nightly backups described above. Each backup is encrypted on our server before it is sent, and Backblaze does not have the key, so it cannot read what it stores.
Stripe Payments Europe, Ltd. (Ireland, part of Stripe, Inc. in the United States): payment provider. It runs the checkout page for paid plans, takes the card payment and manages the subscription, so it handles your name, email address, billing details and card details. Stripe also acts as an independent controller for what it must do under its own legal obligations, such as preventing fraud and meeting financial regulation, under Stripe's privacy policy. No uploaded file, packed result, or job data is ever sent to it.

Those four are the complete list. We use no other processors. If that changes, this list is updated before the new processor begins handling any data, and business customers who have a data processing agreement with us are notified.

Advertising. There is none today. If we later show advertising on the free plan, it will be served by an outside provider, it will load only after you have given consent to it separately, and paid plans will not show it. This policy and the provider list above are updated before any advertising starts.

Google and Microsoft are involved only if you choose to sign in with one of them, and then not as our processor: your Google or Microsoft account is your own arrangement with that company, and it handles that sign-in under its own privacy policy. Choosing one lets that company know that you signed in here. We receive only what is listed above, and send neither anything about your files, jobs or results.

International transfers

Cloudflare, Postmark and Backblaze are United States companies, and Stripe's parent is one, so the data each one handles for us can be transferred to, or accessed from, the US.

Cloudflare handles request data in transit. That transfer is safeguarded by the EU-US Data Privacy Framework, under which Cloudflare is certified, and by the standard contractual clauses in Cloudflare's data processing addendum.
Postmark handles your email address and the contents of the service messages we send you. That transfer is safeguarded by the standard contractual clauses in ActiveCampaign's data processing addendum.
Backblaze stores the encrypted backups in the EU (the Netherlands). Because Backblaze is a US company, any access from the US is safeguarded by the standard contractual clauses in Backblaze's data processing addendum, and by the encryption itself: Backblaze holds the backups but not the key to read them.
Stripe handles payments through its European entity in Ireland. Any transfer to its US parent is safeguarded by the standard contractual clauses in Stripe's data processing agreement.

Your stored data (files, results, account details) stays in the EU: on our server in Denmark, and as encrypted backups in the Netherlands. To get a copy of the safeguards mentioned above, write to privacy@pack3d.net.

Your rights

If you are in the EU/EEA you have the right to access, correct, export, restrict, or delete your personal data, and to object to processing. Email privacy@pack3d.net and we will take care of it within the time the law requires. You may also complain to your national data-protection authority (in Denmark, Datatilsynet).

Giving us your username, email address and files is necessary to use the service: without them we cannot provide it. Nothing else is required of you.

We make no decisions about you by automated means alone that have legal or similarly significant effects on you, and we do no profiling.

Children

Pack3D is a tool for production printing and is not directed at children. You must be at least 16 to create an account, and at least 18 to buy a paid plan.

Changes

We may update this policy as the service evolves. When we make a material change, we update the effective date above, tell you by email if your address is confirmed, and ask you to accept the new version the next time you sign in, as described in the Terms of Service.