Privacy Policy
How Pogclip handles account information and uploaded media.
Last updated:
Smart Lazy LLC operates Pogclip. Contact support@pogclip.com about privacy, deletion or access to your data.
Information we use
We use your name, email address and sign-in records to provide your account. Passwords are stored as hashes. Uploaded video and audio, transcripts, captions, selected moments, edits and exports are used to provide clip processing. We keep project status, minute balances, usage history and billing references so we can run the service and resolve problems. Operational logs can include request details and errors.
We send verification and password-reset email and project completion or terminal-failure notices. A project notice is attempted once for each terminal state; email delivery is not guaranteed. Newsletter auto-subscription and Discord notifications are disabled in this deployment.
Providers and storage
- Cloudflare hosts the app, stores account and project data in D1, stores private media and preview assets in R2, provides cache storage, and sends transactional email through Cloudflare Email Service.
- Oracle Cloud hosts the processing VM, which downloads source media and runs transcription, highlight preparation and rendering tasks.
- APIMart processes audio for transcription and transcript content for AI highlight selection. Its model services receive the material needed for those tasks and handle it under their own terms and policies.
- Stripe processes payments and manages subscriptions. We store customer, invoice and subscription references, not full card details.
These providers can process information in countries other than yours. We do not sell your uploaded content. Processing providers receive content as needed to perform their tasks. Google sign-in is offered only when configured; if you choose it, Google supplies the account details needed to sign in.
Media access requires ownership checks or a private signed link, normally valid for 15 minutes. Anyone with a valid signed link can use it until it expires or the underlying file is deleted. Do not share private media links publicly.
Retention and your controls
Uploaded sources and rendered exports expire 30 days after the project is created. Preview assets are removed with the source. Expired projects show an expired status instead of playable media. An hourly cleanup removes expired objects; failures are retried on a later run. Unused or unfinished uploads are removed after 30 days. Account and project metadata remain until deletion.
The project page lets you delete that project's clips, exports and source files. If a source is shared by other projects in your account, it remains until those projects also expire or are deleted. Usage ledger entries remain with their project link removed. Shared demonstration media is retained for other users.
Account deletion removes your owned clip data and R2 files before deleting your authentication account. A subscription must have ended before deletion; use Billing to cancel it. Stripe can retain transaction records under its own retention obligations. Signing out or cancelling a subscription does not otherwise delete your content.
The processing VM removes temporary job media when a job ends. Cached AI responses, transcripts and diagnostic records on the VM currently require separate operational removal; contact support to request it. Deleting a project in the app does not itself erase those caches or a provider's independent records. Service logs and provider backups follow their respective retention policies.
Contact support for access, correction, or deletion requests that the app does not provide. See the Cookie Policy for browser storage and optional analytics.