Privacy
Route & Remember uses the contact, delivery and product details you provide to prepare your order, answer questions and arrange delivery. Stripe handles your payment. We send order emails through SendGrid. These emails include a private order link. Keep it private.
Optional website analytics
If configured and you choose website analytics in “Privacy preferences”, we use PostHog to understand visits and where people stop in the order process. We send randomly generated browser and session identifiers, generic page categories, device/browser information, coarse traffic-source tags and step or error-code events. PostHog receives your IP address as part of the network request; geographic enrichment is disabled.
We do not send GPX files, route coordinates, poster text, names, contact or delivery details, payment details, private order/artifact identifiers, full query strings or private links. Session replay, automatic click capture and automatic error recording are disabled. A payment confirmation view is not treated as a verified purchase count.
Your analytics consent choice lasts up to 90 days. After acceptance, PostHog uses browser storage for anonymous identifiers and sessions. Declining or withdrawing stops future collection and clears the SDK’s persisted tracking data in this browser; it cannot recall requests already sent. Use “Privacy preferences” in the footer to change your choice. Analytics and advertising are separate choices, and neither is required to order.
See PostHog’s Privacy Policy. To request access or deletion, contact us using the footer link.
Optional advertising measurement
If you accept advertising measurement, we measure customer page visits and send Sydney cart and checkout events and confirmed purchases to Meta through its Conversions API. This includes browser and ad-click identifiers, your IP address and browser type, and the purchase amount and currency. We do not send GPX files, route coordinates, poster text, your name, email, phone number or shipping address to Meta through this integration.
When configured, Meta Pixel measures page views on our home, Sydney, custom-product, help, privacy and checkout pages after you accept advertising measurement. On Sydney checkout, Pixel also sends a checkout-start event with the product price and currency supplied by our server. This event shares an identifier with its server-side copy so Meta can avoid counting it twice. We do not send the contact or delivery fields you type into the checkout form. It can use browser cookies such as _fbp and _fbc. We remove query strings and fragments before loading Pixel, disable automatic event capture and do not provide advanced-matching contact details. Other private customer pages (studio, personalisation, cart, order and payment return) use server-side page views with generic page categories instead of Pixel. Private identifiers and query strings are not included. We do not measure admin pages. Purchases are sent only by our server after payment verification, not by Pixel.
We store your consent choice and server-side advertising identifiers for up to 90 days. Campaign tags from the ad link help us connect an order to its source. Sydney commerce events use the public Sydney campaign address. Server-side page views use generic paths such as /checkout or /order, never your private order link.
Use the advertising option in “Privacy preferences” (or “Advertising preferences” when website analytics is unavailable) at the bottom of the page to decline or withdraw permission. Checkout works without advertising measurement. Withdrawal stops future collection, clears Pixel cookies in this browser and cancels queued events that have not started sending. It cannot recall events already sent to Meta.
Order records are separate from optional advertising data. To ask about access to or deletion of your data, use the contact link in the footer or reply to your order email. Some order records may need to be retained for fulfilment or required business records.
See Meta’s Privacy Policy for its use of information.