How Made by Binary handles website data.

Contact and project enquiries

When you submit the project form, Made by Binary receives the name, contact details, project type, budget range, and message that you choose to provide. This information is used to review the enquiry, respond, and manage the project conversation. The form also uses security controls such as CSRF protection, a honeypot, and rate limiting.

Consented website analytics

Made by Binary’s first-party analytics records only after analytics consent. It uses pseudonymous visitor and session identifiers to count page views, sessions, contact actions, and successful enquiries. The analytics table stores canonical page paths and broad source, device, and action categories; it does not store raw IP addresses, full URLs with query strings, message text, email addresses, phone numbers, browser user agents, or cookie values.

While a consented public page remains visible, a zero-content pseudonymous presence marker is refreshed so the private admin dashboard can show an approximate active visitor count. This short-lived marker contains no page, contact, or message data, is not added to analytics totals, and expires automatically after activity stops.

Raw first-party analytics events are configured for a maximum retention period of 90 days and require a monitored maintenance task to enforce deletion. Aggregate reporting may be kept longer without the original visitor identifiers.

Google and Meta measurement

If these services are enabled on the server, Google analytics/advertising tags and the Meta Pixel or Conversions API are used only according to the choices shown in the privacy settings. Made by Binary sends sanitized page paths and approved conversion details. A successful project enquiry may include normalized, SHA-256 hashed email or phone data in server-side Meta matching only when marketing consent is confirmed; raw contact details are not placed in browser analytics events.

Google and Meta may process device or network information under their own privacy terms when their services are allowed. Made by Binary does not use the Meta sending token as an analytics-reporting credential.

Your choices

You can accept, reject, or change optional analytics and marketing choices from the privacy settings. A supported Global Privacy Control or Do Not Track signal is treated as a denial. Withdrawing consent stops optional collection, clears related browser identifiers where possible, and requests deletion of the associated first-party analytics identity.

Hosting, security, and retention

The website and its database are hosted on infrastructure used by Made by Binary. Technical server logs may temporarily process standard request information for availability and security. Enquiry records are retained only as needed to respond, manage the business relationship, meet legitimate security needs, or satisfy applicable obligations.

Questions or deletion requests

For a privacy question or a request concerning information you submitted, email hello@madebybinary.com. Made by Binary may need enough information to locate and verify the relevant record before changing or deleting it.

Last updated: 6 September 2026. This operational notice should be reviewed whenever the website’s forms, analytics providers, hosting, or retention practices change.