This notice is intended to explain how Crftdev Technology handles personal information connected with its website and project enquiries.

Before launch: confirm the legal entity responsible for processing, its address, a privacy contact and any applicable data protection contact. The trading name alone does not complete this section.

The project-enquiry form collects your name, work email, optional company and phone number, service selection, project description, budget range, desired timeframe any known demonstration-project context and, when selected, a published package identifier and snapshot of its name and pricing basis. Successful submissions are stored in the database. Downloading a brief alone keeps a copy on your device and does not submit it.

Details are used to handle project enquiries. Optional marketing consent is separate, unchecked by default and recorded with its wording version and submission time. No marketing campaign service is connected. Before launch: approve the lawful basis, consent withdrawal arrangements and handling of hosting logs and email correspondence.

The final notice should identify the categories of service providers and other recipients involved in handling information.

Before launch: confirm hosting, database, storage, email and analytics providers, data locations and any international-transfer arrangements. No providers or safeguards are asserted by this draft.

The final notice should explain how long each category of personal information is retained, or how that period is determined.

Before launch: approve a retention and deletion schedule covering enquiries, correspondence, logs and backups. Verify actual security controls and avoid making unverified guarantees.

The website saves theme, cursor and enhanced-scrolling preferences in local storage when configured by the visitor. The homepage stores a visual-motion pause preference in session storage. The brief tool keeps its working notes in memory in the current tab. The staff administration area uses a necessary authentication cookie for signed-in sessions. Staff account details and private enquiry notes are held in the database. No analytics or advertising integration has been added to the application at this stage.

Before launch: audit the deployed site and its providers for cookies, storage and similar technologies. Update the notice and implement any consent controls required for the actual setup.

The final notice should explain the rights that apply to the processing, how to make a request and how to raise a concern.

Before launch: add a confirmed contact channel and accurate information about requests, response arrangements and complaints to the relevant regulator.

This draft has no approved effective date and is not a completed privacy notice.

Before launch: verify it against the actual website and enquiry operations, complete all outstanding information and record approval and an effective date.

For project information, visit Contact.