Single named operator. No team of fifty. Direct accountability.

Meet the Team

Last updated: May 2026

The "team" here is one person. We're not pretending there's a fifty-strong engineering org. The Site is a small operation with a named operator who handles editorial decisions, infrastructure maintenance, and reader correspondence directly.

Giovanni Picaro — Operator

Role: Sole publisher and operator. Responsible for the format catalogue, the Laravel infrastructure, AdSense ad-network configuration, and reader / abuse correspondence.

Background: Years of professional experience in customer support, technical operations, and digital publishing. iloveimg.online is one of several content sites in a small portfolio. Self-taught working knowledge of Laravel, image processing fundamentals (compression trade-offs, colour profiles, format-specific quirks), and Linux server administration.

What Giovanni handles directly:

  • Format-catalog editorial. Which formats to add, which to deprioritise, when to add a new conversion pair.
  • Conversion-engine maintenance. ImageMagick / libvips / libheif / libavif / libraw library updates, security patches, server administration.
  • Format-fidelity testing. When a new conversion pair is added, output is verified against ImageMagick command-line and visual reference outputs.
  • AdSense operations. Publisher-account management, ad-density calibration, category exclusions, ads.txt maintenance.
  • Reader correspondence. Direct response to substantive correspondence at the four public addresses.
  • Data-protection role. Giovanni is the data controller for personal data processed through the Site (per Privacy Policy).
  • Bug response. Reader-reported conversion errors, with corrections per Corrections Policy.
  • DMCA / takedown response. Per DMCA.

What Giovanni is not

  • Not a credentialled imaging scientist. Working knowledge of compression theory and colour management at the user-of-libraries level, not at the formal-research level.
  • Not affiliated with any image-processing library author. We use ImageMagick, libvips, libheif, libavif — we are users of these libraries, not their developers.
  • Not affiliated with Adobe, Apple, Google, or any commercial format-licensor. We support HEIC, AVIF, WebP — supporting a format does not mean partnership with the format's promoter.
  • Not iLoveIMG.com. Different operator. See Brand Identity.

What iloveimg.online does not have

  • No 24/7 ops team. Substantive email is read during European business hours; urgent safety / DMCA matters are reviewed regardless of time of day.
  • No engineering organisation. One operator with the conversion engine running on standard libraries and a Laravel front-end.
  • No customer-support hotline. No phone support; email at the four public addresses is the channel.
  • No formal certification (SOC 2, ISO 27001). The Site is a free public utility, not an enterprise service.

Why a single-operator model works for this Site

  • Named accountability. Decisions traceable to a person, not "the team".
  • Editorial consistency. Format choices, copy voice, ad-density decisions all applied with one editorial sensibility.
  • Direct correspondence. Substantive reader email reaches the decision-maker, not a tier-1 support layer.
  • Fast iteration on bugs. No ticket queue / sprint-cycle delay between report and fix.

Where the limits show

  • Response time to general email is days-to-week, not hours.
  • Outages outside European business hours may be longer-resolved.
  • Format support can grow only as fast as one operator can vet new conversion pairs.
  • If you need an SLA-backed image-conversion API, we're honestly not the right fit — CloudConvert and similar commercial services exist for that case.

How to reach the operator

  • info [at] iloveimg [punto] online — general inquiries, format requests, partnership inquiries.
  • dmca [at] iloveimg [punto] online — copyright takedown.
  • privacy [at] iloveimg [punto] online — data-protection requests, parental concerns.
  • abuse [at] iloveimg [punto] online — security concerns, problematic ads, image-misuse reports, urgent safety matters.

Related pages: About Us · Our Approach · Contact Us · DMCA · Brand Identity

Application offline!