Olivier Berger

Website notice / Updated 3 November 2026

Terms of use

Conditions for reading the studies and discussing a separately agreed design engagement.

The portfolio presents digital interface design through proposed services and fictional screen studies. It does not claim that the pictured products are available software, that a backend has been deployed or that measured business outcomes resulted from them. The named individual is the publisher of the design collection. A real engagement must distinguish visual design, interaction specification, implementation, testing and ongoing operation, identifying which of those tasks are included. A polished screen alone cannot establish that an application functions or is suitable for production use.

The three concept products make particular interface questions concrete: arranging everyday tasks, presenting a personal reading collection and comparing a small travel plan. Their example records and scenarios are invented for the studies. They are not client names, customer accounts, publicly released applications or evidence of user research outcomes. A button drawn inside a study image is a visual element, not a promised portfolio control. Follow the project explanation to understand the intended screen hierarchy and what further work an actual product would require.

A real interface brief should identify the user problem, supported devices, required states, supplied terminology and constraints of the existing system. Confirm who approves business rules, content, accessibility criteria and any consequential statements shown in the product. Do not assume visual design independently validates the underlying data or software. Source screenshots and files should be supplied only with appropriate permission. If customer research or production access is required, define its scope and handling separately rather than including sensitive records in an initial website message.

The enquiry mechanism prepares a local email draft and offers opening in your own application. It does not automatically send a message, accept a commission, reserve time or agree a deadline. Review the topic, recipient and content before choosing whether to send. A browser preview cannot prove delivery or acknowledgement. Obtain a response before relying on a proposed arrangement, and establish the actual scope and responsible parties in correspondence. No payment or professional engagement is created merely by following a project link.

Interface direction, a screen system and an interaction specification can form different scopes. Agree which screens, states, responsive variations, review rounds and handover formats belong to the engagement. An additional workflow or a change to the product’s logic may alter the brief. This portfolio does not supply a universal fixed package, unlimited revisions or an accepted launch date. Implementation, integration, security review and usability testing should be assigned explicitly where needed, with the people responsible for the actual product involved in the relevant approvals.

A design handover should make clear which final screens, component specifications and source files are provided, and which usage or modification rights accompany them. Draft directions and unused concepts may have different treatment from approved deliverables. Third-party fonts, icons, images and software can retain their own conditions. The public portfolio grants no automatic licence to ship an illustrated interface as a real product. Confirm rights and permissions for the actual application, including supplied assets, rather than assuming that a file’s appearance resolves every ownership question.

No fee is charged by the portfolio’s browsing or draft-form workflow. A later engagement should state deliverables, price, currency, payment arrangements and timing before a commitment is made. There is no universal published package, automatic subscription or accepted quotation hidden behind a contact button. Additional work and changed requirements need discussion under the actual agreement. Do not enter card numbers, bank credentials or authentication codes in an introductory message, and verify later payment instructions through an appropriate agreed channel.

Use the site and enquiry route for lawful reading and genuine project discussions. Do not impersonate another person, supply material without the necessary authority or attempt to access systems and records that are not public. Avoid malicious code, unsolicited credentials and unnecessary personal information in messages. Ordinary accessibility tools and legitimate browsing are appropriate uses. If a feature fails or content is unclear, identify the page and concern without exploiting a technical problem or exposing another person’s confidential information in the process.

Email applications, software and external destinations operate under their own terms and capabilities. Check the actual provider and address before supplying information, relying on a service or accepting another arrangement. Hosting and delivery providers are not presented as clients, endorsers or suppliers of the professional design work. A mention of a production tool or output format does not create an account connection. The website cannot guarantee the availability or behaviour of a service operated by someone else.

Responsibility is determined by the facts, applicable agreement and law. These website conditions do not remove a mandatory remedy, excuse a binding misrepresentation or silently replace a commitment made in a real engagement. If a concern remains, identify the relevant page, conversation and outcome you seek. Keep the correspondence and version that matter to the issue. A later notice date identifies an updated edition, rather than automatically rewriting an earlier agreement or limiting an available complaint or dispute procedure.

Related information: Company details · Contact · Privacy policy · Terms of use.