The Chomp API maintains specific guidelines around data caching and storage to balance platform performance with data freshness and intellectual property protection.

Caching for Performance

To ensure optimal performance and reduce latency for end-users, short-term caching is permitted for Standard and Premium plans. 

Developers may cache API responses (e.g., using Redis or Memcached) for session continuity and performance optimization, provided the cache Time-To-Live (TTL) does not exceed 24 hours.

Note: The Limited plan does not permit any form of caching.

Permanent Storage of User Data

Applications often need to store food data that a user has specifically interacted with (e.g., a logged meal, a saved recipe, or a favorite food). 

You are permitted to permanently store specific food data (such as Name, Calories, and Macros) if a user has explicitly selected and logged it to their personal history.

This is considered user-generated data. Upon termination of your Chomp API subscription, you are not required to delete these historical user records.

Database Replication Restrictions

While operational caching and user data storage are allowed, you may not use the API to scrape, rebuild, or replicate the Chomp Database. 

Specifically, you may not:

• Cache search results indefinitely to build an offline search index.
• Store data to bypass the API for new, unlogged queries.
• Create derivative database products for resale.

Data Licensing Alternatives

For applications that require offline access, massive-scale processing, or complete database replication, a Data License is required. Purchasing a data license provides a full, downloadable copy of the database to host on your own infrastructure. 

For more details on data licensing or enterprise agreements, please contact our sales team or review the Terms & License Agreement.