You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue depends upon the resolution decided upon in #279.
While it is not required, I think it would be best practice and a darn fine thing to do to have a page in GitHub where we note the various services we use for InstructLab (e.g. Google Workspace tools and YouTube), chat service (whatever we decide upon), etc. and how these services may make use of our users data. For example, if we choose to remain on Slack free tier we would record Slack's use of user data including DMs for training AI models.
Given everything else we have to do, I cannot advocate for making this a top priority as we are all ostensibly responsible for reading a particular application's Terms of Service and understanding what we are agreeing to, but I still think that this work would be good and noble and demonstrate our demonstration to all and sundry that this project understands and respects user privacy and autonomy when it comes to personal data.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had activity within 90 days. It will be automatically closed if no further activity occurs within 30 days.
This issue depends upon the resolution decided upon in #279.
While it is not required, I think it would be best practice and a darn fine thing to do to have a page in GitHub where we note the various services we use for InstructLab (e.g. Google Workspace tools and YouTube), chat service (whatever we decide upon), etc. and how these services may make use of our users data. For example, if we choose to remain on Slack free tier we would record Slack's use of user data including DMs for training AI models.
Given everything else we have to do, I cannot advocate for making this a top priority as we are all ostensibly responsible for reading a particular application's Terms of Service and understanding what we are agreeing to, but I still think that this work would be good and noble and demonstrate our demonstration to all and sundry that this project understands and respects user privacy and autonomy when it comes to personal data.
The text was updated successfully, but these errors were encountered: