Rhinobird

How does Rhinobird store uploads, generations, and History?

Uploads and History tie to your signed-in account; retention and privacy follow Privacy Policy—export downloads you need and contact support for data questions.

Account & Content Rights Natalie Nov 5, 2026 3 min
How does Rhinobird store uploads, generations, and History?

Product photos, reference videos, and generated ads pass through Rhinobird servers when you upload and press Generate. Teams wonder who can see those files, how long they remain, and what happens if an employee leaves. Authoritative answers live in Privacy Policy and Service Agreement; this article explains practical behavior on the English UI so you can align DAM practices, client NDAs, and export habits without guessing.

Account-scoped storage model

While signed in via Login / Sign up—Continue with Google or Continue with Email—uploads and outputs associate with your user identity. History lists generations for that account: previews, metadata, and download actions. There is no anonymous public feed of your creatives; visibility is whoever controls the login. Shared agency logins mean shared visibility—use team discipline or enterprise arrangements when clients require separation.

Uploads: what enters the system

  • Product and reference images (typically JPG or PNG within tool limits).
  • Reference videos for flows such as Video Clone, subject to model duration rules.
  • Text briefs including Creative Requirements and product names typed into forms.

Preparation tools—AI matting and AI upscale—also process images you provide under the same account context. Do not upload confidential unreleased SKUs on personal test accounts if policy forbids it.

Generations and History

Successful jobs land in History for retrieval. Failed jobs may leave status records without downloadable files—check credit transaction details when membership rules apply returns for non-delivery. History is the primary in-product archive; Rhinobird is not a replacement for your company DAM with legal hold features unless a separate enterprise agreement says otherwise.

Privacy principles to read in policy

Open Privacy Policy for categories of personal data, processing purposes, subprocessors, cross-border transfer, and rights available in your region. Help Center summarizes behavior but does not amend policy. Key operational habits:

  1. Download approved assets promptly to your controlled storage.
  2. Remove sensitive drafts from shared drives after client delivery if NDAs require.
  3. Request deletion or export through support when GDPR-style rights apply—email support@rhinobird.ai or call 13378452864.
  4. Do not embed personal data of unrelated individuals in briefs without lawful basis.

Security practices for teams

Use unique strong passwords for email sign-in and protect Google accounts with two-factor authentication. Sign out on shared studio machines. Revoke access when staff leave instead of rotating passwords silently while juniors still export client History. Monitor credit usage for anomalies that might indicate credential sharing.

Retention and deletion expectations

Operators may retain logs and backups for security, billing dispute, or legal compliance even after you delete visible UI entries—Privacy Policy states timelines and exceptions. Plan campaigns assuming you should keep local copies of final ads regardless of cloud retention. For account closure requests, follow the account update article pathway; do not assume instant erasure of every backup tape.

Children and prohibited content

Service Agreement and Privacy Policy define acceptable use and age eligibility. Upload only content you may process for advertising; illegal or policy-violating material can be removed and accounts restricted. Rhinobird is a business creative tool—not a consumer photo locker for unrelated personal archives.

More information

Company identification and contact paths appear on About Us. For generation troubleshooting unrelated to privacy, see Generation and Download Help articles. For credit disputes tied to stored jobs, see Credits and Usage content.

Treat uploads and History as confidential business data scoped to your login. Read Privacy Policy, export what matters, and use verified support channels for rights requests.

GOT ANY QUESTIONS LEFT?

Who can see my uploads and generations?

Content is tied to the authenticated account; anyone with that login can see History—do not share passwords across untrusted teammates.

Where do finished files live?

Completed runs appear in History with preview and Download; treat History as account-scoped storage, not a public gallery.

How long is data kept?

Retention follows Privacy Policy and operational needs—export important downloads locally for long archival.

Can I request deletion of uploads?

Contact support with a verified request; deletion timelines and exceptions are described in Privacy Policy.

Does signing in with Google change privacy rules?

Authentication method does not change policy—Privacy Policy and Service Agreement still govern handling.