tugraz.at Privacy policy — 78/100 (Medium privacy risk)
Last analyzed
Technische Universität Graz (TU Graz) · tugraz.at
Report details
Medium privacy riskTU Graz handles your data lawfully with strong privacy controls, but some third-party tools and log data practices could be more privacy-friendly.
TU Graz's privacy policy is highly transparent and GDPR-compliant in many areas, particularly regarding user rights and consent mechanisms. However, gaps exist in data minimization (e.g., MAC addresses in logs), international transfer safeguards, and clarity on third-party data sharing. The use of US-based marketing tools, even with consent, introduces compliance risks under Schrems II.
Category Assessment
Breakdown of the policy across key compliance areas. Good = strong, fair = mixed, poor = concerning.
Log data includes MAC addresses, which may exceed necessity; analytics data is anonymized (e.g., IP truncation in Matomo).
Detailed breakdown of data categories, purposes, and legal bases, with clear references to GDPR and TKG 2021.
Extensive use of third-party marketing/analytics tools (Meta, Google, LinkedIn, Reddit) with consent, but transfers to US raise concerns.
Relies on Data Privacy Framework for US transfers but lacks explicit mention of SCCs or supplementary measures for non-DPF providers.
No evidence of user data being used for AI/model training; analytics are aggregated and anonymized.
All GDPR rights are explicitly described, with a dedicated form for requests and clear instructions for cookie consent withdrawal.
Key Findings
Notable clauses, issues, or positive practices discovered (critical first)
Ambiguity in International Transfer Safeguards
Third-party marketing tools (Meta Pixel, Google Ads, LinkedIn Insight Tag, Reddit Pixel) are used with user consent, but data may be transferred to the US. While the policy cites the Data Privacy Framework (DPF) for US transfers, it does not explicitly mention Standard Contractual Clauses (SCCs) or supplementary measures for non-DPF-certified providers, which could be a compliance gap under Schrems II.
Overbroad Log Data Retention
Log data (including IP and MAC addresses) is collected for system security and stored for up to 12 months, which is justified under Art. 6(1)(f) DSGVO (legitimate interest). However, MAC addresses are highly identifiable and their necessity for security logging is debatable under data minimization principles.
Unclear Necessity of Functional Cookies
The policy clearly states that functional cookies (e.g., session cookies) are exempt from consent under § 165 Abs. 3 TKG 2021, but it does not explicitly confirm whether these cookies are strictly necessary for the service, which is a GDPR requirement for consent exemption.
Potential Re-Identification Risk in Study Explorer
The Study Explorer tool uses functional cookies for basic functionality (e.g., storing anonymous user codes) and optional analytics cookies. The policy does not specify whether the anonymous user codes could be linked to other data, raising potential re-identification concerns.
Lack of Clarity on Payment Data Handling
The policy mentions that payment data is processed for electronic transactions (e.g., via PAYONE GmbH) but does not specify whether payment data is stored or shared with other third parties beyond the payment processor.
Consent-Dependent Social Media Integration
Social media plugins (e.g., X, YouTube) require explicit user consent before activation, and data is only transmitted upon user interaction (e.g., clicking 'Video aktivieren'). This is a privacy-friendly approach, but the policy does not clarify whether third-party cookies from these plugins are blocked by default.
Comprehensive User Rights Documentation
User rights (access, rectification, erasure, restriction, portability, objection) are explicitly listed, and a dedicated form is provided for exercising these rights. This is a strong compliance signal.
Consumer Takeaway
TU Graz processes personal data lawfully under GDPR, with strong transparency and user rights, but some third-party transfers and marketing practices require scrutiny.
Compliance Posture
GDPR-compliant with minor gaps
EU Transfers
Mixed: Data mostly processed in EU/EEA, but some third-party tools (e.g., Meta, Google, LinkedIn, Reddit) may transfer data to the US under Data Privacy Framework or SCCs.
Detected Signals
Specific data points and practices identified in the text
Evidence Snippets
Direct quotes from the policy supporting these findings
Wir verarbeiten Ihre Daten ausschließlich auf Grundlage der gesetzlichen Bestimmungen zum Datenschutz und zur Datensicherheit, insbesondere nach dem österreichischen Datenschutzgesetz („DSG“), der EU-Datenschutzgrundverordnung („DSGVO“), sowie nach dem Telekommunikationsgesetz („TKG 2021“).
Die Logdaten werden nicht mit anderen personenbezogenen Daten verknüpft.
Wir verwenden den Advanced Consent Mode. Ohne Ihre Zustimmung werden keine Cookies gesetzt.
Die Übermittlung dieser Daten in die USA erfolgt auf Grundlage eines Angemessenheitsbeschlusses (Art 45 DSGVO) an Unternehmen, die nach dem Data Privacy Framework zertifiziert sind.
Sie haben das Recht auf Auskunft, Berichtigung und Löschung Ihrer Daten. Zusätzlich haben Sie das Recht auf Einschränkung sowie das Recht auf Datenübertragbarkeit der von Ihnen bereitgestellten Daten.
Missing or Unclear
- Explicit confirmation that functional cookies are strictly necessary (GDPR requirement for consent exemption).
- Details on supplementary measures (e.g., encryption, pseudonymization) for international transfers to non-DPF-certified providers.
- Clarification on whether MAC addresses in log data are hashed or otherwise pseudonymized.
- Information on whether payment data is retained by TU Graz or only processed by PAYONE GmbH.
- Explicit statement on whether Study Explorer's anonymous user codes are truly unlinkable to other data.
Questions to Ask
- Are MAC addresses in log data hashed or pseudonymized to comply with data minimization principles?
- What supplementary measures (e.g., SCCs, encryption) are in place for international transfers to non-DPF-certified third parties?
- Are functional cookies strictly necessary for the service, and if so, how is this documented?
- Is payment data retained by TU Graz after transaction processing, and if so, for how long?
- Can Study Explorer's anonymous user codes be linked to other data, and if so, under what circumstances?
- Are third-party cookies from social media plugins blocked by default until consent is given?
Share this analysis
Anyone with this link can view the result above.
Built by DentroChat
100% European AI chat for everyone
Chat with AI, work with files, generate images, and search the web. Data stays in Europe.
Other analysed privacy policies
View allsykik.ai
78/100
Medium privacy riskSykik offers EU-hosted AI agents with strong data localization and GDPR-aligned practices, but lacks explicit details on data minimization, AI training opt-outs, and third-party sharing controls.
View report →europealternatives.com
78/100
Low privacy riskEurope Alternatives is a privacy-friendly directory that collects almost no personal data, but clicking partner links can send your data to third parties—including potentially outside the EU—with no clear safeguards described.
View report →langdock.com
78/100
Low privacy riskLangdock is a privacy-conscious EU-based AI platform that explicitly bans using your content to train AI models and keeps data in the EU, though it relies on some US sub-processors and has vague retention periods in places.
View report →berlin.de
80/100
Low privacy riskThe Berlin Senate Chancellery's privacy policy is generally strong, using two-click consent for third-party media and anonymizing IPs, though it relies on standard contractual clauses for some sub-processors outside the EEA and lacks clarity on AI training.
View report →