Security and privacy
Brandable changes how your Moodle looks, not your data. Here is what we receive, where it is processed, how long we keep it, and what stays entirely under your control.
Two services, two hosts
This website, brandablelms.com
The site you are reading. It is hosted by Vercel and only serves static pages: no account, no form, no analytics, no third-party cookies. The only cookie remembers the language you pick.
The Brandable platform
Your account (app.brandablelms.com) and the API that receives requests from the plugin. It is hosted on Microsoft Azure, France Central region, with its database and storage. Generation runs on Azure OpenAI in the European Union data zone.
You stay in control
Private preview
Every change first appears in a preview only you can see, on your real Moodle. Your users see nothing until you publish.
Manual, reversible publishing
Publishing is always a deliberate action by an administrator. Every publish creates a version: going back takes one click.
A design stored in your Moodle
Your published design lives in your Moodle, not with us. It stays in place if you stop using Brandable or if our service is unavailable.
Export as a standard theme
You can export your design as a standalone Moodle theme your team can review and version. It never degrades, even when your subscription ends.
JavaScript: off by default
Some components (welcome pop-up, accordion, countdown) need JavaScript. It is the most sensitive part, so every step is guarded.
- JavaScript is off by default. Only an administrator can allow it on the site.
- Every generated module is automatically analyzed before it is offered: it cannot contact another site, read browser cookies or storage, or access Moodle. Anything not allowed is rejected.
- An administrator must review the code before anything is published.
- On Pro and Multi-site, an AI security review helps you read the code. It is an aid, not a guarantee: the decision stays yours.
- A kill switch instantly turns off all JavaScript added by Brandable.
What Brandable receives
To prepare a change, the plugin sends what is strictly needed, and nothing else.
Sent with a request
- Your request, written in plain words.
- The structure of the pages involved (templates and styles), stripped of personal information.
- The element you point at in the preview, if any, without personal data.
- The images and fonts you attach.
Never sent
- Your learners’ accounts, profiles and data.
- Grades, submissions and course content.
- Your Moodle credentials or your users’ credentials.
Generation runs on Azure OpenAI in the European Union data zone. Responses are not stored by Azure, and Microsoft does not use this data to train its models.
How long we keep it
| Data | Retention |
|---|---|
| Page context, targeted element, attached images and fonts | Deleted automatically within 24 hours |
| Session content (requests, summaries, changes), Free and Essential plans | Deleted 7 days after the session’s last activity |
| Session content and saved versions, Pro and Multi-site plans | Kept for your history, as long as your plan includes it |
| After losing history (moving to a plan without it) | Kept for 30 days, with an email and an export option, then deleted |
| Technical data (status, durations, credits used) | Kept, without the content of requests |
Fonts and external resources
The Google fonts you choose are downloaded by Brandable and then hosted in your Moodle. Your learners’ browsers contact no third-party service. Generated code loads nothing from another site.
Platform protection
- All traffic is encrypted (HTTPS).
- Each Moodle connects with its own key, stored as a hash and revocable from your dashboard.
- Connecting a site requires approval in your account, protected against interception (PKCE).
- Technical logs contain no page content, names or email addresses.
- Access is rate-limited to curb abuse.
Subprocessors
We rely on a small number of providers: Microsoft Azure for the platform, Vercel for this website, Stripe and Link for payments, Brevo for email, and Google if you choose to sign in with Google.
Report a vulnerability
Think you found a security issue? Email us at security@brandablelms.com. We respond quickly and keep you posted on the fix.