We now store access logs for the puspose of avoiding/solving abuse.
I feel it is necessary to edit the privacy section to reflect our recent practices.
We now store access logs for the puspose of avoiding/solving abuse.
I feel it is necessary to edit the privacy section to reflect our recent practices.
While we are at this should we also perhaps mention something along the lines of not intending to pass any data to law enforcement?
well this largely depends on availability of the logs, which:
you should provide if they ask
those that we are storing are only simple access logs and I don't really consider this service to be sensitive
we are not readily handing anything to anybody without a proper warrant, though
> While we are at this should we also perhaps mention something along the lines of not intending to pass any data to law enforcement?
well this largely depends on availability of the logs, which:
1. you *should* provide if they ask
2. those that we are storing are only simple access logs and I don't really consider this service to be sensitive
we are not readily handing anything to anybody without a proper warrant, though
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
dalahast
We now store access logs for the puspose of avoiding/solving abuse.
I feel it is necessary to edit the privacy section to reflect our recent practices.
While we are at this should we also perhaps mention something along the lines of not intending to pass any data to law enforcement?
well this largely depends on availability of the logs, which:
we are not readily handing anything to anybody without a proper warrant, though
Fair enough, the section can always be updated later should the need arise.
looks good
cheers @dalahast