I have developed an online app using Streamlit, which functions effectively and meets my requirements. The app is a simple tool for uploading datasets and performing data cleaning. I am now inquiring about the data protection measures in place.
Could you please clarify whether the dataset I uploaded is shared with any third party? I am particularly interested in understanding how data protection is implemented. Is the data hosted locally on my device, or is the dataset stored elsewhere with the code executed remotely? I am concerned about the security of the data in my files and want to ensure that it remains inaccessible and confidential. Could you guide this matter?
When Streamlit is described as SOC 2 Type 1 compliant, focusing on security and confidentiality, it means they have been audited and found to have appropriate systems in place to ensure the security of the system (protecting against unauthorized access) and the confidentiality of the information processed by the system (ensuring that sensitive data is accessed only by authorized individuals) at a specific point in time.
Streamlit has a sever-client structure. The server executes the Python code and the client is a browser, typically on a different computer from the server.
When you deploy an app on Community Cloud, for example, all the files in your GitHub repository are copied into a container that executes the Python code of your app. If your app saves any files to disk, they would be saved into this container (server).
When you use something like st.file_uploader, the data is sent from the client to the server and held in memory. It doesn’t result in a saved file on disk unless you explicitly perform an operation to create and save the data to a file. (And even if you did, rebooting the app would delete it.)
Thanks for stopping by! We use cookies to help us understand how you interact with our website.
By clicking “Accept all”, you consent to our use of cookies. For more information, please see our privacy policy.
Cookie settings
Strictly necessary cookies
These cookies are necessary for the website to function and cannot be switched off. They are usually only set in response to actions made by you which amount to a request for services, such as setting your privacy preferences, logging in or filling in forms.
Performance cookies
These cookies allow us to count visits and traffic sources so we can measure and improve the performance of our site. They help us understand how visitors move around the site and which pages are most frequently visited.
Functional cookies
These cookies are used to record your choices and settings, maintain your preferences over time and recognize you when you return to our website. These cookies help us to personalize our content for you and remember your preferences.
Targeting cookies
These cookies may be deployed to our site by our advertising partners to build a profile of your interest and provide you with content that is relevant to you, including showing you relevant ads on other websites.