Legal
Privacy Policy
How BinaryRise handles the information you send through this website.
This page is not finished
The text of this policy has to be written and approved by BinaryRise. It is a legal document, not website copy, and nobody on the build side is going to draft it — a privacy policy that reads as finished but was invented by a developer is worse than an obviously empty one.
The headings below are the four things the policy has to answer. Engineering has already written down exactly what the contact form collects, where it is stored, who can read it and how long it is kept, so this is a fill-in-the-blanks job rather than a blank page: see .docs/privacy-content-request.md in the repository.
What we collect
[TO BE SUPPLIED AND APPROVED BY BINARYRISE]
Every field the contact form stores, plus what the server records on its own (IP address, browser user agent, the page the form was submitted from) — the full list is in .docs/privacy-content-request.md.
Why we collect it, and who can see it
[TO BE SUPPLIED AND APPROVED BY BINARYRISE]
The lawful basis for each purpose, whether the details are used for anything beyond replying to the enquiry, and every third party the data reaches — including the email provider that delivers the notification.
How long we keep it
[TO BE SUPPLIED AND APPROVED BY BINARYRISE]
A retention period for the submissions themselves and for the database backups, and what happens at the end of it. There is currently no automatic deletion of submissions — that is a decision, not an oversight, and it has to be made here.
How to ask us to delete it
[TO BE SUPPLIED AND APPROVED BY BINARYRISE]
A named contact route that a member of the public can use, and how long BinaryRise takes to act on such a request.