Data processing
AndonPulse is a Software Engineering Intelligence Platform. We help engineering leaders understand delivery performance, identify bottlenecks, and see where engineering investment goes—so they can make better decisions about priorities, resources, and improvements.
This page explains how information moves through the service and the choices available to your organization.
Documents and roles
Your organization decides which systems to connect and provides the instructions for processing its information. For personal data processed on your organization’s behalf, the Data Processing Agreement describes the customer and AndonPulse’s respective responsibilities, including customer instructions, security, assistance, and deletion or return.
Use these documents alongside this practical explanation:
- Data Processing Agreement: The terms for processing personal data on your organization’s behalf.
- Privacy Policy: How we handle website, account, and other personal information, and how individuals can exercise applicable rights.
- Subprocessors: The providers that help deliver the service and their processing activities and locations.
- Terms of Service: The service relationship, including customer information and retention obligations.
The applicable agreement governs processing; this explanation does not replace it. Website and account activities can have different purposes and responsibilities from processing your organization’s connected information.
Information and purposes
Depending on the integrations and features used, we handle the following information:
| Information | What it includes | Why it is needed |
|---|---|---|
| Work records | Titles, descriptions, fields, and historical activity. | Understand delivery performance and where work is delayed. |
| Development activity | Pull requests, commits, reviews, and comments. | Understand engineering work and the context behind delivery. |
| Account and contributor information | Names, email addresses, usernames, and identifiers. | Provide accounts, attribute activity, and connect information to the relevant contributors. |
| Workforce and cost information | Working schedules, time off, and labor costs, where enabled. | Understand capacity and where engineering investment goes. |
| Integration credentials | Tokens and API keys for customer-authorized connections. | Connect and synchronize the systems your organization authorizes. |
Descriptions and review comments are free text. They can contain sensitive information or code that someone has included in the source system. Consider that content when deciding what to connect and which information to make available to the service. If your organization does not need the metrics that depend on particular information, you can contact our Privacy team to discuss excluding that information from collection and how this would affect the insights available to you.
Integration permissions and customer choices
Your organization authorizes a connection through the source system. The permissions granted determine what that connection can do; the information collected depends on the integration and how it is configured. A granted permission does not mean every available field is imported.
Where an integration supports selecting projects, repositories, or another scope, use those controls to limit the connection to the work you want to understand. Available choices and permissions vary by provider. Review the requested permissions before authorizing access and use credentials appropriate to the intended scope.
You can stop synchronization by disconnecting an integration. When synchronization is disabled, retained credentials are not used to access that connection. Disconnecting does not automatically erase information already imported. If you also want that information returned or deleted, send an authorized request using the contact below.
Removing a credential from AndonPulse and revoking access in the source system are separate actions. For a customer-managed token or API key, revoke or rotate it with the provider when it is no longer needed. For an application grant, use the provider’s revocation controls as applicable. Local removal alone does not establish that the upstream credential or grant has been revoked.
Processing and access
Information follows this progression:
Customer-authorized source systems → extraction → processing and storage → engineering insights for your organization.
We organize connected information into a consistent view so your team can understand delivery, bottlenecks, capacity, and investment across its tools. Customer analytics are stored in a separate database for each organization. Shared application records, such as accounts and organization settings, are scoped to the relevant organization.
Authenticated customer access is limited to that organization and governed by customer roles and permissions. Production and customer-data access is limited to authorized personnel who need it. Administrative access requires individual accounts, multi-factor authentication, and only the permissions needed for the work. Access is reviewed quarterly and after material changes, and removed when no longer required.
Browser connections to AndonPulse require TLS 1.3 to protect information in transit. External integration connections also use TLS; compatibility and supported protocol versions are assessed separately for each integration. Customer databases and application-server storage use AES-256 encryption, with an additional layer of encryption for integration credentials. The Security overview explains these safeguards and the service’s other security practices.
Locations and providers
Core application and database hosting is on Amazon Web Services in Northern Virginia, United States.
If your organization has specific data-location requirements, contact us to discuss them before connecting your systems. We review regional-hosting requests individually and confirm any agreed arrangement in writing.
Other providers support activities such as content delivery, payments, and monitoring. Their processing locations can differ from our core hosting location. The Subprocessors register identifies those providers and their purposes; the DPA describes the applicable international-transfer arrangements.
We limit information shared with a provider to what it needs to perform its service. Contact us if your review requires more detail about a provider or processing activity.
Retention, return, and deletion
We keep information for as long as needed to provide the service and fulfill the applicable purposes and obligations. Cancelling a paid subscription, disconnecting an integration, ending the customer agreement, and asking for deletion have different effects:
| Event | What happens |
|---|---|
| Active service | Information is retained as needed to provide the service and fulfill its purposes under the applicable agreements. |
| Paid service ends after cancellation | Synchronization and use of integration credentials stop. Imported source records and derived analytics are retained solely for customer reactivation for 90 days after paid service ends, then deleted unless reactivated. Cancellation does not automatically close organization or user accounts or delete integration credentials. Earlier authorized deletion requests and DPA obligations take precedence. |
| Integration disconnected | Synchronization stops, and retained credentials are not used to access that connection. Already imported information is retained unless a separate deletion or return obligation applies. Revoke or rotate source-system credentials as needed. |
| Customer agreement terminated or expired, or authorized written request received | We arrange deletion or return under the DPA and Terms, stop further collection and associated processing jobs, and handle the applicable copies. |
| Retention required by law | The required information is retained for the applicable legal purpose, with access restricted. |
| Backup copies | Encrypted copies can remain for up to the existing 90-day maximum, isolated from further processing. Routine automated database backups are kept for seven days. |
| Data restored for recovery | Recovered data is quarantined while deletion records are reconciled. Previously deleted customer information is erased again before normal processing resumes. |
The 90-day reactivation period covers both information imported from connected systems and the analytics calculated from it. It is separate from backup retention. Other retained records remain subject to the Terms, DPA, Privacy Policy and applicable law.
An authorized request is scoped to your organization and covers applicable application records, raw and derived analytics, pending jobs, logs, exports, and relevant provider-held copies. We confirm the requester’s authority, arrange a safe handoff for returned information, and record any legally required retention or actions your organization needs to take.
Before deliberately deleting a database, we retain a final recovery copy with an owner and a cleanup deadline within the 90-day maximum. Final recovery copies require explicit cleanup. Creating a new recovery copy or restoring data does not restart an existing customer-data deletion or backup-expiry deadline.
Contact [email protected] to arrange return or deletion. Include your organization, the affected connection or information, and whether you need return, deletion, or both. Avoid sending credentials or customer contents in the initial message. The DPA and Terms set out the applicable obligations.
Privacy assistance
You can update your own account name and email through account settings. For information imported from connected systems, contact the administrator of the organization that connected those systems, or email our Privacy team. That organization decides how its information is used, and we can help direct your request to it.
We assist authorized customers with relevant privacy requests and other obligations under the DPA, and handle individual requests under the Privacy Policy and applicable law. We may need to confirm identity and authority to protect the information involved.
Contacts and related resources
For questions about processing, return, deletion, or privacy requests, contact our Privacy team. For security reviews or supporting evidence, contact our Security team.
The Security self-assessment answers common procurement questions, and the Security overview summarizes the safeguards around customer information. We review these explanations quarterly and after material changes.
Reviewed