Write to a person who builds the product.
Contact us.
Email is the way in, and it is the only channel, so nothing here promises a line that would go unanswered. The inbox is read by the people who build the product, which is why a specific question beats a meeting request.
- Email.
- contact@primesurvey.eu
- Data protection.
- dpo@primesurvey.eu
- Office.
- Terenure Enterprise Centre, 17 Rathfarnham Road, Terenure, Dublin, D6W X921, Ireland
Who answers
The inbox is read by the people who build the product.
This inbox reaches the people who build the product, with no sales team or ticket queue in between. Say which of these you are in the first line and the first reply can answer something.
- 01
A researcher or a project coordinator
contact@primesurvey.eu- What you are studying, and roughly how many participants.
- Whether the data will be pseudonymised, and whether any question touches special-category data.
- The deadline your ethics committee or funder has set, if there is one.
- 02
A data protection officer or a compliance function
dpo@primesurvey.eu- The assessment you have to complete, and which parts of it you need from a processor.
- Whether your institution requires EU-sovereign hosting and operation, and whether sub-processors need naming individually.
- Any question you already know we will fail. The answer is on the product page and we would rather point at it than talk around it.
- 03
A research IT lead or a CISO
contact@primesurvey.eu- Whether you intend to self-host or use the managed platform.
- Your identity provider, and whether you need OIDC or SAML.
- The security review you run on new suppliers, so we can tell you up front which parts we can answer today.
What we can send you today
- A written answer on where data is processed and by whom, with the sub-processors named.
- The product page, which lists what the software cannot do as well as what it can.
- A written description of how the launch gate refuses a study whose lawful basis or impact assessment is missing, precise enough to check against the product yourself.
What we are still preparing
- A signed data processing agreement. It is being drafted and we will not pretend otherwise.
- A jurisdictional exposure statement, the artefact that would end most of these conversations fastest.
- An accessibility conformance statement. WCAG 2.2 AA is our tested target and we have not earned a conformance claim.
- A penetration-test summary or an ISO certificate. Neither exists.
Contact
Write us a message.
One inbox, read by the people who build the product. Say in the first line whether you are a researcher, a data protection officer or a research IT lead, and what you have to satisfy. It makes the first reply useful instead of a request for a meeting.
- inbox
- 1inbox
- bots
- 0bots