Colofon
Angaben gemäß § 5 DDG:
Kai Raschke
Leipziger Straße 31
06108 Halle
Deutschland
Wirtschafts-Identifikationsnummer: DE455706595-00001
E-Mail: geocanvas@kaju.it
Verantwortlich für den Inhalt nach § 18 Abs. 2 MStV:
Kai Raschke, Adresse wie oben
Kontaktstelle nach Art. 11 und 12 DSA / Point of contact under Art. 11 and 12 DSA
Diese Stelle steht Behörden der Mitgliedstaaten, der Europäischen Kommission, dem Gremium für digitale Dienste und den Nutzern zur Verfügung.
This is the point of contact for the authorities of the Member States, the European Commission, the European Board for Digital Services and users.
E-Mail: geocanvas@kaju.it
Telefon / Phone: +49 176 72239837
Sprachen: Deutsch, Englisch / Languages: German, English
Rechtswidrige Inhalte melden / Report illegal content
Regeln zur Moderation / Moderation rules
Built With
This application was built using the following open-source libraries and frameworks:
Next.js & React
- next-intl - MIT
- next-seo - MIT
- next - MIT
- @socialgouv/matomo-next - Apache-2.0
- react-dom - MIT
- react-dropzone - MIT
- react - MIT
- zustand-persist - MIT
- zustand - MIT
Styling
- tailwindcss - MIT
- @mui/icons-material - MIT
- Material Icons (Google) - Apache-2.0
- @mui/material - MIT
- @mui/x-tree-view - MIT
- @emotion/react - MIT
- @emotion/styled - MIT
- @uiw/react-color - MIT
- chroma-js - BSD-3-Clause AND Apache-2.0
Geo Data Visualization
- d3 - ISC
- d3-geo - ISC
- d3-geo-polygon - ISC
- d3-geo-projection - ISC
- d3-geo-scale-bar - BSD-3-Clause
- geotiff - MIT
- @turf/turf - MIT
- shpjs - MIT
- topojson-client - ISC
UI & Interactions
- @dnd-kit/core - MIT
- @dnd-kit/sortable - MIT
- marked - MIT
- rbush - MIT
- driver.js - MIT
- @tanstack/react-ranger - MIT
- @fseehawer/react-circular-slider - MIT
- @tanstack/react-virtual - MIT
- lodash.isequal - MIT
Rendering (WebGL / WebGPU)
- @deck.gl/core - MIT
- @deck.gl/layers - MIT
- @deck.gl/geo-layers - MIT
- @deck.gl/react - MIT
- @luma.gl/core - MIT
- @luma.gl/engine - MIT
- @luma.gl/shadertools - MIT
- @luma.gl/webgl - MIT
- @luma.gl/webgpu - MIT
- mjolnir.js - MIT
Geometry & Math
- @math.gl/core - MIT
- @math.gl/polygon - MIT
- @math.gl/sun - MIT
- @math.gl/web-mercator - MIT
- gl-matrix - MIT
- earcut - ISC
- polylabel - ISC
- astronomy-engine - MIT
- proj4 - MIT
Data Formats & Services
- @loaders.gl/core - MIT
- @loaders.gl/images - MIT
- @loaders.gl/schema - MIT
- @mapbox/vector-tile - BSD-3-Clause
- @mapbox/togeojson - BSD-2-Clause
- @mapbox/tiny-sdf - BSD-2-Clause
- pbf - BSD-3-Clause
- @maplibre/maplibre-gl-style-spec - ISC
- d3-tile - BSD-3-Clause
- jszip - MIT OR GPL-3.0-or-later
- @camptocamp/ogc-client - BSD-3-Clause
- ol - BSD-2-Clause
Content & Citations
- @citation-js/core - MIT
- @citation-js/plugin-bibtex - MIT
- @citation-js/plugin-csl - MIT
- @citation-js/plugin-ris - MIT
- react-markdown - MIT
- remark-gfm - MIT
Map Material
This application uses the following sources for map material:
Privacy Notice
This is an English translation of ourGerman privacy notice (Datenschutzerklärung). If the two versions differ, the German version prevails.
1. Privacy at a glance
General information
The following gives a simple overview of what happens to your personal data when you visit this website or use the GeoCanvas apps. Personal data is any data by which you can be personally identified. Detailed information follows below.
Data collection on this website
Who is responsible for data collection on this website?
Data processing on this website is carried out by the website operator. You will find their contact details in the section “Controller” in this privacy notice.
How do we collect your data?
Some data is collected because you give it to us, for example data you enter into a form.
Other data is collected automatically, or after your consent, by our IT systems when you visit the website. This is mainly technical data (e.g. browser, operating system or time of the page view). It is collected automatically as soon as you enter the website.
What do we use your data for?
Part of the data is collected to provide the website without errors. Other data may be used to analyse how the website is used. Where contracts can be concluded or initiated through the website, the data transmitted is also processed for contract offers, orders or other requests.
What rights do you have regarding your data?
You have the right at any time to receive information free of charge about the origin, recipients and purpose of your stored personal data. You also have the right to request that this data be corrected or deleted. If you have given consent to data processing, you can withdraw it at any time with effect for the future. You also have the right, under certain circumstances, to request the restriction of the processing of your personal data, and the right to lodge a complaint with the competent supervisory authority.
You can contact us at any time about this and any other questions about data protection.
Analysis tools and third-party tools
When you visit this website, your browsing behaviour may be evaluated statistically, mainly with so-called analysis programs. Detailed information follows below.
2. Hosting
External hosting
This website is hosted externally. Personal data collected on this website is stored on the host’s servers. This may include IP addresses, contact requests, meta and communication data, contract data, contact details, names, website access and other data generated through a website.
External hosting serves the performance of contracts with our potential and existing customers (Art. 6(1)(b) GDPR) and our interest in a secure, fast and efficient provision of our online service by a professional provider (Art. 6(1)(f) GDPR). Where consent has been requested, processing is based solely on Art. 6(1)(a) GDPR and § 25(1) TDDDG, insofar as the consent covers storing cookies or accessing information on the user’s device (e.g. device fingerprinting) within the meaning of the TDDDG. Consent can be withdrawn at any time.
Our host processes your data only to the extent necessary to fulfil its service obligations and follows our instructions regarding this data. We use:
netcup GmbH
Emmy-Noether-Straße 10
76131 Karlsruhe, Germany
All GeoCanvas servers, including the backups, are hosted by netcup; the data processing agreement below covers all of them.
Data processing agreement
We have concluded a data processing agreement (DPA) for the use of this service. It is a contract required by data protection law that ensures the host processes our visitors’ personal data only on our instructions and in compliance with the GDPR.
3. General information and mandatory information
Data protection
We take the protection of your personal data very seriously. We treat your personal data confidentially and in accordance with the statutory data protection regulations and this privacy notice.
Please note that data transmission over the Internet (e.g. when communicating by e-mail) can have security gaps. Complete protection of data against access by third parties is not possible.
Controller
The controller responsible for data processing on this website and in the GeoCanvas apps is:
Kai Raschke
Leipziger Straße 31
06108 Halle, Germany
Phone: +49 176 72239837
E-mail: geocanvas@kaju.it
The controller is the natural or legal person who alone or jointly with others decides on the purposes and means of processing personal data (e.g. names, e-mail addresses).
Storage period
Unless a more specific storage period is stated in this privacy notice, your personal data remains with us until the purpose of processing no longer applies. If you make a justified request for deletion or withdraw your consent, your data will be deleted unless we have other legally permissible reasons for storing it (e.g. retention periods under tax or commercial law); in that case it is deleted once those reasons no longer apply.
Legal bases of processing
If you have consented to data processing, we process your personal data on the basis of Art. 6(1)(a) GDPR, or Art. 9(2)(a) GDPR where special categories of data are processed. In the case of express consent to the transfer of personal data to third countries, processing is also based on Art. 49(1)(a) GDPR. If you have consented to the storage of cookies or to access to information on your device (e.g. via device fingerprinting), processing is additionally based on § 25(1) TDDDG. Consent can be withdrawn at any time. If your data is required to perform a contract or to take steps prior to entering into a contract, we process it on the basis of Art. 6(1)(b) GDPR. We also process data where required to comply with a legal obligation (Art. 6(1)(c) GDPR), and on the basis of our legitimate interest (Art. 6(1)(f) GDPR). The relevant legal basis in each case is stated in the following sections.
Recipients of personal data
We work with various external bodies. We pass personal data to them only where this is necessary to perform a contract, where we are legally obliged to (e.g. disclosure to tax authorities), where we have a legitimate interest under Art. 6(1)(f) GDPR, or where another legal basis permits it. When we use processors, we pass on personal data only on the basis of a valid data processing agreement. In the case of joint processing, a joint controller agreement is concluded.
Withdrawal of your consent
Many processing operations are only possible with your express consent. You can withdraw consent you have given at any time. The lawfulness of processing carried out until the withdrawal remains unaffected.
Right to object to data collection in special cases and to direct marketing (Art. 21 GDPR)
WHERE PROCESSING IS BASED ON ART. 6(1)(E) OR (F) GDPR, YOU HAVE THE RIGHT TO OBJECT AT ANY TIME, ON GROUNDS RELATING TO YOUR PARTICULAR SITUATION, TO THE PROCESSING OF YOUR PERSONAL DATA; THIS ALSO APPLIES TO PROFILING BASED ON THESE PROVISIONS. THE LEGAL BASIS FOR EACH PROCESSING IS STATED IN THIS PRIVACY NOTICE. IF YOU OBJECT, WE WILL NO LONGER PROCESS THE PERSONAL DATA CONCERNED UNLESS WE CAN DEMONSTRATE COMPELLING LEGITIMATE GROUNDS FOR THE PROCESSING THAT OVERRIDE YOUR INTERESTS, RIGHTS AND FREEDOMS, OR THE PROCESSING SERVES THE ESTABLISHMENT, EXERCISE OR DEFENCE OF LEGAL CLAIMS (OBJECTION UNDER ART. 21(1) GDPR).
IF YOUR PERSONAL DATA IS PROCESSED FOR DIRECT MARKETING, YOU HAVE THE RIGHT TO OBJECT AT ANY TIME TO SUCH PROCESSING, INCLUDING PROFILING RELATED TO SUCH MARKETING. IF YOU OBJECT, YOUR PERSONAL DATA WILL NO LONGER BE USED FOR DIRECT MARKETING (OBJECTION UNDER ART. 21(2) GDPR). WE DO NOT CARRY OUT DIRECT MARKETING.
Right to lodge a complaint with a supervisory authority
In the event of breaches of the GDPR, you have the right to lodge a complaint with a supervisory authority, in particular in the Member State of your habitual residence, your place of work or the place of the alleged infringement. This right exists without prejudice to any other administrative or judicial remedies.
Right to data portability
You have the right to receive data that we process automatically on the basis of your consent or to perform a contract, in a common, machine-readable format, for yourself or a third party. If you request direct transfer to another controller, this is done only where technically feasible.
Access, rectification and erasure
Within the applicable legal provisions, you have the right at any time to free information about your stored personal data, its origin, its recipients and the purpose of processing, and, where applicable, a right to rectification or erasure of this data. You can contact us at any time about this.
Right to restriction of processing
You have the right to request the restriction of the processing of your personal data in the following cases:
- if you dispute the accuracy of your personal data stored with us, for the time we need to verify it;
- if the processing was or is unlawful, and you request restriction instead of erasure;
- if we no longer need your personal data but you need it to establish, exercise or defend legal claims;
- if you have objected under Art. 21(1) GDPR, while it has not yet been determined whose interests prevail.
If processing has been restricted, this data may – apart from its storage – only be processed with your consent, for the establishment, exercise or defence of legal claims, for the protection of the rights of another natural or legal person, or for reasons of important public interest of the European Union or a Member State.
SSL/TLS encryption
For security reasons and to protect the transmission of confidential content, this site uses SSL/TLS encryption. You can recognise an encrypted connection by the “https://” in the address bar and the lock symbol. When encryption is active, the data you transmit to us cannot be read by third parties.
4. Data collection on this website
Server log files
The hosting provider automatically collects and stores information in server log files that your browser transmits automatically:
- browser type and version
- operating system
- referrer URL
- host name of the accessing computer
- time of the server request
- IP address
This data is not combined with other data sources. The server log files are deleted after 14 days.
To limit requests, we also form a pseudonymous identifier from the IP address with a secret key. It stays on our own servers; our own map and data services also receive it, to limit requests, and hold it for this in memory only. Some forms and endpoints, such as the report form, the form for enquiries about commissioned work and checkout, count requests per IP address. The website itself holds the identifier and IP addresses for this in memory only, at most 48 hours after the last request.
This data is collected on the basis of Art. 6(1)(f) GDPR: we have a legitimate interest in the technically error-free presentation and optimisation of the website, for which server log files are needed, and in protecting it from abuse.
Basemap (OpenFreeMap)
The map can show an optional basemap with roads, land cover and place names. It is loaded only if you add the “OpenFreeMap” layer to the map yourself, or if you turn on 3D buildings from OpenStreetMap, which are read from the same OpenFreeMap tiles. Your browser then fetches the map tiles and the map style directly from the servers of OpenFreeMap (tiles.openfreemap.org), operated by Hyperknot Software Kft., Petőfi Sándor utca 48., 2724 Újlengyel, Hungary. The requests do not pass through our server.
As with any request to a web server, your IP address, the address of each requested map tile (from which the area of the map you are viewing can be derived), the time of the request, your browser type and operating system, and the referrer are transmitted. We do not send OpenFreeMap any account data, and no cookies are set.
According to its own privacy policy, OpenFreeMap keeps access logs without IP addresses; error logs may contain the IP address and the requested address. Server logs are deleted after 7 days. To investigate incidents, IP logging may be switched on temporarily for at most 30 days. OpenFreeMap states that it may use the content delivery network of Cloudflare, Inc. (USA) to deliver the tiles, so processing outside the EU cannot be ruled out. Details: openfreemap.org/privacy.
The legal basis is Art. 6(1)(f) GDPR: we have a legitimate interest in offering a detailed basemap without operating a worldwide tile infrastructure ourselves. You can prevent the transfer by not adding the basemap, and end it at any time by removing the layer from the map. The map data comes from OpenStreetMap contributors.
5. Analysis tools
Matomo
We use the open-source program Matomo to see which pages and features of this website are used and whether they work without errors. It records the page visited, the time, the referring page, browser type, operating system and screen resolution, whether the website was opened in a browser or in our Android or iOS app, and individual named actions in the application (e.g. adding a layer, exporting, saving a project).
The legal basis is Art. 6(1)(f) GDPR. Our legitimate interest is operating the website reliably and improving it.
IP anonymisation
Your IP address is shortened before it is stored, so that it can no longer be attributed to you.
No cookies, no user identifier
Matomo is configured not to store any cookies in your browser. We assign no user ID and do not combine the data with your account or any other data source.
Automated access
Besides visits by people, we also record access by automated programs such as AI assistants or search-engine crawlers. Matomo evaluates these separately from visits, in a statistic of its own. Only the identifier of the accessing program (user agent) and the page path without query parameters are transmitted; no visitor IP address is sent. Requests that Matomo does not classify as automated are discarded and not stored.
Hosting
Matomo runs exclusively on our own servers. The data stays with us and is not passed on to anyone.
Objecting to collection
Separately from Matomo, on one in ten page loads the website measures how quickly it loads and responds: when its largest element appears, how long it takes to react to taps and clicks, how much the layout shifts, and when the map is ready. These timings are sent to our own server together with the kind of page (e.g. map or collection), whether the screen is narrow or wide, the software version and a general category of the control that was used (e.g. “navigation”). No page address, no content and no identifier are sent, and nothing is stored in your browser. The figures are written only to our server's log. The legal basis is Art. 6(1)(f) GDPR. The objection to Matomo described below also stops this measurement.
You can object to collection by Matomo. Use the switch below to set an opt-out cookie that prevents future collection in this browser:
Note: if you delete this cookie, you need to set the opt-out again. It applies only to this browser and this website.
6. AI assistant (chatbot)
This section applies only if you actively switch on the AI assistant (“AI Chat”) in the map application. It is off by default; until you switch it on, none of the processing described here takes place. Before it starts, the chat window asks you to read this section and confirm that your input is sent to Mistral AI for processing.
Taking back the permission
The chat window remembers your confirmation for 30 days and does not ask again in that time (see the “gc_adult” cookie in section 7). You can take the permission back here at any time with effect for the future. The assistant then asks again before it next starts.
Description and scope of processing
The assistant lets you control the map and ask questions about our data. When you send a message, the text (prompt) is transmitted to our service provider’s servers so the AI can generate an answer. In addition to your input, the following is sent so that the assistant can operate the map:
- a short description of the current map state, e.g. projection, map extent, names of the loaded layers and the current selection,
- attribute values of these layers where the assistant looks them up to answer, e.g. feature or place names,
- descriptions of the functions the assistant may call, and the function calls and parameters it produces.
We do not permanently store your input or the answers on our systems. Our server only forwards the messages and returns the answer; no log of conversation content is kept. The only exception is a rating you choose to give; see “Voluntary rating of the assistant” below.
Please do not enter sensitive or personal data (such as names or contact details) in the chat window. Note that an assistant query can also reveal such data if the map data you loaded contains it.
Recipient
The recipient is Mistral AI SAS, 15 rue des Halles, 75001 Paris, France.
Legal basis
Processing is based on our legitimate interest in answering user requests efficiently and promptly and in optimising our online service (Art. 6(1)(f) GDPR). If you have a GeoCanvas Creator subscription (section 9), processing is necessary to perform that contract (Art. 6(1)(b) GDPR).
Usage measurement
We measure how much you use the assistant in tokens (units of text), to keep to the free allowance and the allowance of a subscription. No content is stored for this, only numbers. Details are in section 8.
Separate accounts with the provider
Mistral AI processes requests from subscribers through a separate account, kept apart from free requests. Recipient, retention and the exclusion of model training are the same.
No model training; retention
We have configured our account with the provider so that your input is not used to train AI models. The provider keeps the data after answering only for abuse detection; retention is set to 30 days in our settings with the provider. It is then deleted. This applies equally to free requests and requests under a subscription.
Transfers to third countries
Mistral AI is a European company and processes data within the European Union by default. Should sub-processors outside the EU/EEA be involved in exceptional cases, the level of protection is ensured by EU Standard Contractual Clauses.
Usage statistics for the assistant
To tell whether the assistant works reliably and usefully, we record a few anonymous figures through our self-hosted Matomo (see section 5). Only events with numeric values are recorded:
- opening the chat window and switching the assistant on,
- sending a message,
- per answer, the number of tokens processed and produced, the speed in tokens per second and the number of function calls (tool calls),
- which technical variant of the assistant you were assigned,
- a rating you give, as a number.
The content of your messages, the answer texts and layer, feature or place names are not transmitted. The legal basis is Art. 6(1)(f) GDPR. An objection to Matomo as described in section 5 also covers these events.
Voluntary rating of the assistant
As we neither store conversations nor can view them at the provider, we cannot tell whether an answer was useful without your feedback. After a few answers, the chat window therefore offers you to rate the conversation.
Only if you click one of the three ratings do you send us the conversation so far:
- your input, verbatim,
- the assistant’s answers, verbatim,
- the function calls it made, with their parameters,
- technical measurements for these answers, such as token counts, speed and number of processing steps,
- the technical variant assigned to you, the interface language and a random conversation identifier.
Your IP address, any user or device identifier, and the full results of data queries the assistant ran are not transmitted.
The legal basis is your consent under Art. 6(1)(a) GDPR. The rating is voluntary; the assistant works the same without it. You give consent by clicking a rating after the notice above the buttons has been shown.
The sole purpose is to improve and assure the quality of the assistant. Submitted conversations are stored on our own servers in the European Union, not passed on to third parties and not used to train AI models. We delete them no later than 6 months after submission.
After submitting, you are shown a reference number. You can withdraw your consent at any time with effect for the future (Art. 7(3) GDPR) and request deletion of the submitted conversation by sending the reference number to the e-mail address in the imprint. Without it we cannot identify your conversation, as we never store a user identifier.
Assignment of a technical variant
We are currently testing four technical variants of the assistant, which differ in the language model used and in how the available functions are offered to it. The variant is chosen at random when you switch the assistant on.
So that you get the same variant on a later visit, we store it in your browser’s local storage (localStorage), only once you switch the assistant on. It is a short technical label without personal reference; no cookie is set. You can view and delete the entry in the section on data stored on your device above.
7. Customer account (optional)
You can use GeoCanvas fully without an account. You only need one to take out GeoCanvas Creator on the web, to link a purchase from the app (for example a Creator subscription from the App Store or Google Play, for use on the website), or to have your usage counted on your account rather than your internet connection.
What data and why
We use the Auth0 service for sign-in. We process your e-mail address, when signing in with Google or Apple the identifier provided by that provider and possibly your name, and the time and technical details of sign-in. When you register with an e-mail address and password, Auth0 also stores the language you registered in, so that e-mails about your account arrive in that language. We keep your account under a random internal identifier; only this identifier is passed to payment and subscription providers, not your Auth0 identifier.
The legal basis is the performance of the user agreement for the account (Art. 6(1)(b) GDPR). The sign-in cookie is strictly necessary for the service you request (§ 25(2) no. 2 TDDDG); it is valid for at most 24 hours.
Linking purchases from the app
The apps work without an account. A GeoCanvas Creator subscription bought in the App Store or on Google Play is linked automatically to the account you are signed in with in the app, when you use it there, if it is not linked yet. We then store the link between your internal account identifier and the subscription; the first account it is linked to keeps it. You can also link a purchase yourself, or move the link to another account: if you choose “Use with an account” in the app, we create a one-time code from the purchase proofs of that device (section 8). We store only a hash of the code, which is valid once for 15 minutes. When you enter the code on the /account page while signed in, we store the link between your internal account identifier and the subscription or app purchase (the paid iOS app or the Android unlock). A linked Creator subscription then also grants Creator on the website, with the same allowance. A linked app purchase gives you its map exports without the GeoCanvas wordmark on the website as well, in a desktop browser; required source credits remain. A purchase is linked to one account at a time: a newer code redeemed by another account moves the link there. The link ends when you remove it on /account or delete your account; the store purchase itself is unaffected.
To make this possible, we record for each verified app purchase an internal identifier and the store’s identifier of the purchase (for Apple the app transaction identifier, for Google the order identifier), without any other data about you. The app confirms the purchase again at every start. We delete a record that is not linked to an account once the purchase has not been confirmed for 13 months, and codes one day after they expire. The legal basis for the automatic link is the performance of the contract (Art. 6(1)(b) GDPR): under the service terms, a Creator subscription from a store also grants Creator on the website once it is linked to your account. Linking or moving a purchase with a code is the performance of the user agreement at your request (Art. 6(1)(b) GDPR). For recording the purchase identifier, the legal basis is our legitimate interest in offering linking (Art. 6(1)(f) GDPR).
Recipient and transfer to third countries
Auth0 is a service of Okta, Inc., 100 First Street, San Francisco, CA 94105, USA. We use a tenant in the EU region. Where data nevertheless reaches the USA, the transfer is based on the adequacy decision for the EU-US Data Privacy Framework, alternatively on EU Standard Contractual Clauses. A data processing agreement with Okta is in place.
Deleting your account
You can delete your account yourself at any time: sign in and choose “Delete account” on the /account page, in the browser or in the app. We revoke local account access immediately and retry cleanup if a provider is unavailable. We delete your account at Auth0 and with us, your account-related usage periods and the links to subscriptions and app purchases; usage events lose any reference to you. A Creator subscription on the web ends at the end of the paid period. Creator subscriptions from the App Store or Google Play are billed by the store; cancel them in your store settings. A confirmation is queued for e-mail delivery after cleanup succeeds. A revocation record is retained for 30 days after completion to prevent old sessions from recreating the account.
We record your 18+ declaration with its exact wording, version, language, time and the account/chat/purchase screen used. A new account makes this declaration in a step of the sign-in at Auth0, which keeps its version, language and time with your account there. We do not collect your birth date or identity document for this declaration. Your browser receives the necessary “gc_adult” cookie for this. We sign it, and it holds only the versions of the texts you confirmed (the age declaration and, in the AI assistant, the permission to share with Mistral AI) and a random identifier that refers to the stored record; it is valid for 30 days. When you take back the permission for the AI assistant (section 6), we replace it with one without the AI permission. The stored record is also deleted after 30 days. The cookie is strictly necessary for the service you request (§ 25(2) no. 2 TDDDG). This supports our adult-only service policy (Art. 6(1)(f) GDPR); it is not consent to all data processing or verified proof of age.
Newsletter
You receive the newsletter only if you expressly subscribe to it on the page /account; the box is not pre-ticked and requires a confirmed e-mail address. For this we store your choice, the wording, version and language of the text you agreed to, and the time, and we confirm the subscription by e-mail. The legal basis is your consent (Art. 6(1)(a) GDPR, Section 7(2) No. 2 UWG). You can withdraw it at any time with effect for the future: on the page /account or with the unsubscribe link in every e-mail, without signing in. We keep the record of your consent and of its withdrawal for up to three years; the choice itself is deleted with your account.
Private datasets and saved maps
If you use the private workspace, we store your uploaded datasets, map documents, names, view and style settings, sizes and modification times under your internal account identifier. This lets you reopen, edit, view and download your own maps in the browser or app. Maps created or imported through MCP use the same private account storage. They are not published in a public catalogue. A map becomes public only when you publish it (section 11); there are no other public links to your maps. You can share a saved map with other GeoCanvas accounts by entering their e-mail address. We then store that address, in lower case, with the map, until you stop sharing, the map or your account is deleted, the recipient removes the map from their list, or the recipient deletes their account. Whoever signs in with that confirmed address can read the map and the datasets it uses. If a confirmed account uses the address, we send it one e-mail saying that the map was shared, which names your e-mail address; we do not write to addresses without an account and do not tell you whether an address has one. The legal basis is the performance of the contract with you (Art. 6(1)(b) GDPR) and, for the recipient’s address, our legitimate interest in providing the sharing you asked for (Art. 6(1)(f) GDPR). Using your data through an AI client you connect to MCP can disclose data to that client and its provider; their processing is separate from our storage.
Your datasets and maps remain stored until you delete them or delete your account. Ending a GeoCanvas Creator subscription stops new uploads and cloud saves but does not automatically delete existing content, except the public copies of published maps (section 11): viewing, download and deletion remain available. You can delete a published map, and a dataset that a published map uses, only after the publication ends. A map can reference a dataset rather than contain another copy; deleting that dataset leaves its layer unavailable in maps that use it. If you delete your account, we delete all your content: your datasets, saved maps, published maps (including blocked ones) and registered websites. Unavailable provider or storage cleanup is retried.
8. Usage allowance of the AI assistant
Use of the AI assistant is limited: free use to an allowance per 30 days, twice that with a purchase of the app, and with a GeoCanvas Creator subscription to an allowance per billing period. To enforce this, we process:
- when used without an account, an identifier we compute from your IP address with a secret key that is changed regularly (HMAC). We do not store the IP address itself for this, and treat the identifier as pseudonymous personal data, not anonymous data. Everyone behind the same IP address shares one allowance;
- when used with an account, your internal account identifier; with a GeoCanvas Creator subscription (web, App Store or Google Play), an internal subscription identifier;
- per request: time, model used, platform (web, iOS, Android), number of processed and generated tokens, and the resulting cost. We do not store the content of your messages for this.
In the app, a purchase proof signed by Apple or Google confirms that you bought the app or took out a subscription. We verify the signature and remember the result in a signed cookie (“gc_buyer” for the app purchase, with our internal identifier of that purchase where the store provides one, at most 30 days; “gc_sub” for the subscription, at most until the end of the billing period and no longer than 7 days). Both cookies are strictly necessary for the service you request (§ 25(2) no. 2 TDDDG); the app renews them at every start.
The legal basis for free use is our legitimate interest in protecting a free service against abuse and unlimited costs (Art. 6(1)(f) GDPR); for a subscription, the performance of the contract (Art. 6(1)(b) GDPR). The data is processed on our own servers in the EU.
Retention: allowance periods without an account are deleted 30 days after they end, usage events after 13 months. Account-related periods are deleted with the account.
9. Purchases and subscriptions
Our subscription for the website and the apps is GeoCanvas Creator. It is billed monthly and sold on the website, in the App Store and on Google Play; which provider processes your data depends on where you buy it (see below). A Creator subscription bought on the website grants nothing inside the iOS or Android app. The paid iOS app and the Android unlock are one-off purchases in the store.
App Store (iOS)
Purchases in the iOS app are made with Apple (Apple Distribution International Ltd., Hollyhill Industrial Estate, Hollyhill, Cork, Ireland). Apple processes your payment data under its own responsibility; we receive no payment data, no name and no e-mail address, only the transaction details signed by Apple (product, period, transaction identifier, status such as renewal, cancellation or refund).
Google Play (Android)
Purchases in the Android app are made with Google (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland). Here too we receive only purchase proofs (purchase identifier, product, status), no payment data.
RevenueCat
To handle store purchases in the app we use RevenueCat (RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA). The app transmits a random user identifier and the store’s purchase details; no account is needed and none is transmitted. RevenueCat informs us of events such as renewal, cancellation or refund. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). The transfer to the USA is based on EU Standard Contractual Clauses or the EU-US Data Privacy Framework, where RevenueCat is certified; a data processing agreement with RevenueCat is in place.
GeoCanvas Creator on the web (Stripe)
GeoCanvas Creator on geocanvas.app is paid through Stripe (Stripe Payments Europe, Ltd., 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, Ireland). Stripe processes your payment data, name, e-mail address and billing address. The merchant of record is Sold through Link, LLC (Stripe Managed Payments), which charges the price and processes your order and payment data as a controller in its own right under its own privacy notice. Kai Raschke is the seller and provides the service. We receive the subscription details (identifier, period, status) and the customer identifier, but not the full payment data. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR); retention obligations under tax and commercial law (Art. 6(1)(c) GDPR) remain unaffected. If you send Link a request for deletion of your data, Link ends your Creator subscription on the web.
Web subscriptions are sold only in countries where the merchant of record handles the customer’s taxes. Before checkout we therefore ask for your country of residence, pass it to Stripe with the order, and compare it with the billing country Stripe reports to us. If you end or continue a subscription on the page /account, we pass that instruction to Stripe. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR) and our legitimate interest in selling only where the tax is handled (Art. 6(1)(f) GDPR).
Cancellation and withdrawal
If you submit a declaration through “Cancel contracts here” or “Withdraw from contract”, we store your name, e-mail address, the contract reference if given, the type and time of the declaration and the outcome, and send you an acknowledgement of receipt. The legal basis is compliance with our legal obligations (§§ 312k, 356a BGB; Art. 6(1)(c) GDPR) and our legitimate interest in proof (Art. 6(1)(f) GDPR).
Retention
We keep subscription records and cancellation or withdrawal declarations until the end of the third calendar year following the subscription end or receipt of the declaration; unresolved requests and records subject to a specific legal hold are retained until their purpose ends. Identifiers of provider notifications are deleted after 90 days.
10. Embedded maps on other websites
With an account, you can register a website on which you embed a GeoCanvas map (service terms, “Schedule: embeds on your website”). Readers of that website then load the map through our viewer at embed.geocanvas.app.
Your registered website
For your account we store the website address, the address of your data server if you give one, the website key, the chosen projection, whether zoom buttons are shown, the colour theme, the status (active, revoked or blocked) and when the entry was created and last changed. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR). We keep this data until you delete your account. A revoked website stays recorded so that its key is never issued again. If we block a key, the measure and its statement of reasons are handled as described under “Moderation records” (section 12).
When the map loads
When a browser loads an embedded map, our server at embed.geocanvas.app records in server log files: the IP address, the time, the requested address including the site key, the status of the response, the amount of data sent, the embedding page (referrer) and the browser identification. For some refused requests, the viewer application writes the same data to its own log. We delete both logs at most 15 days after the day of the request. We also count loads per website and day, to apply the daily load limit, to show the account that registered the website how often its map is loaded, and to determine our average number of recipients under the Digital Services Act. The count is a single number per website and day; it holds no IP address and no other data about readers. To recognise repeated loads from the same network, the viewer keeps a keyed hash of the reader’s network address (the IPv4 address, or the first half of an IPv6 address) in memory for 30 minutes; it is never written to disk and cannot be turned back into the address once the viewer restarts. We store only the daily count in our database and delete it 13 months after the day it counts. The legal basis is our legitimate interest in delivering the map, applying the limits and preventing abuse (Art. 6(1)(f) GDPR).
The viewer sets no cookies, uses no browser storage (neither local nor session storage) and includes neither Matomo nor any other analytics tool. It therefore stores nothing on the reader’s device and reads nothing from it; § 25 TDDDG is not engaged. Our own simple basemap (land and borders) comes from our data server data.geocanvas.app. That server also records the reader’s IP address, the time, the requested address, the referring page and the browser identification in its access log, which is deleted at most 15 days after the day of the request. These requests are not passed to Matomo. A basemap or other service that the website’s map file names, such as OpenFreeMap (see “Basemap (OpenFreeMap)” in section 4), is loaded by the browser directly from that provider.
The embedding website
Whether a map appears on a website is decided by its operator. For embedding the map, and the transmission to us that comes with it, the operator may be a joint controller with us (CJEU, judgment of 29 July 2019, C-40/17, Fashion ID). The browser loads the map file from the embedding website’s server, and its data from the servers and services the file names; we do not receive that data. The website alone is responsible for that processing; its own privacy notice explains it.
11. Published maps on maps.geocanvas.app
With a GeoCanvas Creator subscription you can publish a saved map (service terms, “Schedule: published maps”). Readers then open it at maps.geocanvas.app, without signing in, or on a website where it is embedded.
Your published maps
For your account we store, for each published map, a reference to the datasets it shows (the datasets are not copied for this), its title, description, alt text, the credit line you chose, the reader options, whether readers may open it in GeoCanvas and whether search engines may index it, two preview images, the times it was published and changed, its status (published, blocked, taken offline or unpublished), the evidence of your rights declaration (its version and time, and each layer’s licence and source) and the version of the service terms. At your first “Publish” we also store that you accepted the schedule, with its version and wording and your account reference, until you delete your account, and at the latest for four years. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR) and, for the record of acceptance, our legitimate interest in proof (Art. 6(1)(f) GDPR). A published map is public, with everything in it. If it shows personal data, for example in its title, its description, the credit line or its data, that data becomes public too; you are responsible for having a legal basis for that (service terms, “Schedule: published maps”). If we block a map, the measure and its statement of reasons are handled as described under “Moderation records” (section 12).
Retention
When your GeoCanvas Creator access ends, a published map stays online for 14 more days and then goes offline. For 90 days you can restore it by subscribing again; after that we delete the public copy for good. Your private map is kept. A blocked map stays blocked until we lift the block (for example after a successful review); while it is blocked, you cannot unpublish it yourself. We delete the public copy of a blocked map 6 months after our last decision on it, unless a procedure about it is still pending (a complaint or a request for review not yet decided); your private map is kept. If you unpublish a map, or we delete a public copy after the 90 days or that of a blocked map after 6 months, a record without the map itself stays stored until you delete your account: identifier, times, the evidence of the rights declaration with each layer’s name, licence and source, the terms version, and the chosen reader and display options; the views per day stay stored for 13 months, as described below. If you delete your account, we unpublish your maps and delete their public copies, including blocked ones, with the records of their publication. We keep moderation records as described under “Moderation records” (section 12).
When a map is viewed
When a browser loads a published map, our server at maps.geocanvas.app records in server log files: the IP address, the time, the requested address including the map's public identifier, the status of the response, the amount of data sent, the referring page (referrer) and the browser identification. For some refused requests, the viewer application writes the same data to its own log. We delete these logs at most 15 days after the day of the request. The legal basis is our legitimate interest in delivering the map, applying the limits and preventing abuse (Art. 6(1)(f) GDPR).
We also count views of each published map per day, to apply the daily view limit, to show the account that published the map how often it is viewed, and to determine our average number of recipients under the Digital Services Act. To recognise repeated views from the same network, the viewer keeps a keyed hash of the reader's network address (the IPv4 address, or the first half of an IPv6 address) in memory for 30 minutes; it is never written to disk and cannot be turned back into the address once the viewer restarts. To count how many different readers a map has per day, the viewer also forms a hash of that network address with a salt that changes every day and with every restart of the viewer. The salt is never stored. The viewer holds the hashes and the salt in memory until the end of the day (UTC) and then discards them; they are never written to disk. Only the number of different hashes, a single number per map and day, is stored, for 13 months; it holds no IP address and no other data about readers. That account sees the views per day and that number, as an estimate of the readers: the same person counts again on another network, on another day or after a restart of the viewer. The legal basis is our legitimate interest in applying the limits and preventing abuse (Art. 6(1)(f) GDPR).
The viewer sets no cookies, uses no browser storage (neither local nor session storage) and includes neither Matomo nor any other analytics tool. It therefore stores nothing on the reader's device and reads nothing from it; § 25 TDDDG is not engaged. Map files, data, images and the basemap that a published map shows from our own catalogue are loaded from GeoCanvas servers, which also keep an access log of at most 15 days, as described above.
Sources from other servers
The account that publishes a map can add layers from other services or from its own server outside GeoCanvas. The reader's browser then loads them directly from those servers, for example a WMS, WMTS or XYZ service or the vector basemap of OpenFreeMap (see “Basemap (OpenFreeMap)” in section 4). These providers receive the reader's IP address and the other data a browser sends with every request. We do not host, relay or control these requests. That account is responsible for them and has to name these servers in its own privacy notice; the publish dialog and the service terms tell them so. Datasets that account uploaded to GeoCanvas are served by us through maps.geocanvas.app.
The browser always receives a copy of the map and of the data it shows, whether or not the Creator allows readers to open the map in GeoCanvas. If a website embeds the map, its operator decides that, and its own privacy notice has to explain it; the operator may be a joint controller with us for the embedding (CJEU, judgment of 29 July 2019, C-40/17, Fashion ID).
12. Reports of illegal content
If you report content through the form at /melden or by e-mail, we process the category you choose, where the content is (for example its link), your explanation, your confirmation that you report in good faith, the language of the form and the time of receipt, and, if you give them, your name and e-mail address. Name and e-mail address are optional; if you give an e-mail address, we confirm receipt and tell you our decision by e-mail. We use the data to examine and decide your notice. We do not pass your name or e-mail address on to the person whose content you reported.
The legal basis is compliance with our legal obligation to receive and process notices (Art. 6(1)(c) GDPR in conjunction with Art. 16 of the Digital Services Act, Regulation (EU) 2022/2065). Apart from the mail servers of our host netcup (section 2), through which the e-mails are sent, we pass the data to no one, unless the law obliges us to, for example towards a court or an authority.
Moderation records
If we restrict content or an account, we record the account concerned, the measure, its scope and duration, the facts and the law or terms clause we rely on, whether a notice led to it, the statement of reasons we send and, if one is requested, the voluntary review and its outcome. We send the statement to the confirmed e-mail address of the account, which we look up at Auth0 for this purpose (section 7). The legal basis is Art. 6(1)(c) GDPR in conjunction with Art. 17 of the Digital Services Act; for the voluntary review, our legitimate interest in correcting wrong decisions (Art. 6(1)(f) GDPR). The recipients are the same as for notices.
Retention
We keep notices and moderation records until the end of the second calendar year after the year in which we received the notice or recorded the measure; a notice received in 2026, for example, is kept until the end of 2028. A notice not yet decided, or a review not yet closed, is kept until it is.
13. Enquiries about commissioned work
If you send us an enquiry through the “Commissioned work” form at /products, we process your name, your e-mail address, the kind of project, your message, the language of the page and the time of receipt. We send the enquiry by e-mail to our business address and confirm receipt to the e-mail address you give. We use the data to answer your enquiry and, if you wish, to prepare an offer. The legal basis is taking steps at your request before entering into a contract (Art. 6(1)(b) GDPR).
To protect the form against automated mass submissions, we count enquiries per IP address in the server’s memory, as described in section 4. The form also contains a field that people do not see, and your browser sends how long the form was open before sending; an enquiry in which the field is filled in, or which was sent after less than three seconds, is discarded. The legal basis is our legitimate interest in a working form that cannot be misused to send e-mails (Art. 6(1)(f) GDPR). Apart from the mail servers of our host netcup (section 2), we pass the data to no one.
Retention
The copies in our mail queue are deleted 30 days after sending. We delete the enquiry in our mailbox six months after the last message about it if no contract follows. If a contract follows, we keep the correspondence for as long as commercial and tax law require (up to six years for business letters, § 257 HGB, § 147 AO).
14. E-mail notifications
We send e-mails only when a process requires it: confirming a subscription contract, confirming a cancellation or withdrawal, notices of changes to the service or these terms, confirming the deletion of an account, confirming receipt of a notice and telling the person who sent it our decision, statements of reasons for a moderation measure and the outcome of a review (section 12), and confirming receipt of an enquiry about commissioned work (section 13). We do not send advertising; the only exception is the one e-mail about the shop waitlist that you ask for (section 16). E-mails are sent through the mail servers of our host netcup (section 2). The legal basis is Art. 6(1)(b) or (c) GDPR.
15. Information for users outside the EU
GeoCanvas is operated from Germany; all processing follows the GDPR, even if you use the website or the app from another country. We grant the rights described in this notice to all users, regardless of where they live. Contact us at the address in section 3; we reply within one month.
- United Kingdom and Switzerland: the UK GDPR and the Swiss FADP apply accordingly. Transfers from these countries to the EU are covered by adequacy decisions.
- USA, including California: we do not sell personal data and do not share it for cross-context behavioural advertising (“no sale or sharing” within the meaning of the CCPA/CPRA). You can request access, correction and deletion; we will not discriminate against you for doing so.
- Republic of Korea (PIPA): we collect and use the items named in sections 4 to 14 for the purposes and periods stated there, and destroy them when the period ends: records in our databases are deleted, and backups expire after 14 days. Your personal information is stored and processed outside Korea. It is transmitted over the encrypted connection at the moment you use the feature concerned, to: netcup GmbH, Germany (hosting of the website, the account and all stored content, for as long as described in this notice); Okta, Inc. (Auth0), EU region with possible access from the USA (e-mail address and sign-in data, for the account, until the account is deleted); Stripe Payments Europe, Ltd., Ireland, and Sold through Link, LLC, USA (name, e-mail address, billing address, payment data and country of residence, for a web subscription, for the periods the law requires of them); Mistral AI SAS, France (the text you send to the AI assistant and the map context, to produce the answer, 30 days); and RevenueCat, Inc., USA (a random identifier and store purchase details, for purchases in the apps). You can refuse these transfers by not using the account, the subscription or the AI assistant; the map works without them. You may ask to see, correct, delete or suspend the processing of your personal information, yourself or through a representative, at the address in section 3, which is also the contact of the person responsible for privacy. We do not knowingly process data of children under 14; accounts are for adults.
- Japan (APPI): we use personal information only for the purposes stated in this notice. It is provided to the recipients named above, which are in Germany, Ireland, France and the United States. Germany, Ireland and France are in the European Economic Area, which Japan recognises as providing equivalent protection; for recipients in the United States we rely on contractual safeguards, and their legal system does not provide all the protections of the APPI. You may request disclosure, correction, suspension of use, deletion and the records of provision to third parties at the address in section 3.
- Brazil (LGPD): the web subscription is not sold in Brazil at present; the free website and the apps can be used. The legal bases in this notice correspond to Art. 7 LGPD (performance of a contract, legitimate interest, consent, legal obligation). You have the rights of Art. 18 LGPD: confirmation that processing exists, access, correction, anonymisation, blocking or deletion, portability, information about who data is shared with, and withdrawal of consent. International transfers follow Art. 33 LGPD on the basis of contractual safeguards. The address in section 3 is also the contact of the person in charge of data protection (encarregado); you can also complain to the ANPD.
- India (DPDP Act), Canada (PIPEDA), Australia (Privacy Act) and other countries: our application server is located in Germany. The providers named in this notice may also process data outside the EU, depending on the service and feature used. When you use the AI assistant, an account or a purchase, your data is transferred to where the respective recipients process it (EU, USA); the safeguards are described for each recipient. You can withdraw a consent, ask for access, correction and deletion, and complain to us at the address in section 3.
- Where subscriptions are sold: web subscriptions are offered only in the countries selectable before checkout. They are not offered in, among others, Brazil, mainland China, Cuba, Iran, North Korea, Russia and Syria.
- Adults only: accounts, the AI assistant and subscriptions are restricted to people aged 18 or over. Store family and parental settings also apply.
16. Webshop
On geocanvas.app you can buy art prints of our maps. The shop pages are part of this website. You place the order in a checkout that Shopify operates for us at checkout.geocanvas.app; the prints are printed and shipped for us by our print partner. We are the controller for your order (section 3).
Shop pages and product images
Our shop pages use no cookies and no browser storage for advertising, analysis or tracking. Like every page of this website, they use two technical entries without personal data: the cookie “NEXT_LOCALE”, which remembers the language of the pages for up to one year, and the entry “geocanvas:storage-epoch” in local storage and session storage, a version number that tells the website which data stored by the map application is still valid. Both are strictly necessary to show you the website as you asked for it (§ 25(2) no. 2 TDDDG). The server log files (section 4) and Matomo (section 5) apply. Matomo records as named actions that a shop page was viewed, a size was chosen, a print was added to the cart or “Go to checkout” was clicked, without any data from the checkout. We serve the product images from our own server: our server fetches them from Shopify, and your browser does not connect to Shopify for them.
Cart and “Go to checkout”
When you click “Add to cart”, your browser stores the prints you chose (the size and the number of each) in its local storage, in an entry whose name ends in “shop-cart”, so that the cart is still there on the next page and on a later visit. The entry stays on your device until you empty the cart or delete it, or until an order with it has been placed; it is strictly necessary for the cart you asked for (§ 25(2) no. 2 TDDDG). Our server receives the cart only when you click “Go to checkout”: it then asks Shopify to create a cart with the chosen prints in the chosen sizes and in the language of the page, and sends you to the checkout. Your browser then also keeps the identifier of that Shopify cart in the same entry. When you return to the shop, our server asks Shopify with it whether the cart still exists; once the order has been placed it no longer does, and your browser empties the cart. Our server also passes your IP address to Shopify, so that Shopify can tell buyers apart and protect its systems against automated attacks and abuse. We do not store the cart on our server. The legal basis is steps prior to entering into a contract at your request (Art. 6(1)(b) GDPR) and, for the IP address, our legitimate interest in a secure checkout (Art. 6(1)(f) GDPR).
Checkout and order processing by Shopify
The checkout, the order confirmation, the order status page and the e-mails about the order are provided by Shopify International Limited, The Sidings, 4th Floor, Grand Canal Quay, Dublin D02 E7K8, Ireland (“Shopify”), as our processor; the data processing agreement is part of Shopify’s terms of service. In the checkout we process your e-mail address, your name, the delivery address and, where needed, the billing address, your telephone number if you give it, the print ordered, the price and the shipping method, and technical data about your device and connection (IP address, browser, time). We need this data to conclude and perform the contract; without it no order is possible. You can leave fields marked as optional empty. The legal basis is Art. 6(1)(b) GDPR.
In the checkout, Shopify sets cookies that are strictly necessary for the order you asked for, for example for the checkout session, the cart, language and country, and your cookie choice (§ 25(2) no. 2 TDDDG). Shopify sets cookies for statistics or marketing only if you agree in the checkout’s cookie banner (Art. 6(1)(a) GDPR, § 25(1) TDDDG); you can withdraw your consent there at any time. Details of the cookies: shopify.com/legal/cookies.
Shopify also processes data at Shopify Inc. in Canada and at sub-processors, including in the USA. Transfers to Canada are based on an adequacy decision of the European Commission; other transfers are based on the EU standard contractual clauses. If you use Shop Pay or sign in with Shop, Shopify processes your data for that service as a controller in its own right under its privacy policy (shopify.com/legal/privacy/consumers); send requests about it to Shopify at privacy.shopify.com.
Payment
Payments are made through Shopify Payments, a service of Shopify International Limited, together with a payment processor; for Germany Shopify names Stripe Payments Europe, Limited, PayPal (Europe) S.à r.l. et Cie, S.C.A. and Adyen N.V. (shopify.com/legal/processor-list). For the payment service and to prevent fraud and money laundering, Shopify and the payment processor process your payment data, your name, your address, the amount and data about your device as controllers in their own right; this may include automated fraud checks. We do not make automated decisions ourselves and do not receive your full card details. The legal basis is Art. 6(1)(b) GDPR.
Production and shipping by our print partner
Your print is produced and shipped by our print partner: theprintspace GmbH, Jahnstraße 18, 40215 Düsseldorf, Germany, in its studio in Düsseldorf. It is our processor; the data processing agreement under Art. 28 GDPR is part of its terms. Through the creativehub app in our Shopify account it receives from the order your name, the delivery address, your e-mail address, your telephone number if you gave it, and the print ordered, and it reports the tracking number back to Shopify. Passing on this data is necessary to perform the contract with you (Art. 6(1)(b) GDPR). creativehub is operated by the parent company Printspace Studios Limited, 74 Kingsland Road, London E2 8DL, United Kingdom; the United Kingdom has an adequacy decision of the European Commission. Orders to the USA may be printed and shipped by the print partner’s studio in Brooklyn, New York; your data is then processed in the USA. This transfer is necessary to perform the contract with you (Art. 49(1)(b) GDPR).
Delivery
For delivery, our print partner passes your name, the delivery address and your e-mail address to the carrier, so that the carrier can deliver the parcel and send you messages about the delivery. Our print partner chooses the carrier for each parcel: in Germany and the EU usually DHL Paket GmbH, Charles-de-Gaulle-Straße 20, 53113 Bonn, Germany, in the USA the United States Postal Service; some parcels may go with DHL Express or UPS. The carriers process this data under their own responsibility. The legal basis is the performance of the contract (Art. 6(1)(b) GDPR); for messages about the delivery, also the legitimate interest in a successful delivery (Art. 6(1)(f) GDPR).
The telephone number in the checkout is optional. If you give it, it may be passed to the carrier so that the carrier can reach you about the delivery; by entering it you agree to this (Art. 6(1)(a) GDPR). You can withdraw your consent at any time by e-mail to us, with effect for parcels not yet handed to the carrier.
E-mails about your order and customer service
Shopify sends the order confirmation, the shipping notice with the tracking number and updates about the order on our behalf to the e-mail address you gave in the checkout. If you write to us about an order, for example about transit damage or a defect, we process your message, the order number and any photos, and pass what is needed to our print partner so that it can replace the print (Art. 6(1)(b) GDPR). We do not use your e-mail address for advertising.
Withdrawing from an order
If you withdraw from an order through “Withdraw from contract”, what section 9 says under “Cancellation and withdrawal” applies. In addition, we store that the declaration concerns an order of a print, and the order number if you give it; we look up the order in Shopify and refund the amount there (Art. 6(1)(c) GDPR with § 356a BGB; Art. 6(1)(f) GDPR).
Bookkeeping
We keep orders, invoices and payment records for our bookkeeping. Where we use a tax adviser, they receive these records. The legal basis is our legal obligation to keep records (Art. 6(1)(c) GDPR in conjunction with § 147 AO and § 14b UStG).
Retention
We keep order data for as long as it is needed for the contract and for claims under it, usually until claims for defects become time-barred (two years from delivery). We keep invoices and accounting records for eight years and business letters about the order for six years, each from the end of the calendar year in which they were created (§ 147(3) AO, § 14b UStG). After that we delete the data in Shopify and have our print partner delete it. Shopify keeps the data of a closed store for up to two years.
Waitlist for countries we do not deliver to yet
On the shop pages you can ask to be told when we start delivering to your country. The form sends your e-mail address, the chosen country and the language for the e-mails directly from your browser to notify.geocanvas.app. We run this waitlist ourselves, with the open-source software WordPress and its plugin “Newsletter”, on the servers of our host netcup (section 2); no other provider receives the data. You then receive an e-mail with a confirmation link, and only when you click it are you put on the list (double opt-in). To prove your consent, we store the time of the sign-up and of the confirmation and the IP address used each time. After you sign up, confirm or unsubscribe, the plugin sets a cookie (“newsletter-…”) on notify.geocanvas.app that recognises your entry for one month, so that the waitlist’s pages (such as unsubscribing) can be matched to you; it is used for nothing else. It is needed for the service you asked for (Section 25(2) no. 2 TDDDG). We use the data only to tell you once, by e-mail, when we start delivering to your country. The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time through the link in each e-mail or by writing to us; this does not affect the lawfulness of the processing before. We delete your entry once that e-mail has been sent, when you withdraw, or 30 days after the sign-up if you do not confirm it.
Your rights
The rights described in section 3 also apply to your order data. Send requests to us; we pass them on to Shopify and our print partner where needed. Send requests about Shop Pay or your Shop account to Shopify at privacy.shopify.com.
Source of the German original: https://www.e-recht24.de