Pick a time

Acceptable use policy

Version 1.0 · Effective 21.10.2026

You own your work, we host it, and we never train machine learning
models on it. This policy sets out what you confirm when you upload, what
neither of us may do, and how we handle a complaint about your content:
notice first, never deletion first.

This policy forms part of your agreement with OneCodeToRuleAll d.o.o. (OCTRA), trading as EditWise. It applies to you, to everyone you give access to your workspace, and to every client contact, reviewer and guest you invite into it.

1. The short version

You own your work. We host it. We do not use it for anything except running the service you are paying for, and we never train machine learning models on it. In return you confirm you have the right to put it here, and you keep the platform out of the two or three uses that would get us both into trouble.

Everything below is that, in the detail a contract needs.

2. Ownership of what you upload

2.1 You keep everything. As between you and us, you own all right, title and interest in the content you upload: video, images, PDFs, text documents, comments, annotations, project records and everything else. Uploading it to EditWise transfers nothing.

2.2 Your clients' rights are unaffected. Where the content belongs to your client rather than to you, this policy does not change that. We acquire no rights against your client either. Nothing you do inside EditWise dilutes, licenses or encumbers your client's ownership of their own material.

2.3 We claim no ownership and we assert none. We will not register, license, sell, sublicense, publish, or use your content for our own purposes.

2.4 We will not use your content in marketing without your written permission. Not in a screenshot, not in a demo, not in a case study, not on a conference stand. Where you agree to be a reference customer under a separate written arrangement, that arrangement governs and you can withdraw it: a named customer comes out of our public materials within five working days of asking.

2.5 We will not train machine learning models on your content. Not our own models, not a third party's, not on anonymized or aggregated derivatives of your media, comments or documents. This is not a temporary position pending a change of mind, and if it ever changes it changes by an amendment you sign, not by a policy update.

2.6 What we do use. We use aggregate, de-identified operational statistics (storage volumes, request rates, error rates, feature usage counts) to run, secure, bill and improve the service. None of it contains your content, your clients' identities, or anything traceable to a person or a project.

3. The license you give us, and its limits

3.1 You grant us a non-exclusive, worldwide, royalty-free license to host, store, copy, transcode, encode, cache, transmit, display and deliver your content, and to create derivative technical artefacts such as proxies, thumbnails, previews and format conversions.

3.2 The license is limited to four purposes and no others.

  1. Operating the service for you and the people you authorize.
  2. Providing support you have requested.
  3. Making backups and maintaining disaster recovery capability.
  4. Complying with a binding legal obligation.

3.3 The license lasts as long as we hold the content, and ends when the content is deleted under our data exit terms at editwise.io/data-exit. It survives only to the extent content persists in backups, which are overwritten in the ordinary cycle within 35 days.

3.4 We sublicense only to the sub-processors listed at editwise.io/sub-processors, and only to the extent needed to deliver the service. Each is contractually bound to the same limits.

3.5 A transcode is not a new work. Where we generate a proxy, a preview or a format conversion, you own that output on the same terms as the source. We claim nothing in it.

4. What you confirm when you upload

This is the section that matters most, and it is the one most likely to be tested. Read it properly.

4.1 You confirm that for everything uploaded to your workspace, by you or by anyone you give access to, you have all rights, licenses, consents and permissions necessary for it to be uploaded, stored, viewed, annotated and shared through EditWise by the people you give access to.

4.2 That includes, and this list is not exhaustive:

4.3 You are responsible for what the people you invite upload. Your staff, your freelancers, your clients and your reviewers all act under your workspace. If a freelancer uploads unlicensed stock footage into your workspace, that is your obligation to us, not theirs, and not ours.

4.4 We do not check. We do not inspect, index, screen, watermark or verify the rights position of anything uploaded, and nothing in the service should be read as us having done so. We could not do it if we tried: the whole point of the platform is that the material is unreleased and we have no independent way to know what is licensed.

4.5 If a rights holder contacts us about your content, we come to you first. Section 8 sets out how.

4.6 Special categories of personal data. The service is not designed for material containing health data, biometric data, or the other special categories under Article 9 GDPR, and it is not designed for criminal-offense data. If your work involves such material, such as documentary, healthcare, public sector or campaign work, you remain responsible for the lawful basis, and you should tell us so we can talk about whether the configuration is right for it. We would rather have that conversation than discover it in an incident.

5. Confidentiality runs both ways

5.1 Your workspace is yours. Other customers cannot see it. Tenant isolation is enforced at the data access layer, tenant identity is derived from the authenticated session and never from anything a browser sends, and cross-tenant access is covered by explicit automated tests.

5.2 We do not look at your content except where necessary to provide support you have asked for, to investigate a security incident, or where legally required. Every such access is written to the activity log in your own workspace, where you can read it.

5.3 You do not look at anyone else's. You must not attempt to access another customer's workspace, another customer's content, or any part of the platform you have not been given access to.

5.4 Review links are the loose end and they are your responsibility. A review link lets someone see a deliverable without an account. Anyone holding the link can use it. Treat them as you would treat an unlisted file-sharing link: send them to the people who should have them, use the download and copy-link controls, and revoke access when a project ends.

6. What you must not do

6.1 Content. Do not upload or distribute material that is unlawful; that infringes intellectual property or privacy rights; that is child sexual abuse material; that is malware or contains a payload designed to compromise a system; that harasses or threatens a person; or that you have no right to hold.

6.2 Platform. Do not attempt to circumvent authentication, authorization or tenant isolation. Do not probe, scan or penetration-test the service without our prior written permission. Ask, and for a real customer with a real security program the answer is usually yes and we will scope it with you. Do not scrape, crawl or bulk-extract other than through the exports we provide. Do not reverse engineer, decompile, or attempt to derive source code. Do not resell, sublicense or provide the service to a third party as your own.

6.3 Accounts. Do not share individual login credentials. Named seats are freely and unlimitedly reassignable at no charge, so there is never a commercial reason to share one: if a person leaves, reassign the seat.

6.4 Sending. Do not use the platform's notification or communication features to send unsolicited bulk messages.

6.5 Interference. Do not deliberately impose an unreasonable load, disrupt the service for other customers, or interfere with any security control.

7. Fair use

7.1 Storage is included at 0.2 TB per seat, with additional storage sold in 2 TB blocks at the published rate of $60 a month per block, charged on actual usage. Overage is billed; it is not a policy matter.

7.2 Streaming. A published fair-use allowance of 2 TB of streaming per account per month applies. We do not currently meter it and we do not charge for exceeding it. If your usage runs consistently above the allowance we will contact you and have a conversation before anything changes. We will not send you a surprise bill for streaming.

7.3 We reserve the right to introduce metering in future, on notice and on terms stated at the time. We will not apply a charge retroactively to usage that occurred while no charge was published.

8. If someone complains about your content

8.1 If a third party, such as a rights holder, a person appearing in your material or a lawyer, contacts us about content in your workspace, we notify you first, promptly, and we do not act unilaterally, unless the content is manifestly unlawful or we are under a legal obligation to act immediately.

8.2 You get a reasonable opportunity to respond, to demonstrate your rights, or to remove the content yourself.

8.3 Where we must restrict content, we restrict the narrowest thing that resolves the issue. A single deliverable, not a project. A project, not an account. We do not suspend a workspace over one file.

8.4 We keep a record of every complaint received and every action taken, and it is available to you on request.

8.5 Nothing here obliges us to adjudicate a rights dispute between you and a third party. We are a hosting provider, not a tribunal.

9. Enforcement

We escalate. We do not delete first and discuss afterwards. Your unreleased work is the least appropriate thing on earth to handle abruptly.

Step When What happens
1. Notice Suspected breach We contact you, describe the issue, and set a reasonable time to fix it
2. Content restriction Not resolved, or a specific item is the problem The narrowest possible restriction on the specific content. Everything else keeps working
3. Feature suspension Ongoing or repeated The specific capability being misused is suspended. The workspace stays live and your data stays accessible
4. Account suspension Serious, repeated, or unresolved after step 3 Access suspended. Your data is retained and your export rights are unaffected
5. Termination Material breach not cured, or a legal obligation to terminate Under the master agreement. The 30-day export window still applies, per editwise.io/data-exit

Immediate action without notice is reserved for: child sexual abuse material; an active attack on the platform or on another customer; a credible and immediate threat to a person; and a binding legal order. In every other case you get notice first.

Cure period. Where a breach is capable of being fixed, you get 10 working days from written notice, unless the breach is one of the immediate-action categories.

10. Our own conflict of interest, stated

OCTRA, the company behind EditWise, also operates Lumaris Studio, a video production business.

That is a fair thing for a video agency to want an answer about before uploading unreleased client work, so here is the answer without being asked.

11. Changes

We may update this policy. Material changes take effect 30 days after we notify you by email and by updating this page. A dated copy of every version is archived, so you can always see the version that applied on the day you signed. Continued use after the 30 days is acceptance; if a change is unacceptable to you, tell us and we will work it out.

12. Contact

contact@editwise.io