it helps some times I can address the specific concerns you have listed: While you may be able to see other user's files, it's because they haven't changed the permissions on their files. You can use standard linux file permissions to keep other users from reading or writing your files.
chmod 600 file
mod_wsgi, django, apache: failed to load "mod_wsgi.so" module in httpd.conf
To fix the issue you can do Your copy of mod_wsgi is compiled against a different version of python than what you have. Looks like it's looking for python version 2.5. If you run python -V on your system, see what version(s) you have installed and try to find a mod_wsgi built against that version (python will output something like 2.7.3, which would be python 2.7). It's either that or your copy of libpython2.5.so isn't in apache's library path. you could try and symlink it to one of the lib directories in apache's library path, or you can add the directory where your libpython2.5.so resides and add that to apache's library path. This serverfault question has a few answers that might help you set that up.
Django JWT Authentication behavior different between local & mod_wsgi servers with Django REST framework
it helps some times Well, I would have never thought the official release of Django (2.1) would be the issue, but here we are! When creating my new virtual env under python 3.7, I did not pay attention immediately to the new version of django. Even afterward, I supposed it was a stable release and that's it. So maybe something's wrong on my Ubuntu install (but really I can not see what), but downgrading from django 2.1 to django 2.0 just solved my issue! Happy even if I spent waaay too much time on that. Notice that it works just fine with Python 3.7 (just like my initial wish). for reading!