Privacy policy

This policy explains what Quant Compose collects when you visit www.quantcompose.com or use the private beta workspace at app.quantcompose.com, and what we do with it. It is written in plain English rather than dense legal language, because a policy nobody can actually read is not a meaningful protection.

Who is responsible for your data

Quant Compose, London, England, is the data controller for the personal data described in this policy. A registered business address will be added to this policy before the site leaves private beta. Until then, the fastest way to reach us about anything in this policy, including a request to exercise your rights, is contact@quantcompose.com.

The marketing website

www.quantcompose.com is a static site without Google Analytics, advertising pixels or comparable visitor analytics. We do not load analytics scripts, set analytics cookies or send page visits or form contents to an analytics service. Hosting providers may retain request logs and use security mechanisms to operate and protect the site.

Your colour scheme is stored locally on your device across visits; your accent is stored for the current tab session. These appearance preferences are not sent to an analytics service. Any analytics choice saved by an earlier version is ignored. See the cookie policy for storage details.

The forms on the site, and what each one collects

The site has five forms, each submitting to a small handler running on the same host as the website. No third-party marketing platform receives your submission directly.

Contact form. Collects your name, email address, and the message you write. Used to answer your question and, if the conversation continues, to correspond with you about it. Lawful basis: legitimate interest in responding to enquiries directed at us. Retention: 12 months from your last message, after which it is deleted unless a legal or accounting reason requires it to be kept longer.

Private beta application. Collects your name, email address, and the information you provide about your intended use of the workspace — for example, your research focus or institutional affiliation, if you choose to share it. Used to evaluate and, where a place opens up, to invite you to the private beta by email. Lawful basis: legitimate interest in operating a staged, invitation-only beta programme, and your consent to being contacted about it, given by submitting the form. Retention: 24 months from submission, after which an application that has not converted to an account is deleted.

Institution enquiry form. Collects your name, work email, organisation name, and the details of your enquiry. Used to respond to enquiries about institutional plans, SSO/SCIM provisioning, or deployment options. Lawful basis: legitimate interest in responding to commercial enquiries. Retention: 24 months from submission.

Newsletter sign-up. Collects your email address only. Used to send occasional updates about the product, if and when we publish them. Lawful basis: your consent, given by submitting the form. To unsubscribe, email marketing@quantcompose.com from the subscribed address. Removal is handled manually; this website does not currently provide an immediate automated unsubscribe link.

Article feedback. Collects the article’s page address and your Yes or Not really response. The handler also accepts an optional note of up to 1,000 characters. No name or email address is requested. Feedback is stored on our server to help review the usefulness of articles; the feedback handler does not send an email notification.

How form submissions are stored and handled

Each form is handled by a small script running on the same server as the website. Submissions are written to files, preferably outside the public web directory. If that location is unavailable, the handlers use a protected api/_data/ directory with server rules denying web access. Stored records also include the submission time, a hash of the IP address and a shortened browser user-agent string. Enquiries and newsletter sign-ups send email notifications to the relevant team address; article feedback is stored without an email notification. We do not sell, rent, or otherwise share the contents of any form submission with third parties for their own marketing purposes.

The private beta workspace

The workspace at app.quantcompose.com is currently invitation-only. Creating an account there involves separate data handling from the marketing site — your account profile, the research projects you create, and the data you upload or connect are all covered by the workspace’s own in-app terms and the account-level protections described in our product documentation, including tenant isolation between accounts and redaction of secrets from logs. This privacy policy covers your interaction with the marketing site and its forms; where an invitation email or the workspace itself asks for further information to set up your account, that request will make clear what is being collected and why at the time.

Cookies

The public website does not set analytics or advertising cookies. Appearance preferences use local and session storage on your device. See the cookie policy for details.

If you are in the UK or the EU, you have the right to: request a copy of the personal data we hold about you; ask us to correct it if it is inaccurate; ask us to delete it, subject to any legal reason we may have to retain it for a defined period; ask us to restrict how we use it; object to processing based on legitimate interest; and receive a copy of data you provided to us in a portable format. You also have the right to complain to the UK Information Commissioner’s Office (ico.org.uk) if you believe we have not handled your data correctly, though we would ask that you contact us first so we have the chance to put things right.

To exercise any of these rights, email contact@quantcompose.com. We will respond within one month, as required by law, and will ask for reasonable proof of identity where necessary to protect your data from being disclosed to the wrong person.

Security

Form submissions are stored outside the public web directory where available, or in the protected api/_data/ fallback with server rules denying web access. The workspace applies further protections described in our security documentation, including per-user password hashing, optional two-factor authentication, redaction of secrets from logs, and tenant isolation between accounts. No system is perfectly secure, and if we become aware of a breach affecting your personal data, we will notify you and the ICO as required by law.

Changes to this policy

We will update the date at the top of this page whenever this policy changes, and for a material change we will make reasonable efforts to notify beta users and newsletter subscribers directly rather than relying solely on a page update.