Open ja-fra opened 2 months ago
Thanks @ja-fra for clarification.
Would it be possible to add a web hosting service using the Docker Compose configuration to host the static HTML files for "Terms of Service" and "Privacy Policy" and specify URL(s) like more-health.at/PrivacyPolicy to have access to the coresponding files, and then use this URL(s) in the mobile app as an embedded value?
The following content represents a draft version of Privacy policy and Terms and conditions at 3 levels of the app. The first part would be the gernaral level.
Description
On startup, we want to have the possibility to show additional info-screens about "Terms of Service" and "Privacy Policy" to the user. We distinguish between two levels of such info-screens: (a) General (generic) T&S for the MORE App as it comes from the App Stores, and (b) the T&S of the Institution running a study.
While for (a) the source of the T&S need to be defined during the release process, in (b) the source can be configured in the study manager.
The following chart shows a possible workflow for such additional screens (new screens highlighted):
Notes:
Study Enrollment
is the screen where the user enters the "registration token" (and could change the endpoint-url)Study Consent
is the already existing consent-screen where the user is presented the general information and consent on the study (and individual observations).New Screens:
MORE T&S [a]
: These are the general/generic "Terms of Service" / "Privacy Policy" of the app. The content (source or link) is embedded into the App on build- or release-time and cannot be configured per instance of the backend. All users will be shown the same information.Institutional T&S [b]
: This content is loaded from the backend. It is intended for general "Terms of Service" / "Privacy Policy" of the institution running the instance of the MORE Platform. Study-specific T&S should be added to the existing "Study Consent"-screen.Additional Hints
Split from #246