October 7, 2026
Privacy policy
Welcome to Rhinegold Consulting BV. This Privacy policy explains how we collect, use, and protect your personal information when you use our website.
1. Information We Collect
1.1 Personal Information
We may collect personal information, such as your name, email address, and other contact details when you voluntarily provide it to us. For example, when you register for an account, subscribe to newsletters, or contact us through the website.
1.2 Usage Information
We may collect information about your use of the website, including your IP address, browser type, device information, and pages visited. This information helps us analyze trends, administer the site, and improve user experience.
2. How We Use Your Information
We use the collected information for various purposes, including:
Providing and maintaining the website
Communicating with you about your account and our services
Sending newsletters, promotional materials, and other information you request
Analyzing website usage and improving our services
3. Sharing Your Information
We do not sell, trade, or otherwise transfer your personal information to third parties without your consent, except as described in this Privacy Policy. We may share information with trusted third-party service providers who assist us in operating our website or conducting our business.
4. Cookies and Similar Technologies
This website (rhinegold.de) and our publication at insights.rhinegold.de set no cookies for analytics or advertising, and we use no session recording or heatmap tools. There are two exceptions, both described in this privacy policy:
If you object to our web analytics, one cookie (
mtm_consent_removed) stores your objection (section 5).If you log in to Dietrich at chat.rhinegold.de, a strictly necessary session cookie keeps you logged in (section 10).
Our website host Framer provides basic page statistics without cookies and without identifiers on your device (section 5).
5. Web Analytics (Matomo)
We use Matomo, an open-source web analytics application, to understand how this website and our publication at insights.rhinegold.de are found and used. Matomo runs on our own server infrastructure in Amsterdam, Netherlands. Analytics data is not passed to any third-party analytics provider, is not used for advertising, and is not combined with data from other sources.
What is recorded.
For each page view: the address and title of the page, the address of the referring page — which tells us, for example, that a visit arrived from a search engine or an AI assistant — the date and time, and technical characteristics of the request such as browser, operating system, device type, screen size and language. Your IP address is shortened before it is stored, with the last two blocks removed, and the shortened value is used only to derive an approximate country.
No cookies.
Matomo is configured not to set cookies. It does not store an identifier on your device and does not read one. Page views are grouped into a visit using a short-lived technical value derived from the request itself, which changes daily. As a result, we cannot recognise you across days, across devices, or on any other website.
The only exception: if you object below, one cookie (mtm_consent_removed) stores your objection, so it can be respected on later visits.
Framer. Our website is built and hosted with Framer. Framer records basic page statistics (pages viewed, referring sites) for us without cookies and without any identifier on your device; according to Framer, this data is anonymised and cannot be traced back to a person. We use it only to see how the website is used.
Why we do this.
To see which of our texts are found and read, and to operate and improve this website. We rely on our legitimate interest under Art. 6(1)(f) GDPR.
How long.
Individual request records are deleted after 180 days. Aggregated statistics, which cannot be traced back to a single visit, are kept for longer.
Your choice.
You can object to this measurement at any time, with effect for the future:
6. Your Choices
You can manage your communication preferences by unsubscribing from newsletters or adjusting your account settings. You may also contact us to update or delete your personal information.
7. Security
We take reasonable measures to protect the security of your personal information. However, no method of transmission over the internet or electronic storage is completely secure. Therefore, we cannot guarantee absolute security.
8. Children’s Privacy
Our website is not directed to individuals under the age of 18. If you become aware that a child has provided us with personal information, please contact us, and we will take steps to remove such information.
9. Changes to This Privacy Policy
We may update this Privacy Policy periodically. We will notify you of any changes by posting the new Privacy Policy on this page. Your continued use of the website after such modifications will constitute your acknowledgment of the modified Privacy Policy.
Dietrich — the pre-flight check for AI-visibility claims
This section explains how we process data when you use Dietrich on our websites (chat.rhinegold.de). It supplements the general parts of this privacy policy.
Controller: rhinegold consulting bv, Putstraat 29, 3630 Maasmechelen, Belgium · admin@rhinegold.consulting · +32 473 713032
1. What data we process
Account data
What it is: E-mail address, password (stored only as a salted hash), confirmation links (stored only as a hash, valid 48 hours), password-reset links (stored only as a hash, valid 60 minutes), whether the address is a private e-mail address, time of registration, of e-mail confirmation and of accepting that exploring is not a verified test
When: When you register
Session cookie
What it is: A random session token in a strictly necessary cookie that keeps you logged in until 30 days after your last visit
When: When you log in; renewed when you use Dietrich
Usage counters
What it is: Number of questions, live checks and second opinions per account per day, to apply your quota and to see which accounts reached their daily limit (for misuse defence only)
When: Every question, live check and second opinion
Visit statistics
What it is: For each day, how often each public page was viewed and how many different visitors came. To tell visitors apart within one day, your IP address and browser identifier are combined with a random value that changes every day and turned into a one-way code in the server’s memory. The IP address, the browser identifier and the code are never saved; only the daily totals are kept. Nothing is stored on or read from your device.
When: Every view of a public page
Usage statistics
What it is: Weekly and daily totals calculated from the data above: new and confirmed accounts, conversations, questions, live checks, active accounts. Never per person and never from the content of conversations.
When: When we review them
Your messages
What it is: The text you type, including company names, website domains and anything else you write
When: Every message
Company profile
What it is: Company name, domains, market, industry, search terms and buyer questions, competitors and your comments on them, saved automatically from what you tell Dietrich so that you do not have to repeat it. Agency accounts can keep profiles for several client companies. The profile is your own statement; we do not verify it
When: When you give these details in a conversation; you can change or delete the profile at any time
Your reports
What it is: Which Page Quality Check reports and comparisons you ran while logged in, so that you find them again in your account
When: When you run a check while logged in
Conversation content
What it is: Dietrich’s answers and the course of the conversation, stored on our server as the authoritative history of your conversation and linked to your account; per answer also the time, the model used, token usage and the live-check steps
When: Every conversation
Block list
What it is: E-mail addresses and IP addresses we have paused because of misuse, and the e-mail addresses of accounts we have exempted from the daily quotas
When: When we pause an account or connection or grant an exemption
Security counters
What it is: Short-lived counters of login, registration, password-reset and deletion attempts per IP address, e-mail address or account, kept only in memory for up to 60 minutes to prevent abuse
When: Every such attempt
Derived search term and buyer question
What it is: A neutral search term and buyer question that Dietrich derives from the conversation, without your company name
When: When a live check runs
Check data
What it is: Company and competitor names, domains, the answers of the four AI models including the sources they cite, Google top-10 results, visibility index values, and the counts derived from them
When: When a live check runs
Scope-check events
What it is: Time, a random conversation ID, your internal account number, a reason code and the topic category — not the text of the message
When: When a message touches an excluded topic
Technical access data
What it is: IP address, browser user agent, time, requested address, status and duration of each request, recorded by our hosting provider’s network edge. Dietrich’s own application logs contain only internal network addresses of the hosting provider, not your IP address
When: Every request
Booking data
What it is: Name, e-mail address, chosen time and your note
When: Only if you book a call on Calendly
Asking your own question requires a verified account; the question page and prepared answers can be read without one. Dietrich uses only the strictly necessary session cookie — no analytics or advertising cookies, and no tracking across websites or across days. We count visits on our own server as daily totals (see “Visit statistics”). While you register, your typed question is kept in your browser’s local storage so that it can run after confirmation; it is removed once it has been sent. Conversations and check results are linked to your account by an internal account number.
Please do not enter personal data about other people or confidential information (see the usage rules).
2. Purposes and legal bases
Creating and managing your account, logging you in, applying your quota
Data: Account data, session cookie, usage counters
Legal basis: Art. 6(1)(b) GDPR — use of the service under the usage rules
Running the conversation and answering your questions
Data: Your messages, conversation content
Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in offering an interactive pre-flight check; where you ask about our services, Art. 6(1)(b) GDPR (steps prior to a contract at your request)
Remembering your company details and listing your conversations and reports in your account
Data: Company profile, your reports
Legal basis: Art. 6(1)(b) GDPR — use of the service under the usage rules
Live checks you trigger by giving a company, domains and a market
Data: Derived search term and buyer question, check data
Legal basis: Art. 6(1)(f) GDPR — legitimate interest in providing the check you asked for
Keeping Dietrich within its scope and preventing misuse (automatic topic check)
Data: Your latest message (processed, not stored), scope-check events
Legal basis: Art. 6(1)(f) GDPR — legitimate interest in a safe and focused service
Reviewing, reproducing and improving Dietrich’s answers and checks
Data: Stored conversations and check data
Legal basis: Art. 6(1)(f) GDPR — legitimate interest in quality and further development
Operating and securing the web server, preventing brute-force and abuse
Data: Technical access data, security counters, block list, usage counters (accounts that reached their daily limit)
Legal basis: Art. 6(1)(f) GDPR — legitimate interest in secure operation
Knowing how Dietrich is used, in totals only, to improve it
Data: Visit statistics, usage statistics
Legal basis: Art. 6(1)(f) GDPR — legitimate interest in understanding the use of our service without profiles and without cookies
Arranging a call
Data: Booking data
Legal basis: Art. 6(1)(b) GDPR
3. How the processing works — who receives what
Your input passes through separate steps. Each recipient receives only the data listed for it.
0. Account
Recipient: Resend (sender dietrich@rhinegold.de)
What the recipient receives: Your e-mail address and the confirmation link or password-reset link, to send that e-mail. Nothing you type in Dietrich is sent to any AI provider before you are logged in.
1. Topic check
Recipient: Anthropic (Claude)
What the recipient receives: Your latest message, before anything else happens. If the topic is excluded, the process stops here.
2. Conversation and derivation
Recipient: Anthropic (Claude)
What the recipient receives: The conversation so far: your messages including company names and domains, Dietrich’s earlier answers, and results of live checks. Claude writes Dietrich’s answer and derives the search term and the buyer question. Anthropic is the only AI provider that receives the conversation.
3a. Google top 10
Recipient: SISTRIX GmbH
What the recipient receives: The derived search term and the country
3b. Visibility index
Recipient: SISTRIX GmbH
What the recipient receives: The domains of the company and the compared competitors, and the country
3c. Four-model check
Recipient: OpenAI, Anthropic, Google, Perplexity
What the recipient receives: A separate request containing only the derived buyer question — no company name, no domains, nothing else from the conversation. The providers may use their own web search to answer it.
3d. Counting
Recipient: rhinegold (no third party)
What the recipient receives: Company and competitor names and domains are matched against the answers on our own systems.
4. Booking
Recipient: Calendly
What the recipient receives: Only what you enter on the Calendly booking page. Dietrich passes no data to Calendly.
The questions shown on the page “What people are asking” come from search data and published sources, never from Dietrich conversations.
4. Recipients and processors
Railway
Role in Dietrich: Hosting of the Dietrich app; storage of accounts, conversations and check data; request logs
Contracting entity: Railway Corporation, San Francisco, USA
Where data is processed: Servers and storage in the region EU West (Amsterdam, Netherlands); the provider is a US company
Safeguards: Data processing addendum; EU-US Data Privacy Framework (certified), standard contractual clauses
Anthropic
Role in Dietrich: Topic check, conversation, one of the four check models
Contracting entity: Anthropic Ireland, Limited, Dublin, Ireland
Where data is processed: Processing may take place outside the EU, including the USA
Safeguards: Data processing addendum incorporated in the terms; standard contractual clauses
OpenAI
Role in Dietrich: One of the four check models
Contracting entity: OpenAI Ireland Ltd., Dublin, Ireland
Where data is processed: Processing may take place outside the EU, including the USA
Safeguards: Data processing addendum incorporated in the terms; standard contractual clauses or adequacy decision
Google
Role in Dietrich: One of the four check models (Gemini API, paid service)
Contracting entity: Google Cloud EMEA Limited, Dublin, Ireland
Where data is processed: Processing may take place outside the EU, including the USA
Safeguards: Google data processing addendum; EU-US Data Privacy Framework (Google LLC certified), standard contractual clauses as fallback
Perplexity
Role in Dietrich: One of the four check models
Contracting entity: Perplexity AI, Inc., San Francisco, USA
Where data is processed: USA
Safeguards: Data processing addendum incorporated in the terms; EU-US Data Privacy Framework (certified), standard contractual clauses
Resend
Role in Dietrich: Sending confirmation and password-reset e-mails from dietrich@rhinegold.de
Contracting entity: Plus Five Five, Inc. (Resend), San Francisco, USA
Where data is processed: E-mails are sent from the EU (Ireland); e-mail records are stored in the USA
Safeguards: Data processing addendum incorporated in the terms; standard contractual clauses, EU-US Data Privacy Framework
Calendly
Role in Dietrich: Booking a call, only if you choose to
Contracting entity: Calendly, LLC, Buford, Georgia, USA
Where data is processed: USA
Safeguards: Data processing addendum incorporated in the terms; EU-US Data Privacy Framework (certified), standard contractual clauses as fallback
SISTRIX
Role in Dietrich: Google top 10 and visibility index
Contracting entity: SISTRIX GmbH, Bonn, Germany
Where data is processed: EU
Safeguards: Receives only search terms, domains and the country, no data from your conversation
Use of data by the AI providers. Under their terms for API customers, Anthropic, OpenAI, Google (paid Gemini API) and Perplexity do not use the data we send them to train their models. They may keep it for a limited time, mainly to detect misuse: Anthropic up to 30 days, OpenAI up to 30 days, Google up to 55 days (and 30 days for answers grounded with Google Search), Perplexity according to its data processing addendum at the latest until 30 days after our contract ends. Longer periods can apply where content is flagged for a policy violation or where the law requires it.
5. Transfers to third countries
Some of the providers above process data in the USA or can access it from there. Where a provider is certified under the EU-US Data Privacy Framework, the transfer is based on the adequacy decision of the European Commission (Art. 45 GDPR); otherwise, and in addition, on standard contractual clauses (Art. 46(2)(c) GDPR). Dietrich’s stored data — accounts, conversations and check data — is kept on servers in the Netherlands.
6. How long we keep data
Account data
Retention: Until you delete your account. Registrations that are never confirmed are deleted after 90 days
Session cookie
Retention: 30 days after your last visit, or until you log out, reset your password or delete your account
Usage counters
Retention: 90 days
Visit statistics
Retention: Daily totals are kept; they contain no personal data. The value used to tell visitors apart exists only in memory and is replaced every day
Company profile
Retention: Until you delete it or your account
Link between your account and your reports
Retention: As long as the report: 90 days
Downloads (“this conversation”, “all my data”)
Retention: Created when you request them; we do not keep a copy
Conversations (messages, answers, per-answer metadata)
Retention: 90 days after the last activity in the conversation
Check data (model answers, results)
Retention: 90 days
Scope-check events (no message text)
Retention: 90 days
Block list
Retention: Until we lift the block or the exemption
Security counters
Retention: In memory only, at most 60 minutes
Technical access data at our hosting provider
Retention: Up to 30 days
E-mail records at Resend
Retention: 30 days
Booking data
Retention: Calendly keeps it for as long as needed to arrange the call; we delete it from Calendly when it is no longer needed
Deletion of Dietrich data runs automatically once a day. Data processed only for the topic check of an excluded message is not stored by us. We do not keep separate backups of Dietrich data.
7. Automated processing
Each message is checked automatically for excluded topics (violence, sexual content, religion, race or ethnicity, antisemitism). If a message touches one of them, the conversation ends. This is not a decision with legal effect on you or a similarly significant effect within the meaning of Art. 22 GDPR: you can start a new conversation at any time, and you can contact us.
8. Is providing data required?
No. Using Dietrich is voluntary. You decide what you type. Without a company, domains and a market, Dietrich cannot run a live check, but you can still ask questions.
9. Your rights
You have the right to access, rectification, erasure, restriction of processing, data portability and to object to processing based on legitimate interests (Art. 15–21 GDPR), and the right to lodge a complaint with a supervisory authority. To exercise your rights regarding Dietrich, contact us using the details above.
You can delete your account yourself while logged in (“Delete account”, confirmed with your password). This deletes your account data, company profiles, the conversations, the Page Quality Check reports and comparisons you ran while logged in, live-check results, scope-check events and usage counters linked to your account. In your account you can also download one conversation as a page, or all data stored for your account as one file (Art. 15 and 20 GDPR). You can also ask us to do this by e-mail from your registered address.
Page Quality Check
This section explains how we process data when you use our Page Quality Check (chat.rhinegold.de/rate). It supplements the general parts of this privacy policy.
Controller: rhinegold consulting bv, Putstraat 29, 3630 Maasmechelen, Belgium · admin@rhinegold.consulting · +32 473 713032
1. What the tool does
You enter the address of a public web page and, optionally, a search query. Our server loads that page, converts its visible text into plain text and asks an AI model typed questions about it, based on Google’s public Search Quality Rater Guidelines. Fixed rules in our code turn the answers into a rating. You need no account. The tool sets no cookies and stores nothing on your device.
2. What data we process
Your input: The page address and the optional search query you enter
Pasted content. If our server cannot load a page you entered, you can paste its visible text or HTML source instead. We process the pasted content like a page we load. Our server loads nothing for it. The page address you entered is still sent to Google for the speed measurement described above. If you ask for a second opinion or an explanation (“Why?”), the pasted text goes to the AI providers listed for these functions, as for any other report.
Page content: The publicly available text of the page you entered, as our server loads it. Public pages can contain names or contact details of people, for example on team or contact pages. Before the text is sent to the AI model, we replace e-mail addresses and phone numbers by placeholders and names of people by invented names, on our own server. Name recognition is automatic and not complete; a name it misses can remain in the text. Names that are part of the website’s own domain are kept, because they name the company (for example a company named after its founder).
Competitor page: If you compare your page with another page: the address and public text of that page, processed in the same way as your page
Images on the page: Up to 8 images from the main content, loaded by our server and read on our server: file metadata (credit or copyright, camera data, a marker for AI-generated images) and file size. For each image we store a short numeric fingerprint together with the website’s domain, so that the same image found on other websites can be recognised as stock material. We store no image and no image address. Without your request, no image is sent to an AI model or to another provider (see “Image check” below)
Reachability: Facts our code reads from the website: its robots.txt, sitemap and llms.txt, noindex and canonical tags and structured data. No AI model is involved
Speed measurement: The address of the page you entered (and of a compared page), without parameters and anchors. Google loads that page from its own servers and measures how fast it loads and responds on a simulated phone; it also returns, if it has enough data, how fast the page or website was for real Chrome users over the last 28 days. We store the resulting figures with the report
Report: The rating, the model’s answers, the statements from the page that were checked, and the time of the check; for a comparison, which two reports were compared
Objections: If you tell us that a rating seems wrong: your text, the e-mail address if you give one, the report and question it refers to, our reading at that moment and the time. No account is needed; your IP address is used only in memory to limit the number of objections
Technical access data: IP address, browser user agent, time, requested address, status and duration of each request, recorded by our hosting provider’s network edge
Abuse counters: A short-lived count of checks per IP address, kept only in memory, to limit the number of checks
We do not ask for your name or e-mail address. A report you run without logging in is not linked to you. If you are logged in, the report and any comparison are listed in your account (see the section “Dietrich”).
3. Purposes and legal bases
Running the check you asked for and showing the report: Your input, page content, report — Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in offering a free page check on request
Processing personal data that happens to appear on the checked public page: Page content — Legal basis: Art. 6(1)(f) GDPR — legitimate interest in assessing publicly available web pages; before the AI step we replace e-mail addresses, phone numbers and names of people, and we do not use the content for any other purpose
Image check on your request: Images of the checked page, page address, text next to the images, result — Legal basis: Art. 6(1)(f) GDPR — legitimate interest in checking public web pages on request; images are sent only when you ask for it
Showing load time and mobile usability in the report: Page address, measured figures — Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in offering a free page check on request
Improving the check and our content: Reports and objections, evaluated in aggregated form: which questions, errors and topics come up often — Legal basis: Art. 6(1)(f) GDPR — legitimate interest in improving the check and publishing useful content; we publish no report and nothing that identifies a checked page or a person
Improving the check from your objections, and answering you if you give an e-mail address: Objections — Legal basis: Art. 6(1)(f) GDPR — legitimate interest in correcting the check; the e-mail address is voluntary
Operating and securing the service, limiting misuse and costs: Technical access data, abuse counters — Legal basis: Art. 6(1)(f) GDPR — legitimate interest in secure and affordable operation
4. Recipients
Railway: Hosting of the tool, storage of reports, request logs — What it receives: Everything listed above — Where: Servers and storage in the region EU West (Amsterdam, Netherlands); the provider is a US company
Cloudflare, Inc., San Francisco, USA: Gateway through which we call the AI model (Cloudflare AI Gateway) — What it receives: Page address, page title, page text with e-mail addresses and phone numbers replaced by placeholders and names of people replaced by invented names, checked statements, today’s date and, if you enter one, the search query — Where: Cloudflare’s global network; no restriction to the EU is available for this service
TypeSafe AI, Inc., San Francisco, USA: Provider of the AI model “Jev” that answers the questions; we use it through Cloudflare — What it receives: Same as Cloudflare — Where: USA
The operator of the page you entered (and of a compared page): Their server receives ordinary requests from our server when we load the page, its images, robots.txt, sitemap and llms.txt, and from Google’s servers when Google measures the speed — What it receives: The requests from our server and from Google (not your IP address) — Where: Wherever that website and its images are hosted
We have switched off request logging at the Cloudflare gateway. According to Cloudflare’s model catalogue, the model is offered with zero data retention; TypeSafe states that it does not train models on the input it receives.
Second opinion (signed-in users only). If you are logged in to your Dietrich account and ask for a second opinion on a report, we send the same page text (e-mail addresses and phone numbers replaced by placeholders, names of people by invented names), the page title, the page address in the same form and today’s date to four AI providers: Anthropic (Claude), OpenAI (GPT), Google (Gemini API, paid service) and Perplexity. Each returns the three points that hold the page back most, with a quote from the page; we store these with the report. The providers receive nothing about you, and their web search is not used. Which company of each provider receives the data, where it is processed, the safeguards for transfers outside the EU and how long the providers keep the data are described in the section “Dietrich” of this privacy policy. Using your account for this, and counting how many second opinions you request per day, is covered there as well.
“Why?” (signed-in users only). If you are logged in and ask why the model read a question the way it did, we send the page text (and, in a comparison, the text of the other page), with e-mail addresses and phone numbers replaced by placeholders and names of people by invented names, together with the question, to Perplexity (model Sonar, through its Agent API, without web search); if Perplexity is unavailable we may use OpenAI instead. The answer names passages from the page, each checked word for word against the page, and is stored with the report. It is labelled as an explanation by another model, not as the reason for the rating. The provider receives nothing about you. Provider details are in the section “Dietrich”.
Image check (on request only). If you choose “Check the images too?”, we send up to 8 images from the main content of the checked page to Google: to Google Cloud Vision, which reports where the same image appears on the web, and to the Gemini API (paid service), which answers fixed questions about each image, together with the page address and the text next to the image. Images can show people, for example staff on a team page; unlike the page text, images cannot be pseudonymised. We store with the report the result for each image (for example “stock photo, found on istockphoto.com”) and the time you asked for it, but no image and no image address. The providers receive nothing about you. Which Google company receives the data, where it is processed and the safeguards for transfers outside the EU are described in the section “Dietrich” for the Gemini API; Google Cloud Vision is provided by the same company under the same terms.
Speed measurement. To show load time and mobile usability, we send the address of the page you check to PageSpeed Insights, a service of Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA. Before sending, we remove all parameters and anchors from the address (everything after “?” or “#”). Google receives no information about you. Google processes the address as an independent controller. The transfer to the USA is based on the EU-U.S. Data Privacy Framework, under which Google LLC is certified.
Transfers to the USA. Cloudflare, Inc. is certified under the EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR). TypeSafe AI, Inc. is not certified under the Data Privacy Framework, and we have no standard contractual clauses with TypeSafe: under Cloudflare’s terms, the model is a third-party product to which Cloudflare passes the data on our instruction, outside Cloudflare’s data processing addendum. The data sent is the text of a public web page in which e-mail addresses and phone numbers are replaced by placeholders and names of people by invented names; a name that the automatic recognition misses can remain. The same applies to names in the page address.
5. How long we keep data
Report (rating, answers, checked statements, speed figures and, if requested, the second opinion and the image check; names and contact details replaced as above): 90 days, then deleted automatically
Page text in the report: 30 days
Comparison (which two reports were compared, and when): 90 days
Objections (text, optional e-mail address, report and question): 90 days
Image fingerprints with the website’s domain: 365 days
Link between a report and your account (logged in only): 90 days, or earlier if you delete your account
Technical access data at our hosting provider: Up to 30 days
Abuse counters: In memory only, at most 60 minutes
6. Your rights
You have the right to access, rectification, erasure, restriction of processing and to object to processing based on legitimate interests (Art. 15–21 GDPR), and the right to lodge a complaint with a supervisory authority. Because reports are not linked to a person, we can only find a report if you tell us the page address and the approximate time of the check. If your own name or contact details appear in a report and you want it removed, write to us using the details above.
12. Contact Us
If you have questions, contact us at admin@rhinegold.de