Optional persistence of activities

[lennartblom]

Is there any way to setup the sync process, that your application does not store any data inside the mongo db?

One of my running club mates is complaining about data privacy aspect, that he did not approve my attempt to sync the club activities and would like to be excluded from the channel where the activities are synchronized.

Is there any way your application can skip specific users or is just acting as a "relay" of the activity data? So the stuff is not stored anywhere except the slack channel?

[dblock]

This is a very valid feature request, there's really no reason for the bot to store all the identifiable information other than for stats, so something that I support. Open to suggestions of what that looks like. A retention policy where older activities are deleted could definitely be a start (https://github.com/dblock/slack-strava/issues/107).

For clubs, the issue is that the club activity does not say what user it belongs to (for privacy reasons), so I don't see a way to give someone a way to exclude themselves from the sync.

[dblock]

Implementing complete passthrough would be doable, but there are a few places where this is tricky/requires work. First we don't notify in the synchronous path of a Strava event. Second some information needs to be stored to update recent posts following edits.

[lennartblom]

Thanks Daniel for reaching out so nicely! Unfortunately I stopped syncing our club activities because I feel uncomfortable if one member is concerned regarding the data stuff. Otherwise I would have picked up my credit card 💳 to subscribe for one year.

But I guess there's always one in the group how has concerns. Too bad! I like your implementation and see your technical reasons to not be able to provide my desired software routine. What a pity. 😞

[dblock]

In https://github.com/dblock/slack-strava/commit/ebfb98bbcd4d0baafcb9918b5190e1c93cb70409 I've capped data storage to 30 days.