How Oona handles your images

Plain-language expectations for uploads, renders, privacy, deletes, attachments.

Updated 2026-05-045 min read

Review this before uploads, shares, deletion requests, or contacting us about imagery. Tone follows our privacy posture — not legal doctrine.

What imagery is used for

Understanding layout, furnishings, finishes, constraints.
Delivering conversational guidance.
Rendering AI preview imagery.
Remembering iterations inside your workspace.
Diagnosing support issues once you escalate.

Processors & retention reality

Imagery traverses Oona infrastructure and subcontractors required to run AI, hosting, telemetry, backups, fraud prevention, etc. Detailed commitments live in our privacy policy; do not infer zero retention or blanket “no-training” clauses from this overview.

Sharing

Treat share links like invitations: only circulate them to people allowed to view your project. Rotate or revoke them from product controls when collaborators change.

Support attachments

The public contact form does not accept uploads in V0. When uploads return alongside our admin tooling, consent will be mandatory per attachment batch.

Deletion & requests

Need account deletion? Use Settings ▸ Account ▸ Delete account when logged in on the web app. For broader privacy questions, contact us with privacy data request — legal minimums and vendor delays may still apply.

Prefer a teammate?

Questions about your data?

Was this guide helpful?