This page lists the third-party services that may process Taska customer data on behalf of Enrevia Technologies, the operator of the Taska service. We notify customers at least 30 days before adding a new sub-processor (per the DPA). If you'd like to be on that notification list, email legal@enrevia-taska.com.
Engaged for every customer
| Sub-processor | Purpose | Region |
|---|---|---|
| Amazon Web Services (AWS) | Application hosting, database (RDS Postgres), object storage (S3), encryption (KMS), and large-language-model inference (Bedrock). | us-east-1 (N. Virginia) |
| Amazon Cognito | Authentication, password hashing, and session management. | us-east-1 |
| Amazon Simple Email Service (SES) | Transactional email delivery (briefs, booking notifications, lifecycle email). | us-east-1 |
| Stripe | Payment processing, subscription billing, and tax calculation. Card numbers never touch our infrastructure. | United States (with EU + UK affiliates) |
| PostHog | Product analytics — page views and feature usage. Fires only after the user accepts the cookie consent banner. | United States or EU (configurable; we use US) |
| Sentry | Error monitoring and performance traces. | United States |
| Cloudflare | DNS, edge caching, and bot mitigation for the marketing site. | Global edge network |
Optional — engaged only when the customer connects them
These are not engaged by default. They process customer data only when an individual user authorizes Taska to access their account.
| Sub-processor | Purpose | Region |
|---|---|---|
| Google (Gmail + Google Calendar) | Read-only access to email and calendar when the user connects a Google account. | Global (Google data centers) |
| Microsoft (Outlook + Microsoft 365) | Read-only access to email and calendar when the user connects a Microsoft 365 account. | Global (Microsoft data centers) |
| Slack | Read-only access to channels and DMs when the user installs the Taska Slack app. | United States |
Changes to this list
When we add a sub-processor, we publish the change here and emit a notice on /changelog. Customers on the notification list also receive an email. Customers may object to a new sub-processor in writing within 30 days; if we can't substitute a different vendor, the customer may terminate the affected service.