The basis for using this portfolio and starting a design enquiry. Project terms are agreed separately.
1. Operator and use of the portfolio
The website is presented by MAURITS WILLEM EWOUD STORM VAN S GRAVESANDE, an independent professional using the public name Maurits Storm. The identification address is Maroastraat 22, 1060 LG Amsterdam, Netherlands, and the contact route is an email draft to [email protected]. These terms cover access to the portfolio, its concept studies, service descriptions and enquiry tools. They do not by themselves create a design commission, partnership, employment relationship or agency appointment. Reading a page or preparing a message does not indicate that a project has been accepted.
2. Permitted browsing and fair use
You may browse the pages, follow their navigation and refer to the work when discussing a potential design project. Use the site in a way that respects other people's rights and the availability of the service. Do not impersonate another person, submit misleading identity information, interfere with the site's operation or attempt to gain access to systems that are not publicly offered. A public portfolio is an invitation to view the material; it is not a general license to republish the artwork or sell it as your own.
3. Meaning of the concept studies
Find the useful note, A clear route, A useful response are original independent concept studies, created to explain frontend interface development through specific examples. Their names, scenarios and any sample values are fictional. They are not commissioned client projects, launched products, actual business findings or customer endorsements. The supporting explanations describe the work visible in each example. They do not claim a measured commercial result. Keep the concept label with the example when discussing it, and do not rely on an illustrative figure as evidence about a real organisation or an actual service.
4. Service descriptions and project fit
Descriptions of frontend interface development outline types of work that can be discussed. The appropriate deliverables depend on a project's purpose, supplied content, medium and constraints. A description does not establish a fixed package, fee, production schedule or acceptance of every requested task. State important technical requirements and intended uses before a scope is agreed. Where a project needs specialist production, legal review, writing, photography or other services, responsibility for those components should be made explicit rather than assumed from a general design description.
5. Enquiries and email drafts
The form prepares a message for review and offers a mailto link to your email application. It does not send the message from a website server, take payment or reserve time. You decide whether to send the draft through your own email service, and can edit it beforehand. A generated draft is not an acknowledgement of receipt. Email services may reject, delay or fail to deliver messages. Any confirmation of scope, receipt or acceptance must come from the actual conversation, not from the website's draft preview.
6. Proposals and agreement
If a discussion proceeds, the parties should establish the scope in a written proposal or other clear agreement. Useful points include deliverables, source files, revision stages, responsibilities for content, intended uses, schedule, fees, payment arrangements and the treatment of changes. These website terms do not supply missing project details or imply unlimited revisions. A later agreement may contain more specific conditions for the work it covers. Resolve conflicts or uncertainty before relying on either document, while preserving any requirements that cannot lawfully be excluded.
7. Fees, payments and availability
The portfolio has no checkout and does not publish a standard price list. No payment is collected through its enquiry form. A proposed fee, deposit, invoice method or cancellation arrangement must be established in the actual project discussion, together with any applicable currency and relevant charges. Similarly, a preferred deadline entered in the form is a request rather than a confirmed delivery commitment. Do not send card numbers or banking credentials in the message. Verify payment instructions in the agreed communication before making any separate project payment.
8. Materials supplied for a project
When supplying text, data, code, illustrations or other project materials, make sure you can authorise their intended use. Identify licence conditions, confidentiality needs and any restriction on distribution before work begins. Initial enquiries should not contain passwords, private third-party records or unrestricted account access. Sample information can be sufficient to discuss an approach. The parties need to agree who checks facts, approves source content and reviews technical requirements. A useful visual or working prototype cannot supply missing permissions or automatically certify the underlying information.
9. Intellectual property and files
Portfolio artwork, page content and design studies are presented for viewing. Ownership and permitted use of any commissioned design, concepts, rejected options, source files or licensed components must be addressed separately in the engagement terms. Viewing an example does not grant rights to use its fictional identity for a real product or event. Fonts or other components can also have their own licenses. Discuss intended reproduction, modification, distribution and file handover before commissioning work so the final scope supports the uses you actually need.
10. Third-party services and production
Your email application, network access and any separately chosen publishing, software or hosting provider have their own terms and technical behaviour. A portfolio example cannot certify compatibility with every browser, document format, device or data source. A commissioned project needs agreed target environments, input formats, file handover, licences and acceptance criteria. Third-party subscriptions, live hosting, operational monitoring and external data access are not automatically included. Responsibility for factual checking, publication approval and any specialist review should be assigned before relying on a deliverable in a real service or decision.
11. Accuracy, access and responsibility
The site aims to explain its subject clearly, but a portfolio cannot anticipate every production context or visitor requirement. Pages may change and technical access can be interrupted. No specific business result, sales increase, audience response or uninterrupted access is promised. Consider the examples alongside the actual requirements of your project rather than relying on them as universal instructions. These statements do not exclude responsibilities or remedies that applicable rules do not allow the parties to exclude, and do not replace commitments in an agreed project contract.
12. Changes, questions and related notices
The displayed revision date identifies this version. Later updates apply to the website as published; they do not silently amend a separately agreed commission. Consult the Privacy policy for the form and data workflow, the Cancellation and refund policy for the distinction between an enquiry and a paid project, and the Portfolio disclaimer for the status of examples. If you need to clarify use of the portfolio or a proposed engagement, prepare an email to [email protected]. Include the relevant page or agreement so the question can be understood in context.