contact@editsqlite.com — answered by the person who built it
Worth writing about: a database or dump that wouldn't open (quote the exact refusal — the errors name their reasons — and where the file came from). An export the official engine rejected: that's a top-priority defect against the certification bar, so describe everything and attach nothing. Console queries that surprised you — odd behavior in three hundred lines is findable and fixable within days. And feature votes: joins in the console, overflow-row writing, and index regeneration are all on the maybe list, waiting on demand.
Out of scope, honestly: connecting to live MySQL or Postgres servers — browsers can't speak those protocols and shouldn't hold your credentials; dump, edit, reload is the honest loop. Editing encrypted databases — keys stay between you and your own software. And recovering corrupted files — rebuilding prevents corruption here, but repairing damage from elsewhere is forensics, an entirely different job.