Privacy Policy

Effective: 10 June 2026

[OPERATOR: review with counsel before launch — add controller legal entity + address, confirm processor list and DPAs, and complete the DPIA required by Doc 5 §25.2 before public launch.]

1. Who is responsible

BattleMyPhoto processes photos of real people, which is personal data. We act as the data controller. Contact for privacy and removal requests: [OPERATOR: add privacy email, e.g. privacy@battlemyphoto.app].

2. What we collect

  • the photo you upload and processed versions of it;
  • the generated video and its thumbnail;
  • nicknames you optionally enter for the people in the photo;
  • an anonymous session ID (cookie) and, if you create an account, your email;
  • a payment customer reference if you buy credits (handled by Stripe);
  • generation logs, moderation results, and consent records (with timestamps);
  • product analytics events (no photos, no email addresses in event data);
  • reports and deletion requests you submit (including an optional contact email).

We do not collect contacts, precise location, social media credentials, or profile data beyond the above.

3. Why we process it

  • To create your video — uploading, person detection, AI animation, and delivery (based on your consent, confirmed at upload).
  • For the other people in your photo — we rely on our legitimate interest in providing a consent-gated parody service, protected by: your confirmation that everyone agreed, short retention, an easy report and removal channel for anyone depicted, and no training on your content.
  • Safety — automated moderation of uploads and outputs, abuse prevention, and report handling.
  • Payments, accounting, fraud prevention — legal obligations and contract performance.

Our pipeline detects where people are in a photo (bounding boxes) to animate them. We do not create face-recognition templates and we never try to identify who the people in your photo are.

4. Who processes data for us

  • hosting and database providers (Vercel, Supabase) and private file storage;
  • an AI video generation provider that receives the processed photo to animate it [OPERATOR: name the chosen provider and its data-processing terms once O-002 is decided];
  • AWS Rekognition for person detection and image safety checks;
  • OpenAI moderation for image safety checks;
  • Stripe for payments (we never see your card details);
  • PostHog for product analytics (EU-hosted; no photos or emails in events).

Some providers may process data outside the EU. Where that happens, transfers are covered by appropriate safeguards. [OPERATOR: the AI video provider shortlist includes non-EU (China-based) model providers — verify EU data-transfer terms (DPA / EU-hosted inference) before launch per Doc 5 §25.2.5; update this section with the result.]

5. How long we keep things

  • original and processed photos: deleted after 7–30 days;
  • generated videos: kept while your result link is active;
  • deleted content: access removed immediately;
  • reports: minimal record kept for abuse prevention;
  • payment records: kept as legally required;
  • consent records and safety logs: kept as required for accountability.

6. No AI training on your content

Uploaded photos and videos are not used to train AI models. If this ever changes, it will only happen with your explicit opt-in.

7. Private by default

Your photos and videos are private — stored in private buckets and reachable only through your result link. We never feature user content in marketing or social media without a separate, explicit public-use permission.

8. Your rights

  • Delete — every result page has a Delete button that removes the photo and video from access; you can also email us to request deletion of anything connected to you.
  • If you appear in someone else’s upload — you can object without an account: use “Report” on the result page and choose “I am in this photo and did not consent”, or email us. Default action is fast removal — we do not demand excessive proof.
  • Under the GDPR you also have rights of access, rectification, restriction, portability, and complaint to a supervisory authority. Contact: [OPERATOR: privacy email].

9. Cookies

We use an anonymous session cookie to run the product (free-generation limit, your results) and analytics cookies/identifiers for product measurement. [OPERATOR: confirm consent-banner requirements for the analytics identifier with counsel.]