Hello is there anyway to prevent users copying the project forms from the Adroid Device directory?
Hi @Rusti,
I don't think if there is a built-in feature in ODK Collect to prevent users from accessing or copying forms directly from the Android device file directory. The forms are stored in a folder that users can access with a file manager. May be if you can try setting up device-level security measures like password protection or using apps that restrict access to certain folders, but I have not done it myself, just thinking out loud.
@Rusti It would be helpful to know more about the high-level problem you are trying to solve. For example, do you mistrust the people who are collecting data? Are you thinking about devices being lost? Are you worried about data that is being collected, sensitive data in a CSV attachment, something else?
In general, we recommend configuring devices to automatically lock with either biometrics or a passcode. We recommend using Android 10+ devices which encrypt all files with that device lock. That addresses concerns around device loss/theft but not about end users who are not trusted. You can find these recommendations and a few more in the documentation.
If the data you are collecting is highly sensitive, we recommend turning on the delete after send setting. Unsent data will still be potentially accessible but sent data will not.
Hello Thanks for the feedback.
The problem we are facing is that we have developed several forms for use in widescale data collection and long-term monitoring programmes across mutiple countries. We have found that these have now been pulled off tablets and shared and new independent servers have been setup which are collecting data on our forms. We are trying to prevent this happening going forward.
The one option is to use MDM software on the tablets which will stop this, this will work if we issue the tablets and control them, but sometimes we are working with partner organisations so we cannot enforce MDM softare on their devices.
File manager app has access to all device files but is forbidden to see "Android/data" folder since android 11 , if you are using an android application of odk collect ,the user will not have access to the Android Device Directory.
Hello Sandar,
Thanks for the feedback, I am still able to access the folder and files on Android 13 on my samsung if I grant permissions.
Has anyone needed this function or looked into this further?
Is there still no real interest or need from other people on this security aspect, is it not possible to write in a password rptect on the xml form to prevent opening if copied off a device, and build the passowrd protection into the ODK collect app?
Since the introduction of entities, I think this feature might come in handy for users using odk to develop highly powerful functional forms that might outcompete some ERP softwares in some niches.
With that said I believe the xml form might need to be protected as an intellectual property. Also the csv entities may need to be protected from access or malicious modification(as they might contain PII or passwords) even if using usb to access android odk folder on the laptop.
For me one particular case I wish this feature existed is when i was using xml form calculate question to generate a random number as a password to skip some group of questions. This was a time use repeat section of survey. It recorded the task performed during the last 24hrs. Some respondents find this sensitive or much involving and therefore aborted the interview.
I could also not let it optional as the Enumerators are like current flow in electricity, they would opt for an easy path to meet their daily targets 
.
So I wanted away to skip these group of questions by entering the immutable form instance specific random generated password. Using the hint generated from the form note i would compute the password and share with the enumerators to proceed with the interview without the time use section. So this acted as a valve to control the number of submissions with time use section missing.
However, some enemerators were cheeky and were able to view the form definitions.
So I concur with Rusti. This is a feature that its time is due.