Security, privacy, and data handling
If you need the short version for client work, start here.
What we do not do
- We do not train AI models on your uploads or outputs.
- We do not keep a long-term archive of source files and generated outputs on our side.
- We do not store card details on our application servers.
What we do keep
Some data has to exist for the service to work:
- account and authentication records
- billing and transaction metadata
- job status, logs, and other operational metadata
That is the difference between "we do not keep your files forever" and "we keep enough account data to run the product safely."
How files move through the system
At a high level:
- you upload a file to ModelMyImage
- the job is routed through the generation pipeline
- the result is attached to your account for download and history
Some inference work is handled by third-party providers. Where those providers support cleanup or no-retention controls, we use them.
Retention in plain English
Here is the least confusing way to think about it:
- source files and generated outputs are not treated as a permanent archive on our side
- temporary processing data is cleaned up
- history entries are kept for 60 days so you can revisit recent jobs
- account, billing, and security records can be retained where they are needed for operations or legal obligations
If you need the formal wording, use the Privacy Policy and Terms of Service.
Access and isolation
- authentication is handled through a managed identity provider
- downloads are tied to the account that owns the job
- other users cannot browse your files or history
- billing is handled through Stripe