Privacy Policy

This policy applies to the Opndrive service we operate: the app at opndrive.app and the documentation at docs.opndrive.app.

It does not apply to a copy of Opndrive that somebody else runs. Opndrive is open source software, and when you use somebody else’s installation, they decide what happens to your data, not us. See self-hosting at the end.

Starting with the part that matters most. We do not collect:

• Your name, email address, phone number or password. There is no sign-up.
• The contents of your files. They never pass through our servers.
• The names or paths of your files, which stay between your browser and your bucket.
• Your storage credentials.
• Anything used for advertising, retargeting, conversion tracking or profiling.
• Session recordings or heatmaps.

We do not sell or share personal information, and we never have.

Opndrive connects to storage you already own. You supply your own S3-compatible credentials, and the app uses them to talk to your provider directly from your browser. There is no Opndrive server between the two, which is why we cannot see your files even if we wanted to.

Those credentials are held in this browser, in localStorage, so that your session survives a page refresh. That has a consequence worth stating plainly: anything able to run JavaScript on the page, or anyone with access to your browser profile, could read them.

Everything below is first-party, stays on your device, and is never sent to us or used to identify you. Each entry exists to deliver something you asked the app to do, which is why none of it requires a consent banner.

Only one of them is a cookie, and it is written only if you opt out of analytics, to record that choice. Take no action and Opndrive sets no cookie at all.

Clearing site data for opndrive.app in your browser removes all of it. The documentation site stores one value of its own, the light or dark theme you picked.

We use Vercel Web Analytics and Vercel Speed Insights to see which pages are used and how quickly they load. Neither sets a cookie, neither stores anything on your device, and neither builds a profile of you or follows you to other sites.

Page addresses are stripped before they are sent. Search terms and file paths are removed, so what is recorded is which page was opened, never what was in it. Our host also keeps standard server logs containing IP addresses and browser user agents, as any web server does, which we use to keep the service running and to investigate abuse.

The landing page asks GitHub for our public star count, so GitHub sees the request. That is the only third party contacted by a page you have not chosen to visit.

You can turn it off here, and the choice applies to both sites:

• Vercel hosts both sites and provides the analytics described above.
• GitHub receives a request for our public star count when the landing page loads, and hosts our source code and issue tracker.
• Discord receives nothing unless you follow our invite link.
• Your own storage provider, whoever that is, receives your files and requests. They act for you, not for us, and their privacy terms apply to that data.

For visitors in the UK and the EU, we rely on legitimate interests under Article 6(1)(f) of the GDPR to measure how the site is used and to keep it secure. That measurement is aggregate, cookieless and not used to profile anyone, which is why it does not ask for consent. You can object to it at any time using the opt-out described above.

Storage on your device is limited to what is strictly necessary to provide the features you asked for, so it is exempt from the consent requirement in Article 5(3) of the ePrivacy Directive.

Analytics data is aggregate and retained by our host on a rolling window. Server logs are short-lived and kept only for operational and security purposes. Anything stored in your browser stays until you clear it, or until you disconnect, whichever comes first.

If the UK or EU GDPR applies to you, you have the right to access, correct, erase, export and restrict the processing of your personal data, and to object to it.

There is an honest complication. Because we hold no account and no identifier for you, we usually cannot tell which data is yours, and Article 11 of the GDPR does not require us to collect more information just to be able to. In practice this means:

• Everything we hold about you personally is in your own browser. Clearing site data for opndrive.app erases it, immediately and completely.
• Your files are in your own storage account, so exporting or deleting them is entirely in your hands and does not involve us.
• Analytics data is aggregate and cannot be traced back to an individual.

If you are in the EU or UK and think we have handled your data badly, you may complain to your national data protection authority. Californian residents have rights under the CCPA, though we do not sell or share personal information, so there is nothing to opt out of.

Our host operates globally and processes data in the United States among other places. Where personal data leaves the UK or the EEA, it is covered by the Standard Contractual Clauses in our agreement with that provider.

Opndrive is a developer tool and is not directed at children under 16. We do not knowingly collect anything from them.

The date at the top changes whenever this document does. Because Opndrive is open source, every revision is a public commit, so you can see exactly what changed and when in the history of this page.

Privacy questions go to privacy@opndrive.app.

Security issues should not go in a public issue. Please report them through our security advisory form.

When you run Opndrive yourself, you are the data controller and this policy does not apply to your users. It is worth knowing what the software does on its own:

• It has no phone-home and reports nothing to us.
• The analytics components address a collector that only exists on Vercel’s platform. Deployed anywhere else there is nothing behind that address, so no usage data is sent to anyone.
• It writes the browser storage listed in section 5 and sets no cookies.
• It talks only to the storage provider whose credentials the user supplies.

You are welcome to copy this page as the starting point for your own policy. It is licensed with the rest of the project.