Sub-Processor List
Overview
Trackless Telemetry ("Trackless," "we," "us") uses a limited number of third-party sub-processors to deliver the service. This page lists all sub-processors that process data on our behalf.
We are committed to minimizing the number of sub-processors and the scope of data each sub-processor can access. In particular, telemetry data (event names, event counts, device dimensions) is never shared with payment processors, advertising networks, analytics providers, or data brokers.
Current Sub-Processors
| Sub-Processor | Purpose | Data Processed | Location |
|---|---|---|---|
| Amazon Web Services, Inc. (AWS) | Infrastructure provider — DynamoDB (data storage), Lambda (compute), Cognito (authentication), SES (transactional email), CloudFront (CDN and edge security), AppSync (GraphQL API) | Dashboard account data (email address, hashed password), aggregate telemetry counts (event counts by day with coarse device context), API key hashes, waitlist request data, usage metering records, operational logs | us-east-1 (Virginia, USA) |
| Stripe, Inc. | Payment processing for paid subscription tiers — Checkout, Customer Portal, webhook-based subscription lifecycle management | Cognito user sub (as customer metadata), email address, payment information (payment method details, invoices, subscription status) | United States |
Stripe Data Minimization
Stripe receives only the minimum data required for payment processing. Specifically, no telemetry data, app names, event names, usage event counts, or usage details are transmitted to Stripe. The Stripe integration is limited to subscription management and payment collection. The Cognito user sub is stored as Stripe Customer metadata solely to link payment records back to the correct Trackless account.
Changes to Sub-Processors
When we add or replace a sub-processor, we follow this process:
- Advance notice. Changes to this sub-processor list are communicated via email to all customers with active subscriptions at least 30 days before the change takes effect.
- Right to object. Customers may object to a new or replacement sub-processor within the 30-day notice period by contacting us at legal@tracklesstelemetry.com. We will work with the customer to find a reasonable resolution. If no mutually acceptable resolution can be reached, the customer may terminate their subscription in accordance with the Terms of Service.
- Publication. This page is updated to reflect the change on or before the effective date. The changelog below records all modifications.
Changelog
No changes since initial publication.
Contact
For questions about our sub-processors or to exercise your right to object to a sub-processor change, contact us at legal@tracklesstelemetry.com.
For general privacy inquiries, contact privacy@tracklesstelemetry.com.