Privacy & analytics

What we process

We do not require user accounts and do not intentionally collect names, emails, or precise home addresses for normal model generation. We process limited technical data needed to operate, secure, debug, and improve the service.

• Generated models are built from the map area you select and downloaded to your device. Your generations are not public and are not indexed; a model is only shared if you choose to create a share link (the area then travels inside that link).
• Server logs & security: the server keeps short-lived technical logs (request metadata, coarse/rounded location, error diagnostics) and uses your IP address transiently for rate-limiting and abuse prevention. We do not store raw IP addresses in analytics.
• Support: if you email support or use a “Report issue” link, we receive what you send (which may include a diagnostic ID and your browser) to reply. These never include payment data, passwords, or tokens.
• Retention: paid download files and their records are deleted automatically (within roughly 72 hours); diagnostic logs are kept only as long as needed to operate and secure the service.

Payments, if enabled, are handled by Stripe; we do not receive or store your card details. Privacy, personal data, or deletion requests: privacy@printmap3d.com.

Analytics consent

Product analytics (PostHog)

We use PostHog product analytics. Purpose: to understand how the product is used, improve generation quality, and debug failed generations.

Analytics help us understand aggregate product usage: page views, generation starts and completions, export downloads, popular generation settings (style, layers, format, tile mode) and failure categories. Exact values are reduced to coarse buckets before sending — e.g. the selected area, model duration, file size and triangle count become size ranges, not exact numbers.

We do not intentionally send names, emails, precise addresses, raw search queries, exact coordinates or bounding boxes, your model label, payment data, authentication tokens, or cookies to analytics, and we do not send your raw IP address. Approximate country may be inferred from the request; we never send your IP ourselves. Autocapture and session recording are disabled, and server-side analytics carries no user identity.

Analytics only runs if you accept it, and you can reject or withdraw consent at any time using the Analytics consent controls above. If analytics is disabled for the site, nothing is tracked at all.

Production analytics uses PostHog Cloud EU where available.

Error monitoring

We use Sentry, provided by Functional Software, Inc. d/b/a Sentry, for error monitoring and application diagnostics. Sentry helps us detect, diagnose, and fix crashes, failed generations, export failures, and other technical issues.

Sentry may process limited technical diagnostic data such as error stack traces, browser/device information, application route, request metadata, generation ID, and diagnostic context needed to debug failures.

We do not intentionally send payment data, passwords, authentication tokens, precise personal addresses, or sensitive personal data to Sentry. Session Replay is not enabled.

Maps & data

Using the map, place search, the live elevation readout and model generation may involve requests to third-party services: OpenStreetMap map tiles and Nominatim search (from your browser), and — on our server — the Overpass API for map features and AWS Terrain Tiles / Mapzen for elevation. These providers may receive technical information such as your IP address and the map area or search needed to provide this functionality. Map tiles and place search are essential for choosing locations.

For the full list of data sources, what enters a downloaded model, and the applicable licenses, see our Data Sources & Licenses page.