PixMenderOpen image toolSecurity
How PixMender protects accounts, API keys, uploads, processing jobs, webhook deliveries and temporary image storage.
Last updated
Private, temporary files
Originals, intermediate files and results are stored as private objects with isolated identifiers. Upload and download access uses short-lived signed URLs instead of a public bucket. Image assets receive a 24-hour expiry time; automated cleanup starts after expiry and retries temporary storage failures until deletion succeeds.
Upload validation
An upload is treated as untrusted until processing verifies its declared type, file signature, decoded dimensions and supported format. Limits on file size and dimensions reduce resource-exhaustion risk. Remote imports accept public HTTPS targets and revalidate redirects to reduce server-side request forgery risk.
Accounts and API keys
Passwords and API keys are stored as hashes rather than readable secrets. Browser sessions use HTTP-only, Secure production cookies with SameSite protection. API keys support scopes and revocation, and administrative routes require separate authorization.
Jobs and processing workers
The public API validates and records a job before asynchronous workers execute ordered operations. Provider errors are normalized, retries are bounded and credits are released on terminal processing failure. Remote GPU workers connect outward and use separately issued worker credentials rather than customer API keys.
Webhooks and integrations
Webhook events are signed so recipients can verify their source. Deliveries are recorded and retried independently. Outbound webhook destinations are checked to block private and non-routable network targets, and integrations should still validate signatures, timestamps and duplicate events.
Operational access and logging
Access is limited by role and service function. Security, audit and error records support incident investigation without placing complete passwords or API keys in normal logs. Infrastructure, dependencies and provider access should be kept patched and reviewed as the service changes.
Your security responsibilities
Use a unique password, protect your email account, keep API keys in a secret manager, grant the narrowest scopes and rotate credentials after exposure. Do not embed server keys in browser or mobile code. Validate downloaded results before automated publication and expire webhook secrets when an endpoint changes owners.
Report a vulnerability
Email [email protected] with a clear description, affected URL or component, impact and safe reproduction steps. Do not access another person's data, disrupt the service, use destructive tests or include live credentials and private images. We will acknowledge useful reports and coordinate remediation and disclosure in good faith.
Need help? [email protected]