Privacy policy

This is a translation for convenience. Only the German version is legally binding.

1. Controller and contact

This privacy policy informs you which personal data we process when you use Spielbuchschmiede. Personal data is all data with which you can be personally identified.

The controller within the meaning of the General Data Protection Regulation (GDPR, German: DSGVO) is RPG Welten UG (haftungsbeschränkt), Stolzestraße 10, 44139 Dortmund, Germany, represented by its managing director Jörg Strube. You can reach us by email at [email protected].

2. Visiting the website and server log files

Every time the website is accessed, our servers and the service providers named in section 3 process server log files. The following data, which your browser sends to us and which is technically necessary to show you the website, is stored in them:

• address accessed (URL) and request method used
• date and time of the access
• response status and amount of data sent in bytes
• page from which you came to us (referrer)
• browser and operating system used (user agent)
• IP address

The processing is based on Art. 6(1)(f) GDPR and our legitimate interest in stability, security and error analysis. We do not evaluate the server log files to create user profiles. We examine them if there are specific indications of misuse or unlawful use. The connection to the website is encrypted with TLS.

3. Hosting and upstream service

The application, the database and the stored files run on servers of Hetzner Online GmbH, Industriestraße 25, 91710 Gunzenhausen, Germany. The servers we use are located in Germany. Hetzner processes the data on our behalf on the basis of a data processing agreement. The legal basis is Art. 6(1)(f) GDPR (reliable and secure operation) and, where it concerns the performance of the contract with you, Art. 6(1)(b) GDPR.

To deliver the website we use the upstream service of Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA. Every access to Spielbuchschmiede passes through the servers of Cloudflare. In doing so Cloudflare processes your IP address and the connection data named in section 2 in order to encrypt the connection, deliver content and ward off attacks and overload. The legal basis is Art. 6(1)(f) GDPR; our legitimate interest lies in fast and secure delivery. For the transfer to the USA see section 16.

4. Cookies and local storage in the browser

On our website nothing that is not required for operation is stored on your device without your consent. Technically necessary storage is based on § 25 (2) no. 2 TDDDG; the processing of personal data arising in the process is based on Art. 6(1)(b) or (f) GDPR. We only use all other storage with your consent (Art. 6(1)(a) GDPR in conjunction with § 25 (1) TDDDG).

We use the following cookies:

• sbs_session (after sign-in): keeps you signed in. The cookie contains a random identifier. It ends with the session or when the session duration expires. On a secure connection it is called __Host-sbs_session.
• sbs_second_step (only during a sign-in with a second step): remembers for a few minutes that you have already confirmed your password or your sign-in link and still have to enter the code.
• sbs_oidc (only during sign-in with Google): protects the sign-in process against forgery and is valid for a few minutes.
• sbs_consent_v1 (duration 365 days): stores your decision in the privacy settings. It does not contain an identifier of your person.
• sbs_access (only after entering an access code for a protected web book, duration 30 days): contains a random identifier with which the server recognises that you have entered the access code for this book. It contains neither the code nor any information about you.

The reach measurement with Matomo (section 11) does not set any cookies. The game progress of a web book is kept in the local storage of your browser (section 12). Settings that you make in the application can also be kept in the local storage of your browser. They do not leave your browser. You can set your browser so that you are informed when cookies are set and allow or exclude them case by case. Without the session cookie, signing in is not possible.

5. Contacting us

If you contact us by email, we process your email address, the content of your message and the other information you give us solely to deal with your request. The legal basis is Art. 6(1)(f) GDPR and, where the request relates to a contract, additionally Art. 6(1)(b) GDPR. Incoming emails are forwarded to our mailbox through the Mailgun service (section 7). We delete your message as soon as your request has been finally dealt with and no statutory retention obligations stand in the way.

6. Account, sign-in and security

6.1 Registration

You need an account to use Spielbuchschmiede. When you register we process your email address, your display name, your password (only as a hash value, not in plain text) and the times of registration and of the confirmation of your email address. We also store which version of the terms and conditions and of the privacy policy you have accepted. The legal basis is Art. 6(1)(b) GDPR. Without this information we cannot create an account.

6.2 Sign-in by password, sign-in link and second step

You can sign in with your email address and password or have a sign-in link sent to your confirmed email address. The link is valid for 15 minutes and can be used once. In the database we store only hash values of the link, of confirmation codes and of the password.

In addition you can set up a second step with an authenticator app (one-time code, OTP). For this we store the secret of the app in encrypted form and ten recovery codes as hash values.

For traceability and protection against misuse we show you the most recent events in your account, for example sign-ins with method and time, the linking or unlinking of sign-in methods and wrong codes. We store the type of the event, the sign-in method and the time. To ward off attacks we also count failed attempts per account and per IP address. The legal basis is Art. 6(1)(b) and (f) GDPR; our legitimate interest lies in the security of your account.

6.3 Sign-in with Google

Alternatively you can sign in with your Google account. When you choose this button, you are redirected to Google and sign in there. Google then sends us your Google identifier, your email address, the information whether it is confirmed, and your name. We store this information in your account in order to recognise you the next time you sign in. We do not store access and refresh tokens from Google. When you open the Google sign-in page, Google processes data such as your IP address under its own responsibility. For users in the European Economic Area the provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland; processing can also be carried out by Google LLC, USA (section 16). The legal basis is Art. 6(1)(b) GDPR. You can find Google's privacy notices at https://policies.google.com/privacy.

6.4 Deleting the account

You can have your account deleted yourself at any time (Art. 17 GDPR). You find the function in Spielbuchschmiede under Account and Delete account. An administrator account cannot be deleted this way. The procedure:

1. **Request.** You confirm with your password that you have read the notices. If you sign in without a password (for example with Google or by sign-in link), you enter the email address of your account instead. While an order is open, the request cannot be made. 2. **Confirmation by email.** We send a confirmation link to the address of your account. The link is valid for 24 hours and can be used once. Opening the link triggers nothing; only the button on the page confirms the deletion. Only a hash value of the link is stored in the database. 3. **Period of 14 days.** After your confirmation we tell you the date of deletion by email. Until then you can keep using your account and withdraw the request at any time under Delete account. 4. **Deletion.** After the period has expired we delete the data automatically. The deletion takes place in one step. Afterwards we send you a closing email to your previous address. If an order is still running at the time of deletion, the deletion waits until the order has been completed.

**What is deleted:** series, volumes, sections, maps, images and export files, recordings and music, requests to providers, the content of jobs (inputs and results), play sessions, published web books with access codes, outputs for the phone, test reader links and their reports, your author profile, your ratings and comments, your library and your saved game progress, your memberships and comments in other people's series, your sign-in data (sessions, sign-in links, link with Google, second step, events), your billing address and emails to your address that have not yet been sent.

**What is retained:** invoices with name and address from the purchase, the related orders with your consents to the terms, the privacy policy and the withdrawal policy, the bookings and the account of your credits, and the book licences as a data record are kept for ten years (§ 147 German Fiscal Code (AO), § 257 German Commercial Code (HGB)). The period begins at the end of the calendar year in which the document was created. Jobs remain as a data record without content (identifier, type, status and times), because bookings of your credits and the cost ledger refer to them. Unused credits lapse with the deletion. Withdrawal declarations that you have submitted through the withdrawal function are also retained (section 15). In addition, the consent to the legal texts (version, checksum, time) is retained for the same period. Your account remains as an empty shell until the period has expired, so that the documents stay assigned to an account: the email address is replaced by an unreachable address, the name is Deleted account and the password is unusable. In volumes of other authors your earlier versions of sections appear only with the name Deleted account.

We keep a log of every step. It contains the event, time, counter and a hash value of the account identifier, but no email address, no name and no plain-text identifier. Payment data is held by Mollie (section 8.2) and is deleted there according to Mollie's rules.

7. Sending emails

For sending and receiving emails we use the Mailgun service of Mailgun Technologies, Inc., 112 E Pecan St. #1135, San Antonio, Texas 78205, USA. We use the European Union region of Mailgun. Through Mailgun we send messages that are necessary for performing the contract or for the security of your account: the confirmation of your email address, the sign-in link, the resetting of the password, notices of changes to your account, the confirmation of your orders and the acknowledgement of receipt of your withdrawal. In doing so Mailgun processes your email address, the content of the message and information on delivery. The legal basis is Art. 6(1)(b) GDPR, and for receiving emails at our contact address Art. 6(1)(f) GDPR. We do not send advertising emails. For the transfer to the USA see section 16.

8. Orders, payment and invoice

8.1 Order data and invoice

When you buy credits or a book licence, we store your order, the payment status, the invoice and the bookings on your balance. For the invoice we process the information that you enter in your account as your billing address, for example name, address and, for businesses, the VAT identification number. We also store which version of the terms and conditions, of the privacy policy and of the withdrawal policy you confirmed at the time of purchase and that you agreed to immediate performance, with the time of confirmation. After the purchase we send you a confirmation email with the contract content, your consent and the legal texts (section 7). The legal basis is Art. 6(1)(b) GDPR and, where we fulfil obligations under tax and commercial law, Art. 6(1)(c) GDPR.

If, as a business, you give a VAT identification number, we check its validity through the VAT Information Exchange System (VIES) of the European Commission. In doing so we send the number and the country. We store the result with the invoice. The legal basis is Art. 6(1)(c) GDPR in conjunction with the provisions of VAT law. For consumers in other EU countries we determine value added tax according to the country of the billing address.

Authors can offer a web book for payment. This sale is only possible if we have switched it on. When you buy a book as a reader, we store your order, the amount, the payment status, the versions of the terms, of the privacy policy and of the withdrawal policy that you confirmed, the consent to immediate performance with the time, and your right to read the book. For this you need an account with a confirmed email address. Payment works as described under 8.2. The purchased book is in your library. The legal basis is Art. 6(1)(b) GDPR and, where we fulfil obligations under tax and commercial law, Art. 6(1)(c) GDPR.

8.2 Payment service provider Mollie

We process payments through the payment service provider Mollie B.V., Keizersgracht 126, 1015 CW Amsterdam, the Netherlands. The payment process runs through the payment system of RPG Welten UG. When you pay, you are redirected to the payment page of Mollie and enter your payment data there, for example card data or bank details. We do not receive the payment data ourselves. We send Mollie the amount, the currency, a description of the purchase and an internal payment identifier. From Mollie we receive the status of the payment. Mollie processes some data as an independent controller, where Mollie is legally obliged to do so, for example for fraud and money laundering prevention. In this respect Mollie's privacy notices apply. The legal basis for the disclosure is Art. 6(1)(b) GDPR.

8.3 Withdrawal

You can submit your declaration of withdrawal by email to [email protected] or online with the button "Withdraw from a contract", also without an account. With the online function we store your name, your email address, your information on the contract, the assigned order and the time of receipt, and send you an acknowledgement of receipt by email (section 7). We retain this information like the related order (section 15). We process it to handle the withdrawal under Art. 6(1)(b) and (c) GDPR.

9. Your content, collaboration and playing with fellow players

We store the texts, images and settings that you enter, upload or have generated in Spielbuchschmiede in your account on our servers in Germany, so that you can work on them, output them as a print PDF and play them. The legal basis is Art. 6(1)(b) GDPR. We keep finished export files only for a limited time (section 15).

When you invite other people to a series as co-authors or editors, we send them an email with an invitation link. For this we process the email address that you give. If the person accepts the invitation, all members of the series see the names of the other members, who is currently working on which section, comments and the history of changes with name and time. Invitations that are not accepted expire. The legal basis is Art. 6(1)(b) GDPR, and for inviting a person without an account Art. 6(1)(f) GDPR (our interest and that of the inviting person in working together).

When you play a gamebook together with others, we invite fellow players by link. Fellow players do not need an account. For the game we store the name that a fellow player gives themselves, the role and the game progress. Please do not enter personal data of third parties for which you have no authorisation into your projects, and do not upload images of real people without their consent.

10. Artificial intelligence functions

10.1 Text functions with OpenAI

When you use a text function (for example suggestions for a series, the planning of a volume, the writing of sections or the AI editing), we send your inputs and the content of your project that is necessary for the task to OpenAI Ireland Limited, Dublin, Ireland, or, for processing in the USA, to OpenAI, L.L.C. These are, for example, descriptions of series, characters and places, the outline and sections already written. In addition we check inputs and results for impermissible content with the moderation service of OpenAI. We do not send your email address and your name. For misuse detection at the provider we send an internal identifier of your account from which the provider cannot identify you.

Everything that you enter into an artificial intelligence function goes to this provider. Please do not enter confidential information or personal data of third parties there. We store which function was used, the time, the scope of the processing, the costs and the result of the check. The legal basis for the text functions is Art. 6(1)(b) GDPR, and for the content check Art. 6(1)(f) GDPR; our legitimate interest lies in protection against abusive and impermissible content and in the protection of minors. For the transfer to the USA see section 16.

10.2 Image generation with Ludo

When you use an image function, we send the image description, the settings such as style and format and, if the function requires it, an already generated image from your project as a template to the Ludo service (api.ludo.ai). The service generates the image and returns it to us. We do not send any information about your account. Everything that you enter into an image description goes to this provider. A transfer to a third country cannot be ruled out. The legal basis is Art. 6(1)(b) GDPR. Please do not enter personal data of third parties into the image description.

10.3 Voice output with ElevenLabs and music and upscaling of covers with Stability AI

If we have switched these functions on and you use them, we send the data for the respective task to the provider. If they are not switched on, no data is sent to these providers. The upscaling of covers runs automatically for every generated cover image as soon as it has been set up and is not blocked by a cost limit or an emergency switch.

• Voice output: To narrate a book, we send the text of the section, the selected voice and the voice settings to ElevenLabs (ElevenLabs, Inc., USA). The provider generates the recording and returns it to us. We do not send any information about your account.
• Upscaling of covers: When you generate a cover image, we upscale it for printing. For this we send the image generated by Ludo to Stability AI (Stability AI Ltd., London, United Kingdom). The provider returns the larger image to us. We do not send any information about your account and no text. If the upscaling does not succeed, the original image is kept.
• Music and sounds: For the generation we send the description that you enter and the desired length to Stability AI (Stability AI Ltd., London, United Kingdom). The provider returns the audio file to us. We do not send any information about your account.

Everything that you write in the text or in the description goes to the provider. Please do not enter confidential information or personal data of third parties there. We store the generated recordings and pieces of music in your account, together with the type of processing, the time, the scope and the costs. The legal basis is Art. 6(1)(b) GDPR. For the transfer to the USA and to the United Kingdom see section 16.

The use of the artificial intelligence functions is voluntary. Without them you can keep using Spielbuchschmiede and write yourself.

11. Reach measurement and consent

On the public pages of the website (home page, features, pricing, imprint, privacy, terms and conditions, withdrawal) we use the software Matomo to measure how the pages are used. Matomo runs on a server that we operate. Data is not sent to the manufacturer of the software. The script is only loaded after you have agreed to the Matomo service in the privacy settings. Matomo does not set any cookies and does not use a user identifier. Only the public pages are measured. Your account, the editor, the administration, the game, the invoices and the sign-in are never measured. What is sent is the address of the page without parameters, the time, the referring page (for external pages only the domain), information on browser and device and the IP address, which is shortened in Matomo.

The legal basis is your consent under Art. 6(1)(a) GDPR in conjunction with § 25 (1) TDDDG. You can withdraw or change it at any time with effect for the future through the link Privacy settings in the footer. Your decision is stored in the cookie sbs_consent_v1 (section 4). If the services or texts in the consent dialogue change, we ask you again.

12. Web books, sample reading, test readers and reading statistics

A web book is a gamebook that an author publishes at its own address (/lesen/ followed by the name of the book). You can read it without an account. We are responsible for the operation of the page, the author is responsible for the content of the book.

12.1 Reading a web book

• **Game progress.** The game progress (current section, stats, items, dice counter) is kept in the local storage of your browser. It is not sent to us. If you delete the website data of your browser, you also delete the game progress. The button for sharing the game progress creates a link that contains the game progress behind a hash sign. This part of the address is never sent to us by the browser. Whoever passes the link on passes on the game progress.
• **Accessing the page.** The technical data from section 2 arises when the page is accessed. A web book does not set any cookies unless you enter an access code (section 4), and does not load any content from third-party servers.
• **Limiting requests.** To protect against overload we count requests per IP address in short time windows. For this we store only a hash value of the address. The counters are deleted after two days at the latest.
• **Legal basis** is Art. 6(1)(f) GDPR (operation and protection of the page).

12.2 Sample reading, protected and paid edition

The author decides whether their web book can be read freely in full, whether only a sample can be read freely, or whether the edition is protected. The sample can be read without an account. At the end of the sample the page tells you how you can continue reading.

• **Access code.** The author can create and pass on access codes or invitation links. When you enter a code, the server checks it. Only a hash value of the code is stored in the database. With a valid code we store a random identifier of your access with time and expiry and set the cookie sbs_access (section 4). We do not store who entered the code, and no IP address. For each code the author sees a label, the number of redemptions and the expiry. The legal basis is Art. 6(1)(b) GDPR (access to the book) and (f) (protection of the edition against unauthorised use).
• **Purchase.** If the paid edition is switched on, you can buy a book with an account. The data processed is set out in sections 8.1 and 8.2. The author does not learn who bought a book. They see only the number of purchases.

12.3 Anonymous reading statistics

The server counts, per book and day, how often a game was started, how often an ending was reached, in which section readers left the book and how fights ended (victory, defeat, escape). Only counters are stored, with book, date without time, type of event and section. The IP address, browser identifier, cookie, device identifier or any other feature that makes individual readers identifiable are not stored. The browser does not send a count if Do Not Track or Global Privacy Control is switched on. The author sees the counters of their book. We do not show numbers below 5 individually; they appear as under 5. The counters of a book are deleted with the book. The legal basis is the legitimate interest of the author and of us in improving the book (Art. 6(1)(f) GDPR). Because the counters have no personal reference, we do not ask for consent.

12.4 Private test reader links

An author can create a secret link with which test readers can play the current draft and send reports.

• The link contains a random identifier. Only a hash value of it is stored in the database. The link expires after 180 days at the latest. The author can revoke it at any time.
• The author can give the link a name, for example a first name. The name appears on every report. The author decides which name to assign and informs the test readers about it. The author is themselves responsible for these names.
• A report contains the type (typo, wrong reference, unfair, unclear, other), your text, the section, the titles of the most recently visited sections and the game progress. As the time we store only the hour. We do not store the IP address and the browser identifier.
• Please do not write any personal information in your text. The author can delete reports at any time. If you want information or deletion regarding a report, contact the author or [email protected].
• The test readers' page is not indexed by search engines and does not pass on any referrer information.

The legal basis is Art. 6(1)(f) GDPR (the author's interest in feedback on their draft).

13. Book portal

The book portal consists of the directory at /buecher, the book pages, the author profiles, the ratings, the comments and the library. You can read everything without an account. For ratings, comments, reports of contributions, the library and an author profile you need an account with a confirmed email address.

• **Ratings and comments.** We store the stars (1 to 5), an optional text of up to 2,000 characters, the time and the identifier of your account. There is one rating per account and book. Your display name appears publicly, never your email address. If you change the display name, it also changes on your contributions. You can delete your own contributions at any time. The author of a book can hide comments on their book and reply to them; they cannot influence ratings.
• **Protection against misuse.** The server checks the texts (no HTML, no links in the first 7 days after registration, a short word list against advertising) and limits the number of contributions per account. We do not store any additional data in doing so.
• **Reports of content.** On every book page you can report content, also without an account. We store the text of the report, the book, the time and, if you are signed in, your account and the reason. We can hide or delete contributions and block an account for ratings and comments. Every decision is recorded with its reason in a log.
• **Author profile.** A profile is optional and only becomes public when you publish it. Public are the name in the profile, the short biography, up to five links and the published books. You can withdraw or delete the profile at any time.
• **Library and game progress.** The wish list stores which books you have bookmarked. You can save up to three game saves per book on the server so that you can continue playing on another device. We store endings reached only for books that are in your library. Purchased books also appear in the library. You can delete game saves and entries individually.
• **Sharing.** The sharing buttons are simple links. No scripts, images or fonts from third parties are loaded.

The legal basis is Art. 6(1)(b) GDPR (use of the account) and, for protection against misuse, (f) GDPR.

14. Information published by the author

The book page shows the title, the name of the author, the blurb and the cover image as the author has entered them for the volume. If a volume contains texts, images or recordings that were created with artificial intelligence, a label to this effect appears on the page. The author can withdraw a book at any time. After that the address no longer delivers any content. Cached copies at Cloudflare (section 3) become invalid within one minute at most.

15. Storage period

The storage period depends on the purpose of the processing and on statutory retention periods. In detail:

• We delete server log files after 14 days.
• We store the account and content for as long as your account exists. After a deletion request we delete them after the period of 14 days (section 6.4).
• We keep invoices, orders with your consents, bookings and book licences for ten years (§ 147 AO, § 257 HGB, § 14b German VAT Act (UStG)). The period begins at the end of the calendar year in which the document was created. When your account is deleted, these records are retained and separated from your information as far as possible (section 6.4).
• We store withdrawal declarations with name, email address and information on the contract for as long as we need them for processing and as evidence, and delete them at the latest with the related order. When your account is deleted they are retained until then.
• We store access codes for web books until they expire, until the author revokes them or until the book is deleted. The identifier of your access is valid for 30 days.
• We delete the counters of the reading statistics and the counters for limiting requests as described in section 12.
• Sessions end when the session duration expires.
• Backup copies: We back up the servers on which Spielbuchschmiede runs daily in our own infrastructure. If you delete your account, your data is deleted in the live systems under section 6.4. It can still be contained in backup copies until these are deleted automatically after their retention period has expired.
• We keep finished export files for a limited time and delete them afterwards. You can create them again at any time.
• Your decision in the privacy settings is stored for 365 days.
• We store emails to us for as long as the purpose requires.

Where processing is based on your consent, we store the data until you withdraw your consent. Where processing is based on legitimate interests, we store the data until you object, unless we can demonstrate compelling legitimate grounds for further processing. Otherwise we delete personal data when it is no longer necessary for the purposes for which it was collected.

16. Recipients and transfers to third countries

The recipients of your personal data are, depending on use: Hetzner Online GmbH (hosting), Cloudflare, Inc. (upstream service), Mailgun Technologies, Inc. (email), Mollie B.V. (payment), OpenAI (text functions and content check), Ludo (image generation), ElevenLabs (voice output, only if switched on) and Stability AI (music and upscaling of covers) and Google Ireland Limited and Google LLC (sign-in with Google). Where these service providers process data on our behalf, they do so according to our instructions. Beyond this we only pass on data if we are legally obliged to do so, for example to authorities, or if you have consented.

Some of these service providers are based in the USA or process data there: Cloudflare, Mailgun, OpenAI, ElevenLabs and Google. Stability AI is based in the United Kingdom, for which an adequacy decision of the European Commission exists. With the EU-US Data Privacy Framework, the European Commission has adopted an adequacy decision for transfers to certified companies in the USA (Art. 45 GDPR). Where a recipient is certified under it, the transfer relies on that. Otherwise we base it on standard contractual clauses of the European Commission under Art. 46(2)(c) GDPR. For Ludo a transfer to a third country cannot be ruled out; here too we rely on standard contractual clauses. You can request a copy of the safeguards through [email protected]. No data is sent to the manufacturer of Matomo.

17. Your rights

You have the following rights against us as the controller:

• Right of access under Art. 15 GDPR
• Right to rectification under Art. 16 GDPR
• Right to erasure under Art. 17 GDPR
• Right to restriction of processing under Art. 18 GDPR
• Right to notification under Art. 19 GDPR
• Right to data portability under Art. 20 GDPR
• Right to withdraw consent given under Art. 7(3) GDPR
• Right to lodge a complaint with a supervisory authority under Art. 77 GDPR

You can download the information about your account yourself at any time, in your account under "Download your data". The file kontodaten.json contains, for example, your profile, your billing address, your orders and invoices, your consents and your contributions. You download the texts of your volumes as a backup in the respective volume.

To exercise your rights, an email to [email protected] is sufficient. The withdrawal of consent does not affect the lawfulness of the processing carried out up to that point.

Right to lodge a complaint

You have the right to lodge a complaint with a data protection supervisory authority, in particular in the member state of your habitual residence, your place of work or the place of the alleged infringement. The supervisory authority responsible for us is the State Commissioner for Data Protection and Freedom of Information of North Rhine-Westphalia (Landesbeauftragte für Datenschutz und Informationsfreiheit Nordrhein-Westfalen), Kavalleriestraße 2-4, 40213 Düsseldorf, https://www.ldi.nrw.de.

Right to object

If we process your personal data on the basis of a balancing of interests under Art. 6(1)(f) GDPR, you have the right to object to this processing at any time on grounds relating to your particular situation. We will then stop the processing, unless we can demonstrate compelling legitimate grounds that override your interests, rights and freedoms, or the processing serves the establishment, exercise or defence of legal claims. You can lodge the objection by email to [email protected].

18. Necessity of the information and changes

The information given at registration and at the time of ordering is necessary for the conclusion of the contract. Without it we cannot conclude the contract and provide the service. Sign-in with Google, the artificial intelligence functions, the reach measurement, the author profile and the library are voluntary.

We adapt this privacy policy when our processing changes. The version published on this page at the time applies.