Sub-processors
Last updated: July 1, 2026
Contents
Autorender, Inc. ("Autorender") engages the third-party sub-processors listed below to help provide, secure, and operate our media transformation, optimization, and delivery platform (the "Service"). Each sub-processor is engaged under a written contract requiring appropriate confidentiality and security and permitting it to process personal information only as needed to provide its service to us. We remain responsible for our sub-processors' acts and omissions.
This page is referenced by, and forms part of the transparency commitments in, our Privacy Policy, our Terms of Service, and our Data Processing Addendum (DPA).
Current sub-processors
| Sub-processor | Function | Processing location | Data involved |
|---|---|---|---|
| Amazon Web Services (AWS) | Cloud hosting, object storage (S3), CDN delivery (CloudFront), job queue (SQS), database (RDS PostgreSQL), analytics ETL (Athena) | United States | Account data, Customer Content, usage/logs |
| Upstash (Redis) | Caching, rate-limiting, and session data | United States | Session/usage data |
| SendGrid (Twilio) | Transactional email | United States | Email address, message content |
| Resend | Transactional email | United States | Email address, message content |
| Google Cloud — Vertex AI / Gemini | AI image analysis, captioning, editing, and agent features | United States | Customer Content and prompts submitted to AI features |
| Google Cloud Vision | Image object/label detection | United States | Customer Content submitted to AI features |
| Google & GitHub (OAuth) | Social sign-in | United States | Profile/email you authorize |
| PostHog | Product analytics | United States | Usage/device data |
| Sentry | Error and performance monitoring | United States | Diagnostic/error data |
| ConfigBee | Feature-flag management | United States | Limited configuration/usage data |
| Slack | Internal operational notifications (e.g., feedback) | United States | Limited feedback/contact data |
AI sub-processors and your content
When you use our AI-powered features, the relevant Customer Content and prompts are transmitted to the applicable AI sub-processor(s) above solely to perform the operation you requested. These sub-processors do not use your Customer Content to train their models; we access them through enterprise/paid API tiers whose terms prohibit such training.
Customer-connected storage
If you connect your own Amazon S3, Google Cloud Storage, or Azure Blob storage as an origin, those assets remain in your storage under your control and are governed by your agreement with that provider; that storage is not an Autorender sub-processor.
Changes to this list
We may update our sub-processors as the Service evolves. Where you have an active account, we will provide reasonable advance notice — at least fourteen (14) days where practicable — before a new sub-processor begins processing your personal information, by updating this page and/or notifying you by email or in-product. You may object to a new sub-processor as described in our DPA.
Contact
Questions about our sub-processors: engineering@autorender.io · Autorender, Inc., 8 The Green, STE R, Dover, DE 19901, United States.