Podpally

GDPR overview

There is no mention of the GDPR anywhere on Podpally's site, and none in any page collected. No privacy policy is published, no Article 27 representative is named, no data protection officer is identified and no contact address is given. The vendor never claims compliance, and never states non-compliance either: the subject is simply absent. What can be observed, from the page source rather than from any commitment, is the technical stack: Supabase for database and authentication, PostHog on its European instance, a self-hosted Plausible analytics endpoint and Stripe for payment. The web server resolves to Hetzner in Nuremberg, Germany. These are network observations, not vendor undertakings, and they carry no legal weight for a European buyer.

Who owns the data?

Podpally publishes no terms and conditions, so data ownership cannot be established from any accessible document. The login screen at app.podpally.com shows Terms of Service and Privacy Policy links, but both point to a dead anchor and open nothing, and no terms page exists on podpally.com today or in the Wayback archive since November 2024. Nothing therefore states who owns the material you submit, who owns the intros, insights and questions the tool generates, or what the vendor may do with either. The point matters more than usual here, because the tool processes the LinkedIn profiles and recent posts of third parties, people who are not the account holder.

Reuse rights

No published document says whether you may reuse what Podpally generates. With no terms in circulation there is no stated licence over the intros, insights and interview questions the tool produces, and no stated restriction either. Two signals suggest downstream use is expected rather than forbidden: the Pro and Agency plans include a PDF export, which only makes sense outside the platform, and the Agency plan is sold explicitly to teams working on their clients' shows, which is commercial reuse by definition. None of this is confirmed in writing, so any professional dependency on the output rests on an unwritten understanding until the vendor publishes terms.

Hosting summary

Podpally publishes nothing about where data is hosted. There is no trust or security page, no privacy policy and no statement of jurisdiction, so no processing location is committed to by the vendor. What can be observed from outside is purely technical. The web server resolves to 46.225.108.20, an address operated by Hetzner Online GmbH in Nuremberg, Germany. The page source shows a Supabase backend handling database and authentication, PostHog analytics pointed at its European instance, and a self-hosted Plausible endpoint. Payment runs through Stripe. None of this is a promise. Infrastructure can be moved without notice, and a German IP address tells you nothing about where user content, guest research or account records are actually stored or replicated. No subprocessor list, no standard contractual clauses and no data processing agreement are offered. A buyer with hosting requirements should treat this area as undocumented and put the question to the vendor before committing.