Skip to main content
All CollectionsOther
Security Policy
Security Policy

Technical measures to prevent unauthorised access, use, alteration or disclosure of customer data.

Daniels Korens avatar
Written by Daniels Korens
Updated over a week ago


At Sage HR we take the protection of customer data extremely seriously. This Sage HR Security Policy describes the organisational and technical measures Sage HR implements platform wide designed to prevent unauthorised access, use, alteration or disclosure of customer data.

The Sage HR services operate on Amazon Web Services (AWS); this policy describes activities of Sage HR within its instance on AWS unless otherwise specified. As you continue to learn more about Sage HR we recommend you also review our Terms & Conditions and Privacy Policy.

Best Practices

Incident Response Plan

  • We have implemented a formal procedure for security events and have educated all our staff on our policies.

  • When security events are detected they are escalated to our emergency alias, employees are notified and assembled to rapidly address the event.

  • After a security event is fixed we write up a post-mortem analysis.

  • The analysis is reviewed in person, distributed across the company and includes action items that will make the detection and prevention of a similar event easier in the future.

  • Sage HR will promptly notify you in writing upon verification of a security breach of the Sage HR services that affects your data. Notification will describe the breach and the status of Sage HR’s investigation.

Build Process Automation

  • We have functioning, frequently used automation in place so that we can safely and reliably rollout changes to our application within minutes.

  • We typically deploy code to production once per week and have high confidence that we can get a security fix out quickly when required.


  • All of our services run in the cloud. Sage HR does not run our own routers, load balancers, DNS servers, or physical servers.

  • All of our services and data are hosted in AWS facilities in Ireland and protected by AWS security, as described at

  • Amazon does not disclose the exact location of its data centres. As such, Sage HR builds on the physical security and environmental controls provided by AWS. See for details of AWS security infrastructure.

  • Sage HR uses a backup solution for datastores that contain customer data. Created snapshots are encrypted by multi-factor Server-Side Encryption with Amazon S3-managed keys (SSE-S3) at rest.


  • All customer data are stored in the European Union (EU).

  • Customer data is stored in multi-tenant datastores; we do not have individual datastores for each customer. However, strict privacy controls exist in our application code that are designed to ensure data privacy and to prevent one customer from accessing another customer’s data (i.e., logical separation). We have many behaviour and integration tests in place to ensure these privacy controls work as expected. These tests are run every time our codebase is updated and even one single test failing will prevent new code being shipped to production.

  • Each Sage HR system used to process customer data is adequately configured and patched using commercially-reasonable methods according to industry-recognized system-hardening standards.

  • Sage HR engages certain sub-processors to process customer data. These subprocessors are listed in “Third parties” policy, as may be updated by Sage HR from time to time.

  • We back up Customer data every 24 hours. In addition to that, we keep 4 weekly backups and 12 monthly backups. All backup files older than 12 months are automatically deleted.

  • Our production data and backups are encrypted 'at rest' using AES-256 block-level storage encryption.

  • When Customer account is deleted, we keep the data in our backup files for 12 months. If there is a requirement to delete all data, please contact our support.

Data Transfer

  • All data sent to or from Sage HR is encrypted in transit using 256-bit encryption.

  • Our API and application endpoints are TLS/SSL only and score an "A" rating on SSL Labs' tests. This means we only use strong cipher suites.


  • Sage HR is served 100% over HTTPS.

  • There are no corporate resources or additional privileges from being on Sage HR’s network.

  • We have strong password policies and Multi-Factor Authentication for employees of Sage HR on GitHub, Google, AWS and Sage HR to ensure access to cloud services are protected.

Permissions and Admin Controls

  • Sage HR enables permission levels to be set for any employees with access to Sage HR.

  • Permissions and access can be set to include app settings, billing, user data

  • We enforce 2FA into Sage HR administration system for every Sage HR employee.

Application Monitoring

  • On an application level, we produce audit logs for all activity.

  • All access to Sage HR applications is logged and audited.

  • All actions taken in the Sage HR application are logged.

Security Audits and Certifications

  • Sage HR is compliant to ISO 27001 as per the standards body of the United Kingdom, BSI (certificate IS 692128).

  • We annually engage with well-regarded third-party auditors to audit our code-base, and work with them to resolve potential issues.

  • Information about AWS security certifications and obtaining copies of security reports from AWS is available at

  • Our data is stored in data centre which is up-to-date compliant to set of standards and requirements such as ISO27001, SOC 1 and SOC 2/SSAE and others. Read more:

  • SOC audit of Sage HR is planned for the period up to year 2024.

Payment Processing

All payment instrument processing for purchase of the Sage HR services is performed by Stripe. For more information on Stripe’s security practices, please see

Customer Responsibilities

  • Managing your own user accounts and roles from within the Sage HR services.

  • Protecting your own account and user credentials by using long passwords or enabling Single Sign On (SSO) for all of your employees accessing the Sage HR services.

  • Compliance with the terms of your services agreement with Sage HR, including with respect to compliance with laws.

  • Promptly notifying Sage HR if a user credential has been compromised or if you suspect possible suspicious activities that could negatively impact security of the Sage HR services or your account.

  • You may not perform any security penetration tests or security assessment activities without the express advance written consent of Sage HR.

Service Level Agreement

This Sage HR Service Level Agreement ("SLA") accompanies the Sage HR Subscription Terms of Service (the "Agreement") entered into between you ("Customer") and Sage HR. Capitalized terms used in this SLA that are not defined herein have the meanings given to them in the Agreement.

  1. Target Availability. Sage HR will use commercially reasonable efforts to make each Service available with an uptime of 99.8% of each calendar month ("Target Availability").

  2. Exclusions. The calculation of uptime will not include unavailability to the extent due to: (a) use of the Service by Customer in a manner not authorized in this Agreement or the applicable Documentation; (b) general Internet problems, force majeure events or other factors outside of Sage HR's reasonable control; (c) Customer's equipment, software, network connections or other infrastructure; (d) third party systems, acts or omissions; or (e) Scheduled Maintenance or reasonable emergency maintenance.

  3. Scheduled Maintenance. "Scheduled Maintenance" means Sage HR's scheduled routine maintenance of the Services for which Sage HR notifies Customer at least twenty-four (24) hours in advance. Scheduled Maintenance will not exceed eight (8) hours per month. Customer will not be notified is Scheduled Maintenance is less than ten (10) minutes long.

  4. Remedy for Failure to Meet Target Availability. If there is a verified failure of a Service to meet Target Availability in two (2) consecutive months, then Customer may terminate the applicable Subscription Term by sending written notice of termination within thirty (30) days after the end of the second such month, in which case Sage HR will refund to Customer any fees Customer has pre-paid for use of such Service for the terminated portion of the applicable Subscription Term. This termination and refund right is Customer's sole and exclusive remedy, and Sage HR's sole and exclusive liability, for Sage HR's failure to meet the Target Availability.

Third Parties

Sage HR engages certain onward sub-processors that may process personal data submitted to Sage HR's services. These subprocessors are listed below, as may be updated by Sage HR from time to time:

Amazon Web Services Inc.
PO Box 81226, Seattle, WA 98108-1226, United States
Server & data storage

ChartMogul, Ltd.
Oberwallstraße 6, Berlin, 10117, Germany

CloudFlare, Inc.
665 3rd Street, Suite 200, San Francisco, CA 94107, United States
Content delivery network & DDoS mitigation service

Convert API
UAB Baltsoft

Lauksargio 111,

Vilnius, LT-10105,


File conversion

Google, Inc.
1600 Amphitheatre Parkway, Mountain View, CA 94043, United States
Calendar, document viewing & Single Sign On Integration (SSO used only when G Suite integration in enabled)

Intercom, Inc.
55 2nd Street, 4th Floor, San Francisco, CA 94105, United States
Customer helpdesk & chat

Recurly Inc.
400 Alabama Street Suite 202 San Francisco, CA 94110 United States
Billing & Invoicing

Pusher Ltd
28 Scrutton Street, London, EC2A 4RP, United Kingdom
Push notification for mobile app

Stripe, Inc.
185 Berry Street, Suite 550, San Francisco, CA 94107, United States
Card payment processing

SendGrid, Inc.
1801 California Street, Suite 500, Boulder, CO 80202, United States
Email delivery

Functional Software, Inc.
1 Baker Street, Suite 5B, San Francisco, CA 94117, United States
Error logging

Slack Technologies, Inc.
155 5th Street, 6th Floor, San Francisco, CA 94103, United States
Internal chat (used when Slack integration is enabled)

Zapier Inc.
548 Market St. #62411. San Francisco, CA 94104, United States
Data integration

Last updated: 25 Mar 2024

Did this answer your question?