pop-cam is a small, independently run product. This page says plainly how your data is handled and protected, what we do and do not do, and where to go if something looks wrong. We hold no formal security certification such as SOC 2 or ISO 27001 and we do not claim one here; what follows is what is actually in place.
1. Your content
- Encrypted in transit. Every request to pop-cam.com and to our storage uses HTTPS (TLS).
- Encrypted at rest. Uploaded photos and generated images and videos are stored in Cloudflare R2, which encrypts objects at rest. The database on Supabase is encrypted at rest.
- Private by default. Stored files are not publicly listable. They are served through signed, short-lived links or our own image endpoint, which checks the request.
- Sent to AI providers only to fulfil your request. A photo goes to the model provider named on the tool you used, for that generation, and nowhere else. We do not use your content to train models. See Subprocessors.
- Not used for marketing without permission. Images appear in our public showcase only when we add them deliberately, with the creator's agreement.
2. Your account
- Authentication is handled by Clerk. We never see or store your password; social sign-in uses the provider's own login.
- API keys (
pk_ tokens) are tied to your account and can be revoked at any time from /developer. Treat them like a password: anyone holding one can spend your credits. - Access to production systems is limited to the people who run pop-cam, with multi-factor authentication on every provider console.
3. Payments
Card payments are processed by Stripe and in-app purchases by Apple. Your card number never reaches our servers. We store only what we need to run your subscription: Stripe's customer and subscription identifiers and your credit balance.
4. Retention and deletion
- Your generations stay in your gallery until you delete them or close your account.
- When you ask us to delete your account we remove the account record, its generations and uploaded files from our primary storage within 30 days; copies in backups expire on the backup schedule of our database and storage providers.
- AI providers receive content for inference only and are not instructed to keep it; their own retention periods for abuse monitoring are set out in their terms.
- To request deletion or a copy of your data, use the privacy rights request form.
5. Availability and monitoring
- The site runs on Vercel's managed platform, which handles scaling, TLS and failover of the serverless functions for us.
- A daily automated check exercises every external dependency end to end, including a real image generation, and alerts us when anything fails.
- Failed generations are refunded automatically; a credit is only kept when a result was delivered.
6. Privacy and compliance
7. Reporting a security issue
If you believe you have found a vulnerability, email [email protected] with the subject "Security report". Please give us a reasonable time to fix it before disclosing it publicly, and do not access other users' data while testing. We reply to security reports within two business days, and we will credit you if you want us to.
8. Incident notification
If a security incident affects your personal data we will tell you by email without undue delay, and within 72 hours of confirming it where the law requires, describing what happened, what data was involved and what we are doing about it.