Skip to content

Your work

File handoversPresent your files. Make them yours.ProjectsA shared page for files, folders, and versions.Review and approvalClear feedback. A finished piece.

Make it yours

Diado for ResolveFrom your timeline to your client.BrandingShared pages that feel like your studio.AI integrationsWork from ChatGPT or Claude.

Get started

GuidesPractical help for your next project.Questions and answersFind an answer about using Diado.

About Diado

SecurityHow we protect your work.Our storyWhy we’re making Diado.
PricingLog in
Log inStart free trial

Privacy Policy

Last updated November 18, 2026

Diado is where creative teams send files, share projects and collect feedback. This policy explains what we collect when you use Diado, what we do with it, and the choices you have. In short:

  • Your files are yours. We store them, make previews of them and deliver them to the people you choose. That’s all.
  • We don’t sell your data, show ads, or use your files or comments to train AI models.
  • No advertising cookies. Analytics cookies only with your consent where the law asks for it, and never on the pages your recipients open.
  • Sends expire and are then deleted. Projects stay until you delete them.
Privacy PolicyTerms of Service

1. Who we are

Diado is operated by Studio Oranje LLC, a limited liability company registered in California, at 11307 Shoemaker Ave, Santa Fe Springs, CA 90670, USA (“Diado”, “we”, “us”). This policy covers the Diado app at app.diado.io and the addresses our customers set up under diado.io, our website at diado.io, Diado for DaVinci Resolve, and Diado’s connector for AI assistants (together, the “Services”).

We have two roles, depending on the data:

  • Your account. For the details of your account, your team and your billing, we decide how the data is used. We are the controller.
  • What you share. For the files you upload, and for the recipients, guests and comments that come with them, we act on behalf of the account they belong to. The account holder decides what goes in and who sees it. We are their processor or service provider.

If you received a send or were invited to a shared project, the person or studio who shared it with you controls that content. You can ask them, or us, about it (see Your rights).

2. What we collect

Your account

  • Your name, email address and profile picture, and how you sign in. Sign-in is handled by Clerk; if you use a password, we never see it.
  • Your studio name, your team (who is a member, who was invited) and your settings, including notification settings.

Billing

  • Payments are handled by Stripe. Stripe collects your card details, billing address and, if you give one, your VAT number. We keep what we need to run your plan: your Stripe customer ID, your plan, seats, billing interval and renewal date. We never see or store your full card number.

Your content

  • The files you upload, with their names, folders, sizes, versions and technical details such as format, resolution and duration.
  • What we make from your files so they can be viewed in a browser: thumbnails, previews and, for video formats browsers can’t play, playable copies.
  • Comments, replies, drawings on a frame and review decisions made on your files.
  • Your customization: page templates, logos, images and colors, and your own address under diado.io.

The people you share with

  • The email addresses you send to, and the messages you include.
  • The name and email address a guest gives on a shared project, and what they comment.
  • A download record for each send and project: who downloaded (if we know), which files, when, whether the download finished, and the city, region and country it came from. The location is worked out from the IP address at the time of the download; the IP address itself isn’t kept in the record. The sender sees this record. Someone who opens a link without giving their name appears as an unnamed visitor.
  • The name, email address and note someone gives when they send files to your file request, and the files they send.

What happens in a team

  • An activity record of who in the account created, changed, shared, deleted or bought what. The account’s people can see it.

Diado for DaVinci Resolve and other apps

  • Your sign-in is stored on your computer, in your user folder. Renders made by the plugin are saved on your computer, in Movies → Diado Exports.
  • While the plugin is open, it checks in with Diado about once a minute with your computer’s name, the plugin’s version and Resolve’s version. This is how the Integrations page shows which Macs are connected, and how you disconnect one.
  • With each version you send from Resolve, we store the timeline’s name, its Resolve project’s name, its frame rate and its start, so comments can be placed on the right frame of the timeline later.

When you write to us

  • Your name, email address and message, when you email us or use the contact form on diado.io. A message sent with the form is delivered to our inbox and isn’t stored on the website. To keep out spam, the form checks that it’s being sent by a person, and we keep scrambled records of the sender’s IP address and email address for about a day.

How Diado is used

  • With analytics cookies on (section 7): the pages you visit on diado.io and in the app, the site, link or campaign that first brought you to Diado, and actions such as starting an upload, creating a project or opening the plan page. Never file names, messages or anything in your files.
  • When you sign up, first send files or add them to a project, start a trial or first pay, we record that step with your account, along with where you first came from if analytics cookies were on.

Technical data

  • Like any website, our hosting and service providers record requests to the Services, including IP address, browser, device and time, to keep the Services running, secure and free of abuse. We don’t use this data to build profiles of you.
  • Error reports. When something goes wrong in the app, a report goes to Sentry, our error monitoring provider: the error, the page it happened on, and your browser and device. It isn’t linked to your name or email address.
  • Session recordings. For about one in ten visits to the app, and for any visit where an error happens, Sentry also records how the page behaved, so we can see what led to a problem: clicks, scrolling and the pages opened. All text is replaced by placeholders, anything typed is hidden, and images and video are left out, so file names, comments, messages and previews are not in a recording. This includes the pages recipients and guests open (download pages, shared projects, file requests). It uses no cookies and isn’t used for analytics or advertising. Our website, diado.io, has no error reports or recordings.

3. How we use it

  • To provide the Services: storing and delivering your files, making previews, sending the emails you ask us to send, showing comments and download records, and running your team and plan.
  • To keep Diado secure: protecting accounts and links, limiting password attempts, and preventing fraud and abuse.
  • To support you: answering your questions. When you ask for help with a specific file or project, we may look at it to solve the problem, with your permission.
  • To tell you about Diado: important notices about your account, your plan and changes to these policies. If you have an account, we may also email you about getting started and product news; every one of those emails has a way to stop them (section 6).
  • To meet legal obligations: tax and accounting records, and lawful requests from authorities.

We don’t look at your files, other than through the automatic processing described above (previews, playable copies, zips), when you ask us to, or when the law requires it.

If you are in the European Economic Area, the United Kingdom or Switzerland: we process your data to perform our contract with you, for our legitimate interests in running a secure and reliable service, to comply with the law, and, where we ask for it, with your consent.

4. AI assistants

Diado doesn’t use your files, comments or any other content to train AI models, and doesn’t send your files to AI services.

You can connect Diado to an AI assistant, such as Claude or ChatGPT, to send files and read feedback from a chat. When you do, the information you ask the assistant to work with, such as file names, comments and review decisions, becomes part of your conversation with that assistant, and its provider’s terms apply to it, including whether your conversations are used to train its models. Your files themselves are never part of the conversation. You can remove Diado from the assistant’s settings at any time.

5. Who we share it with

We don’t sell your personal information, and we don’t share it for advertising. We share it only:

  • With the people you share with. That’s the point of Diado: recipients see what you send them, guests see the project you shared, and the sender sees the download record and comments.
  • Within your team. The account’s owner and members see the account’s projects, sends and activity record.
  • With the service providers that run Diado for us, under contracts that let them use the data only to provide their service:
ProviderWhat they do for Diado
CloudflareStores your files, makes previews and playable copies, delivers our emails, runs our domain names, and checks that file requests and contact messages are sent by a person.
VercelHosts the app and runs our scheduled jobs, such as removing expired files.
NeonHosts our database: accounts, projects, comments, download records.
ClerkAccounts and sign-in.
StripePayments, invoices and sales tax.
GoogleGoogle Analytics: statistics on how diado.io and the app are used, only with analytics cookies on (section 7). It gets a random account ID, never your name, email address or files.
LoopsSends our emails about getting started and product news to people with a Diado account (section 6). It gets their name and email address, their plan and when it changes, whether they’re a member of someone’s team, and when they signed up. Never recipients, guests, files or comments.
SentryError monitoring for the app: error reports and session recordings with text, typing, images and video left out (section 2, Technical data).
  • When the law requires it, or to protect the rights, safety and property of our users, the public or Diado.
  • In a business transfer, such as a merger or sale, in which case this policy continues to apply to your data.

6. Emails

We send emails that are part of using Diado: sign-in codes, invitations, a send to its recipients, new comments, finished downloads, expiry reminders and billing notices. You choose which notifications you get in Diado’s settings.

If you have a Diado account, we may also email you about getting started and what’s new in Diado. These emails are sent through Loops, and every one has an unsubscribe link. Recipients and guests don’t get them.

A recipient or guest gets an email from Diado because someone shared with them. Every notification email to them has a link to stop further emails about that send or project.

7. Cookies and browser storage

What the Services need to work

  • Sign-in cookies from Clerk, which keep you signed in.
  • A guest cookie on a shared project you gave your name on, so you stay the same guest when you come back. It lasts 90 days.
  • An unlock cookie for a password-protected link, so you don’t enter the password again for 12 hours.
  • Browser storage for things like your view preferences and uploads that can resume after a dropped connection, and a service worker that streams large zip downloads to your disk. This stays in your browser.
  • A session marker for error monitoring (section 2), kept in your browser’s storage until you close the tab.

You can block or delete these in your browser, but you won’t be able to stay signed in.

Analytics cookies

To see how Diado is used and what brings people to it, we use Google Analytics on diado.io and in the app (its sign-in and sign-up pages and your workspace). When you follow a link from diado.io to sign up or sign in, the link also tells the app which page you first arrived on, the site that sent you and any campaign tags. Google sets cookies that tell one browser from another (_ga and _ga_…, up to two years). We set two of our own: diado_consent, your choice (one year), and diado_attr, the page you first arrived on, the site that sent you and any campaign tags in the link (90 days).

  • In the EU, the EEA, the UK and Switzerland we ask first, going by your device’s time zone. Until you accept, nothing from Google loads and none of these cookies is set. Elsewhere they’re on unless you turn them off below.
  • The pages your recipients and guests open (download pages, shared projects, file requests) never carry analytics, whatever anyone chose.
  • We use no advertising cookies and no advertising pixels.

Analytics cookies in this browser:

8. How long we keep it

  • Sends expire after the time the sender chooses, up to 30 days, or sooner if the sender ends one early. Their files are kept for 30 days after expiry and deleted within a day after that. A send set to delete after download has its files deleted within a day.
  • Projects and their files stay until you delete them. A file deleted from a project can be restored for 24 hours, and is then deleted. A deleted project’s files are deleted within a day.
  • Files sent to a file request stay until you delete them or the request, or move them into a project. Once deleted, they are removed within two days.
  • Unfinished uploads are deleted after 7 days.
  • Comments, download records and the activity record stay with the account while it exists, so the history of a send or project stays complete.
  • Your account. When you ask us to delete your account, we delete it and its content within 30 days. We keep invoices and payment records for as long as tax and accounting laws require.
  • Logs, error reports and session recordings kept by our providers for security and operations are deleted after a limited period.

We don’t keep backup copies of your files: once deleted, a file can’t be recovered. Our database provider keeps short-term backups of the database, to recover from failures, which are overwritten as they age.

9. Security

Files travel over encrypted connections and are stored encrypted by our storage provider. Links to files are signed and expire; passwords on links are stored only as secure hashes; and access to your account is checked on every request. Within Diado, only the people who need to, to run and support the Services, can access production systems.

No system is perfectly secure. Keep your sign-in safe and share links only with the people meant to have them: anyone with a link can open it, unless it has a password. To report a security issue, email hello@diado.io.

10. Where your data is stored

Diado is run from the United States, and our service providers may store and process data in the United States and other countries. When we transfer personal data out of the European Economic Area, the United Kingdom or Switzerland, we rely on safeguards approved for that purpose, such as the European Commission’s Standard Contractual Clauses.

11. Your rights

Depending on where you live, you can ask us to:

  • tell you what personal information we have about you, and give you a copy;
  • correct it, or delete it;
  • give it to you in a format you can take elsewhere;
  • stop or limit some uses of it, or object to them.

Most of your account details can be changed in Diado itself. For anything else, email hello@diado.io. We answer within 30 days, and we may need to confirm it’s you first. If you are a recipient or guest asking about content someone shared with you, we may pass your request to that account, which controls it.

California residents: you have the right to know, delete and correct the personal information we hold about you, and not to be treated differently for using these rights. We don’t sell or share personal information as the California Consumer Privacy Act defines those terms.

In the EEA, UK and Switzerland, you can also complain to your data protection authority. We’d appreciate the chance to help first.

12. Children

Diado is a tool for professionals and is not meant for anyone under 18. We don’t knowingly collect personal information from children. If you think a child has given us their information, email us and we’ll delete it.

13. Changes to this policy

When we change this policy, we’ll update the date at the top. If a change matters for how we use your data, we’ll tell you by email or in Diado before it takes effect.

14. Contact

Questions about privacy, or a request about your data: hello@diado.io. How you may use Diado is in our Terms of Service.

By post: Studio Oranje LLC, 11307 Shoemaker Ave, Santa Fe Springs, CA 90670, USA.

Share your next cut
with your client.

Start free trial

For the work you make.
And the people you share it with.

Product

  • File handovers
  • Shared projects
  • Review and approval
  • Teams
  • AI integrations
  • Branding

Explore

  • Diado for Resolve
  • Plans and pricing
  • Help and guides
  • Security

Comparison

  • Diado vs. WeTransfer
  • Diado vs. Frame.io
© 2026 Diado
Privacy policyTerms of service
Back to top ↑