First question

The API ToS states:

YOU SHALL NOT

3) Cache any TMDb metadata or photos other than for reasonable periods in order to provide your service.

With my application I would need to store the series/movies TMDb-ID aswell as TITLE permanently in a database. Does this count as TMDb metadata and is therefore forbidden? If the above is not forbidden, is it also okay to store the series/movies genres in the database? Without that posibility a filtering operation by genre would be very heavy on the api calls, and thus impossible.

If any of the above is not ok, would it be possible to get an exception from these rules? I would have planned to continue to build on this project, but if it's not possible according to the ToS it would be really nice to at least get an exception to these rules that I can use only during the time I need to show up my project for the course.

Second question

Since this is a school project, I would need to share my api key with the course teacher. Is this ok? If not, is it possible to get a temporary key that I could share?

My project

My project is a series/movies listing site, a la MyAnimeList that utilizes TMDb API to add and get information about series/movies. It does not have a focus on supplying a complete database over series/movies so it is not like MyAnimeList (or TMDb) in that regard, just the listing part. Most data, such as overview, rating e.t.c. is always received dynamically with the TMDb API when a user wants information about an item in their list, but certain kinds of information (like ID, Title and to some degree genres) would be in the least very impractical (and for the ID completly devastating for the project) if they could not be stored in a local permanent database.