Your draft is measured, answered, and discarded
Eyelicium needs an image, title, and channel context to run a review. It does not need to build a library of user drafts.
Request data
Uploaded images, titles, and computed draft features live in memory for the request and are not written to persistent storage. Inputs are not used to train or fine-tune models.
Public channel data
Channel assessment reads public YouTube metadata and thumbnails. Eyelicium does not request OAuth access, owner analytics, click-through rate, or A/B-test exports.
Rate limiting
The proxy reduces an IP address to its network prefix and hashes it before forwarding a request. The hash is used for abuse protection, not user identification.
Deletion
Because submitted drafts are not retained after the response, there is no stored draft to delete. Questions can be sent to jpaul.fernandez18@gmail.com.