Skip to content
Back to home

Privacy Policy | Pawdeo

How Pawdeo handles account data, private pet photos, generated videos, safety review, provider processing, retention, and deletion requests.

Last updated: 2026-10-23

Scope

This policy explains how Pawdeo handles personal information when providing pet image-to-video features. Pawdeo is a small-volume beta service. Processing regions, downstream model providers, backup deletion, and contractual data-processing terms are not fully documented publicly; submit only authorized pet media you are comfortable sending to the named providers.

Information We Handle

We may handle:

  1. Account and transaction data — Name, email, sign-in records, credits, and order records. Payment providers process full card numbers; we do not store them on our servers.
  2. Creation content — The fixed prompt, pet source images, generated videos, selected model, and task state. Pawdeo rejects uploads containing clearly identifiable people at launch, but backgrounds may still contain personal information that users must remove.
  3. Safety-review data — Automated decisions, the blocked stage, content-policy version, and your rights and safety confirmations. We do not place secrets or unnecessary raw sensitive content in application logs.
  4. Device and usage data — IP address, browser, device, cookies, errors, and access records used for authentication, security, compatibility, and abuse prevention.

Purposes and Necessity

We process this information only to create and deliver videos, preserve task state, settle credits, review safety risks, prevent fraud, troubleshoot failures, and meet legal obligations. Do not upload unrelated personal information, identity documents, financial records, or medical records.

Pawdeo launch accepts authorized pet media only. Do not upload material containing a clearly identifiable person, public figure, minor, branded character, private document, or work you are not allowed to use.

Service Providers

The creation flow sends necessary data to:

  • HiAPI, which receives source images and generation parameters to create a video.
  • SeeAPI, which receives the fixed prompt, source images, and generated result for text, image, and video safety review.
  • Storage, authentication, and payment providers, only when required for the relevant function.

These providers may process data on their infrastructure. HiAPI currently says temporary generated outputs are normally deleted after about 7 days and API request logs are kept for 90 days; its public policy does not clearly promise that API inputs and outputs are excluded from model training. SeeAPI states that it does not train on API inputs or outputs and keeps request logs for 60 days, but currently gives input files, output files, task data, and moderation results no automatic expiry; deletion is requested through support. Model subprocessors, processing regions, backup deletion, and contractual data-processing terms remain unresolved. Ordinary-user generation is available only for the pet-media use cases and safeguards described here; do not upload sensitive, human, or irreplaceable material.

Retention and Deletion

  • Uploaded pet source images are held in private R2 storage and automatically expire after 2 days. Membership does not extend source-photo retention.
  • Successful results are kept for 15 days without a subscription or with credit packs only, and 30 days on Creator. The period is assigned when the result succeeds, so later cancellation does not shorten an existing result.
  • At expiry, playback and download stop and a scheduled job deletes the private object. Task state, credit, and transaction records may remain while the account is active or as needed for legal, security, and dispute purposes, but do not retain an expired media file.
  • Deleting Pawdeo's R2 object does not delete a copy already retrieved by a provider. Provider copies, logs, and moderation records follow provider policies and support processes. Pawdeo therefore does not promise that expiry removes every copy from every provider system.

Sharing and Model Training

We do not sell personal information or use creation content to train our own models. SeeAPI publicly states that it does not train on API inputs or outputs. HiAPI has not published an equally explicit commitment. By using generation, you acknowledge this disclosure and should submit only authorized pet media without people or sensitive information. We may disclose necessary information when legally required or to protect users and the service.

Security and Limitations

We use encryption in transit, access controls, server-side validation, usage limits, and staged moderation. Automated review can produce false positives and false negatives and does not replace copyright, publicity, privacy, or human judgment. We may reject generation, stop distribution, suspend accounts, and retain necessary safety records when high-risk content is detected.

Your Rights

Subject to applicable law, you may request access, correction, a copy, deletion, or restricted processing of personal information, and may withdraw consent. Withdrawal does not affect prior lawful processing; some safety or transaction records may need to be retained by law.

Contact and Changes

Privacy, copyright, publicity, and abuse requests may be sent through the support email shown on the site. Material changes will update the date above and, where appropriate, be communicated in the service.