What you should know about your model

Parcel boundaries are advisory

Parcel geometry comes from the Danish cadastre through Datafordeler. The lines are official map data, but their position is advisory. Only a licensed land surveyor can establish a legally valid boundary on site.

Sources used by the map and model

• Addresses: Adressevælger and DAR. Parcels and BFE: Datafordeler and the Danish Geodata Agency's cadastre.
• Terrain heights: the Danish elevation model from the Danish Agency for Climate Data via Mapterhorn, CC BY 4.0.
• Road centrelines, lakes and selected watercourses: official GeoDanmark source data delivered through Datafordeleren, CC BY 4.0. Sea areas follow the OpenFreeMap/OpenStreetMap map data. MapBorn adapts and stylises the data for print. Attribution for the official layers: @geodanmark · CC BY 4.0.
• Printable buildings and building parts use OpenStreetMap geometry, including available height and roof tags, so the exported model follows the same building-data family as the background map. The geometry is still simplified into printable solids and is not an architectural LOD2 model. Attribution: © OpenStreetMap contributors, ODbL 1.0.
• Background map: OpenFreeMap and OpenStreetMap data.

What leaves your device?

When you search, the address text is sent through MapBorn's bounded server route to the official Adressevælger and DAR services. The selected area is used for bounded requests for parcels through Datafordeleren, OpenFreeMap/OpenMapTiles building data, GeoDanmark roads and water through Datafordeleren, and terrain tiles. Studio uses the same building source as the map at all supported area sizes. Hosting and data providers may process IP address, time and ordinary technical log data to deliver and protect their services.

Imported project files, GeoJSON areas and GPX/KML tracks are processed locally in the browser. They are not included in short sharing links. Free previews use the browser; an invited customer's print package is built by the server from the selected model snapshot.

Customer account and login

Customer login uses a one-time email link. The free preview needs no account; purchases and downloads of your own models require login. We store your email, a hashed login token and session, and the records needed for historic credits, projects, builds, orders and files. Login links expire after 15 minutes; sessions expire after 30 days. We do not store a customer password.

Server-built print packages belong to the model owner's account. Completed files are kept in private object storage for 90 days. Download access expires at the stored expiry time; scheduled cleanup then deletes the ZIP and individual 3MF files. This does not delete the account or its order and build records. A free preview alone does not grant access to print files.

An authenticated customer can download a JSON copy of their account, project, credit, order, build, file and privacy-request records from the account page, including withdrawal declarations sent to their verified account email. Security secrets, payment webhook payloads, private storage paths and stored model files are not embedded in that export. Contact support for information not included in the account export or for a request without an account.

The account page also accepts an authenticated deletion request. The request is recorded and reviewed before any deletion takes place, can be cancelled while it is still waiting, and does not automatically erase records that MapBorn must retain for legal or accounting reasons.

Withdrawal declarations without an account

The withdrawal form records the name, agreement reference and receipt email you provide, your selected language, the confirmed declaration and its receipt time. We use these to receive and document your declaration, send a receipt and review it. A separate notice goes to the operator for handling. Submitting the form does not give access to an order or automatically authorise a refund.

Please do not enter payment-card details, passwords or sensitive personal information. The form does not ask for a reason. Receipt and review records are not automatically erased after 90 days; that period applies to model files. You can contact support about your declaration and your data rights without creating an account.

Who is responsible for your data?

MapBorn is operated by Rasmus Rød Nørgaard Hvilsom, the data controller. Address: Engvej 2, 4130 Viby, Danmark. For questions about your data and requests to exercise your rights, contact support@mapborn.com.

Why we process account data

We use contact, account and project data to fulfil your requests and the services agreed with you, or steps you request before an agreement (GDPR Article 6(1)(b)). Public map requests and limited technical/security events support our legitimate interests in providing the requested preview, keeping the service available and preventing abuse (Article 6(1)(f)). We use records required to handle statutory data rights, withdrawal and accounting obligations under Article 6(1)(c), where those obligations apply. These purposes are separate from advertising or marketing profiling.

The required account email enables login and transactional messages. Without it we cannot provide an account. Model selections and project data are needed for the model features you choose; do not submit unnecessary personal or sensitive information. You may object to processing based on legitimate interests, and we assess your particular circumstances rather than treating all processing as unconditional consent.

Cloudflare hosts the application, database, private model storage and transactional email. Stripe is the selected payment provider, but live payments are not enabled. The official Danish map services and the map/terrain providers receive bounded requests needed to show or build the selected location. Any transfer of personal data outside the EU/EEA and the relevant safeguards remain part of the pre-launch privacy review.

The customer database and private model-file bucket are restricted to the EU. This storage setting is not a promise that every hosting, email, logging or payment operation takes place only in the EU.

Messages you send to MapBorn's contact addresses are handled in mailboxes hosted by Simply.com. This is separate from Cloudflare's delivery of automatic login and receipt emails.

Cloudflare's storage of full sent-message previews is disabled for mapborn.com. The customer-facing Worker keeps sanitised application/error logs but does not persist automatic request invocation logs containing full visit URLs. Cloudflare describes up to seven days of retention for Workers Paid logs; this is separate from the private account and transaction records. Disabling new logging does not prove that earlier provider-held copies or logs have already been erased. Resend is not configured on the current live Worker; historical deliveries still require individual review where relevant.

Cloudflare's data-processing terms include the EU standard contractual clauses for restricted transfers. Stripe describes both processor activities on a merchant's instructions and its own controller activities, including fraud prevention and regulatory duties; its transfer information describes the EU–US Data Privacy Framework where applicable and standard contractual clauses. These provider safeguards are not a claim that all processing stays in the EU. Contact support for information about the applicable safeguards and copies. Cloudflare data-processing terms · Stripe privacy information.

The 90-day file period is not a retention period for every account record. Other records are assessed against the ongoing account/service, outstanding credit or refund claims, disputes and any specific legal retention duty. Account, project, order and support records do not currently have a general automatic deletion timer. A deletion request therefore requires an individual review and actual deletion or a specific reason for retaining each necessary category; it is not fulfilled merely by hiding an account. Any retained financial documentation must be distinguished from model or support data, and backups must not restore data already erased.

Purpose-specific retention

Operational retention policy 2026-10-07-v1. The periods below are applied through individual review and housekeeping; they are not a claim that every system has an automatic deletion job. A deletion request can require earlier removal. A specific legal duty or unresolved claim can justify retaining only the necessary records for longer, with a documented reason and review date.

• Completed model files: 90 days of download availability, followed by the existing scheduled file cleanup. Account deletion also requires removing private model snapshots and project geometry, not only the downloadable ZIP.
• Necessary financial documentation: five complete years after the accounting year concerned. Original agreement and refund evidence needed for accounting or a concrete claim are kept separately from non-essential model data; the rule is not a five-year permission for all support messages or projects.
• Ordinary support cases: normally no more than 12 months after closure. Unnecessary attachments and identity documents are removed earlier; a financial dispute is assessed separately.
• Data-rights case evidence: the minimum record needed to document handling and possible claims, normally no more than 3 years after closure. This does not justify retaining an entire deleted model or all account information.
• Private rolling backup copies: a 30-day housekeeping target, with the latest verified recoverable copy protected. Erasure records must be maintained outside the restored database, and their deletions must be reapplied before a restored service is reopened. Testing an offline copy does not by itself prove production erasure or provider-side deletion.

Cookies, local data and your rights

The necessary customer-session cookie expires after 30 days and the login-state cookie after 15 minutes. The language cookie remembers your choice for one year; your explicitly selected theme remains until changed or browser site data is cleared. Error events are no longer persisted in browser storage, and the previous diagnostic-history key is removed on your next page visit without removing your theme or projects. An unfinished Studio login draft is stored in IndexedDB, is usable for 24 hours and is pruned on subsequent draft use, not while the browser is closed. MapBorn does not currently add its own marketing cookies.

Sanitised error reports are also sent to MapBorn's own support endpoint and written to the hosting provider's logs. They contain an incident code, time and bounded technical model information, not the selected address, raw coordinates, imported project files or credentials. Expired server login tokens and sessions are removed by scheduled cleanup; abuse-prevention rate-limit records are removed once their window is more than two hours old.

You may request access, correction, deletion, restriction, objection or data portability where the rules apply. Signed-in customers can export account records and submit a deletion request from the account page. You may also complain to the Danish Data Protection Agency. Contact support@mapborn.com for privacy requests.

We respond without undue delay and normally within one calendar month of receiving a data-rights request, including if it is refused. If the rules permit an extension for a complex request, we explain the reason and extension within the first month. We may ask for proportionate information to verify identity, but not for a new purchase or an account just to receive your request. The account export is not automatically a complete access response; contact support for records held elsewhere.

Before you print

1. Open the 3MF file in Creality Print.
2. Assign the named parts to your actual filament colours.
3. Check overall dimensions, every layer and any repairs.
4. Confirm small boundaries and details suit your nozzle and layer height.
5. Only start printing when the slicer preview looks correct.

Read the sources

Danish Geodata Agency on cadastral mapsDanish elevation modelGeoDanmark terms and attributionOpenStreetMap copyright