JETENCODE / LEGAL & TRUST
Security
JetEncode runs inside infrastructure you control. Security therefore depends on both the published cloud image and the way your provider environment is configured and maintained.
Shared responsibility
JetEncode is responsible for addressing security issues in the JetEncode software and published cloud images. You are responsible for your cloud account, workload identities, network access, operating procedures, input media, outputs, backups, monitoring, and the lifecycle of resources you launch.
The browser UI and HTTP API use TCP port 80. Restrict inbound access to trusted operator and application source ranges.
HTTP authentication protects application access. Put TLS in front of port 80 for untrusted networks and enable encryption for buyer-created EBS and S3 storage where required.
The base image starts without a licensing or telemetry service. Jobs connect only to the HTTP or object-storage sources and destinations configured by the customer.
Recommended deployment practices
- Use least-privilege workload identities instead of embedding long-lived provider credentials.
- Restrict inbound access to the minimum ports and trusted source ranges you need.
- Keep JetEncode and its supported base operating system current.
- Encrypt sensitive traffic and storage where supported by your cloud architecture.
- Monitor logs, resource usage, and provider security findings for unexpected activity.
Report a vulnerability
Email support@jetencode.com with the subject “Security report.” Include the affected version, impact, reproducible steps, and any non-sensitive evidence. Do not include active credentials, customer media, or personal data.
Please avoid accessing data that is not yours, disrupting services, degrading cloud resources, or publicly disclosing an unremediated issue. We will acknowledge good-faith reports and coordinate next steps by email.
Security incidents
If we confirm a JetEncode security issue that requires customer action, we will provide remediation or upgrade guidance through an appropriate customer-facing channel. Security events limited to your cloud account should also be reported through your provider security and support process.