Registro de cambios

EPFL – École polytechnique fédérale de Lausanne

Source-backed change history with no release-to-release policy diff rows recorded yet; current claims, official sources, review state, and freshness remain visible across 0 public release records.

Resumen de cambios

Estado actual de actualización y revisión del registro público.

EPFL – École polytechnique fédérale de Lausanne currently has 5 source-backed claim records and 6 official source attributions. Latest tracked changed date: 10 may 2026. No tracker diff rows are recorded in the latest public release.

Esta página combina todas las diferencias de versiones públicas para EPFL – École polytechnique fédérale de Lausanne. Las instantáneas individuales de lanzamiento siguen disponibles desde sus URL específicas del lanzamiento.

Aún no se han registrado filas de diferencias de políticas entre versiones para esta universidad. La página sigue rastreando afirmaciones respaldadas por fuentes actuales, atribuciones de fuentes oficiales, estado de revisión, actualidad de las fuentes y JSON públicas para su descubrimiento y citación.

This tracker is not legal advice, not academic integrity advice, and not an official university statement unless a linked source is the university's own official page.

Las afirmaciones extraídas recientemente son adiciones al seguimiento y no necesariamente han sido publicadas por la universidad. Los cambios en las instantáneas de origen muestran cambios de hash para la misma URL de origen y no constituyen por sí mismos cambios en la política.

Categorías de diferencias

Clasificación semántica para esta diferencia de versión.

Texto de la política0Extraído recientemente0Evidencia0Instantáneas de origen0Texto de origen0Fuente añadida0Fuente eliminada0

Diferencias de versión combinadas

Diferencia del seguimiento unificado generada a partir de todas las instantáneas de lanzamiento público para esta universidad.

EPFL – École polytechnique fédérale de Lausanne combined release diferencias

Initial tracked release. Lines represent public claim/evidence records entering the release snapshot.

+10-0
11 # EPFL – École polytechnique fédérale de Lausanne AI policy record
2+privacy: EPFL advises students not to input confidential, private or personal information into generative AI tools. When using generative AI tools, students are sharing data with private companies and lose control over it.
3+Evidence (en, 5eeaf435b051): Never input confidential, private or personal information about yourself or others into these tools. Always reflect first on the nature of the information you are using, because once you enter it into one of these tools, it’s no longer confidential.
4+academic_integrity: EPFL requires students to disclose the use of AI tools in assessment work. EPFL rules (Lex 1.3.3, Article 4) require that all assessment material that is not the student's personal and original contribution must be recognizable as such.
5+Evidence (en, 87edcd847e7d): EPFL rules (Lex 1.3.3, Article 4) require that all assessment material that is not the student’s personal and original contribution must be recognizable as such. Therefore, the use of AI tools should be disclosed in a statement.
6+teaching: EPFL recommends that teachers make explicit to students what AI use is not legitimate in a course and what rules accompany AI tool use.
7+Evidence (en, fba7ab5ff6ba): Since there is no ‘one-size-fits-all’ rule regarding the use of AI in assessment, it is recommended that teachers make explicit to students what kind of use is not legitimate in their course, and what rules accompany the use of AI tools.
8+academic_integrity: EPFL considers the use of AI-generated content in assignments without proper attribution as AI plagiarism. Tools that detect AI-generated content are not admissible as stand-alone evidence of AI plagiarism due to high risk of false positives.
9+Evidence (en, 2760bf9bac8e): The use of AI-generated content in assignments without proper attribution is considered AI plagiarism. Tools that specifically aim to detect whether content was AI-generated (e.g., turnitin ) are not admissible as stand-alone evidence of AI plagiarism due to their high risk of false positives
10+privacy: EPFL guidance says enterprise licenses such as Microsoft 365 Copilot via EPFL account are currently not a secure solution for processing regulated data because EPFL has not signed a data processing agreement guaranteeing aligned data protection measures.
11+Evidence (en, 2760bf9bac8e): However, enterprise licenses such as Microsoft 365 Copilot via your EPFL account are currently not a secure solution for processing regulated data, because no data processing agreement has been signed by EPFL that would guarantee that data protection measures align with institutional needs or with Swiss legislation on personal data protection.

Historial de versiones

0 public release diffs

Cambios en las afirmaciones

5 Afirmación registros

privacy

EPFL advises students not to input confidential, private or personal information into generative AI tools. When using generative AI tools, students are sharing data with private companies and lose control over it.

Revisión: Revisado por un agenteConfianza96%Evidencia1Idiomasen

academic_integrity

EPFL requires students to disclose the use of AI tools in assessment work. EPFL rules (Lex 1.3.3, Article 4) require that all assessment material that is not the student's personal and original contribution must be recognizable as such.

Revisión: Revisado por un agenteConfianza95%Evidencia1Idiomasen

teaching

EPFL recommends that teachers make explicit to students what AI use is not legitimate in a course and what rules accompany AI tool use.

Revisión: Revisado por un agenteConfianza94%Evidencia1Idiomasen

academic_integrity

EPFL considers the use of AI-generated content in assignments without proper attribution as AI plagiarism. Tools that detect AI-generated content are not admissible as stand-alone evidence of AI plagiarism due to high risk of false positives.

Revisión: Revisado por un agenteConfianza93%Evidencia1Idiomasen

privacy

EPFL guidance says enterprise licenses such as Microsoft 365 Copilot via EPFL account are currently not a secure solution for processing regulated data because EPFL has not signed a data processing agreement guaranteeing aligned data protection measures.

Revisión: Revisado por un agenteConfianza92%Evidencia1Idiomasen

Instantáneas de origen

6 source attributions