Policies

Privacy Policy

How Atlas Studio handles design, route, checkout and order information.

Last updated: 8 May 2026

UK launch status: UK GDPR draft. It covers categories, purposes, processors, retention, rights and cookies, but final controller/business identity details must be added before launch.

Controller and contact

Atlas Studio is responsible for the personal data processed to run the website, create proofs, take payment, fulfil orders and provide support.

UK launch note: the website still needs the final legal trading name, geographic business address, company number if incorporated, VAT number if registered, and a non-electronic contact route before this policy set can be treated as complete.

For privacy questions or deletion/access requests, email hello@atlasstudio.design with enough detail to identify the relevant order or design record.

Information we process

Atlas Studio may process map area, route/activity metadata, selected style, product options, proof assets, order reference, customer email, name, shipping address, support messages and basic technical/debug information.

Payment card details are handled by Stripe Checkout. Atlas Studio does not intentionally collect or store full card numbers.

Why we use this information

Design and proof data is used to render your artwork, recover checkout sessions, fulfil orders and provide support if something goes wrong.

Order and delivery data is used to take payment, produce the print, deliver it, meet accounting/legal obligations, prevent fraud and respond to customer service requests.

Legal bases

Atlas Studio uses personal data where it is needed to perform the purchase contract, take steps before you place an order, comply with legal obligations, or pursue legitimate interests such as service security, debugging and customer support.

Where optional marketing or non-essential cookies are used, Atlas Studio should rely on consent and provide a clear way to withdraw that consent.

Processors and sharing

Order and delivery data may be shared with service providers needed to operate the site, take payment, render artwork, produce prints, deliver orders, store assets, host infrastructure, analyse service health or debug support issues.

The launch stack includes third-party providers such as Stripe for payment and print/fulfilment partners for production and shipping.

Route and connected-service data

If route import is enabled and you connect an activity service, Atlas Studio uses the imported activity data to compose the artwork you request.

Disconnecting or revoking a third-party integration may stop future imports, but it may not remove design/order records already needed for an order, legal record or support case.

Retention

Order records are retained for operational, accounting and customer-support purposes. Proof and design assets may be kept while needed to fulfil, support, reprint or audit an order.

Debug logs are intended to avoid sensitive data and should be kept only as long as needed for operations, security and troubleshooting.

Your UK data rights

Under UK data protection law, you may have rights to be informed, access your data, correct inaccurate data, request erasure, restrict processing, object to certain processing and receive data portability in applicable cases.

You can also complain to the Information Commissioner's Office if you are concerned about how your personal data is handled.

Cookies

Strictly necessary cookies or similar storage may be used to run checkout, security and the service you request.

Non-essential analytics or marketing cookies should not be used unless the site presents a clear cookie notice with accept/reject choices and records consent appropriately.

These policies are practical UK launch drafts, not bespoke legal advice. They should be checked against the final business setup and replaced with solicitor-approved wording when available.