myFenix.app

myFenix.app is a mobile app to access and with Fenix Academic Management System instances that are deployed in some portuguese universities/faculties.

The Android app beta version was released in November 2018 and the iOS beta version was released in February 2019. After both versions become widely used, the release cycle of new versions will become more regular.

Privacy Policy

All the data presented and used is the data already existing in the university/faculty Fenix information system (being displayed to the users that are already authorized to access it, through GDPR authorization or through legally employee/supplier/contractor defined work relations).

Ownership

myFenix.app is an initiative by Quorum Born IT, Lda, associated with its FenixEdu-based solutions and the universities and faculties that have subscribed this optional app module (as an add-on to the Fenix web-based solution they already use).

Quorum Born IT, Lda has responsibility around the mobile apps, with the responsibility around each FenixEdu-based deployment belonging to the university/faculty operating it.

With the exception of user-inserted data, the remaining data accessed through the app already exists in the correspondent Fenix-based web solution.

Roadmap

In the future, a full website will be available around the myFenix.app initiative. Until then, any questions or inquiries can be sent to hello@myfenix.app or roadmap@myfenix.app.

FAQ

1. Who can use the app ?

The myFenix.app mobile apps can be used by any user that can access the Fenix solution of any of the participating institutions.

2. Which login/password should be used to access the app ?

The login/password to be used are the same as for the Fenix solution of the corresponding institution.

3. What are the available modules in the app ?

The full-version of the app will be comprised of the following modules: Sync (Data), Profile, Announcements, Curriculum, Timetable, Evaluations, Academic Requests, Payments, Quality, Calendar, Degrees, Campus.

4. What information is presented in the app ?

Currently, all the information that is available to the myFenix.app mobile apps is obtained from the correspondent Fenix solution. The exception is user-inserted data around classes (students evaluating the class they attended).

5. Which entities are responsible for the presented information ?

All the information in the Fenix solution is created and maintained, depending on the scope, by its own users, the (academic/financial) services of the institution or from state/central entities (like DGES).

6. What are the mobile devices where the app can be used?

The myFenix.app mobile apps can be used in any Android (v4.x or higher) or iOS (v10.x or higher) device.

7. The app needs network access to run ?

The myFenix.app mobile apps can be used with or without network access, but there are a few operations that always require network, specifically: the login operation, the data synchronization operations and the QR-code based class presence registry functionality.

8. How can I help and give suggestions ?

Ideas and suggestion can be sent to the email address roadmap@myfenix.app.

9. How can I get additional information about the myFenix.app initiative ?

You can contact us through the email address hello@myfenix.app.

Data Collection

The myFenix.app mobile apps do not track, collect or aggregate business/personal data of any kind that could be accessed from its usage.

In the features that take advantage of the mobile device camera, specifically QR-Code reading features, there is no collection or processing of the image obtained, only the runtime interpretation/processing of the code itself.

In the future, mechanisms to aggregate data around which features/screens of the app are the most accessed will exist; the aggregated data will be around the identifier of the feature/screen themselves, and not any data existing in the corresponding fields presented on-screen or processed off-screen.

The myFenix.app mobile apps have inbuilt a technical-error submission mechanism that might collect and submit technical data (if the user accepts its submission). No business or personal data is submitted through this mechanism, only technical information like the source-code files associated with the error or runtime exceptions/errors descriptions.

App Permissions

The myFenix.app mobile apps require a set of runtime permissions to be allowed so the app mechanisms may function properly.

Android . android.permission.CAMERA

The use of the camera is needed to process QR-codes (related with Assiduity mechanisms), used in multi-device interactions (one device generates QR-codes for other devices to process). No other image with the exception of the QR-Code is process, and the camera is not active besides the QR-Code reading screen.

Android . android.permission.READ_PHONE_STATE

The only feature that requires this permission in the app is the obtaining of a device unique internal identifier. This device identifier is then used for the proper functioning of data synchronization protocols and notification mechanisms.

Android . android.permission.WRITE_EXTERNAL_STORAGE

This permission is needed for the app install on an external storage folder (usually an sd card). No other mechanism around the device file system (since the app install/runtime files don't need the permission to execute). There is also no reading or navigation of contents around the file system used.

iOS . NSCameraUsageDescription

The use of the camera is needed to process QR-codes (related with Assiduity mechanisms), used in multi-device interactions (one device generates QR-codes for other devices to process). No other image with the exception of the QR-Code is process, and the camera is not active besides the QR-Code reading screen.

iOS . NSCalendarsUsageDescription

The app uses a UI component that can integrate and synchronize data with the device's calendar (currently, no integration is done, with the data being presented only in the calendar component within the app itself).

iOS . NSPhotoLibraryUsageDescription

There is no access to the photo library, but the permission is needed (since iOS SDK 10) due to the use of the camera to read QR-Codes. The image that is obtained to process the QR-code is not even persisted, being treated only in memory/runtime, so we hope to find a way to not need this permission in the near future.