The project is great, honestly. But I just put a space in the email by mistake, it wasn't censored.

Great catch! Emails with spaces around @ (like "test @ example.com") slip through. This is a classic obfuscation bypass.

The current pattern intentionally matches RFC 5321 compliant emails (no spaces). Adding support for spaced variants creates a trade off. wewould catch more bypass attempts but also increase false positives on text like "send @ 5pm". I'll add this to the roadmap. Appreciate the feedback ! this is exactly the kind of edge case I need to hear about to make my api more better

1000 API Calls daily for $6.99 (~$11.00~) This seems terribly useless to me, except for very small projects, which probably have other more effective solutions, and are made for. ( change my mind, I'm open )

I am also thinking of the change of my plan, but not more than 2-3k calls/day. This pro plan has access to an unlimited Sheets limit as well.

The idea of this application is to help small projects and not for mid-to-high range projects

Average experience with Deutsche Bahn.

I'm french, my first trip in this country was epic. First time going to Köln ( Cologne ), the train back to the airport never arrived, with no explanation. I was literally stranded in another country without money.