Last updated: 12 November 2026
Oropod is a media asset management app, made by Oropod AS (organisation number 936 855 520), a company registered in Norway. This policy explains how we collect and handle your personal data when you use the Oropod app, our backend service at api.oropod.com, the Oropod web app at app.oropod.com, and this website. Oropod AS is the data controller for that processing.
Oropod is designed to work with your own storage and the services you already use. Much of your data stays on your device or flows directly between your device and the services you connect, so we only receive what is described below.
When you create an Oropod account, our authentication provider Clerk stores your email address and a user identifier on our behalf. We use these to identify you, secure your account and associate your workspaces with you. Our backend stores your email address and the identifiers of the workspaces you can access. The people who manage access to a workspace can see the email address of everyone who has access to it, what each person is allowed to do there, and when their access starts and ends. When a person is given access, whether by someone who manages an Oropod Storage organisation or by Oropod itself, our backend asks Clerk whether that email address has an account, and if it has neither an account nor an invitation waiting, Clerk emails it an invitation to create one. Whether an email address has an account or an invitation waiting is never shown to the people who manage access, only to Oropod’s own staff.
If you manage Oropod Storage with the orostore command-line tool, you sign in to it by approving a code on app.oropod.com. For each request to sign in we store the name the computer gave for itself, the IP address the request came from, when it was made, and whether you approved or denied it. For each sign-in we store the email addresses it acts as, when it was created, when it was last used, and when it was revoked. Only a hash of the sign-in’s secret is stored, never the secret itself. The tool keeps the secret on your computer, in a file in your home folder that only your user account can read, until you sign out. Each change made with a sign-in records which sign-in made it. We keep these records to secure your account and to show which sign-ins exist, for as long as your account is active.
If you use Oropod-hosted storage, the media files, derived versions (such as compressed previews) and related metadata you upload are stored in our cloud storage so you can reach them across your devices. You control this content and can add or remove it at any time.
Oropod can connect to other services that you already use. When you connect one, you sign in to that service directly from the app on your device, and any access tokens are stored securely in your device’s Keychain. Because this happens on your device, we do not receive your sign-in credentials for those services. The one account detail the app shares with us is the email address of each connected account, which we use to check whether paid access has been arranged for that address. Our backend uses it only for that check and does not store it. Connecting a service is always your choice, and you can disconnect it at any time. Folders shared over your local network are likewise accessed directly from your device, and their contents are not sent to us.
To keep the app reliable we use Sentry to collect crash and error reports, along with performance summaries of video playback and downloads: how fast data arrived, whether playback had to pause to buffer, and whether the device was on Wi-Fi or mobile data. These reports are configured to exclude personal data, and the performance summaries never include the names of your files or of the networks you connect to. We never send your IP address, and identifiers such as email addresses are replaced with pseudonymous short codes before they leave your device, so reports can be correlated without revealing who you are.
Our backend logs the following for each request: the time, the requested resource, the response status and (if you are signed in) your user ID. Entries for failed or rate-limited requests can also include details of the problem and the IP address the request came from. We use these logs to operate the service and investigate problems, and we keep them for a limited period.
Subscriptions are sold and processed by Apple through the App Store. We receive your subscription status from Apple so we can unlock paid features. We do not receive your payment card details.
This website uses Umami, a privacy-focused analytics tool hosted in the EU. It is cookieless and collects only aggregate, non-identifying statistics.
The Oropod web app at app.oropod.com sets only the cookies it needs to work, and none for analytics or advertising:
__oropod_frameio, set only if you connect Frame.io in the web app, for up to 44 days: the 14 days the connection lasts, and 30 days after it ends, so the web app can ask you to sign in again. It holds a random token, which our backend uses to find your connection.__oropod_adobe_sign_in, set for up to ten minutes while you sign in with Adobe, so the web app can tell that the answer from Adobe belongs to the sign-in you started.__oropod_hs, which counts the browser’s sign-in round trips for about a minute, so it is never redirected in a loop.oropod_sidebar, which remembers that you hid the sidebar. It is set only when you hide it, holds no personal data, and lasts a year.oropod_sort_…, one for each kind of list (such as days or folders), which remembers the order you chose for it. It is set only when you choose an order other than the usual one, holds no personal data, and lasts a year.oropod_hidden_projects, which remembers the projects you hid from your project list in that browser. It is set only while you have hidden a project, holds only the projects’ identifiers, and lasts a year.To sign in or manage your account, the web app loads Clerk’s own forms from Clerk, which keep what they need in your browser’s storage.
Some data is kept only on your device and is never sent to us, including a local cache of file metadata for offline use, downloaded files, and credentials held in the Keychain.
We use the personal data we collect to:
Where the GDPR applies, we rely on the following legal bases.
We do not sell your personal data. We share it only with service providers that process it on our behalf, under contract and only as needed to run Oropod.
We may also disclose data where required by law. As our infrastructure evolves we will keep this list up to date.
If you connect a third-party service such as Frame.io in the Apple app, the connection runs directly between your device and that service, and your use of it is governed by their own privacy policy.
If you connect Frame.io in the web app, you sign in with Adobe, and our backend makes the connection on your behalf. It stores your Adobe user identifier, your email address, whether Adobe has verified it, your name as Frame.io gives it, and an encrypted token that lets it reach Frame.io as you. It uses these to sign you in to the web app and to show you the Frame.io projects your account can see. To show them, it reads the projects’ names and the names, details and metadata of their files from Frame.io. It also reads the contents of the metadata files in those projects, such as camera and sound reports, and runs Oropod’s metadata plugins over them, as the Apple app does on your device. While a plugin reads such a file, a copy of it is held in a temporary location in our backend’s memory and deleted straight after. It also reads a project’s settings file, if the project has one. So that a project opens quickly the next time, our backend keeps what it read, and what the plugins made of it, in its memory for at most a day after you last opened the project, and stores it in our cloud storage at Scaleway. What it stores is kept apart for each Frame.io account and project, under a pseudonymous code rather than your Adobe user identifier, and is never used for anyone else or for any other purpose. Before showing you anything it stored, our backend checks with Frame.io that your account can still see the project. Your clips and posters are not copied: your browser plays and shows them straight from Frame.io. The connection ends after 14 days, when Adobe stops accepting the token, or when you sign out of Frame.io in the web app’s accounts. Our backend deletes what it stored, including what it keeps for your projects, at once when you sign out, and deletes what it keeps for a project 30 days after you last opened it. A connection that ends otherwise is kept for 30 days after its 14 days, without being used, so the web app can ask you to sign in again, and deleted within a day after that. Our backend never shares the token, and your use of Frame.io is still governed by Adobe’s own privacy policy.
Some of our providers are located outside the EEA, in particular Clerk in the United States. Where personal data is transferred there, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses and, where applicable, the EU-US Data Privacy Framework.
We keep your account and content data for as long as your account is active. If you close your account or ask us to delete your data, we remove it within a reasonable period, except where we must keep certain records to comply with the law. Diagnostic data is retained only for a limited period.
We protect your data with encryption in transit, secure credential storage in the device Keychain, access controls on our backend, and the pseudonymisation of diagnostic data described above.
If the GDPR applies to you, you have the right to access, correct, delete, restrict or object to our processing of your personal data, and to receive it in a portable format. Where we rely on consent, you can withdraw it at any time. To exercise any of these rights, contact us at info@oropod.com. You also have the right to lodge a complaint with the Norwegian Data Protection Authority or your local supervisory authority.
When you use Oropod to store media that contains other people’s personal data, you are the controller of that content and Oropod AS acts as your processor. If you need a data processing agreement, contact us at info@oropod.com.
Oropod is a professional tool and is not directed to children. We do not knowingly collect personal data from children.
We may update this policy from time to time. We will post any changes on this page and update the date shown above.
For general inquiries as well as questions about this policy or your data, please contact us at info@oropod.com or the address below:
Oropod AS
Postboks 6 Risum
1761 Halden
Norway
Organisation number 936 855 520.