Acceptable use: image processing in memory

Questions / Help
1

I want to check an acceptable-use question before I deploy.

I’m building a cataloguing app for adults. People photograph their own belongings, clothing etc. Some of it is may be lawful adult content.

Images are stored on a different service, not on Fly. What would run on Fly
is a worker that pulls each image into memory, strips the EXIF data,
generates a thumbnail hash, and sends it to a moderation API. Nothing
is written to disk.

Your ToS says hosted Customer Data shall not be obscene or
pornographic. I read that as being about hosting rather than transient
processing, but I’d rather ask than assume.

Is that acceptable? And is there anything you’d want done differently?

I’d be in LHR.

4

Hi, thanks for reaching out/asking!

This use case is OK - since you’re explicitly mentioning you’re not storing this content or serving it from Fly.io but rather sending it to an API / external storage service, this is acceptable, particularly if the content is “lawful adult content”.

Cheers!