Data retention policy
- Workspace admins can delete their Actioner workspace. In this case, all data that is stored by Actioner within the scope of the deleted workspace will be deleted by Actioner. This cleanup process is automated and may take up to 72 hours. Similarly, the data produced by Actioner for analytics purposes is anonymized in the same time interval.
- Whenever a workspace admin removes the access of a user to a workspace, all data that is stored by Actioner within the scope of the removed user for the particular workspace will be deleted by Actioner. This cleanup process is automated and may take up to 24 hours. Similarly, the data produced by Actioner for analytics purposes is anonymized in the same time interval.
- Whenever a user initiates the right to be forgotten (i.e. user account is deleted), all data that is stored by Actioner within the scope of the deleted user, for all workspaces that the user has access to, will be deleted by Actioner. This cleanup process is automated and may take up to 72 hours. Similarly, the data produced by Actioner for analytics purposes is anonymized in the same time interval.
Please see below for more information:
- https://www.actioner.com/security#data-lifecycle-and-gdpr Data archiving and removal policy
- We operate a comprehensive backup program at Actioner. This includes our internal systems, where our backup measures are designed in line with system recovery requirements.
- Our data backups are retained for 30 days with support for point-in-time recovery and are encrypted using AES-256 encryption
Please see below for more information:
- https://www.actioner.com/security#cloud-infrastructure Data center location(s)
United States
Data hosting details
Actioner is a cloud-native product whose infrastructure is hosted on industry-leading cloud provider Amazon Web Services (AWS). Actioner cloud services and data are hosted on Amazon Web Services (AWS). Where all our computing, messaging, network, and storage layers are located in the US West, our browser application is distributed via our CDN network all over the world.
As a design standard, all Actioner services as well as the upstream computing, messaging, network and storage services are running on multiple availability zones (AZs) so that the traffic and the data are distributed among them. This design allows us to tolerate zone-specific failures with no downtime. This multi-zone high availability is the first line of defense for geographic and environmental risks and means that services running in multi-AZ deployments should be able to withstand AZ failure.
App/service has sub-processors
yes
Guidelines for sub-processors