VicPods How VicPods handles data, what users control themselves, and how privacy is built into the product.
Create account Create
Privacy Policy

Privacy that stays product-minded, not surveillance-minded.

VicPods should work like a creator tool, not an ad network. This policy explains what data VicPods uses, why it uses it, who can access it, and what controls users can exercise directly.

Create account Read Terms Cookie Policy Data Rights
Privacy promise

VicPods is not built around hidden profiling.

The app uses limited first-party analytics for product operations, support, and security. It is not designed to monetise personal data through ads.

Self-serve controls

Settings should matter.

Users can change profile details, password, theme, language, billing settings, and now delete their account directly.

Admin access

Restricted, need-to-know access only.

Product admins may access limited account and activity data for support, security, billing, and operational needs. That access should stay limited and accountable.

01

What VicPods collects

VicPods collects the information needed to run the service: account details such as name and email, authentication data, subscription status, podcast planning content you create inside the product, and limited product activity needed for security and operations.

  • Account data: name, email, password hash or federated login identity
  • Product data: series, themes, episodes, Pantry ideas, launch assets, settings
  • Feedback and support data: feature requests, bug reports, product feedback, and related contact details you choose to send
  • Billing data: Stripe customer and subscription references, not raw card numbers
  • Operational data: session cookies, visitor identifier, IP address, device/browser metadata, page views, login and signup events
02

Why VicPods processes data

VicPods processes personal data to provide the product, secure accounts, operate subscriptions, deliver email and support, and improve the service responsibly.

  • To create and maintain your account
  • To authenticate sign-in and verify account ownership
  • To generate AI-assisted podcast content you request
  • To review feedback, fix issues, and decide what product improvements to prioritize
  • To process subscriptions and billing with Stripe
  • To prevent abuse, fraud, or security issues
  • To understand product usage through first-party analytics, not ad tracking
03

Lawful bases

Depending on the context, VicPods relies on contract, legitimate interests, legal obligations, and consent where required. For example, billing and account operations are usually necessary to perform the service, while certain consent-driven technologies may depend on your cookie preferences.

  • Contract: running your account, billing, and creator workflow
  • Legitimate interests: product security, abuse prevention, first-party service analytics, and support
  • Legal obligations: financial records, compliance, and dispute handling where required
  • Consent: where optional technologies or disclosures require it
04

What VicPods does not do

VicPods is intended to be closer to a user-first product model than an advertising platform model.

  • VicPods does not sell personal data
  • VicPods does not run third-party ad profiling inside the product
  • VicPods does not use creator content as a behavioural ad network feed
05

Who can access data

Access is limited to authorised people and processors who need it to operate VicPods. Admin access should follow a need-to-know principle and stay restricted to support, security, billing, and product operations.

  • Internal admin access is restricted and not public
  • Stripe processes subscription and billing operations
  • Google may process authentication if you choose Google sign-in
  • Email delivery providers process service emails
  • AI providers may process prompts and content when generation features are used
06

Cookies and first-party analytics

VicPods uses essential session cookies, a first-party visitor identifier, CSRF protection, and limited product analytics to understand visits, signups, and account activity. Cookiebot is used to manage consent where applicable.

  • Essential cookies support sign-in, sessions, and security
  • A first-party visitor ID helps distinguish repeat visits and product activity
  • Analytics are used for product operations and improvement, not ad resale
07

Retention and deletion

VicPods keeps data only as long as needed for the service, support, security, billing, and legal compliance. Users can delete their account from Settings. In-app account data tied to the user account is removed from VicPods when deletion succeeds, but some processor-side or legally required records may remain for billing, fraud prevention, or compliance.

  • Active account data is retained while your account is in use
  • Users can self-delete their account from Settings
  • Some billing or compliance records may remain where legally required
08

Your rights and controls

If you are in the EU/EEA or another region with similar privacy rights, you may have rights of access, correction, deletion, restriction, objection, and portability, subject to local law and any applicable exceptions.

  • Edit profile information from Settings
  • Change your password and account defaults from Settings
  • Manage billing through Stripe
  • Delete your account from Settings
  • Contact VicPods at privacy@vicpods.com for privacy questions or formal data-rights requests
  • Open the dedicated Data Rights page for the request workflow
09

Complaints and supervisory authorities

If you believe VicPods has handled your personal data incorrectly, contact VicPods first so the issue can be reviewed. If you are in the EU/EEA, you may also complain to your local supervisory authority, including the Irish Data Protection Commission where applicable.

  • Help Center: first contact point inside the product
  • Supervisory authority complaint rights remain available under applicable law