Skip to content
PodReel

Security & Data Handling

Plain answers about what happens to your audio.

On this page13 sections

This document is a template generated from the site configuration. Bracketed placeholders must be filled in and the whole text should be reviewed by a qualified lawyer before launch.

1.Our approach

Your recordings are unreleased work and may include other people's voices, so we treat them carefully. This page describes the practices [Your Legal Entity Name, Registered Address] aims to follow to protect PodReel and the data you give it. It is a description of intent and current practice, not a guarantee, and it does not claim any third-party certification we do not hold.

2.What we process

  • Uploaded audio file or episode link
  • Transcript generated from the audio
  • Your clip selections and template choices
  • Account details and billing status (card numbers are handled only by Stripe)

We keep the amount of data we handle to what is needed to make your clips.

3.Encryption

  • In transit: traffic between your browser and the Service uses HTTPS (TLS).
  • At rest: files and databases are stored on infrastructure that encrypts data at rest.
  • Passwords: stored using a one-way salted hash, never in plain text.

4.Access controls

  • Your audio and clips are stored in private storage and are not publicly listed. Files are only reachable through your authenticated workspace or time-limited links.
  • Our staff access to production systems is limited to what each role needs, uses strong authentication and is logged.
  • We do not listen to your audio except where you ask us to help with a support issue or where needed to investigate abuse or a security incident.

5.Infrastructure and application security

  • The Service runs on established cloud providers with industry-standard physical and network protections.
  • The marketing site is delivered as static files, which reduces its attack surface.
  • We keep dependencies up to date, apply security patches in a timely way, and review code changes before release.
  • Secrets and keys are kept out of source code and rotated when needed.

6.Retention and deletion

  • Uploaded audio
    What happens
    Uploaded audio is deleted 30 days after your last render, or sooner if you delete it yourself.
  • Episode or clip you delete in the app
    What happens
    Removed from active storage and from our systems under the normal deletion cycle
  • Account closure
    What happens
    Your content is deleted within the retention periods in the Privacy Policy
  • Backups
    What happens
    Roll off on their normal schedule, after which deleted data is overwritten

To request deletion of everything we hold about you, email privacy@podreel.example.

7.Model training

You can opt out of having your content used for model training at signup or later. See the Privacy Policy. Providers that process your audio for us are instructed not to train their own models on it where their terms allow us to require that.

8.Payment security

Payments are processed by Stripe, a PCI DSS Level 1 certified payment provider. Card details go straight to Stripe. We never see or store full card numbers.

9.Monitoring and incident response

  • We monitor the Service for unusual activity and keep logs that help us investigate problems.
  • If we confirm an incident affecting your personal information, we will tell affected users and the relevant authority without undue delay, and within the time the law requires (for example 72 hours for regulators under GDPR), with what happened, what data was involved and what to do.

10.Sub-processors

These providers process data for us. Each is bound by a contract that requires appropriate protection.

  • Cloudflare, Inc.
    Purpose
    Hosting, CDN and file storage
    Location
    Global edge (US / EU)
    Transfer safeguard
    EU–US Data Privacy Framework, SCCs
  • Stripe Payments Europe, Ltd.
    Purpose
    Payment processing (we never see card numbers)
    Location
    Ireland / US
    Transfer safeguard
    EU–US Data Privacy Framework, SCCs
  • [Transcription provider]
    Purpose
    Speech-to-text for your transcript
    Location
    [Region]
    Transfer safeguard
    [SCCs / DPA]
  • [Email provider]
    Purpose
    Transactional email (receipts, password reset)
    Location
    [Region]
    Transfer safeguard
    [SCCs / DPA]

11.Your part

  • Use a strong, unique password and keep it private.
  • Only upload audio you have the right to use, and get consent from guests.
  • Be careful with exported files and links you share, because anyone with a file can post it.
  • Tell us right away if you think your account is compromised.

You are responsible for holding the rights to any audio, music or voices you upload. PodReel does not clear music or third-party content for you.

12.Report a vulnerability

If you think you have found a security issue, email security@podreel.example with the details and steps to reproduce. Please:

  • give us a reasonable time to investigate and fix before you share details publicly;
  • avoid accessing, changing or deleting other people's data, and stop once you have shown the issue;
  • not run denial-of-service tests or social-engineering attacks.

We will acknowledge reports promptly, keep you informed and not take legal action against good-faith research that follows these rules. We do not currently run a paid bounty programme.

13.Questions

General questions: contact form or support@podreel.example. Security reports: security@podreel.example.