Privacy
This notice describes the current Space demonstration. The controller, contact details, hosting arrangements and legal bases still need to be confirmed. It is not yet a complete privacy notice.
Last reviewed: 1 October 2026
Who is responsible?
The name, address, country and contact email of the person or organisation responsible for this project have not yet been provided. These details will also appear in the imprint. MCI is not identified as the operator or controller of this student project merely because its buildings and programmes appear here.
Using the demonstration
Space is a student project for exploring buildings, rooms and teaching administration. The demonstration includes student study-room reservations.
For student access, you provide a display name or nickname. A real name or email address is not required. The app creates a separate temporary account with a random identifier, student role, organisation and expiry time. Without a display name, student access cannot be created. Please avoid entering sensitive information or someone else’s personal data.
Office and lecturer access use presentation accounts protected by a password. The server checks the password and assigns the corresponding role. A successful login creates a session so you do not have to enter the password again on each page.
Delivery and protection against misuse
Your IP address and technical request information are processed when your browser connects to the server. The exact contents and retention of hosting, web-server and system logs still need to be confirmed; this notice does not claim that IP addresses are never stored.
To limit automated or excessive login attempts, the application stores a keyed hash derived from the caller address, the selected role, an attempt count and a time window. This table does not contain the plain IP address. This protection is not behavioural advertising or a personal risk score.
Administrative data and uploaded files
Authorised Office accounts manage rooms, floor plans, study programmes and teaching records. If personal data is entered, it may include account names or email addresses, group memberships, lecturer assignments and event participation. Access is restricted by role and organisation. Administrative changes may retain account references and timestamps in history records.
The currently imported programme catalogue contains public study-programme information, not real student lists or timetables. Uploaded PDFs, images and plan revisions are stored on the application server. Office users should only upload content needed for the project and permitted for this purpose. The application does not send notification emails.
Study reservations and notifications
Reservations store an account and organisation reference, room, start and end time, number of people, status, check-in deadline and check-in time. Cancellations may retain a reason. Office can view and cancel reservations within its organisation; students can manage their own reservations. In-app notifications retain recipient, reservation, event type, creation time and read time. No notification email is sent.
Expired or cancelled reservations generally remain in booking history. For temporary presentation guests without group or event links, automated cleanup deletes the guest account, its reservations (including future reservations), related notifications and sessions from the active database one hour after logout or guest access expiry. Teaching-linked guest records and their bookings are retained by automatic maintenance. Office may explicitly confirm removal of ended guest accounts, their bookings and guest assignments; the events, groups and courses themselves remain. A private recovery snapshot of explicit cleanup remains for seven days before maintenance deletes it. Logging out ends access; a new guest login cannot recover earlier bookings.
How long data remains
Temporary guest access and app sessions expire after eight hours. This ends access; it does not guarantee deletion of every related database record at that moment.
On logout, the guest display name is replaced by “Former guest” and access is disabled. Expired guest names are also retired at subsequent logins and by background maintenance. Unlinked temporary presentation guests are deleted from the active database one hour after logout or their scheduled eight-hour expiry, including their bookings, related notifications and sessions. The worker checks every 30 seconds in bounded batches; downtime or a backlog can delay cleanup. Automatic maintenance preserves guest identities linked to groups or events and their bookings; explicit Office cleanup is described above. Replacing a name is not a guarantee of complete anonymisation.
Login-limiting entries older than 24 hours are removed during a later login. Apart from this narrow temporary-guest cleanup, expired sessions, permanent presentation accounts, teaching-linked guest records, administrative records, uploaded files and their history have no verified general deletion deadline yet. Retention of other backups and infrastructure logs is also awaiting confirmation. A fixed deletion and backup schedule remains to be defined by the operator.
Hosting, recipients and external content
People authorised to operate the app and server can access data as necessary for administration and maintenance. Their roles, the hosting provider, server country, service-provider arrangements and any access from outside the European Economic Area must still be confirmed. No assertion is made that all processing stays within the EEA.
The app serves its fonts, building photos, floor plans and PDF viewer locally. The reviewed application code contains no advertising or analytics tracker. Links to source websites open those services only when you follow them; those websites have their own privacy information. Any additional processing by the hosting infrastructure remains to be checked.
Purposes and legal bases — confirmation pending
The identified purposes are providing the requested demonstration, keeping login and preferences working, protecting the service against misuse and supporting authorised administration. The controller must assign and document the applicable legal basis for each purpose before this notice can be finalised.
For example, reliance on a legitimate interest requires identifying that interest and balancing it against visitors’ rights. This draft does not assume that consent, a contract or a public task automatically covers all processing.
Your rights
Subject to the conditions in the GDPR, you can request access, correction, deletion, restriction and data portability, and object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it for the future. Requests should go to the controller; the contact address is still missing.
You can lodge a complaint with a supervisory authority, particularly in the EU country of your habitual residence, workplace or the alleged infringement. In Austria this is the Austrian Data Protection Authority. Space does not currently make solely automated decisions with legal or similarly significant effects on you.