What we collect
We collect registration details, account and optional business information, project and batch records, consent records, support messages, referral attribution, pricing and transaction records, operational security information, and—when transfer is enabled—working copies of submitted captures and generated deliverables.
Why we use it
We use this information to authenticate accounts, coordinate and perform restoration, validate submitted files, calculate versioned pricing, provide support, deliver results, operate the direct referral program, prevent abuse, maintain audit records, and improve service reliability.
Image ownership and use
The submitting partner retains ownership of original captures and represents that it has the right to submit them. BurlyMingo receives copies for processing and does not acquire ownership of customer images. Source files and deliverables are private by default.
Three separate data purposes
Service files
Source captures and restored derivatives are used to perform, review, deliver, support, secure, validate, and improve the contracted restoration service. They follow the project retention policy rather than becoming a permanent image archive.
Restoration and operational data
Heritage necessarily records technical data created while processing a project. This may include source-device and format compatibility, preflight results, restoration parameters and selections, pipeline and model versions, quality outcomes, failure codes, timing, and aggregate statistics. BurlyMingo uses these non-public records to process current projects and improve restoration behavior for future projects.
Image-content boundaries
Working source and derivative images may be compared and evaluated while they are within the disclosed project retention window. BurlyMingo may retain the resulting technical parameters, compatibility profiles, selections, and quality labels after those image files are deleted.
BurlyMingo does not acquire ownership of customer images, publish them, or keep recognizable source files, crops, before-and-after pairs, masks, or exemplars beyond the stated project retention period solely to create a permanent general training library without a separate written agreement. Public restoration examples always require separate recorded permission.
Access
Access to source files is limited to authorized processing, quality review, support, security, and deletion activity. Project download links are designed to be authenticated and time limited. Permanent object-storage credentials are never provided to partners.
Service providers
BurlyMingo may use Logto for identity, Stripe for payment processing and receipts, Cloudflare infrastructure and private object storage, and separate notification or temporary compute providers when those services are enabled. Relay is BurlyMingo’s business bank rather than a customer checkout processor. Material production providers, processing purposes, and relevant cross-border constraints are documented before the affected service is broadly activated.
Retention
The launch target is 30 days after project completion for both source working copies and restored deliverables, with advance warnings. Operational, consent, invoice, fraud, dispute, audit, and legally required records may have different retention. See the Data Retention Policy.
Your responsibilities and choices
Keep your own source backups. Do not submit images you lack permission to process. You may contact support to request account-data access, correction, or deletion; legal, transaction, security, fraud, and dispute obligations may limit deletion.
Contact
Use the site support form for privacy requests. Do not send customer images or sensitive identity details through the support form.