Privacy
Your privacy
Echoes is designed so you can share an experience without telling us who you are. This page explains, in plain language, what is collected, what is not, and what happens to your response.
No account required
You can submit a response without signing up, logging in, or providing an email address. There is no social login and no user account for the public form.
What the form collects
The form only stores the answers you choose to give:
- Whether you experienced, witnessed or have a concern about discrimination
- The general context and type of discrimination (optional)
- Your written answers (optional)
- How much the experience affected you (optional)
- Your suggestions for the community (optional)
- The date the response was submitted (the day only, not the time)
The form does not intentionally request your name, email, phone number, student or employee ID, or social media accounts. Please avoid including such information about yourself or anyone else in your written answers.
Technical information
- No tracking. Echoes does not use advertising trackers, social media pixels or third-party analytics.
- No cookies on the public site. The public pages do not set cookies. (Cookies are used only to keep project administrators signed in to the private dashboard.)
- Your draft stays in your browser. While you fill in the form, your answers are kept in your browser tab so they aren't lost if you go back a step. They are cleared when you submit or close the tab, and are not sent anywhere until you press “Submit Anonymously”.
- IP addresses are not stored with responses. To prevent spam, the server briefly keeps a scrambled (hashed) version of your connection address in memory to limit how many responses can be sent in an hour. It is never written to the database and is discarded automatically.
- Hosting logs. Like most websites, the hosting provider may keep standard server logs (which can include IP addresses) for security and reliability. These logs are not linked to responses. [Project team: confirm the hosting provider and its log retention period here.]
How responses are stored
Responses are stored in a private database on a secured server and sent over an encrypted (HTTPS) connection. Responses are never displayed publicly on this website. [Project team: confirm hosting location / provider.]
Who can access responses
Only authorised members of the project team ([Project team / institution name — to be confirmed]) can view responses, through a password-protected dashboard. Team members may review responses, group suggestions into themes and archive responses.
How findings are used
Responses are analysed together to understand patterns and recurring themes. Aggregated findings and community suggestions may be presented to relevant stakeholders — for example university leadership or student and staff groups — to encourage improvements. Individual stories are not published automatically. If a short excerpt is ever quoted in a report, it will be anonymised and edited to remove identifying details.
How long data is kept
[To be confirmed by the project team — e.g. “Responses are kept until the end of the research project and deleted within 12 months of its completion.”]
Contact
If you have questions about this project or how responses are handled, contact the project team at [email protected]. Because responses are anonymous, we may not be able to locate or remove a specific response unless you can describe it precisely.
Last updated: September 2026