Formerly Sovereign House

Principality of Hohenzollern-Hechingen

Principality of Hohenzollern-Hechingen – House of Hohenzollern

Jurisdiction
Hohenzollern-Hechingen
Entry type
House
Editorial status
Reviewed - Verified

Fürstentum Hohenzollern-Hechingen

House of Hohenzollern

Hohenzollern-Hechingen was a county and principality in southwestern Germany. Its rulers belonged to a branch of the senior Swabian branch of the Hohenzollern dynasty. The County of Hohenzollern-Hechingen was created in 1576, upon the partition of the County of Hohenzollern, a fief of the Holy Roman Empire. When the last count of Hohenzollern, Charles I of Hohenzollern (1512-1579) died, the territory was to be divided up between his three sons:

  • Eitel Frederick IV of Hohenzollern-Hechingen (1545-1605)
  • Charles II of Hohenzollern-Sigmaringen (1547-1606)
  • Christopher of Hohenzollern-Haigerloch (1552-1592)

Unlike the Hohenzollerns of Brandenburg and Prussia, the Hohenzollerns of southwest Germany remained Roman Catholic. The County was raised to a principality in 1623. The principality joined the Confederation of the Rhine in 1806 and was a member state of the German Confederation between 1815 and 1850. The democratic Revolution of 1848 was relatively successful in Hohenzollern, and on 16 May 1848, the Prince was forced to accept the establishment of a constitution. However, the conflict between monarch and democrats continued, and on 6 August, Hohenzollern was occupied by Prussian forces. On 7 December 1849, Prince Friedrich Wilhelm Konstantin sold the country to his relative, King Frederick William IV of Prussia. On 12 March 1850, Hohenzollern-Hechingen officially became part of Prussia, and formed together with Hohenzollern-Sigmaringen the Hohenzollernsche Lande.

Counts of Hohenzollern-Hechingen (1576-1623)

  • Eitel Frederick IV (1576-1605)
  • John George (1605-1623) became Prince in 1623

Princes of Hohenzollern-Hechingen (1623-1850)

  • Eitel Frederick V (1623-1661)
  • Philip Christopher Frederick (1661-1671)
  • Frederick William (1671-1735)
  • Frederick Louis (1735-1750)
  • Josef Frederick William (1750-1798)
  • Hermann (1798-1810)
  • Frederick (1810-1838)
  • Constantine (1838-1850) died 1869; last male member in dynastic line

The Family Titles and Styles

The members of this family bore the title Prince or Princess von Hohenzollern, together with the formal appellation of His or Her Serene Highness.

The Genealogy of the Princely House

HERMANN Fst von Hohenzollern-Hechingen 9 Apr 1798 (Lockenhaus 6 Nov 1748-Hechingen 2 Nov 1810); m.1st Maastricht 18 Nov 1773 Luise Gfn von Merode (Merode 28 Sep 1747-Maastricht 14 Nov 1774); m.2d Brussels 15 Feb 1775 Maximiliane Pss de Gavre (30 Mar 1753-Brussels 6 Aug 1778); m.3d Dagstuhl 26 Jul 1779 Antonie Gfn von Waldburg-Zeil-Wurzach (Wurzach 6 Jun 1753-Vienna 25 Oct 1814)

1a) Luise Juliane Konstantine (Maastricht 1 Nov 1774-Glogau 7 May 1846); m.1806 Ludwig Frhr Heer von der Burg (16 Dec 1776-13 Oct 1833)

  • 2a) FRIEDRICH Hermann Otto Fst von Hohenzollern-Hechingen (Namur 22 Jul 1776-Schloß Lindich 13 Sep 1838); m. Prague 26 Feb 1800 Pauline Pss Biron von Kurland (Mitau 19 Feb 1782-Vienna 8 Jan 1845)
  • 1b) Friedrich Wilhelm KONSTANTIN Hermann Thassilo Fst von Hohenzollern-Hechingen, ceded his sovereign rights to the King of Prussia 7 Dec 1849 (Sagan 16 Feb 1801-Schlesien-Nettkow 3 Sep 1869); m.1st Eichstädt 22 May 1826 Eugénie de Beauharnais Fstn von Leuchtenberg (Milan 23 Dec 1808-Freudenstadt 1 Sep 1847); m.2d (morganatically) Görlitz 12 Nov 1850 (div 1863) Amalie Frn Schenk von Geyern, cr Gfn von Rothenburg 8 Nov 1850 (Fürth 13 Jul 1832-Wiesbaden 29 Jul 1897); their children bore the title Graf/Gräfin von Rothenburg
  • 1c) Friederike Wilhelmine Elisabeth Amalie Adelheid (Löwenberg 13 Feb 1852-Dresden 31 Dec 1914); m.1st Löwenberg 23 Apr 1869 (div 1878) Arthur von Rosen; m.2d Berlin 14 Jun 1879 Julius von Lübtow (d.30 Sep 1905)
  • 2c) Friedrich Wilhelm Karl (Löwenberg 19 Feb 1856-Schlesisch-Nettkow 23 Aug 1912); m.1st London 29 Apr 1877 (div 1884) Dorothea Schirmer (Kassel 15 Dec 1852-Dresden 7 May 1898); m.2d Schlesisch-Nettkow 14 Apr 1885 (div 1892) Elfriede Frn von Krane (Öls 5 Feb 1861-12 Nov 1943); m.3d Berlin 14 May 1892 Katharina Billig (Dresden 18 Jul 1869-Liegnitz 21 Jan 1934)
  • 1d) Friedrich-Wilhelm Leopold Constantin (Schlesisch-Nettkow 29 Mar 1886-Charleville 23 Jul 1916)
  • 2d) Albrecht Joachim Paul (Schlesisch-Nettkow 19 Sep 1887-Wiesbaden 18 Jun 1903)
  • 3d) Barbara Katharina Friederike (Schlesien-Nettkow 18 Dec 1893-Haus Auel 3 Nov 1965); m.1st Schlesisch-Nettkow 8 May 1918 (div 1920) Wilhelm Siegfried Moennich (Berlin 12 Nov 1889-Berlin 13 Apr 1932); m.2d Schlesisch-Nettkow 25 Aug 1920 Paul Baron von La Valette St. George (Düsseldorf 22 Aug 1890-Köln 20 May 1970)
  • 4d) Ursula Leonore Ines (Schlesisch-Nettkow 10 Nov 1896-Engelskirchen 26 Sep 1984); m. Schlesisch-Nettkow 22 Dec 1924 (div 1930) Ferdinand Papházy; Note: I have received the following communication from a correspondent: “My uncle Ferdinand Paphazy was born in 1898. His brother Josef (my father) in 1900. Their father Ivan P and mother Margit. Around 1922-23 Ferdinands wallet was stolen together with other articles. It was not until 1932 that a certain Ursula presented at the family home, claiming to be Ferdinand’s widow. She was very disturbed and destitute. The real story emerged and the thief had impersonated my uncle. I understand that Ursula died in a mental institution. Ferdinand was a lawyer ,married with no offspring and he died in1952 in Budapest. I hope this helps so that an inaccuracy may not be perpetuated. John Paphazy, Melbourne, Australia.” A subsequent communication from John Paphazy explained that his mother remembered that it was Ferdinand’s passport which had been stolen.
  • 5d) Friedrich Wilhelm Konstantin (Schlesisch-Nettkow 23 Oct 1897-Schlesisch-Nettkow 16 Jan 1932); m. Schlesisch-Nettkow 25 Aug 1918 (div 1930) Margarethe Herhudt von Rohden (Ettlingen 1 Jan 1894- )
  • 1e) Eitel-Friedrich (Berlin-Charlottenburg 11 Sep 1919-k.a.in Russia 17 Mar 1944); m. Berlin 14 Apr 1942 Maridore Niebuhr (b. Uelzen 3 Oct 1920)
  • 2e) Johann-Georg (Schlesisch-Nettkow 8 Feb 1921-k.a.2 Nov 1943)
  • 6d) Katharina Susanna Margarete Justine (San Remo 9 Feb 1900-Düsseldorf 20 Dec 1975); m. Schlesisch-Nettkow 24 Nov 1920 Hans-Herbert Frhr von Ohlen u. Adlerscron (Reichen 9 Sep 1895-Hannover 20 Aug 1958)
  • 3c) Wilhelm Friedrich Ludwig Gustav (Schönbühl, Switzerland 16 Nov 1861-Dresden 17 Feb 1929); m. Schlodien 16 May 1894 Freda-Marie Bggfn u. Gfn zu Dohna-Schlodien (Carwinden 21 Apr 1873-Dresden 18 Jun 1959)
  • 1d) Friedrich Wilhelm Gustav Adolf (Ziegenberg 6 Mar 1895-Feldafing 19 Oct 1961); m. Dresden 19 Feb 1935 Ellinor Geller (Limbach 2 Mar 1908-Bernried 1 Jan 1975)
  • 1e) Stefan Adolf (Dresden 20 Jul 1940-Going, Austria 28 Feb 1997); m. Bernried 6 Feb 1970 Hella Eisentraut (b. Kempten 13 Mar 1946)
  • 1f) Vera Felizitas Maria Theresia (b. Munich 21 Jan 1977)
  • 2f) Caroline Julia Johanna Maria (b. Munich 9 Oct 1979)
  • 2e) Viktor Wilhelm Josef (b. Dresden 22 Apr 1945); m. Feldafing 19 Aug 1966 Angelika Madeja (b. Munich 12 Jun 1949)
  • 1f) Jessica (b. Starnberg 14 Feb 1967); m. Feldafing 7 Oct 1994 Heinz Hönigschmid (b. Starnberg 27 Jan 1968)
  • 2f) Tania (b. Nürnberg 28 Jun 1971); m. Feldafing 31 Jul 1998 Dieter Kitzendorf (b. Munich 26 Feb 1965)
  • 3f) Friedrich Josef Wilhelm (b. Starnberg 29 Jul 1982)
  • 3e) Angela Veronika Ellinor (b. Munich 9 Dec 1950); m.1st Feldafing 18 Oct 1968 (div 1985) Manfred Schubert (b. Neumarkt, OberPfalz 14 Sep 1949); m.2d Pöcking 28 Oct 1994 Werner Benedikt Brandl (b. Munich 30 Aug 1959)
  • 2d) Joachim-Albrecht Karl (Ziegenberg 30 Aug 1897-Munich 3 Sep 1978); m.1st Berlin 10 Sep 1932 (div 1934) Adelheid Chmielewski (Saarbrücken 12 Sep 1910-Karlsruhe 24 Apr 2000); m.2d Berlin 7 Jan 1942 Charlotte Hetzer (Bockau 6 Dec 1893-Bremen 7 Jan 1959)
  • 1e) Armin Kurt Karl (b. Karlsruhe 20 Feb 1933); m.1st Mont-de-Marsan 13 Aug 1955 (div 1958) Edith Friedrich (b. Medellür, Colombia 17 Aug 1938); m.2d Holzminden 31 Dec 1964 (div 1983) Oda Liecker (b. Hannover 2 Jan 1935); m.3d Köln 8 Jul 1991 Ursula Kremp (b. Bexbach 14 Mar 1942)
  • 1f) Christian Peter Uwe (Holzminden 14 Jul 1965)
  • 2f) Andreas Rainer Lutz (b. Holzminden 15 Jul 1966)
  • 2e) Karl-Heinz (b. Wiesbaden 7 Apr 1934); m.1st Meersburg 30 Jun 1967 (div 1978) Beatrix Conradi (b. Holzen, Kr Lörrach 22 Jun 1940); m.2d Halle 21 Dec 1984 (div 1985) Cäcilia Hemmer (b. Bottrop 5 Sep 1944); m.3d Aachen 11 Nov 2000 Galina Volosevich (b. Belozersk 6 Jul 1964)
  • 1f) Alexandra Vera (b. Heidelberg 23 Nov 1967)
  • 2f) Indira Annette (b. Munich 6 Apr 1970)
  • 3a) Marie Antonie Philippine (Dagstuhl 8 Feb 1781-The Hague 25 Dec 1831); m. Hechingen 12 Jul 1803 Friedrich Ludwig Gf von Waldburg-Capustigall (25 Oct 1776-18 Aug 1844)
  • 4a) Maria Theresia Franziska (Dagstuhl 11 Aug 1784-Dagstuhl 6 Sep 1784)
  • 5a) Franziska Theresia Karoline (Dagstuhl 19 Jan 1786-1810)
  • 6a) Maximiliane Antonie (Wadern 3 Nov 1787-Baden, nr Vienna 30 Mar 1865); m.1st Hechingen 25 Feb 1811 Eberhard Gf von Waldburg-Zeil-Wurzach (14 Jun 1778-18 Jan 1814); m.2d 12 Jul 1817 Klemens Josef Gf von Lodron (23 Sep 1789-3 Sep 1861)
  • 7a) Josefine (Wadern 14 May 1791-Vienna 25 Mar 1856); m. Hechingen 31 Aug 1811 Ladislaus Gf Festetics von Tolna (Ság 15 Jun 1785-Vienna 12 May 1846)
We use cookies to personalise content and ads, to provide social media features and to analyse our traffic. We also share information about your use of our site with our social media, advertising and analytics partners. View more
Cookies settings
Accept
Decline
Privacy & Cookie policy
Privacy & Cookies policy
Cookies list
Cookie name Active

Privacy and Cookie Policy Last updated: 11 August 2026

Neue Gotha respects your privacy and is committed to handling personal data lawfully, fairly, and transparently. This Privacy and Cookie Policy explains who is responsible for personal data, what information we process, why we process it, how long we retain it, who may receive it, and the rights available to individuals under the General Data Protection Regulation (EU) 2016/679 (“GDPR”) and applicable national data-protection and electronic-communications law.

1. Who is responsible for your personal data?

The controller responsible for the processing described in this policy is:

  • Legal name: Neue Gotha Historical Register gUG
  • Trading or project name: Neue Gotha
  • Postal address: Musterstraße 12, 10115 Berlin, Germany
  • Email: editor@neuegotha.de
  • EU/EEA representative: Not applicable (the controller is established in Germany).
  • Data Protection Officer: No Data Protection Officer has been appointed. Privacy enquiries are handled through editor@neuegotha.de.

Questions about this policy or requests concerning personal data may be sent to the email or postal address above.

2. Scope of this policy

This policy applies to personal data processed through https://neuegotha.com, correspondence with the Neue Gotha editorial office, material submitted for editorial consideration, and editorial or archival records concerning identifiable living individuals.

It does not govern independent third-party websites or services linked from this website. Those providers are responsible for their own privacy practices.

3. Personal data we process and why

Processing activity Personal data Purpose Legal basis Retention
Website delivery, logging, and security IP address; date and time of access; requested page or file; referring page; browser, operating-system, and device information; error and security-event data Deliver the website, maintain availability, diagnose faults, prevent abuse, and protect the website and its users Article 6(1)(f) GDPR — our legitimate interests in operating a secure and reliable website. Where processing is required by law, Article 6(1)(c) GDPR may also apply. Routine access and error logs are retained for 14 days. Records isolated for investigation of a suspected security incident may be retained for up to 90 days after the incident is resolved, or longer where required for legal claims.
Editorial correspondence and enquiries Name, contact details, message content, correspondence history, and any documents or other information voluntarily provided Respond to enquiries, assess corrections or submissions, maintain editorial records, and protect legal rights Article 6(1)(f) GDPR — our legitimate interests in conducting editorial work and responding to correspondence; Article 6(1)(b) GDPR where processing is necessary to take steps at an individual’s request before entering into a contract; Article 6(1)(c) GDPR where retention or disclosure is legally required Correspondence is ordinarily retained for 24 months after the matter closes. Material required to document an editorial decision, resolve a dispute, meet a legal obligation, or establish, exercise, or defend a legal claim may be retained for the applicable limitation period.
Editorial, genealogical, and archival records Names; titles and styles; dates and places associated with public or genealogical events; family relationships; jurisdictions, offices, and public roles; images; biographical information; source and citation information; and correspondence relating to accuracy or provenance Research, document, preserve, verify, correct, and publish material concerning dynastic, genealogical, heraldic, and institutional history Article 6(1)(f) GDPR — our legitimate interests and those of readers, researchers, and institutions in maintaining an accurate historical and genealogical reference work, subject to a documented necessity and balancing assessment. Applicable national rules implementing Article 85 GDPR concerning freedom of expression and information may also apply. For as long as the information remains relevant to the legitimate editorial or archival purpose, subject to accuracy review, correction, restriction, erasure, and applicable archiving or legal requirements
Cookie-consent and language preferences Consent choice, language preference, cookie identifiers, and related technical information Remember privacy choices, demonstrate consent where required, and provide the language selected by the visitor Article 6(1)(f) GDPR for strictly necessary preference and consent-management functions; Article 6(1)(a) GDPR for optional storage, access, or associated processing based on consent As stated in the cookie table below
Optional external services IP address, page URL, device and browser information, language choice, and service-interaction data, depending on the provider Provide optional translation, embedded content, analytics, or similar features actually enabled on the website Article 6(1)(a) GDPR — consent. Non-essential services remain disabled until consent is given. As described for each service and by the relevant provider

We do not use personal data for solely automated decisions that produce legal effects or similarly significant effects concerning individuals.

4. Editorial and archival information obtained from other sources

Neue Gotha is an editorial and historical reference project. Some information in the register may concern identifiable living individuals and may not have been collected directly from those individuals.

Depending on the record, information may be obtained from official gazettes and public registers; archives and libraries; published books and scholarly works; institutional publications; reputable news sources; publicly accessible websites; submissions from the individual concerned or their authorised representative; family representatives; and other documented sources.

The categories of information may include the categories listed under “Editorial, genealogical, and archival records” above. The material may be made available to website visitors and may be indexed by search engines. Neue Gotha seeks to use relevant, proportionate, and appropriately sourced information and to distinguish documented fact from uncertainty or editorial interpretation.

Individuals may contact the editorial office to request access, correction, contextualisation, restriction, or erasure. Requests are assessed under the GDPR and applicable national law, taking into account accuracy, source integrity, the public interest, freedom of expression and information, archival considerations, and the rights and freedoms of other people. No provision of this policy removes a right granted by applicable law.

Neue Gotha does not intentionally publish special-category personal data or information concerning criminal convictions about living individuals unless a specific lawful basis and any additional legal condition have been identified and documented.

5. Cookies and similar technologies

Cookies are small text files stored on, or read from, a visitor’s device. Similar technologies may perform comparable functions. Some are strictly necessary for a website or a service expressly requested by the visitor. Others, including many analytics, advertising, social-media, translation, or embedded-content technologies, require prior consent under applicable EU electronic-communications rules.

Neue Gotha does not place or access non-essential cookies, or activate non-essential external services, before valid consent has been given. Visitors may accept or reject optional purposes separately and may withdraw consent at any time by selecting the permanently available “Cookie settings” control. Withdrawing consent does not affect processing that was lawful before withdrawal. Strictly necessary technologies cannot be disabled through the consent tool, but they may be controlled through browser settings where technically possible.

The following table reflects the technologies currently deployed on the website. It is updated whenever a plugin, host, analytics tool, embedded service, or cookie configuration changes.

Name Provider Purpose Category Duration Third-party access
_scc_session Neue Gotha / managed hosting and site-control provider Maintains a short-lived session for website security and site-control functions Strictly necessary Browser session The contracted hosting or site-control provider may access the identifier when providing technical support
_tccl_visit Neue Gotha / managed website-analytics provider Distinguishes a single website visit and reduces duplicate counting within the same session Analytics — disabled until consent 30 minutes Yes; the contracted analytics provider processes the identifier on Neue Gotha’s behalf
_tccl_visitor Neue Gotha / managed website-analytics provider Assigns a pseudonymous visitor identifier used to produce aggregated website-usage statistics Analytics — disabled until consent 12 months Yes; the contracted analytics provider processes the identifier on Neue Gotha’s behalf
googtrans Neue Gotha / Google Translate Stores or applies the visitor’s language selection for the translation feature Functional — disabled until consent 12 months Google may receive technical and service-interaction data when Google Translate is activated
ng_gt_default_applied Neue Gotha / website translation plugin Records whether the website’s default translation setting has been applied Functional — disabled until consent 24 hours No direct vendor access is assumed; Google may receive data if activation causes Google Translate to load
eu_cookies_bar_consent Neue Gotha / locally hosted EU Cookies Bar plugin Stores the visitor’s cookie choices and prevents the banner from being shown unnecessarily Strictly necessary 6 months No, provided the consent plugin remains locally hosted and does not transmit consent records to its developer
wordpress_test_cookie Neue Gotha / WordPress Checks whether the browser supports cookies when an authorised user visits the sign-in page Strictly necessary Browser session No; the cookie is processed by Neue Gotha and its contracted host

Authorised editorial users may receive WordPress authentication, security, or preference cookies when they sign in. wordpress_logged_in_[hash] maintains an authenticated session for up to two weeks when “Remember Me” is selected; wordpress_sec_[hash] protects administrative access for the session; and wp-settings-[user_id] stores an editor’s interface preferences for up to one year. These internal cookies are processed solely for editorial access and site administration.

6. Google Translate, web fonts, and other external content

Where enabled with the visitor’s consent, Neue Gotha may use Google Translate to provide machine-generated translations. Activating the service may cause the visitor’s browser to connect to Google and disclose technical information such as the IP address, requested page URL, browser or device information, and language or service-interaction data. Machine translations may contain errors and do not replace the original editorial text.

Website fonts are hosted locally by Neue Gotha and do not require a connection to Google. Google Translate remains an optional external service that is activated only after the visitor provides consent.

Information about Google’s processing is available in the Google Privacy Policy and Google’s explanation of how it uses information from sites and applications that use its services.

Embedded material from another website may allow that provider to process personal data as if the visitor had visited the provider directly. Non-essential embeds remain blocked until consent is obtained. Each enabled provider is identified in this policy and in the consent interface.

7. Recipients of personal data

Personal data may be disclosed only where necessary to:

  • hosting, content-delivery, backup, website-maintenance, email, security, and consent-management providers acting under contract;
  • translation, analytics, media, or other external-service providers selected by the visitor through the consent interface;
  • professional advisers, insurers, auditors, or other specialists where necessary to protect legal or operational interests;
  • courts, regulators, law-enforcement bodies, or public authorities where disclosure is required or permitted by law; and
  • the public and search engines where personal data form part of a lawfully published editorial or archival record.

8. International data transfers

Some service providers may process personal data outside the European Economic Area. Where the GDPR restricts such a transfer, Neue Gotha relies on an applicable European Commission adequacy decision or appropriate safeguards under Article 46 GDPR, such as the European Commission’s Standard Contractual Clauses, together with supplementary measures where required.

Cloudflare and Google may transfer limited technical information to recipients in the United States. Where the recipient is validly certified, the transfer is based on the European Commission’s adequacy decision for the EU–US Data Privacy Framework. Where that mechanism is unavailable or does not cover a transfer, the relevant provider’s European Commission Standard Contractual Clauses and supplementary technical and organisational measures are used. Information about the applicable safeguards, including how to obtain a copy, may be requested from editor@neuegotha.de.

9. How long we retain personal data

We retain personal data only for as long as necessary for the purposes described in this policy, including security, editorial integrity, source verification, dispute resolution, and compliance with legal obligations. The specific periods or criteria are stated in the processing and cookie tables above.

When a retention period ends, information is deleted or anonymised unless continued retention is required by law, is necessary for legal claims, or is justified by a documented editorial or archival purpose. Encrypted rolling backups are retained for 35 days and are then overwritten automatically, unless a backup has been isolated for incident recovery or a legal hold.

10. Security

Neue Gotha uses appropriate technical and organisational measures designed to protect personal data against accidental or unlawful destruction, loss, alteration, unauthorised disclosure, or access. No method of internet transmission or electronic storage is completely secure, and absolute security cannot be guaranteed.

11. Your data-protection rights

Subject to the conditions and limitations in the GDPR and applicable national law, an individual may have the right to:

  • obtain confirmation as to whether personal data concerning them are processed and request access to those data;
  • request correction of inaccurate or incomplete personal data;
  • request erasure of personal data;
  • request restriction of processing;
  • object, on grounds relating to their particular situation, to processing based on legitimate interests;
  • receive personal data they provided in a structured, commonly used, machine-readable format and transmit those data to another controller where the right to portability applies;
  • withdraw consent at any time, without affecting the lawfulness of processing carried out before withdrawal; and
  • lodge a complaint with a competent data-protection supervisory authority.

To exercise a right, contact editor@neuegotha.de. Please identify the information or record concerned and the nature of the request. We may request information reasonably necessary to verify identity and protect personal data from unauthorised disclosure. Requests are normally answered within one month, subject to any extension permitted by law.

Where a request concerns published editorial or archival content, applicable rights may be limited where necessary and proportionate to reconcile data protection with freedom of expression and information or other rights recognised by law. Each request will be assessed individually.

12. Complaints

We encourage individuals to contact us first so that we can try to resolve a concern. Individuals also have the right to complain to the supervisory authority in the EU or EEA country of their habitual residence, place of work, or the place of the alleged infringement.

For this Berlin-based controller the supervisory authority is the Berliner Beauftragte für Datenschutz und Informationsfreiheit, Alt-Moabit 59–61, 10555 Berlin, Germany; telephone +49 30 13889-0; email mailbox@datenschutz-berlin.de; website https://www.datenschutz-berlin.de/.

13. Children

The website is intended as a general historical and reference resource and is not directed specifically at children. We do not knowingly request personal data directly from children for an online service requiring parental consent. If you believe a child has provided personal data inappropriately, please contact us.

14. Changes to this policy

We may update this policy when our processing activities, service providers, technologies, or legal obligations change. The current version will be published on this page with a revised “Last updated” date. Where required, we will provide additional notice or request renewed consent before introducing a new processing purpose.

Decline All
Save settings Accept All
Cookies settings