Privacy Policy
Effective date: 10 November 2026
Last updated: 10 November 2026
This Privacy Policy explains how PetVideoAI, a service run by an individual developer as a sole trader ("we", "us", "our"), collects, uses, shares and protects personal information when you use petvideoai.com, including our PetVideoAI pet-video generator and any related pages and services (together, the "Service").
The Service lets you upload a photo of your pet and uses artificial intelligence to generate a short video from it.
Key points
- We only need a few things from you: your Google account email and ID (you sign in with Google), the pet photo you upload, and basic purchase and technical information. When you're signed in, we show your Google profile picture in the site header so you can see which account you're using. You can hide it at any time in Account.
- Your uploaded photo is deleted automatically from our storage 24 hours after upload, unless our safety check holds it for a short human review (see Section 9). Our third-party image safety-check provider doesn't keep it by default, with limited exceptions (see Section 5).
- Your generated videos stay in your account until you delete them. You can delete any finished video yourself in My videos at any time.
- Deleting your account deletes your data. Your email, photos and videos are deleted. The records we must keep for accounting are irreversibly anonymised, so they are no longer linked to your email or account. Database backups expire within 30 days. A minimal chargeback block list, and the limited order-linked identity hashes described in Section 9, are the only exceptions (see Section 9).
- We only send transactional emails, such as order confirmations. We don't send marketing emails. Everything else about your account, videos and purchases is shown on the site.
- We don't sell your personal information, and we don't use your photos or videos to train AI models. We use Google Analytics to measure visits (in the EEA, UK and Switzerland only if you agree). Microsoft Clarity, which Microsoft may also use for advertising, runs only if you agree to it (see Section 12).
- Videos are AI-generated. Downloaded videos carry a machine-readable "AI-generated" tag (see Section 6).
- We never see or store your full card number. Our payment providers handle payments.
1. Who we are (data controller)
The controller responsible for your personal data is:
PetVideoAI (run by an individual developer as a sole trader) Email: support@petvideoai.com
EU representative (GDPR Art. 27): Not appointed. UK representative (UK GDPR Art. 27): Not applicable (not appointed). Data Protection Officer: We are not required to appoint a Data Protection Officer. For privacy questions, contact us at support@petvideoai.com.
2. Personal data we collect
| Category | What it includes | Source |
|---|---|---|
| Account data | Your Google account email address (Google must have verified it) and your Google account ID (a stable number Google uses to identify your account); internal user ID; account creation date; last-activity date; credit balance; session identifier. We don't receive your Google password. When you sign in, Google also sends us the web address of your Google profile picture. We keep that address with your sign-in session and use it only to show your picture in the site header. We don't store the picture itself. Google may also send your name and other basic profile details; we discard them at sign-in and don't use or keep them. | You; Google, through Google Sign-In |
| Uploaded photos | The photo you upload (your pet and, for templates that support it, people); its file type, dimensions and size; the result of our automatic safety check (for example, "accepted", "possible minor", "unsafe image" or "held for review"); and, for photos that show people, your confirmation that every person who will appear as a subject of the video is 18 or older and that you are that person or have their permission (the time and the version of the text you confirmed, no image). When you upload, our server removes embedded metadata such as GPS location, camera model, timestamps and comments (EXIF/XMP and similar). It keeps only the image orientation and colour profile. | You |
| Generated content | The AI-generated videos and cover images we create for you; video settings (resolution, length, aspect ratio). | Generated by the Service |
| Generation inputs | You can't type your own prompt. Every video uses the same fixed text prompt that we wrote, and we don't keep a copy of it with your job, only its length and a hash. Your photo is the only input that is personal to you. | Us |
| Purchase and transaction data | Credit pack bought, price, currency, date, payment status, refunds and chargebacks, and the payment provider's transaction or session IDs. To apply our checkout rules (which payment provider you can use, and whether we ask for the EU/EEA/UK checkout consent; see our Terms, Section 4), we also keep the country we detect from your internet connection, the country you choose at checkout (and, for Canada, the province), the resulting purchase region, the billing country and state or province (or, if there is none, the postal code) that the payment provider sends us, and, for Stripe payments, the card's issuing country. We do not receive or store full card numbers or CVC codes. | You; Stripe or Waffo |
| Communications | Messages you send to our support address and our replies; transactional emails we send you, such as order confirmations (we keep only a record that the email was sent, not its content). We don't send marketing emails. | You; us |
| Technical and security data | IP address, browser and device information, request timestamps, error and diagnostic logs, rate-limit counters, and anti-bot check results (Cloudflare Turnstile, if enabled). | Your device; Cloudflare |
| Usage and analytics data (only with your consent where required; see Section 12) | Pages you view, links you click, referring site, approximate location (country/city), browser, device and screen type, and session timing; if you allow Microsoft Clarity, also mouse movements, clicks and scrolling on our marketing pages, which can be replayed as a reconstructed session. Text you type, your photos and videos are masked and not sent | Your device; Google; Microsoft |
| Fraud-prevention data | If a payment is disputed (chargeback) or a refund is under review when you delete your account, or if you delete an account that has completed payments or a payment still being processed: a one-way hash of your email address and of your Google account ID, the payment provider's name, and the payment or order ID from Stripe or Waffo (for example, a Stripe payment ID or a Waffo order number). Stripe disputes are recorded automatically; Waffo disputes are entered manually by us based on Waffo's notice. We do not store card numbers or card fingerprints. For how long we keep these records, see Section 9. | Stripe or Waffo; us |
Biometric information retention and destruction policy. We don't collect, capture or store biometric identifiers or biometric information, such as scans of face geometry, from photos. If we ever did, we would tell you first, ask for the written consent required by law, and destroy that information when its purpose is fulfilled and no later than 3 years after the person's last interaction with us, whichever is first. Uploaded photos themselves are deleted from our storage 24 hours after upload, except photos held for a short human review as described in Section 9; copies kept by our third-party image safety-check provider are described in Section 5. We do not ask that provider, or any other provider, to identify anyone or to create face templates, and we use its results only to decide whether a photo is allowed.
No face recognition. We don't use photos to identify or recognise anyone, we don't create or keep face templates or "faceprints", and we don't compare faces across photos or users.
Is providing data required? You need a Google account to create an account and buy credits. You need a photo to generate a video, and payment data to buy credits. Without these, we can't provide the Service. Everything else is collected automatically to run and secure the Service.
3. How we use your data and our legal bases (GDPR)
| Purpose | Data used | Legal basis (EEA/UK GDPR Art. 6(1)) |
|---|---|---|
| Create and manage your account; sign you in with Google | Account data, technical data | Contract (b) |
| Check your photo, generate your video, store it in My videos, let you download or share it | Uploaded photos, generated content, generation inputs | Contract (b) |
| Sell credits, process payments and refunds, keep your credit balance, and automatically refund credits when a generation fails | Purchase data, account data | Contract (b) |
| Contact you personally in the rare cases where the law requires individual notice (for example, a serious data breach) | Account data | Legal obligation (c); legitimate interests (f) |
| Answer support requests | Communications, account and purchase data | Contract (b); legitimate interests (f) |
| Keep the Service secure: rate limiting, bot protection, abuse and fraud prevention, chargeback block list, debugging | Technical and security data, fraud-prevention data | Legitimate interests (f) in protecting our Service, our users and our payment accounts |
| Check uploads for safety: we reject photos that are sexual or in which a child is a subject of the video (a child who appears only incidentally in the background of a photo of adults is allowed), keep a minimal record of rejected photos for 30 days, hold a small number of flagged photos for a short human review to check for child sexual abuse material (see Section 9), report apparent child sexual abuse material where the law requires, and comply with our AI processing providers' content rules | Uploaded photos | Legitimate interests (f) in preventing misuse, protecting people's likeness and protecting children; contract (b); legal obligation (c) where the law requires us to report or preserve material |
| Keep tax, accounting and transaction records (in anonymised form after account deletion); respond to lawful requests | Purchase data | Legal obligation (c) |
| Keep a record of your privacy choices so we can show that we obtained, or respected the refusal of, your consent | Random consent ID, date and time, notice and policy version, your choice, where you made it, whether a GPC signal was present | Legal obligation (c): Article 7(1) GDPR requires us to be able to demonstrate consent (EEA, UK and Switzerland); legitimate interests (f) in showing that we respected your choice and handling complaints (elsewhere, and as a fallback) |
| Measure how visitors use our website so we can improve it (Google Analytics), including server-side measurement of purchases and generations (see Section 12) | Usage and analytics data, analytics cookie identifiers | EEA/UK/Switzerland: consent (a), given through the single "Analytics" choice. Elsewhere: legitimate interests (f) in understanding and improving our website; you can opt out at any time, and we treat a Global Privacy Control (GPC) signal as an opt-out (Section 12) |
| Understand how visitors use our marketing pages through heatmaps and session replays (Microsoft Clarity) | Usage and analytics data, interaction data on those pages, Clarity cookie identifiers | Consent (a), everywhere: in the EEA/UK/Switzerland through the single "Analytics" choice; elsewhere through a separate session-recording notice. Clarity does not run unless you agree, and it never records if your browser sends a Global Privacy Control (GPC) signal |
| Show your Google profile picture in the site header while you're signed in, so you can see which account you're using | Google profile-picture address and image | Legitimate interests (f): helping you recognise the account you're signed in with. We use only the picture address, keep it only for your sign-in session and don't store the picture. You can object at any time by turning off Show my Google profile picture in Account. |
Where we rely on legitimate interests, we have balanced those interests against your rights. You can object at any time (see Section 10).
Automated decisions. Our pre-check automatically accepts or rejects a photo before any credit is charged. A rejection only means that this photo can't be used. It has no legal or similarly significant effect on you, and you can try another photo or contact us. We do not profile you.
No AI training. We do not use your photos, videos or other personal data to train or fine-tune AI models, and we do not sell them to anyone for that purpose. See Section 5 for what our AI providers do.
4. Who we share data with
We share personal data only as needed to run the Service. We do not sell it for money. Microsoft Clarity, if you agree to it, is described in Section 4.2 and Section 11.2.
4.1 Service providers
They process data on our instructions under written terms (data processing agreements where available).
| Provider | Role | Data | Location and transfer safeguard | Privacy policy |
|---|---|---|---|---|
| Cloudflare, Inc. (USA) | Hosting and network (Workers), file storage for photos and videos (R2), database for account, job and credit data (D1), database backups, logs, an automated AI check that estimates whether a person in an uploaded photo or a generated video may be under 18, sending transactional emails such as order confirmations (Cloudflare Email), security and bot protection (Turnstile, if enabled) | All categories in Section 2, except full payment card data | Global network. R2 storage region: Cloudflare-selected region (which may be outside the EEA, including the United States or Asia-Pacific). EU-U.S. Data Privacy Framework (DPF) and Standard Contractual Clauses (SCCs) in Cloudflare's Customer DPA | cloudflare.com/privacypolicy · Turnstile |
| AI processing provider(s) (our third-party AI processing provider(s)) | AI generation API. It receives your photo (through a temporary, signed link) and our fixed prompt, passes them to the AI model provider(s) it uses, and returns the video | Uploaded photo, fixed prompt, video settings, generated video | USA; the AI model provider(s) it uses may process data elsewhere (see below). Safeguard: we rely on this provider's standard terms; we have no separate data processing agreement with them beyond those terms. Processing locations and retention follow their published documentation. | Available on request (see Section 10) |
| Image safety-check provider (a third-party AI processing provider) | Automatically checks uploaded photos, and frames of generated videos, for sexual content and returns the result. Photos whose main subject appears to be a child are rejected by our age check first and are not sent to this provider. (The age check is done by our infrastructure provider; see the Cloudflare row.) It is not asked to identify anyone or to create face templates | Uploaded photo (embedded metadata removed); the check result | United States and other countries where it and its service providers operate, including countries in Europe and Asia. Safeguard: the provider's data processing addendum, which forms part of its business terms. Under it the provider acts as our processor and uses the European Commission's Standard Contractual Clauses for transfers (with the UK Addendum for UK data). Retention: under its published documentation, it does not keep submitted photos or check results for this service by default, except where the law requires it or where this is reasonably necessary to protect its services or others from harm (for example, content that may violate its policies). It does not use content we submit to train or improve its models | Available on request (see Section 10) |
| AI model provider(s) used through our AI processing provider | Generates the video from your photo | Uploaded photo, fixed prompt, generated video | Locations follow the AI processing provider's and the model provider(s)' published documentation (which may include the United States and other countries). Safeguard: we rely on each provider's standard terms; we have no separate data processing agreement with them beyond those terms. | Available on request (see Section 10) |
| Stripe (Stripe, LLC, USA, and affiliates such as Stripe Payments Europe, Ltd., Ireland) | Payment processor for purchases outside Europe and Canada (in the United States, the pre-selected option; Europe and Canada purchases are made only through Waffo): hosted checkout, card processing, refunds, disputes | Email, purchase data, payment details and billing address you enter on Stripe's page, IP and device data | USA/EEA; DPF and SCCs under Stripe's DPA and DPF Policy | stripe.com/privacy |
| Google LLC (USA) (Google Analytics) | Website analytics (statistics about visits and use), acting for us | Usage and analytics data, cookie identifiers, device and browser data. Google Analytics uses your IP address to estimate location but, according to Google, does not log or store it | USA/global; DPF (Google LLC is certified) and SCCs in the Google Ads Data Processing Terms | How Google uses information from sites that use its services · Google Privacy Policy |
If you ask us, we will tell you the identity of the specific recipients of your personal data (see Your rights).
Stripe as an independent controller. Stripe also uses some payment data for its own purposes, such as fraud prevention and meeting financial regulations, as described in its privacy policy.
4.2 Independent controllers
Microsoft Clarity. Microsoft Corporation (One Microsoft Way, Redmond, WA 98052, USA; for EU users, Microsoft Ireland Operations Limited) provides Microsoft Clarity, which we use, only if you agree to it, for heatmaps and session replays on our marketing pages. Microsoft collects personal data from visitors to our website through Clarity and acts as an independent controller, not as our processor. Under its terms, Microsoft may use this data for its own purposes, including to provide Microsoft Advertising and to build profiles for advertising, as described in the Microsoft Privacy Statement. We configure Clarity to mask all text, form fields, photos and videos. It runs only on our marketing pages, never on sign-in, checkout, payment, account, My videos or share pages, and we don't send it your email or account ID.
- Waffo (Waffo.com Limited, Room 1903, 19/F Lee Garden One, 33 Hysan Avenue, Causeway Bay, Hong Kong; "Waffo Pancake") is the only payment provider for Europe purchases (purchases made in the EU/EEA, the UK, Switzerland, Québec and the other places listed in our Terms, Section 4) and for purchases made elsewhere in Canada, and an optional choice in the United States. For every purchase made through Waffo, Waffo is the Merchant of Record: it is the legal seller of the credits, collects any taxes, and handles the payment, receipts, refunds and chargebacks. Waffo processes the name, email, billing address (in Canada, including your province) and payment details you enter on its checkout page, and the device and connection data that page collects, as an independent controller under its own Privacy Policy and Buyer Terms. Your data may be processed in Hong Kong and other countries. We send Waffo your email, your account ID, the credit pack and an order reference (and, for EU/EEA/UK purchases, a record of the checkout consent). Waffo tells us your email, the order and its status and, where you entered them, your billing country and state or province (or postal code), so we can add credits to your account and apply our checkout rules.
- Authorities and legal requests. We disclose data when the law requires it, for example to tax authorities or under a court order. If we become aware of apparent child sexual abuse material, we report it, with related account information, to the US National Center for Missing & Exploited Children (NCMEC) and, where the law requires, to law enforcement or other competent authorities. We may also disclose data to protect rights, safety and property, or to enforce our Terms.
- Google provides sign-in ("Sign in with Google") and hosts your Google profile picture. Google processes your sign-in under its own Privacy Policy as an independent controller. Google sends us only the data listed in Section 2. To show your picture, our servers fetch it from Google; your browser doesn't contact Google for it, and we don't pass your IP address, browser details, cookies or the page you're on to Google with that request.
- Transfer of the Service. If we sell or hand over the Service to another person or company, your data may be transferred to them. We will tell you on the site before it happens, and this policy will continue to protect your data.
When you use the Share button, the video (and any share text, which may include our domain) goes to the app or platform you choose (for example, TikTok, Instagram or X). Those platforms process it under their own policies.
5. How AI generation works and what our AI providers keep
We use one or more third-party AI processing providers to turn your photo into a video. They may route the request to the AI model provider(s) they use. If we change providers or models, we will update this section and the table in Section 4.1 where the change affects how your data is handled.
- You upload a photo. It is stored privately in our Cloudflare R2 storage and checked automatically in two steps. First, our infrastructure provider's AI service estimates whether any person in it may be under 18; under that provider's published terms, it does not keep the photo after the check and does not use it to train AI models. If this check suggests that a child is the main subject of the photo, we reject the photo and delete it straight away, and it is not sent to any other provider. Otherwise, our third-party image safety-check provider, a third-party AI processing provider, checks it for sexual content; if the age check could not be completed, the photo is still checked but is not accepted. Frames of generated videos go through the same checks. Photos of adults are allowed. If a photo or video is flagged as sexual and it shows a child in the background, could not be age-checked, or is flagged by the safety-check provider as possibly involving a minor, we hold it for a short human review instead of deleting it straight away (see Section 9). Under its terms, the safety-check provider does not use content we submit to train or improve its models. Under its published documentation, it does not keep the submitted photo or the check result for this service by default. It may keep content longer where the law requires it or where this is reasonably necessary to protect its services or others from harm, for example content that may violate its policies, and may share samples of such content with its service providers for review. You can ask us to request deletion (see Section 10).
- When you start a generation, we send our third-party AI processing provider(s) a temporary signed link to your photo (it expires 2 hours after it is created), together with our fixed prompt. They and the AI model provider(s) they use fetch the photo and generate the video.
- When the video is ready, we copy it into your account storage (R2). From then on, we serve it from our own storage.
- We delete your uploaded photo from our storage 24 hours after upload. After that, the signed link no longer works. This does not delete copies kept by our third-party providers (see below).
What our image safety-check provider may keep. Under its published documentation, our third-party image safety-check provider does not keep submitted photos or check results for this service by default. It may keep content longer where the law requires it or where this is reasonably necessary to protect its services or others from harm, for example content that may violate its policies; its documentation does not set a fixed period for those cases. We cannot guarantee deletion by that provider within any set time. If you want us to ask it to delete a photo you uploaded, email support@petvideoai.com.
What our AI providers may keep. Our third-party AI processing provider(s) and the AI model provider(s) they use may keep inputs, outputs and logs for a limited period set out in their terms/documentation. We copy completed videos to our private storage promptly.
We rely on each provider's standard terms and have no separate data processing agreement with them beyond those terms. Deleting a video from our Service does not itself send a deletion request to our AI processing provider(s) or the AI model provider(s) they use.
Training. We do not use your content to train AI models. Our image safety-check provider's terms say it does not use content we submit to train or improve its models. For the AI processing provider that generates videos, we rely on its standard terms and have not obtained an additional written commitment that photos and videos submitted through our account will not be used to train or improve AI models. Its current public terms do not include such a commitment. They allow it to use submitted content "for the purpose of operating and improving our services". We will update this section if we obtain a written commitment.
6. AI-generated content (EU AI Act transparency)
All videos produced by the Service are generated by artificial intelligence. They are synthetic, not real recordings of your pet. Under Article 50 of the EU Artificial Intelligence Act (Regulation (EU) 2024/1689):
- On our website, videos are shown with a visible "AI-generated" label. This label appears on the video player, the result page, My videos, and the shared-video page.
- Downloaded videos carry machine-readable XMP metadata that we add ourselves: the IPTC "Digital Source Type" value
trainedAlgorithmicMedia, a description saying the video is AI-generated, and petvideoai.com as the creating tool. This identifies the file as AI-generated by our Service. We add this when the video is saved to your account. Our third-party AI processing providers may insert their own technical tags into the files they return; we may remove those tags and replace them with our own metadata. We keep an internal record linking each video to the generation that produced it. - The downloaded video has no visible watermark or label. Only the invisible metadata above marks it as AI-generated.
- The Share version of a video is the same file as the download for labelling purposes: it has no visible watermark or label, and it carries the same XMP metadata described above.
Limits of this labelling, stated honestly: we don't add an invisible watermark, and there is no visible mark in the video itself. We don't currently add C2PA Content Credentials. Metadata can be removed when a video is re-encoded or uploaded to social media. Videos generated before we introduced our own metadata don't have it.
If you publish a video, you are responsible for labelling it as AI-generated where the law or the platform requires it, and you must not remove the AI metadata or present the video as real footage (see our Terms, Section 7).
If you appear in a photo someone else uploaded
Some templates let users upload photos that show people. If someone uploads a photo of you, we process your image as a controller only to make the video they asked for, to check the photo for safety (for example, sexual content or signs that the person may be under 18), and to deal with complaints and legal requirements. The user who uploaded it must confirm that you are 18 or older and that they have your permission.
Legal basis (EEA/UK): our and the user's legitimate interests in providing the requested video and keeping the Service safe (Article 6(1)(f) GDPR), and legal obligations where they apply (Article 6(1)(c)).
No face recognition. We don't use photos to identify or recognise anyone, we don't create or keep face templates or "faceprints", and we don't compare faces across photos or users.
How long: the uploaded photo is deleted from our storage 24 hours after upload (sooner if our safety check rejects it, unless it is held for a short human review; see Section 9); the video stays until the user deletes it or you ask us to remove it; what our image safety-check provider (not kept by default, with limited exceptions) and AI processing providers may keep: see Sections 4.1 and 5.
Why we may not contact you: we usually have no way to contact people shown in uploaded photos, so we can't tell you directly (Article 14(5)(b) GDPR). This section is how we inform you.
Your rights: you can ask us to remove a video that shows you, object to the processing, or ask for access, at /report-content or support@petvideoai.com (subject: "Remove my image"). We may ask for a little information to find the video and confirm it shows you; we won't ask for ID documents unless really needed, and we delete what you send once your request is closed.
7. International data transfers
Our providers process data in the United States and other countries. Some of these countries may not offer the same level of data protection as your home country. When we transfer personal data from the EEA, UK or Switzerland, we rely on one of the following:
- the EU-U.S. Data Privacy Framework (and its UK Extension and the Swiss-U.S. framework) for certified US recipients such as Cloudflare, Stripe, Google LLC and Microsoft Corporation;
- the European Commission's Standard Contractual Clauses (and the UK Addendum), with additional safeguards where needed; or
- an adequacy decision, where one exists.
Photos sent to our image safety-check provider are processed in the United States and other countries where it and its service providers operate, including countries in Europe and Asia. For this provider we rely on its data processing addendum, under which it acts as our processor and uses Standard Contractual Clauses for transfers (with the UK Addendum for UK data). Data sent to the other AI processing providers we use may be transferred outside the EEA/UK, including to the United States and to countries in Asia, which may not have an adequacy decision. For those providers we have not signed Standard Contractual Clauses or a separate data processing agreement; we rely on their standard terms and the measures described in their published documentation. Waffo processes data as an independent controller under its own terms. To get a copy of the safeguards we use, email support@petvideoai.com.
8. Security
We use reasonable technical and organisational measures to protect your data:
- encryption in transit (HTTPS);
- private storage by default: you sign in to your own account to play or download your videos. If you choose to create a public share link in My videos, anyone with the link can view the video and its cover image without signing in, and can forward the link or save copies. Public share links have no fixed expiry. You can revoke a link using Stop sharing in My videos; deleting the video or your account also stops access through the link. Revocation cannot remove copies that others have already saved. A separate signed link gives our third-party AI processing provider(s) access to your uploaded photo for up to 2 hours; it is not the public video share link;
- sign-in through Google (OAuth with PKCE, state and nonce checks, and only verified Google emails accepted), so we never handle passwords;
- session cookies marked HttpOnly and Secure;
- signature checks on payment callbacks, and per-job secret tokens on AI-provider callbacks;
- redaction of emails, prompts and secrets from logs;
- rate limiting and bot protection (Cloudflare Turnstile);
- least-privilege access to production systems.
No system is perfectly secure. If a personal data breach is likely to put your rights at risk, we will notify the relevant authorities as the law requires. Where we must inform you, we will do so by a notice on the site and, if the risk is high, by a personal email to your account address. Under GDPR, we notify the supervisory authority within 72 hours where required.
9. How long we keep your data
| Data | How long we keep it | When and how it is deleted |
|---|---|---|
| Uploaded original photos | 24 hours (1 day) after upload | A scheduled job runs every minute and deletes the photo and its upload record once it is 24 hours old. This applies whether or not a video was made. It does not apply to photos held for a safety review (see the next row). If a generation that uses the photo is still running, the photo is deleted in the first run after that generation ends. What our image safety-check provider (not kept by default, with limited exceptions), our AI processing provider(s) or the AI model provider(s) they use may keep: see Section 5. |
| Photos rejected by our safety check (e.g. possible minor, sexual content) | Photo: immediate deletion attempted on rejection; failed deletes retried every minute. Photos and videos held for review: until reviewed, and no more than 7 days unless reported. Reported material: as long as the law requires after the report. Minimal record: 30 days | For safety-check rejections (including a possible minor or sexual content), we do not keep the photo: we discard it before storage or delete it immediately when it has already been stored. A photo rejected because a child appears to be its main subject is not sent to our image safety-check provider. If a temporary storage failure prevents deletion, access is blocked and the pending deletion is retried by a scheduled job every minute until it succeeds. Short human review: if a photo, or a frame of a generated video, is flagged as sexual and it shows a child in the background, could not be age-checked, or is flagged by our image safety-check provider as possibly involving a minor, we do not delete it straight away. We encrypt it and move it to a separate, access-restricted store that has no public link, is not used to make videos and is not sent to any provider. Only one authorised person can review it, and every access is logged. We keep this access log for 90 days after the review is closed or, if the material was reported to the authorities, for 1 year after the report or the closure of the case, whichever is later. A legal hold can extend these periods. The rejection message you see is the same as for other rejected content. If the review finds that it is not child sexual abuse material, we delete it at once, and in any case no later than 7 days after it was flagged. If the review finds apparent child sexual abuse material, we report it to NCMEC and, where the law requires, to other competent authorities, and we keep it, and related account information, securely and separately for as long as the law requires after the report. We keep a minimal record for 30 days: a cryptographic fingerprint (SHA-256 hash) of the file, the time, the reason it was rejected ("possible minor", "unsafe image" or "held for review"), your account ID, and the version of the checking system used. The record contains no image. We use it to handle appeals and prevent repeated misuse, then delete it. Exceptions: a legal hold can delay deletion for the period it requires. If we become aware of apparent child sexual abuse material in any other way, for example through a report made to us, we will report it as the law requires and keep the related information only where and for as long as the law requires. |
| Generated videos (clean version, share version and cover image) | Until you delete them, or until your account is deleted. They do not expire | Delete a video yourself at any time in My videos. Access to it, including through a public share link, stops immediately. We attempt to remove its stored files immediately; if a temporary storage failure prevents deletion, the pending deletion is retried every minute until it succeeds, subject to the preservation exceptions above. Deleted videos cannot be recovered. You can't delete a video while it is still queued or generating; you can delete it once it finishes. Copies held by our AI processing provider(s): see Section 5. |
| Prompts and generation inputs | You don't enter prompts. We store the fixed prompt per job only as its length and a hash, together with the video settings and job status (no images) | Job records stay while your account exists. When you delete a video, its job record is kept without the video, for credit and cost accounting. When your account is deleted, job records are irreversibly anonymised (see "Payment and transaction records"). Logs held by our AI processing provider(s): for a limited period set out in their terms/documentation (see Section 5). |
| Account data (email, Google account ID, user ID, credit balance, last-activity date, and your choice to hide your profile picture) | While your account exists | Deleted when you delete your account (see below). We don't delete inactive accounts automatically: your account and videos stay until you delete them, or ask us to delete them. If we discontinue the Service, we will delete account data within a reasonable period, keeping only records we must keep by law. |
| Sessions | Up to 30 days | Deleted when they expire, and immediately when you sign out. The temporary Google sign-in cookie lasts 10 minutes. |
| Payment and transaction records (pack, amount, currency, date, status, refunds, the payment provider's payment or order ID, and the purchase-region details described in Section 2) | 7 years after the transaction, as required by tax and accounting law | While your account exists, these records are linked to it. When you delete your account, we remove the link to you: your email is deleted and your user ID is replaced with a random identifier that we can't trace back to you. The limited exception is the order-linked identity hashes in the next row, kept only for later payment disputes and chargeback enforcement. The amounts, dates, statuses and payment-provider IDs are kept for accounting. When the 7-year retention period ends, we delete or further anonymise those accounting records. We do not store card numbers. Stripe and Waffo keep their own payment records under their own policies (Waffo states it keeps transaction records for at least 24 months). |
| Chargeback block list (hashed email, hashed Google account ID, provider, payment or order ID, reason and creation date) | Minimum block-list record: 3 years after the last blocked attempt, then deleted. Additional event references and any historical card-fingerprint data: 3 years | PetVideoAI keeps the minimum block-list record separately from your account profile and its deletion schedule. Deleting your account or reaching the 3-year limit for additional details does not lift the block. We clear additional event references and any historical card-fingerprint data after 3 years; we do not collect new card fingerprints. We keep the hashed identifiers and payment association needed to prevent re-registration and review the block for 3 years after the last blocked attempt, then delete the minimum record. If the dispute is decided in your favour, we review the entry manually and remove it if it is no longer needed (removal is not automatic, and credits are not automatically restored). You can also ask us to review an entry at support@petvideoai.com. While the entry remains, the same email or Google account can't open a new account or buy credits. |
| Order-linked identity hashes after account deletion (one-way hash of email, one-way hash of Google account ID, linked only to the relevant payment or order IDs) | 3 years after account deletion, then deleted. If a payment dispute, open refund request or refund under manual review for that order is still unresolved when the 3 years end, we keep the associated hashes until that matter and any recovery review have finished, then delete them. | Kept only to handle later payment disputes and enforce chargeback restrictions after you delete your account. No name, address, plaintext email, card number or card fingerprint is stored in this record. These hashes are separate from the chargeback block list in the previous row. Deleting your account does not remove them early. You can ask us to review an entry at support@petvideoai.com. |
| Server and security logs (for example, IP address, request details, errors) | Cloudflare Workers Logs: 3 days on our current plan (7 days on Cloudflare's paid plan). Our own event and diagnostic records (job events, payment-webhook receipts, alerts): 30 days. Access logs for content held for human review: 90 days after the review is closed (1 year after the report or the closure of the case, whichever is later, if it was reported; longer under a legal hold). Rate-limit counters: 24 hours | Deleted automatically at the end of each period. Our logs are designed to leave out email addresses, prompts and secrets. |
| Analytics data | Google Analytics: user- and event-level data kept for 14 months, then deleted automatically (the period is not reset by new activity); aggregated reports with no identifiers may be kept longer. Microsoft Clarity: session replays are kept for 30 days; Microsoft may keep a random sample of replays and heatmap data for up to 9 months under its own terms. Cookies on your device: see Section 12 | Deleted automatically by Google and Microsoft. If you withdraw consent, we stop collecting and the cookies are removed. Microsoft Clarity doesn't let us delete individual replays; Microsoft handles its own data under its privacy statement |
| Records of your privacy choices (consent records) | 30 months from the date of each choice | Deleted automatically after 30 months. They contain no IP address, browser details, account ID, email or analytics ID (see Section 12) |
| Support emails | 24 months after your request is closed | Deleted at the end of that period, or earlier if you ask, unless we need them for a legal claim. |
| Backups | Cloudflare D1 database point-in-time recovery keeps a rolling history for up to 30 days (currently 7 days on our plan). We can't shorten it or remove individual records from it. Our file storage (R2) has no versioning, recycle bin or backup | Deleted database data disappears from backups once the history window passes, so within 30 days at most. Deleted photos and videos are removed immediately and can't be recovered. If we ever had to restore the database from a backup, we would repeat all deletions made after the restore point. We make no other backups or exports. |
| Google profile-picture address | For your sign-in session (up to 30 days) | Deleted when you sign out, when the session expires, when you turn off the picture, or when you delete your account. It may remain in our database recovery copies for up to 30 days after that. We don't keep a copy of the picture. |
Deleting your account. Go to My videos and choose Delete my account at the bottom of the page. To confirm, you type your email address and confirm a second time. You can also email support@petvideoai.com from your Google account's email address. Deleting your account:
- deletes your email address and account record, your Google account ID, your credit balance, your sessions, all your uploaded photos, and all your generated videos, share versions and covers. Deletion from our file storage is immediate and irreversible;
- cancels any generation still in progress. Its result is discarded and not stored;
- anonymises, irreversibly, the accounting records we have to keep: payment, refund, credit-ledger and job-cost records. We keep no key that links the anonymous identifier back to you. We also keep an internal record that a deletion happened (date, reason, and counts only, with no personal data);
- keeps a chargeback block-list entry, but only if you have an open or lost payment dispute, a won dispute whose entry has not yet been reviewed and removed, or a refund under review. The entry contains no plain email address (see the table above).
Unused credits are forfeited when you delete your account. If a purchase is still within its 14-day refund window, you can request a refund first (see our Refund Policy).
If a refund on your account is under manual review, self-service deletion is paused and we ask you to contact us. Your right to have your data erased still applies: email support@petvideoai.com and we will handle the request within the legal deadlines (see Sections 10 and 11).
10. Your rights (EEA, UK and Switzerland)
Under the GDPR and similar laws, you have the right to:
- access your personal data and get a copy;
- correct inaccurate data;
- delete your data ("right to be forgotten");
- restrict processing;
- data portability: receive the data you gave us in a common, machine-readable format, or have it sent to another provider;
- object to processing based on our legitimate interests;
- withdraw consent at any time, where we rely on consent (this does not affect earlier processing);
- not be subject to decisions based solely on automated processing that significantly affect you.
Self-service options: in My videos you can view and download each of your videos (one at a time), delete individual videos, and delete your account. There is no one-click export of all your data. To get a complete copy (your account details, purchase and credit history, job records and all your videos), or to exercise any other right, email support@petvideoai.com. We will send your data in a common machine-readable format (for example, JSON or CSV, plus your MP4 files or download links). We will reply within one month. In complex cases this can be extended by two more months, and we will tell you if it is. To verify your identity, we may ask you to send the request from your Google account's email address or to confirm it while signed in.
Complaints. You can lodge a complaint with a data protection supervisory authority, in particular in the country where you live or work, or where you think an infringement happened. A list of EEA authorities is available at edpb.europa.eu. In the UK, contact the Information Commissioner's Office (ico.org.uk). In Switzerland, contact the FDPIC (edoeb.admin.ch). We would appreciate the chance to resolve your concern first at support@petvideoai.com.
Your Google profile picture. You can object to us showing your profile picture at any time, without giving a reason: turn off Show my Google profile picture in Account. We then stop fetching it and delete the stored address, and we remember your choice when you sign in again. You can also remove PetVideoAI's access in your Google account at https://myaccount.google.com/permissions; this doesn't delete your PetVideoAI account. To delete your account, use Delete my account or email support@petvideoai.com.
11. United States: California and other state privacy rights
This section applies to residents of California and of other US states with comprehensive privacy laws (such as Virginia, Colorado, Connecticut, Utah and Texas). It supplements the rest of this policy, and it serves as our Notice at Collection under the California Consumer Privacy Act as amended by the CPRA ("CCPA").
11.1 Categories we collect, why, and how long we keep them
| CCPA category | Examples | Purposes | Disclosed for a business purpose to | Retention |
|---|---|---|---|---|
| Identifiers | Email address, Google account ID, user ID, IP address, session ID, Google profile-picture address; hashed email and Google ID on the chargeback block list | Accounts, sign-in, showing your profile picture to you, security, fraud prevention | Cloudflare; Google (sign-in and profile-picture hosting); Stripe or Waffo (email at checkout) | Email and user ID: while your account exists. IP address: up to 3 days in Cloudflare logs and 24 hours in rate-limit counters. Minimum block-list record: 3 years after the last blocked attempt, then deleted. Order-linked identity hashes after account deletion: 3 years after deletion (or until any still-open dispute, refund request or manual refund review for that order has finished), then deleted. Additional event references and any historical card-fingerprint data: 3 years. Profile-picture address: for your sign-in session (up to 30 days). |
| Commercial information | Credit packs purchased, transactions, refunds | Selling credits, accounting, chargebacks | Stripe; Waffo | Linked to you while your account exists. After that, kept in anonymised form for 7 years |
| Audio, electronic, visual or similar information | Your uploaded pet photo; generated videos | Generating and storing your videos | Cloudflare; image safety-check provider and other AI processing providers (service providers) | Photos in our storage: 24 hours (photos and videos held for a safety review: no more than 7 days unless reported; reported material: as long as the law requires after the report). Our image safety-check provider: not kept by default; kept longer only where the law requires it or to protect its services or others from harm (see Section 5). Copies held by other AI processing providers: for a period set out in their terms/documentation (see Section 5). Videos in our storage: until you delete them or your account |
| Internet or other electronic network activity | Request logs, device and browser data, errors; pages viewed, clicks, scrolling and session replays on our marketing pages; analytics cookie IDs | Security, debugging, rate limiting; analytics and website improvement | Cloudflare; Google (analytics, as our service provider); Microsoft (Clarity, only if you agree to it, as a third party) | Cloudflare logs: 3 days. Our event records: 30 days. Google Analytics: 14 months. Clarity: 30 days (samples up to 9 months). Consent records: 30 months |
| Sensitive personal information | We do not intend to collect any. Payment card details are entered directly with Stripe or Waffo, not with us | Payment (handled by the provider) | Stripe; Waffo | Under the provider's policy |
| Audio, electronic, visual or similar information | Your Google profile picture | Showing it to you in the site header while you're signed in | Cloudflare (hosting); Google (hosts the picture) | Not stored; fetched only to display it |
We collect this information from you, from your device, from Google (when you sign in with Google) and from our payment providers. We do not draw inferences or build profiles about you ourselves. If you allow Microsoft Clarity, Microsoft may build profiles for its own purposes, including advertising (see Section 4.2).
11.2 Sale and sharing
We do not sell personal information for money, and we have not done so in the past 12 months. Google Analytics acts as our service provider: Google LLC processes the data for us, and we have turned off its advertising features and its data sharing with other Google products and services, so this is not "sharing" for cross-context behavioral advertising. Microsoft Clarity is different: Microsoft Corporation acts as an independent controller and may use Clarity data for its own purposes, including advertising (Microsoft Privacy Statement). Under the CCPA, making this data available to Microsoft may count as "sharing" personal information for cross-context behavioral advertising (and some other state laws may treat it as a "sale"). The categories involved are identifiers (cookie and device IDs) and internet or other electronic network activity on our marketing pages. That is why Clarity runs only if you agree to it, everywhere: if you don't click Allow recording (or, in the EEA, UK and Switzerland, accept Analytics), nothing is disclosed to Microsoft through Clarity. You can switch Clarity, and Google Analytics, off at any time under Your Privacy Choices at the bottom of every page.
We honor Global Privacy Control (GPC): if your browser sends a GPC signal, we treat it as a refusal of session recording too: we don't show the recording prompt and Microsoft Clarity does not record your visit. Outside the EEA, the UK and Switzerland, GPC also turns off Google Analytics and our server-side measurement for that browser. In the EEA, the UK and Switzerland, Microsoft Clarity records only if you accept Analytics; if your browser sends a GPC signal, Clarity won't record even if you accept Analytics. We do not knowingly sell or share the personal information of consumers under 16.
11.3 Sensitive personal information
We only use sensitive personal information, if any, for purposes permitted under Cal. Code Regs. tit. 11, § 7027(m), such as providing the Service and preventing fraud. We do not use it to infer characteristics about you. So no "Limit the Use of My Sensitive Personal Information" link is needed. You can still contact us about this at any time.
11.4 Your rights
You have the right to:
- know and access the categories and specific pieces of personal information we collect, use and disclose, and their sources and purposes;
- delete your personal information;
- correct inaccurate personal information;
- opt out of the sale or sharing of personal information, and of targeted advertising or profiling. Microsoft Clarity runs only if you agree to it, and you can turn it (and Google Analytics) off at any time under Your Privacy Choices. We also treat a Global Privacy Control (GPC) signal as an opt-out (see Section 11.2 and Section 12). You can also submit a request by email;
- limit the use of sensitive personal information;
- data portability, under some state laws;
- non-discrimination: we will not deny you the Service, charge you a different price, or give you a different quality of service for exercising your rights.
How to submit a request. You can download your videos one at a time and delete videos or your whole account yourself in My videos. For a full copy of your personal information (right to know/access or portability), a correction, or any other request, email support@petvideoai.com with the subject "Privacy request". We will verify your request by checking that it comes from your Google account's email address, or by asking you to confirm it while signed in. You may use an authorized agent. We will ask for proof that the agent is authorized, and we may ask you to verify your identity directly. We will confirm receipt within 10 business days and respond within 45 days, which can be extended once by another 45 days. If we deny a request, you may appeal by replying to our decision. We will respond to an appeal within the time the law requires. If the appeal is denied, you may contact your state Attorney General.
12. Cookies and similar technologies
We use cookies and similar technologies that are strictly necessary for the Service, and analytics cookies from Google and Microsoft, only with your consent where the law requires it (and, for Microsoft Clarity, only with your consent everywhere). In the EEA, the UK and Switzerland, Google Analytics and Microsoft Clarity are grouped under one choice called Analytics, because both are used for the same purpose: understanding and improving our website.
| Name | Provider | Purpose | Duration | Consent required? |
|---|---|---|---|---|
sid |
Us (first-party; HttpOnly, Secure, SameSite=Lax) | Keeps you signed in | Up to 30 days, or until you sign out | No (strictly necessary) |
g_oauth |
Us (first-party; HttpOnly, Secure) | Protects the Google sign-in step against forgery | 10 minutes; deleted when sign-in finishes | No (strictly necessary) |
catclap.pending (browser local storage) |
Us | Remembers the photo you just uploaded and your chosen resolution while you sign in or pay, so your video can start automatically afterwards | Cleared when the job starts. Otherwise it stays until you clear browser storage, and the referenced upload expires on our side after 24 hours | No (strictly necessary) |
cookie_consent |
Us (first-party; Secure, SameSite=Lax) | Remembers your privacy choices (including a refusal), so we don't ask again on every visit, and holds a random consent ID that links your browser to our record of your choice (see "Record of your choice" below) | 6 months; after that we ask again | No (strictly necessary) |
| Cloudflare security cookies / Turnstile | Cloudflare | Bot and abuse protection | Short-lived (Cloudflare cookie policy) | No (strictly necessary) |
_ga |
Google (Google Analytics), first-party | Distinguishes visitors for statistics | Up to 2 years (Google's default); your browser may set a shorter limit, e.g. 400 days in Chrome | EEA/UK/Switzerland: yes (Analytics). Elsewhere: no, but you can opt out, and a GPC signal turns it off |
_ga_<ID> |
Google (Google Analytics), first-party | Keeps session state for statistics | Up to 2 years (Google's default); your browser may set a shorter limit, e.g. 400 days in Chrome | Same as _ga |
_clck |
Microsoft (Clarity), first-party | Keeps a Clarity user ID and preferences for this site | 1 year | Yes, everywhere |
_clsk |
Microsoft (Clarity), first-party | Links page views into one session replay | 1 day | Yes, everywhere |
CLID |
Microsoft (Clarity), third-party (www.clarity.ms) | Identifies the first time Clarity saw this browser on any site using Clarity | 1 year | Yes, everywhere |
MUID |
Microsoft (Clarity), third-party (.clarity.ms) | Identifying browsers across Microsoft sites, including for advertising, site analytics and operations | About 13 months (about 390 days) | Yes, everywhere |
MR |
Microsoft (Clarity), third-party (.c.clarity.ms) | Refreshing and syncing the MUID browser ID |
7 days | Yes, everywhere |
SM |
Microsoft (Clarity), third-party (.c.clarity.ms) | Syncing the MUID browser ID across Microsoft domains |
Session (deleted when you close your browser) | Yes, everywhere |
ANONCHK |
Microsoft (Clarity), third-party (.c.clarity.ms) | Checks whether the MUID browser ID has been synced |
About 10 minutes | Yes, everywhere |
MUID |
Microsoft (Bing, via Clarity), third-party (.bing.com) | Identifying browsers across Microsoft sites, including for advertising, plus syncing that ID | About 13 months (about 390 days) | Yes, everywhere |
SRM_B |
Microsoft (Bing, via Clarity), third-party (.c.bing.com) | Identifying browsers across Microsoft sites, including for advertising, plus syncing that ID | About 13 months (about 390 days) | Yes, everywhere |
MR |
Microsoft (Bing, via Clarity), third-party (.c.bing.com) | Identifying browsers across Microsoft sites, including for advertising, plus refreshing and syncing that ID | 7 days | Yes, everywhere |
Durations are the expiry periods set when we checked our site; they can vary by browser (some browsers set shorter limits) and may be changed by the provider.
Server-side purchase measurement. When you pay, our server may tell Google Analytics that a purchase or a video generation happened (for example the amount, currency and credit pack, but not your name, email, payment details or photos). We do this only if, in the EEA, the UK and Switzerland, you have accepted Analytics (whether or not your browser sends a GPC signal) or, elsewhere, you have not opted out (including by GPC), and only using the analytics identifier already set with your permission. We tell Google not to use this data for advertising. If you reject or withdraw consent, our server sends Google Analytics nothing about you.
Your choices.
- EEA, UK and Switzerland: the banner offers Accept all and Reject all, equally prominent, and a Settings link. Google Analytics and Microsoft Clarity are covered by one choice, Analytics. Neither tool is loaded, and no analytics cookies are set, until you accept. If you accept, both Google Analytics and Microsoft Clarity (on our marketing pages only) run. If you reject or close the banner, neither loads and our server sends Google Analytics nothing about you. If your browser sends a Global Privacy Control (GPC) signal, Clarity won't record even if you accept Analytics; Google Analytics and server-side purchase measurement still follow your Analytics choice.
- Everywhere else: Google Analytics runs by default. You can turn it off at any time under Your Privacy Choices. Microsoft Clarity records sessions only after you click Allow recording in a separate notice that explains what is recorded. It runs only on our marketing pages, never on sign-in, checkout, payment, account, My videos or share pages, and everything you type, as well as your photos and videos, is masked. If your browser sends a Global Privacy Control (GPC) signal, we treat it as a refusal of session recording too: we don't show the recording prompt and Microsoft Clarity does not record your visit. GPC also turns off Google Analytics and our server-side measurement.
- How to withdraw or change your choice: click Your Privacy Choices at the bottom of any page, switch Analytics off (EEA/UK/Switzerland), or Google Analytics and/or Microsoft Clarity off (elsewhere), and click Save choices, or simply click Reject all. Withdrawing consent is as easy as giving it. We then delete the Google Analytics and Microsoft Clarity cookies on our own domain (
_ga,_ga_<ID>,_clck,_clsk), tell Clarity to stop, stop loading the tool(s) and stop server-side measurement. Cookies that Microsoft sets on its own domains (such as clarity.ms and bing.com, for exampleMUID,SRM_B,MR,SM,ANONCHKandCLID) are technically out of our reach: we can't delete them, but you can clear them in your browser settings. See also the Microsoft Privacy Statement. Withdrawing consent doesn't affect processing done before. - We keep your choice for 6 months in the
cookie_consentcookie, then ask again. - Record of your choice. When you make or change a privacy choice, we keep a short record so that we can show that we asked and what you chose. It contains: a random consent ID (also stored in your
cookie_consentcookie, so the record can be matched to your browser), the date and time, whether you were shown the EEA/UK/Switzerland or the rest-of-world version of our notice, the version of the notice and of this Privacy Policy you saw, what you chose (for example, Analytics on or off), where you made the choice (banner or Your Privacy Choices), and whether your browser was sending a Global Privacy Control (GPC) signal. It does not contain your IP address, browser details, account ID, email or Google Analytics ID. We keep each record for 30 months and then delete it. We use it only to demonstrate compliance and handle complaints. - Other ways to opt out: block or delete cookies in your browser settings, or install the Google Analytics Opt-out Browser Add-on.
- Learn how Google uses information from sites that use its services and read the Microsoft Privacy Statement.
We do not use advertising cookies of our own, and we don't send your email or account ID to Google Analytics or Microsoft Clarity. We verify our site with Google Search Console through a DNS record; this adds no script or cookie to your visit. Payment pages hosted by Stripe or Waffo may set their own cookies, which their own policies govern. Google may set its own cookies on its sign-in pages, which its own policy governs. Strictly necessary cookies don't require consent. You can block cookies in your browser, but signing in won't work without them.
13. Children
The Service is not directed to children or anyone under 18. You must be 18 or older to use the Service. Purchases, including purchases through Waffo, also require you to be 18 or older (Waffo's Buyer Terms require buyers to be 18+). We do not knowingly collect personal data from anyone under 18. If you believe someone under 18 has given us personal data, contact support@petvideoai.com and we will delete it.
We don't allow photos in which anyone under 18 is the subject. A child who appears only incidentally in the background of a photo of adults may be uploaded, but must not be animated or become the focus of a video. If our check suggests a child may be the subject of a photo, we reject and delete it straight away, and we don't send it to any other provider. Photos and videos flagged as sexual that show a child in the background, could not be age-checked, or may involve a minor are held briefly for human review and then deleted, or reported and preserved where the law requires (see Section 9).
14. Changes to this policy
We may update this policy, for example when we add features or providers. We will post the new version here and update the "Last updated" date. If a change is material, such as a new purpose or a new kind of recipient, we will show a notice on the site (and when you sign in) before it takes effect. We don't email you about policy changes, so check this page from time to time. Where the law requires, we will ask for your consent.
15. Contact us
Questions, requests or complaints about privacy:
PetVideoAI (run by an individual developer as a sole trader) Email: support@petvideoai.com EU representative: Not appointed. UK representative: Not applicable (not appointed).