Terms of Use & Privacy Statement in CHT Applications

Product
1

This question came via an email and I will post it here in case anyone from the community has tried this before and/or has suggestions about this feature:

What would be a good way to present the Terms of Use and privacy statement (combined into a 9 page long document!) within a CHT app?

This information should be presented to the users upon first log in. They should either be able to tick a box confirming they read and accept, or by moving past the information, they implicitly agree to them.

Did anyone implement this functionality before? Any suggestions on how to add this feature to the CHT?

2

I would recommend implementing this as training cards! Training cards will be automatically displayed in the app for any configured user who has not completed the training (and will stop prompting the user to complete the “training” once they finished). The contents can be structured, dynamic, and interactive similar to other normal forms. It is also possible to audit which users have completed the “training” because once a user finishes their training cards a report is submitted and recorded in the database.

1 Like
3

Indeed - I think @jkuester’s suggestion of training cards is likely the best solution.

I did want to note that training cards were released in 4.2.0. A work around for deployments using an earlier version of the CHT might be adding a “Terms of Use” workflow and then create a task for anyone that hasn’t completed this workflow. While the UX won’t be quite as nice as the training card option, you’ll get the same granularity of reporting which end users have or have not completed this form.

2 Likes
4

The CHT Privacy Policy Guide the best way to implement a privacy policy. After it is configured, a user must click “Accept” before they can use the app.

1 Like
5

Thank you all for your input, this is super helpful! :star_struck:

@Lorena_Rodriguez, do you know if there an option to “enforce” the acceptance/rejection of the privacy policies feature upon first login?

6

@andra if I understand correctly this is part of the feature:

The app will load normally after acceptance. The user cannot opt out or skip acceptance, meaning, if a privacy policy is configured, the app will be unusable until the user has accepted it. Once accepted, users will not be prompted to accept the same policy again. However, users will be prompted for acceptance again when the policy is updated or when they change their language.

7

I can verify how this works when users are logged in before the privacy policy is established.

8

Thank you @Lorena_Rodriguez! I believe @Kenyuri and his team could look into these options and let us know if any matches their needs, before we do extra testing.

@Kenyuri please let us know if you need extra information or support.

2 Likes