Public legal documents
AiboTask — Subprocessor List
Version: 1.1
Effective date: 5 April 2026
Provider / Platform Operator: AirTek Technologies (RUC 0924829179001)
Registered address: Cooperativa Adesdac MZ 70 S 13, Ecuador
Privacy contact: ruben.lazaro@clitecser.com
This Subprocessor List describes third parties that may process personal data on behalf of Customers (Tenants) when using aibotask, and key service providers that support Provider-controlled SaaS360 admin/commercial workflows where applicable.
1) Definitions (high level)
- Customer / Tenant (Data Controller): the company that configures and uses aibotask for its operations and determines purposes/means of processing.
- Provider (Data Processor): AirTek Technologies, which operates aibotask and processes Customer data only on documented instructions (see DPA).
- Provider-controlled platform data: certain records for SaaS360 tenant provisioning, licensing, billing, support ticketing, and security operations for which AirTek may act as Data Controller under the Privacy Policy.
- Subprocessor: a third party engaged by the Provider to support the delivery of the Service (e.g., cloud hosting, messaging).
2) How we update this list
We may update this list from time to time as we change vendors or add integrations. Material changes will be reflected here.
If you have questions or need prior notice mechanisms, contact: ruben.lazaro@clitecser.com.
3) Current subprocessors
3.1 Cloud infrastructure and core platform
| Subprocessor | Service | Purpose | Primary location/region |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Cloud hosting (compute, storage, databases) | Core infrastructure to run aibotask and store Customer data (work orders, photos, signatures, GPS routes, logs) | us-east-1 (N. Virginia, United States) |
3.2 Email delivery
| Subprocessor | Service | Purpose | Primary location/region |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Amazon Simple Email Service (SES) | Transactional email delivery (e.g., invitations, password resets, notifications, service reports) | us-east-1 (N. Virginia, United States) |
3.3 Push notifications
| Subprocessor | Service | Purpose | Notes |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Amazon Pinpoint | Sending push notifications (e.g., new job assigned, status updates) | Uses mobile platform push services below |
| Apple Inc. | APNs | Delivery of push notifications to iOS devices | Device OS dependent |
| Google LLC | FCM | Delivery of push notifications to Android devices | Device OS dependent |
3.4 Maps / geolocation services
| Subprocessor | Service | Purpose | Primary location/region |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | AWS mapping/geolocation services (e.g., Amazon Location Service) | Display maps and geospatial features (where enabled) | us-east-1 (N. Virginia, United States) |
3.5 Web analytics / performance telemetry (SaaS360 / provider web portals)
| Subprocessor | Service | Purpose | Primary location/region |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Amazon CloudWatch RUM | Measure SaaS360 and related provider web-portal performance and usage telemetry to improve reliability and UX | us-east-1 (N. Virginia, United States) (telemetry storage per AWS configuration) |
3.6 Payments (SaaS360 subscription transactions)
| Subprocessor | Service | Purpose | Notes |
|---|---|---|---|
| Kushki | Payment processing | Process subscription payments in SaaS360 and provide transaction confirmations | Provider does not store full card details |
4) Subprocessors not currently used (examples)
We do not currently use a third-party support ticketing system (such as Zendesk). If we add a support system in the future, this list will be updated.
Contact: ruben.lazaro@clitecser.com