There are a number of different ways that crops can be made including custom rectangle cropping via pixel or percentage values, provided as url string parameters. The face zoom crop is just an additional feature to save some steps for these kinds of scenarios. Ideally this feature can be built into an application providing a user with a suggested face crop, and then allow a to use the alternate custom crop that access a different set of parameters via imgix. imgix is an on demand dynamic api for these operations.

To follow up on Kelly's response:

Our service is only for use with images provided by our customers, and our terms of use specifically require them to have the associated rights for the images they use with us.

From a privacy standpoint, I don't see a practical difference between a website serving a user's profile photo directly from their S3 bucket vs. engaging imgix to serve it (in a more optimal fashion).

We do take security and privacy seriously. We do not sell or in any way utilize our customer's data for any purpose besides operating the service or reporting analytics metrics back to the customer. We do maintain caches of fetched and rendered images, but this is all done in a secure fashion.

Any online service has the potential for a data breach or unintended behavior, and we're not immune to bugs or mistakes. So far, our track record is impeccable, and we'll continue to take the appropriate steps to keep it that way.

Article 29 is geared more toward _facial recognition_, whereas what imgix does is mere _face detection_.

imgix takes finding Waldo very seriously. As a result, we will never offer a parameter to kill the fun.