Legal Policy
Last updated: 5 October 2026
This page is RoleCube’s legal centre. It identifies who operates the product, indexes every policy that governs your use of it, and sets out the standing legal notices that do not belong in a contract or a privacy notice: intellectual property, copyright takedown, third-party attributions, AI transparency, accessibility, security disclosure, and how we respond to legal requests.
If you are looking for the contract between you and us, that is the Terms and Conditions. If you are looking for what we do with your data, that is the Privacy Notice.
1. Who operates RoleCube
| Detail | Value |
|---|---|
| Operator | Mohammed Hamdan, trading as RoleCube |
| General enquiries | info@rolecube.com |
| Legal notices | legal@rolecube.com |
| Privacy enquiries | privacy@rolecube.com |
| Security disclosure and abuse reports | security@rolecube.com |
RoleCube operates the websites rolecube.com and app.rolecube.com. We do not operate any other site, and we will never ask you for a password or payment from any other domain.
2. Policy directory
| Policy | What it covers |
|---|---|
| Terms and Conditions | The contract between you and RoleCube: eligibility, accounts, price, acceptable use, AI-generated content, liability, and how the relationship ends. |
| Privacy Notice | What personal data we collect, why, on what lawful basis, who processes it, where it goes, how long we keep it, and your rights over it, including cookies and AI processing. |
| Help Centre | Practical support: getting started, accounts, how simulations and evaluations work, privacy, and how to reach a person. |
| Legal Policy | This page: company identity, intellectual property, copyright takedown, attributions, AI transparency, accessibility, security disclosure, and legal requests. |
| Cookie Policy | Every cookie and piece of browser storage we use, what it is for, how long it lasts, the signals we honour, and how to change your choices. |
| Sub-processors | The dated list of providers that process personal data on our behalf, what each one handles, and how we give notice before adding a new one. |
3. Intellectual property
3.1 What we own
RoleCube and everything that makes it work is protected intellectual property. That includes:
- the RoleCube name, logo, cube mark, brand colours and visual identity;
- the application source code, architecture, interface design and interaction patterns;
- all scenario content, including company settings, storylines, day structures, briefings, business documents, datasets, stakeholder personas, meeting scripts and meeting audio;
- the assessment layer, including marking rubrics, answer keys, expected outcomes, criterion descriptors, scoring weights, integrity checks and AI instructions; and
- all copy, illustration and marketing material across our sites and emails.
These are protected under UAE Federal Decree-Law No. 38 of 2021 on Copyright and Neighbouring Rights, UAE Federal Decree-Law No. 36 of 2021 on Trademarks, and equivalent laws internationally including the Berne Convention.
The RoleCube name and logo are unregistered trade marks. We claim rights in them at common law, and we may register them in future.
3.2 What you may do
Your account gives you a limited, personal, revocable licence to use RoleCube for your own training. You may take notes and quote short extracts for private study or genuine review and criticism, with attribution.
3.3 What you may not do
- copy, scrape, mirror, republish, sell or redistribute scenario content, datasets, rubrics, audio or evaluation output;
- use our brand, name or logo without written permission;
- register a domain, social account, app name or trade mark that is confusingly similar to ours;
- imply endorsement, partnership or affiliation with RoleCube where none exists; or
- use any part of RoleCube to build, train, fine-tune, benchmark or evaluate a competing product or an AI model.
For permission requests (press, partnerships, academic citation), write to legal@rolecube.com.
4. Copyright infringement and takedown
We respect intellectual property and expect our users to. If you believe material on RoleCube infringes your copyright, tell us and we will act.
4.1 How to submit a notice
Send the following to legal@rolecube.com with the subject line “Copyright notice”:
- your name, postal address, telephone number and email address;
- identification of the copyrighted work you say has been infringed, with evidence that you own it or are authorised to act for the owner;
- the exact location of the material on RoleCube, such as a URL, or enough detail for us to find it;
- a statement that you believe in good faith that the use is not authorised by the owner, its agent or the law;
- a statement that the information in your notice is accurate and that you are authorised to act; and
- your physical or electronic signature.
4.2 What we do
- We acknowledge within 5 working days and investigate.
- If the notice is valid, we remove or disable access to the material promptly and tell whoever posted it.
- We keep a record of every notice, our decision and our reasoning.
- We may suspend or terminate the account of a repeat infringer.
4.3 Counter-notice
If your material was removed and you believe that was a mistake or misidentification, send a counter-notice to the same address with your contact details, identification of the removed material and where it was, a statement under penalty of perjury that you believe in good faith it was removed by mistake, and your consent to the jurisdiction of the courts named in section 14. We will pass it to the complainant and may restore the material.
4.4 Bad-faith notices
Knowingly making a false claim of infringement, in either direction, may make you liable for damages. Please be sure before you file.
5. Third-party attributions and licences
RoleCube is built on open-source software. We are grateful for it, and in several cases we are legally required to say so.
5.1 AI models
| Model | Used for | Provider and terms |
|---|---|---|
| Google Gemini | Replies from fictional colleagues, and assessing the reasoning in submitted reports | Google LLC, under the free-tier Gemini API terms of service |
| Kokoro-82M (ONNX community build) | Generating the synthetic voices in scenario meeting audio, in advance, on our own systems | Apache License 2.0 |
5.2 Software
RoleCube is built with these open-source packages, each used under its licence, along with their own dependencies:
| Package | Licence |
|---|---|
| Next.js | MIT |
| React and React DOM | MIT |
| Tailwind CSS | MIT |
| Drizzle ORM | Apache License 2.0 |
| Neon serverless driver | MIT |
| Neon Auth | Apache License 2.0 |
| Google Gen AI SDK | Apache License 2.0 |
| PostHog JavaScript SDK | MIT and Apache License 2.0 |
| Resend SDK | MIT |
| Lucide icons | ISC |
The full licence text and copyright notice for any of these is available on request from info@rolecube.com.
5.3 Fonts and imagery
| Asset | Licence |
|---|---|
| Plus Jakarta Sans (typeface) | SIL Open Font License 1.1, served from our own domain |
| JetBrains Mono (typeface) | SIL Open Font License 1.1, served from our own domain |
| RoleCube logo, cube mark and the six profile avatars | Created for RoleCube by its operator using AI image tools; we claim all rights in them that the law allows |
6. AI transparency statement
RoleCube uses artificial intelligence, and we think you should be able to see exactly where, without reading a contract to find out.
6.1 Where AI is used
| Feature | What the AI does | What it cannot do |
|---|---|---|
| Messages and meeting questions | Writes replies in character from the scenario’s authored facts | Change the scenario. It is instructed to stay within the authored facts; if it is unavailable, you see the authored text instead. |
| Evaluation of your report | Scores each authored rubric criterion and writes the reasons, quoting your own words as evidence | Set your total on its own. RoleCube combines the AI’s criterion scores with its own rule-based score using fixed weights. |
| Meeting audio | Synthetic speech for scenario meetings, generated in advance from authored scripts | Imitate a real person. The voices are model-generated and belong to no one. |
6.2 What we commit to
- You are told where AI is used. The product says so next to where you message colleagues, ask questions in meetings and read your evaluation. No character is presented as a real person.
- Synthetic content is identified. Meeting audio and colleague replies are machine-generated, and we say so here and in the Help Centre.
- We do not train models on your data. Not your reports, not your messages, not your evaluations. While we use Google’s free Gemini service, Google itself may use what you type to improve its products; see the Privacy Notice.
- Your profile never reaches the AI. See the Privacy Notice for exactly what is and is not sent.
- Human review is available. You can ask a person to look at any evaluation again, and results our own checks consider unreliable are marked as provisional and flagged for a human check.
- Every AI feature degrades safely. If a model is unavailable, the product falls back to authored, deterministic behaviour rather than breaking or guessing.
6.3 Regulatory position
This statement, together with our in-product notices, is intended to meet the transparency obligations of Article 50 of the EU Artificial Intelligence Act (Regulation (EU) 2024/1689) for AI systems that interact directly with people and that generate synthetic audio and text.
The AI Act treats some education and employment uses as high risk, including systems used to evaluate learning outcomes in vocational training or the performance of workers. RoleCube is a self-directed training product: its results are not offered to employers or institutions for decisions about people. If that ever changes, we will assess the product against those rules first.
7. Content standards and reporting
All scenario content on RoleCube is authored or reviewed by us. Every company, person, document and dataset in a scenario is fictional. Any resemblance to a real organisation, person or event is unintended.
What you write (your report, your messages and your meeting questions) is governed by the acceptable use rules in our Terms and Conditions. It is private to your account and is not shown to other users.
If you encounter content that is unlawful, offensive, discriminatory, or that appears to depict a real person or organisation, report it to security@rolecube.com. We investigate every report, and we will tell you the outcome.
8. Accessibility statement
We want RoleCube to be usable by everyone, including people using screen readers, keyboard navigation, magnification or reduced-motion settings.
8.1 What we do
- semantic HTML with meaningful headings, landmarks and labels;
- keyboard operability with visible focus indicators;
- respect for the operating system’s reduced-motion preference;
- text alternatives for meaningful images and icons;
- a full transcript of every scenario meeting, so audio is never the only route to the content;
- layouts that reflow rather than requiring horizontal scrolling.
8.2 Known limitations
RoleCube is designed primarily for desktop use. Some simulation tools, particularly the data query workspace, are difficult to use on a small screen, and we show a notice recommending a desktop browser.
We aim to meet the Web Content Accessibility Guidelines (WCAG) 2.2 at Level AA. We are partially conformant: we have not had RoleCube independently audited, and the limitations above are the ones we know about. Where a part of the product falls short, we would rather hear about it and fix it than have you work around it.
8.3 Tell us
If any part of RoleCube is difficult or impossible for you to use, email info@rolecube.com with what you were trying to do and what got in the way. We will respond within 5 working days and tell you what we can do.
9. Responsible disclosure
If you find a security vulnerability in RoleCube, please tell us before you tell anyone else. We will not pursue legal action against researchers who act in good faith under this policy.
9.1 How to report
Email security@rolecube.com with a description of the issue, the steps to reproduce it, its potential impact, and any proof of concept. We will acknowledge within 3 working days, keep you updated, and credit you when the fix ships if you would like us to.
9.2 Please do
- give us reasonable time to fix the issue before disclosing it publicly;
- use only test accounts you own;
- stop as soon as you have confirmed a vulnerability exists.
9.3 Please do not
- access, modify or delete data belonging to anyone else;
- degrade the service, or run denial-of-service or automated load testing;
- use social engineering, phishing or physical attacks against our staff;
- demand payment in exchange for withholding disclosure.
A machine-readable pointer to this policy is published at /.well-known/security.txt, the convention researchers check first. We do not currently offer a paid bug bounty.
10. Government and legal requests
We may receive requests for user data from law enforcement, regulators or courts. Our approach:
- We require valid legal process. We do not hand over user data on an informal request. A request must come from an authority with jurisdiction over us and be properly issued.
- We disclose the minimum. We provide only what the order actually requires, and we challenge requests that are overbroad, vague or unlawful.
- We tell you. We notify the affected user before disclosing, unless we are legally prohibited from doing so or there is a genuine emergency involving risk to life.
- Emergencies. Where there is an imminent risk of death or serious physical harm, we may disclose the minimum necessary without prior notice, and will notify afterwards.
- We keep records of every request and our response.
Legal process should be served as set out in section 15.
11. Sanctions and export controls
RoleCube is subject to the sanctions and export control laws of the United Arab Emirates and the United Nations, and to those of other jurisdictions where they apply to our providers and technology.
You may not use RoleCube if you are located in, ordinarily resident in, or acting on behalf of a person in a comprehensively sanctioned territory, or if you are a designated person on an applicable sanctions list. By using RoleCube you confirm that you are not. We may suspend or refuse access where necessary to comply.
12. Business conduct
- Anti-bribery and corruption. We do not offer, give, solicit or accept bribes or improper payments, and we comply with UAE anti-bribery law and applicable international legislation.
- Anti-money laundering. We comply with applicable anti-money laundering and counter-terrorist financing requirements. RoleCube does not currently take payments; if it does, it will be only through regulated payment providers.
- Fair dealing. We describe RoleCube accurately, we do not make outcome guarantees we cannot support, and we do not use dark patterns to obtain consent or to keep you from leaving.
13. Disclaimers
The full contractual disclaimers and liability limits are in sections 14 and 15 of our Terms and Conditions.
14. Governing law
This Legal Policy is governed by the federal laws of the United Arab Emirates and the laws of the Emirate of Dubai. The courts of Dubai have exclusive jurisdiction, subject to the consumer protections described in section 20 of our Terms and Conditions.
15. Serving legal notices
Formal legal notices, legal process and copyright notices should be sent to:
| Channel | Address |
|---|---|
| legal@rolecube.com |
Notices sent by email are treated as received on the next working day. Notices sent to any other address, or posted to social media, are not validly served.
