Document and publish opt out guidance

[jeffabailey]

Per the following support correspondence.

We need to document the opt out guidance and make it public for the ISC.

• Determine the best place to publish the guidance.
• Distill the information below into an easy-to-read document.
• Publish the guidance.
• Share the guidance with the ISC community, maybe a community call?

---

Jeff Bailey reported 14 days ago This ticket has been Closed
Is it possible to filter out information about certain users?

https://innersource.biterg.io/

e.g.

1. Remove an Author by request.
2. When a Slack connector is added, remove a user.
3. Basically, zap all PII for a user across all datasets collected.

Why?

To give people an option to not have their behavior analyzed if that is their preference.
S
Support Bitergia said 12 days ago

Cc: [email protected]
You can answer this ticket by replying to this email or going to this link: https://support.bitergia.com/helpdesk/tickets/1433

Hi Jeff,

You can apply certain actions in SortingHat to blurr their activity:

• Rename them in their main name field, which is used in most dashboards. Some fields will still hold their original upstream identifications, but are less used for dashboards.
• Remove manually added affiliations, if any.
• If we are not interested in analyzing bot activity, disguise them as bots by renaming them as bots, marking them as bots, and/or merging their identities with bots.
  Once edited, it will affect both dynamic data and the data loaded thereafter. You need to ask us to update the previously existing data too.

We can also manually execute some database queries to disguise their upstream identifications too.
Or to totally remove their data. But this would affect the metrics, which wouldn't match the numbers shown upstream.

Currently, we don't have an automated way to keep them out. If they keep using their identities in the original services (Github, Slack, etc), their new activity will be loaded.
They should either use pseudonymous accounts in the original services or ask these services to not provide their activity on their APIs (opt out upstream).

It also is possible to pseudonymize fields. This will affect targeted groups of dashboard users and apply to all contributors. But that's a different use case.