Privacy policy

What I collect

When you place an order I receive your name, email and shipping address from the payment processor (Stripe), plus the map design you configured — its coordinates, size, colours and frame. A design code itself holds only the design; no name or email is attached to it. If you save a map to a cart before buying, the email you type is kept with that cart — nothing else — so I can send you its link. To see the 3D preview of a map you design I ask for your email as well; it is kept with the design you were looking at, so I can send you the preview.

Payment

Payment is handled entirely by Stripe on their checkout page. I never see or store card numbers.

How it is used

Your details are used to produce and ship your order and to send you the order emails — confirmation, shipped, and a refund notice if there is one. A cart email goes only when you ask for the link, plus one reminder a few days later if you tick that box when saving. When you unlock the 3D preview with your email, I send one email about that design — a picture of it and a link to finish or keep editing — about an hour after you stop changing it, and not at all if you have already ordered. If you tick the box for news and offers, I add your address to my mailing list (kept at Resend, the service that sends my email); every message from that list has an unsubscribe link, and nothing goes to it otherwise. I don’t sell or share your information.

Carts

A cart lives 90 days from the last time you change it, then it is deleted with its email; the same goes for the email and picture kept when you unlock a preview. If you buy, the order keeps your details as above. The cart link I email you is the key to it — anyone with the link can open the cart, so treat it like a receipt.

Map data

Maps are built from © OpenStreetMap contributors (ODbL) and Mapbox terrain data. The coordinates you frame are sent to those services to build your model — nothing about you goes with them.

Analytics

I use a privacy-respecting analytics tool to count visits, see which steps of the designer people get stuck on, and catch errors. It records events like “map rendered” and “checkout started” with a design code at most — never a name, email or address.

The store also loads the Meta Pixel, so I can tell whether ads on Facebook and Instagram bring visits and orders. It reports the pages you view and the steps you take toward checkout to Meta, sets Meta’s cookie, and Meta may connect the visit to your Facebook or Instagram account under its own privacy policy. When you place an order I also tell Meta about the purchase from my server — the order total, the design code, and a one-way hash of your email so Meta can match the sale to an ad you clicked. Meta never receives your name, address, or the email itself. Your browser’s tracking protection or an ad blocker stops the pixel; the server-side purchase report is sent regardless.

Cookies

Four at most: a cart cookie once you save a map (it holds a signed cart id, not your email), a preview cookie once you unlock the 3D view (a signed id, not your email), the analytics tool’s own, and the Meta Pixel’s — the one advertising cookie here.

AR share links

The “view in your room” link stores only the map design — never personal data.

Questions or deletion requests

Email [email protected] and I’ll handle it within a few days. Order records I am required to keep for tax purposes stay; everything else goes.