...
Cachetur.no is built with the Privacy First principle in mind, and we do not fetch more data than we need from the API.
In fact, you will have to explicitly enable features, before we will fetch certain data.
Shared quotas
Cachetur.no have to share the same quota as all other apps you use, which is currently 16 000 caches per 24 hours (starting from the first cache download).
This means that if you download 16000 caches in another API app (like GSAK), you won't be able to get new caches added to cachetur.no until your quota resets.
Cachetur.no will typically use anywhere from 0 to a couple thousand refreshes per day, for active users with many active trips/lists.
Remember that fetching a bookmark list will count towards your daily quota.
Data we fetch
We fetch your basic profile information, both to be able to determine what you are able to access (premium vs non-premium) and to personalize your experience (profile photo and location).
...
Older caches are refreshed based on the status of the trip (active, upcoming, draft), the time since visit, total number of caches in your trips/lists, general site load and some other factors.
You can also switch of off automatic refresh of caches in your trips/lists, which will make cachetur.no use less of your quota. This can be done on a per-trip/list basis.
...
You can view the current remaining quota on your profile page.
The API has no method to view the usage, so this is unfortunately all we have to show you. We do not have the resources to track all API calls and their results (not all calls are successful).
