Security and Data Handling
AI Podcast Clipper handles private podcast uploads through scoped storage, signed URLs, authenticated dashboard access, and explicit creator review before publishing.
File handling
How uploaded media is protected
Uploads and generated clips are treated as private workflow assets, not public media pages.
Private upload path
Uploads are written to user-specific S3 prefixes and are not exposed as public bucket objects by default.
Signed access links
The app uses presigned URLs for upload and playback/download access rather than permanent public file URLs.
External processors are scoped
Processing services receive only the media references needed to generate clips, captions, and framing output.
Creator-controlled cleanup
The dashboard supports deleting uploaded files and generated clips when creators no longer need them.
Boundaries
What this security page does and does not claim
Current protections
Per-user S3 prefixes, signed URLs, authenticated dashboard access, and delete controls are part of the product workflow.
Creator responsibility
Creators remain responsible for source rights, guest consent, publishing context, and final review before distributing clips.
Frequently asked questions
- Are uploaded videos public?
- No. Uploaded files are stored for authenticated processing and are not exposed as public bucket objects by default.
- How are files accessed by the app?
- The app uses signed URLs for upload, playback, and download operations so access can expire instead of relying on permanent public links.
- Should creators review clips before publishing?
- Yes. Creators should confirm rights, context, caption accuracy, and brand fit before publishing any generated clip.