Skip to content

Privacy policy.

Last updated: 19 September 2026. Prototype draft.

1. Local first principle

The MCP server and document compilers run on your machine or your Docker host. Scanning a repository, drafting chapters, and compiling PDF or DOCX files does not send your code, manifest, or dissertation to UniReport. There is no UniReport account, no hosted datastore, and no telemetry in this prototype.

2. What leaves your machine

3. Website data

This prototype sets no cookies, runs no analytics, and stores no form input because there are no forms. Server access logs, if any are kept by your static host, are the host responsibility. Do not email student IDs, matriculation numbers, or full dissertations to request support unless asked through an official university channel.

4. Student and faculty documents

Faculty templates you inspect, briefs you ingest, and manifests you generate remain files on your disk under paths you choose, such as project_manifest.json or dist/final. Deleting those files removes the data. Committing them to git is your decision. Note that project_manifest.json is gitignored by default in this repo while dist artifacts vary, so check git status before pushing.

5. Security

Keep your repo private until submission, pin dependency versions, and run the MCP server from a trusted checkout. Report suspected vulnerabilities through the support channel listed on the pricing page rather than through a dissertation file.

6. Changes and contact

This policy will be revised if hosted features are added. The revision date above will change. Privacy questions can be raised through the support channel listed on the pricing page.