# Security and Data Handling

{% hint style="info" %}
CONNECTORS ARE COMING AUGUST 2026
{% endhint %}

Connectors follow the same security, privacy, and compliance standards as the wider UbiQuity platform. All data transferred through Connectors is encrypted, authenticated, and logged. No data is shared between customer environments.

***

### How Connectors handle data

Each Connector runs in an isolated execution environment. Customer jobs and credentials are logically separated, and no persistent external connection is maintained between runs.

Key principles:

* Each Connector job runs independently and in isolation
* Credentials are never shared between customer environments
* No data is retained in transit infrastructure after a job completes

***

### Encryption

**Data in transit**

| Storage type                 | Encryption        |
| ---------------------------- | ----------------- |
| Amazon S3                    | TLS 1.2 or higher |
| Microsoft Azure Blob Storage | TLS 1.2 or higher |
| SFTP                         | SSH encryption    |

**Data at rest**

Data processed within UbiQuity is encrypted using AES-256. Credentials and tokens are stored securely and are never viewable in plain text after entry.

***

### Storage ownership and responsibility

UbiQuity does not host file storage for Connectors. Responsibility is shared between UbiQuity and your organisation.

| Responsibility                                 | Your organisation | UbiQuity |
| ---------------------------------------------- | ----------------- | -------- |
| Hosting and managing storage                   | ✓                 |          |
| Controlling access and permissions to storage  | ✓                 |          |
| Ensuring data residency compliance             | ✓                 |          |
| Securely connecting to your storage location   |                   | ✓        |
| Processing data within the platform            |                   | ✓        |
| Maintaining platform security and availability |                   | ✓        |

***

### Access control

Access to Connectors within UbiQuity is controlled by user permissions. Only authorised users can view, create, edit, or activate Connectors.

Administrative access to production systems is restricted, logged, and reviewed.

***

### Monitoring and audit logging

All Connector activity is logged. Within UbiQuity, you can view run history, run status, and timestamps for every Connector.

UbiQuity also maintains system-level monitoring and alerting internally to ensure reliability, performance, and security. Logs are retained in line with UbiQuity's auditing and operational policies.

***

### Compliance

UbiQuity is certified to ISO/IEC 27001:2022 for its Information Security Management System. Connectors operate under the same governance, controls, and secure development practices as the wider platform.

Security measures include regular vulnerability scanning, penetration testing, controlled deployment processes, and continuous monitoring and incident response procedures.

***

### Best practices

To maintain a strong security posture for your Connectors:

* Use dedicated service accounts rather than personal credentials
* Prefer SSH keys over passwords for SFTP connections
* Rotate access keys and tokens regularly, and update the Connector immediately after rotating
* Restrict credentials to the specific folders or containers required — avoid granting broad storage access
* Disable unused Connectors and revoke associated credentials promptly


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.ubiquity.co.nz/documentation/data-and-integrations/connectors/security-and-data-handling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.