GDPR Checker
This module is designed to make it easier to look up if a user appears to be a resident covered by the GDPR based on IP address.
This is only a best-effort guess, no guarantee or claim is made that this information will always be accurate or reliable.
Installation:
pip install gdpr_check maxminddb-geolite2
Usage:
from gdpr_check import Checker
# default uses bundled GeoLite2 DB:
c = Checker()
# optional: pass path to local maxmind GeoIP2 database
c = Checker('/path/to/GeoLite2-Country_20180501/GeoLite2-Country.mmdb')
# check IPs
c.is_gdpr_resident_ip('162.255.119.253') # returns True - Czech Republic IP
c.is_gdpr_resident_ip('98.158.84.74') # returns False - Canadian IP
Metadata
Release files for gdpr_check 0.8
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| gdpr_check-0.8.tar.gz | 2.5 kB | Without provenance | Details for gdpr_check-0.8.tar.gz |
Release files / gdpr_check-0.8.tar.gz
| Download URL | gdpr_check-0.8.tar.gz |
|---|---|
| Size | 2.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
40f4f264005fa9d65161895f9d356698c2764b1574455010f322e0c9a250eaee
|
|
BLAKE2b-256 checksum How to use checksums |
dfd762596ef03f584f5326c051d08a6f1ce815cf340ad0131e654bd4f2ff2c7f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.12.1 pkginfo/1.4.2 requests/2.18.4 setuptools/40.4.3 requests-toolbelt/0.8.0 tqdm/4.28.1 CPython/3.7.0
|
Security for gdpr_check 0.8
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.