Privacy & Security
What client data and PII does Podscribe collect as part of its measurement methodology?
The only PII Podscribe collects from brands are IP addresses.
When the pixel on a brand’s site fires, it sends a request to our AWS servers located in the US. We receive incoming requests and store them in an encrypted format in our Kafka system, which is located in a private VPC. These requests have a Time-to-Live (TTL) of 7 days. We store the complete requests securely for a limited period because we are unable to process all the necessary data quickly enough to maintain a live HTTP connection.
If we receive raw emails (not hashed), we hash them upon receipt, and discard any other PII (other than IP address) in case anything was accidentally shared.
We then store the data in AWS data centers in the US, specifically US-east-1 and US-west-1, encrypting sensitive data. The data is destroyed in 5 years, or if no longer commercially useful, or if deletion is requested.
What data points does Podscribe collect?
Podscribe never collects real names, addresses, billing details, raw emails, or any medical info. Podscribe only relies on anonymous digital identifiers, specifically:
- IP address
- User Agent
- Device Cookie ID
- Page URL
- IDFA or GAID (for in-app events)
- MD5 or Sha256 Hashed Email
- Timestamp
- Order ID / Amount/ Discount Code
What is the script actually doing on my site?
Our script:
- stores via cookies the device ID, landing and referrer URLs
- sends a page view event on every page the user visits where the view tag is placed
- sends a purchase event, when our purchase tag is called
How long does Podscribe store this data?
Until 5 years have passed, no longer commercially useful, or until deletion is requested.
Where is this data stored?
Podscribe stores this data in the US in its AWS cloud datacenters.
What cookies does the Podscribe script set on my site?
Cookie Name | Description | Cookies Used | Expiry |
__podscribe_did | Used by Podscribe to measure the impact of audio campaigns on listeners. | 1st party | 90 days |
__podscribe_[advertiser]_landing_url | Used by Podscribe to store the landing URL of site visitors when measuring the impact of audio campaigns. | 1st party | 90 days |
__podscribe_[advertiser]_referrer | Used by Podscribe to store the referrer URL of site visitors when measuring the impact of audio campaigns. | 1st party | 90 days |
How is Podscribe GDPR compliant?
Podscribe technical storage and processing of data is GDPR-compliant, but Podscribe needs to have a GDPR-compliant Data Privacy Agreement in place with the advertiser. The advertiser must also have certain measures in place on their website.
Email support@podscribe.com for more info.
Powered by