Website information
Privacy & data handling
Saved drafts stay on your device. Choosing Send shares the details with Cobnex by email. This website has no connected advertising or analytics service.
What happens to information on this website
Forms
Drafts and downloads stay on your device. They are not submitted to Cobnex.
Local preferences
Drafts and privacy preferences can be removed through your browser settings.
Request protection
Cloudflare processes network requests. The Worker uses a hashed IP-derived key for rate limiting.
Information you enter
Choosing Send transmits your contact details and request to Cobnex through its configured email provider so the team can respond. Downloading a PDF creates a local copy. Choosing Save draft stores the full project brief, including the contact details you entered, in this browser only. Do not enter passwords or confidential customer records into a project brief.
Browser storage
Your appearance setting and cookie choice use local browser storage. Cookie choices expire after 180 days and can be changed through Privacy settings in the footer. Necessary storage remains available when optional cookies are rejected. The site currently has no connected analytics or advertising service. Saved drafts and preferences can also be removed through your browser settings.
Network requests and rate limiting
The hosting provider processes network requests and associated request metadata. The Node.js deployment uses Hostinger hosting and the review deployment uses Cloudflare Workers. The application uses a hashed key derived from the connecting IP address for request rate limits. These controls operate separately from locally saved form drafts.
Questions about your information
Email hello@cobnex.com.au to ask about the information in an enquiry or to request access, correction or deletion. Do not send passwords, access tokens or unnecessary customer records. Email delivery and storage are handled by the configured mailbox provider. Business-specific retention periods and legal entity details must be confirmed before production launch.
Downloaded documents remain your responsibility
A downloaded brief, enquiry or support document is a local copy that you choose to keep or share. Creating that document does not send its contents to Cobnex or open a support ticket. The browser may place it in a downloads folder that is synchronised by your device or organisation. Those arrangements are controlled outside this website.
Review the document before sharing it through an agreed channel. Remove personal information that is not necessary to explain the request. For support evidence, prefer a redacted example and a description of the impact over a full customer record. Never include passwords, access tokens or private keys.
Using a shared or managed device
Local storage belongs to the browser profile in use. Another person with access to that profile may be able to view saved drafts or downloaded files. If the device is shared, avoid saving sensitive draft information and clear the relevant browser data when you finish. Removing browser data does not remove files already downloaded to the device.
A managed browser, backup service or security product may apply its own retention and monitoring rules. This page does not describe those separate services. Follow your organisation's information handling requirements when preparing a project brief or recording an incident, especially where the request concerns customer or employee information.
Distinguish page access from form submission
Loading a page necessarily makes network requests for the website and its assets. That activity is separate from the local document generation offered by the contact forms. The absence of an advertising service does not mean that hosting and security infrastructure process no request information.
The review site does not specify a provider log retention period or make a promise that all network metadata stays on the visitor's device. Before a live collection service is introduced, its actual processors, retention decisions and contact arrangements need to be documented. Changes to collection behaviour should be reflected here and explained at the point where information is requested.