How would we integrate your systems into our cookie settings?
We have a feature whereby the browsers locations is displayed on our website. However, as I’m sure you can appreciate, we will need to be able to give users the option for your systems NOT to track their locations.
We currently use a third-party cookie compliance system, so it’s simple a case of having IPInfo’s API’s to be able to communicate with our Cookie Compliance Systems
Privacy compliance solutions (like CookieYes, which you’re using, or Termly which we use on our website) are frontend solutions, they operate in the context of a browser session. CookieYes will collect consent information from your users which your frontend code is then able to use to determine which behaviour should be triggered. For example, if a user does not consent to third-party tracking then you would not load third-party tracking scripts (e.g: Google Analytics).
Privacy compliance solutions are relevant when using IPinfo if you are using IPinfo in the user’s browser. For example, if you have a piece of JavaScript which makes a request to ipinfo.io/json to capture the user’s location for your analytics, you would first capture consent from the user using CookieYes and then load the JavaScript once you have received the consent.
Reviewing your website, I do not see any requests made to ipinfo.io, and reviewing your token, I can see that 100% of your requests are being made via Python which is a backend programming language. I think this most likely means that there is misaligned expectations: privacy consent tooling is only applicable in the browser, it does not apply to the backend of an application, as consent information is stored in the browser and we do not receive any requests from your users.
Can you share more about how you’re using IPinfo and what you’re hoping to achieve? We can help identify the correct solution for your use-case.
As you’re making the request to our API from your server, we do not receive any information about your user, only the IP address you provide to the getDetails method. From our system’s perspective, your server is asking us for information about an IP address without any information about where that IP address originated.
(note: if no IP address is provided to the getDetails method then the IP address of the caller (your server) will be used to provide the details.)
If you would like to control whether or not a request is made to our API, you can use the consent information from CookieYes. According to the CookieYes documentation (“How to handle the server side cookies when using CookieYes?”) you can access the visitor’s consent information in the cookie cookieyes-consent which contains the different types of consent.
An alternative option for customers operating in sensitive fields (e.g: healthcare, finance) is our Data Downloads which do not communicate with our server.
Its potentially related, however, I have updated our code to your suggestion in the following manner, which will return an Exception if there are any issues:
I think that’s likely due to the return None. I’m not familiar with Django but according to the documentation:
The context_processors option is a list of callables – called context processors – that take a request object as their argument and return a dictionary of items to be merged into the context. In the default generated settings file, the default template engine contains the following context processors […]
The simplest option would be to return an empty dictionary instead of None or you could return a “default” country that you’d like to use in cases where the call to our API fails.
I give up with this, its becoming the exception rather than the norm that something actually does what you ask it to, & I’ve had enough of troubleshooting things.
Your never know, one day a miracle might happen and something might actually do as it’s told.
Until then, I’ve had it with having the proverbial brown stuff flung in my face.