Features

Here you'll find usage examples of Orejime for common use cases.
Each example presents the configuration needed to set it up (read the docs to learn more).

Purposes

The base building blocks of Orejime are purposes.
Those are meant to group vendors having the same function (i.e. analytics, social media and so on).

Each purpose has a title and an optional description to provide further details to the user.
They can be made mandatory, in which case they couldn't be disabled but would still be shown (think of technical cookies that are required for a website to function properly).

Example

Grouping

Purposes can be grouped together as to let the user consent either to the group as a whole, or to each individual purpose.

Example

Internationalization

Orejime is available in many languages (mainly european as of now).
Each and every text translation can be overriden to fit your needs.

Example

Styling

Orejime provides default styles that are easily customizable, either via CSS variables, or by overriding the styles with plain CSS.

Example

Warning:
Keep in mind that when changing the styles, you must ensure that the resulting color combinations are contrasting enough so the interface remains accessible to all.

Contextual consent

Any content can be handled by Orejime. Instead of simply hiding everything the user hasn't consented to, Orejime can show a fallback notice with a way to consent in place.

Example

Themes

Orejime comes in different flavors.
As of now: the standard one, and one for the design system of the french state, as shown in the following example.

Example

Note:
Themes are meant to integrate Orejime to specific environments where its interface can't be adapted with CSS only.
You should never have to implement a theme yourself, as styling should cover your needs.

Accessibility

Orejime is built with accessibility in mind, as it is the main reason why it was created in the first place.
It is tested thoroughly against the RGAA and thus also complies to the WCAG.

Ecodesign & performance

Consent Management Platforms are present everywhere, and they're probably here to stay. This means that, at scale, they contribute to a lot of network use, processing power and so on.
Orejime is optimized as much as it can be to reduce the weight it imposes on the web platform. This also guarantees that it will not impede your website's performance.

Honest interface

Orejime doesn't trick users into one choice or the other. It presents information with appropriate levels of importance, in a clear and straightforward manner.

They're using Orejime

We're proud to help those services comply with the GDPR:



You're using Orejime? Tell us!

Need a hand?

Orejime is maintained by our software engineering team at Boscop.
Reach out to us, we can provide support for you to set Orejime up on your website.

All fields are mandatory

Boscop only processes the collected data to respond to your request. To learn more about how we manage your personal data and to exercise your GDPR rights, you can consult our data privacy policy .

Upgrading Orejime

Migrating from V2 to V3

With version 3, Orejime is moving away from its initial implementation to lay a more robust ground for future developments.
This has a slight impact on the way it is configured, as many options and translations were renamed for clarity.

To ease the transition, we're providing a tool to migrate you old configuration to the latest format.
Paste your current configuration below to get an up-to-date version.

Warning:
Be sure to paste an Orejime config and not arbitrary JavaScript code, as it will be evaluated in your browser in order to be migrated.