LEGAL / UNAPPROVED DRAFT
Privacy policy
Last updated: 12 April, 2026
A privacy policy should explain, in clear language, what happens to information when someone interacts with Morrow. The final document must reflect verified practices, applicable law, and approved contact details.
01
Information collected
Approved copy should identify the categories of information actually collected through the website, account creation, enquiries, and any product workspace. Distinguish information supplied directly from information generated through use of the service.
Confirm which account details, source materials, technical information, or other categories apply. Do not assume that a field or illustrative workspace in this design establishes a live collection practice. Describe any optional information and the consequences of not providing required information only after verification.
02
How information is used
Replace this section with an accurate explanation of the purposes for which each confirmed category of information is used. The final wording should describe the real service and any applicable legal basis in the relevant jurisdictions.
Any statements about providing the product, managing accounts, responding to enquiries, analytics, or improving systems need verification. In particular, do not make claims about training, model use, or the handling of source material until the actual arrangements have been confirmed.
03
Sharing and service providers
Approved copy should explain whether information is shared, with whom or with which categories of recipients, and for what verified purposes. Identify the relevant roles and responsibilities where applicable.
Do not insert assumed vendors, model providers, integration partners, or transfer locations. Confirm any service-provider relationships, international transfers, and required safeguards with the people responsible for the product and its legal review.
04
Retention and deletion
The final policy should explain how retention periods are determined for the categories of information actually held. Use specific periods or clear criteria only when the operational process has been verified.
Confirm how deletion requests, account closure, backups, legal obligations, and workspace material are handled in practice. This placeholder does not promise a deletion timetable or establish that any information is retained for a particular period.
05
Rights and choices
Approved copy should describe the rights that apply to the intended audience and jurisdictions, together with a verified process for exercising them. Any restrictions, identity checks, or response periods should be reviewed for accuracy.
Confirm whether choices relating to access, correction, deletion, portability, communications, or similar matters apply. Do not imply that every right is available in every situation. Replace this guidance with language appropriate to the actual service and applicable law.
06
Website technologies
Review the website and product to establish whether cookies, local storage, analytics, or similar technologies are used. The approved policy should describe only technologies and purposes that are actually present.
Confirm whether separate notices or consent controls are required. No analytics, advertising, cookie, or tracking practices are established by this static design, and no statement about their absence should be inferred from it.
07
Questions and contact
Insert the approved legal entity details and a verified route for privacy questions or requests. Confirm who is responsible for receiving and handling those enquiries before publication.
The Contact page is included as a design destination, not a confirmed privacy-request process. Replace this paragraph with reviewed contact information and any relevant supervisory authority or complaint information required by applicable law.
