What happens to data when you remove a user's access to your FlightLogger account?

First of all, your organization's data is just as safe in FlightLogger as it has always been. In case you're wondering what happens when you remove a user's access to your account, here's some explanation.

When a user is blocked on your account

In this case the user will no longer have access to your organization's FlightLogger account via my|FlightLogger. The user's my|FlightLogger account will still hold all flight records that were logged at the time the blocking was blocked, but there will be no further synchronization of data in neither direction.

This means that any manual logbook entries made on the user's my|FlightLogger account will no longer be synchronized. Any API tokens set up towards your organization's FlightLogger account will no longer work.

When a user is GDPR neutralized

When a user is GDPR neutralized on your account, the user is automatically also blocked. So the result is the same as when blocking a user (see above).

When a user is deleted

In order to delete a user within FlightLogger, one of the requirements is that there is nothing logged on the user. Therefore, the user's my|FlightLogger account will not hold any data from your organization's FlightLogger account. 

Of course, the user will not have access to your organization's FlightLogger account via my|FlightLogger, and API keys will not work either.