No public evidenceYapsody and GDPR
CertReports found no public GDPR evidence for Yapsody as of unknown date. This does not mean the vendor is non-compliant. It means CertReports found no public evidence at the last check.
Evidence
- Kind
- listing
- Scope
- As an event ticketing system, we store we store the following personal data for the reasons indicated below: Names -- (i) Identify purchasers or sellers to prevent fraud; (ii) search transactions by purchaser name; (iii) reconcile electronic payment transactions against merchant account statements. Name of a purchaser is disclosed to (i) a seller from whom the purchaser has purchased merchandise and (ii) the payment gateway processing the electronic payment transaction. Phone Numbers -- Contact sellers or purchasers (i) about anything important relating to transactions or anything related to their use of the ticketing application that may impact them; or (ii) to resolve customer support inquiries. Email Addresses -- (i) Identify purchasers or sellers to prevent fraud; (ii) username for online accounts; (iii) send transaction confirmations; (iv) search transactions by purchaser's email address; (v) contact sellers or purchasers about anything important relating to transactions or anything related to their use of the ticketing application that may impact them; (vi) resolve customer support inquiries; (vii) contact sellers or purchasers about non-essential matters (e.g., marketing emails) they have opted into. Email address of a purchaser is disclosed to a seller from whom the purchaser has purchased merchandise Billing Address -- (i) an element for determining country of origin for charging GST; (ii) Identify verification to prevent fraud; (iii) troubleshoot issues related to processing of electronic payment transactions requiring billing address. Billing address is disclosed to (i) a seller from whom the purchaser has purchased merchandise and (ii) the payment gateway processing the electronic payment transaction. Last 4 Digits of Credit Card -- (i) appears on transaction receipts; (ii) identity verification to prevent fraud; (iii) reconciling electronic payments against merchant account statements; (iv) troubleshooting issues related to processing of electronic payment transactions. It is disclosed to (i) a seller from whom the purchaser has purchased merchandise and (ii) the payment gateway processing the electronic payment transaction. IP Addresses from which Electronic Payment Transactions are Performed -- (i) Fraud prevention; (ii) troubleshooting issues related to processing of electronic payment transactions.
| Source | Captured | Quote | Links |
|---|---|---|---|
Data Privacy Framework list Official registry · HTTP 200 | 17 Sep 2026 | Yapsody, Inc.: Inactive | Live pagesha256 9c5370710f |
What GDPR means, and what it does not
"GDPR compliant" is a claim, not a certification. The verifiable facts are a public DPA, SCC usage, an EU representative, data residency options and a Data Privacy Framework listing.
Read the GDPR guide and browse all vendors with evidenceQuestions buyers ask
Is Yapsody GDPR compliant?
There is no GDPR certification in general use. The verifiable facts are a public data processing agreement, standard contractual clauses, an EU representative and a Data Privacy Framework listing. See the legal artefacts and the DPF row on this page, each with its capture date.
How does CertReports verify this?
Every state carries a capture date, a source and a snapshot link. Registry rows come from the official registry data; vendor statements come from the vendor’s own page or trust centre; nothing is inferred. Vendors can dispute any row and corrections ship within two business days.
Alternatives with GDPR evidence
Similar vendors (shared product tags) whose GDPR row is verified or vendor-stated, ranked by similarity.
No same-category vendor has GDPR evidence in the index yet.