Security and privacy at Catchr

Protecting your data and connections

Catchr uses encrypted connections to protect information exchanged between your browser and our web application. This helps preserve the confidentiality and integrity of information while you use the service.

Sensitive credentials used to connect your data sources are also encrypted when stored. Protecting these credentials matters because they allow Catchr to retrieve reporting data from the platforms you connect. Their protection is an essential part of maintaining the confidentiality of your connected accounts.

Encryption works alongside our access controls and application safeguards. Together, these measures help reduce the risk of unauthorized access and disclosure throughout your interactions with Catchr.

Controlling access to customer resources

Access to protected Catchr resources requires authentication and is governed by application permissions. These controls help ensure that users access information within the context of their organization and the permissions available to them.

Customer resources are associated with the relevant organization. This association supports the separation of access between customers and helps keep connections, reporting configuration, and related resources within the appropriate company context.

Customers control who they invite to their Catchr space. This lets teams collaborate on reporting while making deliberate decisions about who should have access. We encourage customers to align membership with their internal responsibilities and data-sharing policies.

Supporting authorized reporting workflows

Catchr connects the sources and destinations that customers configure for their reporting needs. Those connections make it possible to retrieve information from selected platforms and deliver it to the reporting tools used by the team.

Our application controls support access to connected resources within the customer's organization. Customers also manage permissions in their destination tools, so the intended audience can access the resulting reports, spreadsheets, or databases.

Considering permissions at both ends of a reporting workflow helps maintain control over how information is shared, from the connected source through to the final report.

Building security into development

Our engineering guidelines include security requirements and the protection of sensitive information. They require security-relevant decisions to be documented, providing a reference for changes that affect how the service handles customer resources.

Development work is supported by automated checks and tests. These checks help identify programming errors and unintended changes in application behavior, including behavior related to connections and access.

Maintaining these checks as part of the development process helps preserve existing protections when features change. Security is therefore considered alongside functionality and reliability as Catchr evolves.

Infrastructure and physical protection

Catchr's application safeguards operate alongside protections provided by the infrastructure services we use. The two have complementary roles: application controls govern access within Catchr, while managed-service providers are responsible for the physical security of their underlying facilities.

Physical protection addresses access to the environments in which those managed services operate. It complements the encryption and access controls used at the application level, with responsibilities distributed between Catchr and the relevant service provider.

Privacy and responsible data handling

Catchr processes connected-source data to deliver the reporting requests and transfers configured by customers. The integrations and features selected determine what information is needed for those workflows and how it is handled.

Data handling and storage vary according to the service being used. Connection information, account settings, and reporting results serve different purposes in providing the requested functionality. Our team can provide further context for customers evaluating a particular integration or reporting workflow.

Our published Privacy Policy provides additional information about our privacy commitments. This includes our commitment to the Limited Use requirements applicable to information received from Google APIs.

Helping you assess our security measures

We understand that choosing a data integration service involves evaluating how it fits your organization's security expectations. This page provides an overview of the protections relevant to using Catchr, including encryption, access control, development safeguards, and infrastructure responsibilities.

For questions about a specific use case, our team can help clarify the data-handling practices relevant to your connected sources and destinations. This gives your team context for its own review and configuration decisions.

Contact our team

For security questions, privacy inquiries, or concerns about your Catchr account, contact us through support in the application or the Catchr Help Center.

Please describe the relevant feature or concern without including sensitive connection information in your message.