Security
Security and privacy overview
A plain-language summary of how SwiftLabel handles datasets, payments, license delivery, admin access, and operational health.
Data Model
Dataset filesSwiftLabel is a desktop application. Image datasets and annotation files are edited locally and are not uploaded to SwiftLabel by the product workflow.
Payment dataCard information is processed by iyzico. SwiftLabel stores order metadata, payment status, license delivery state, and support records needed to operate the service.
License deliveryLicense keys are generated through the licensing system and delivered by email. Order status is protected by a private access token in the customer link.
Admin accessOperational admin endpoints require an admin token. Anonymous access to order, mail log, and webhook administration APIs is rejected.
Operational Controls
- Read-only health endpoint for application, database, and configuration checks.
- Webhook event records for payment callback troubleshooting.
- Mail log records for delivery and retry troubleshooting.
- Rate limiting on checkout creation to reduce automated abuse.
- Jenkins deployment separates demo mutation tests from production deploys.
Security Headers
JSON API responses include security headers such as content type protection, referrer policy, frame protection, and restricted browser permissions. Static marketing pages are served over HTTPS.
Responsible Contact
For security, privacy, or administrative requests, contact admin@swiftlabel.io. For urgent licensing or delivery issues, contact support@swiftlabel.io.