This policy explains what the Harp Isles bug tracker (the website at this address and the Harp Isles bot in the Harp Isles Discord server) collects, why, and how it is handled. It is run by the Harp Isles team.
What we collect
- Bug reports posted in Discord. When you create a post in the
#public-bug-reportsforum channel, the bot reads that post: its title, text, tags, attachments (screenshots and videos), reactions, and any replies you or a Lead Tester add in that thread. The bot only reads messages in that channel; messages elsewhere in the server are ignored. - Your Discord identity. Your Discord user ID, username, display name, and avatar, so a report can be attributed to you and so the bot can reply to you in the thread.
- Staff sign-in. Staff sign in to the dashboard with Discord. We receive your Discord ID, username, avatar, and your roles in the Harp Isles server (to check whether you are a Lead Tester or Admin). We do not receive your email address or password.
- Nothing else. No analytics trackers, no advertising cookies, no game account data.
How we use it
- To organise bug reports: the bot keeps your post as you wrote it, reads any
Label: valuelines from the report template, runs a few fixed keyword checks (for example, whether a post may describe an exploit), and lists similar open reports. Lead Testers make every decision. - To publish approved bugs on the public status board so players can see what is planned, in progress, and fixed. Public pages show the report text, attachments, the number of affected players, and the reporter's Discord display name and avatar.
- To give developers a work board of approved bugs.
- To let you know when a bug you reported changes status (one message in your thread per change).
Who processes it
- Railway (United States) hosts the database, the bot, the website, and the private file storage for attachments.
- Anthropic receives the text of approved bug reports so a short developer summary can be written on the team's work board. Only text is sent, only for that purpose, and that summary is never shown in Discord or on this site.
- Notion holds the developers' work board, which contains approved reports.
- Discord is where reports are posted and where the bot operates, under Discord's own terms and privacy policy.
We do not sell data and do not share it with anyone else.
How long we keep it
Reports and attachments are kept while the bug is being tracked and afterwards as a record of what was fixed. Declined or duplicate reports are kept so they are not re-reported. Staff sign-in sessions expire after seven days.
Your choices
- You can edit or delete your own Discord post at any time; the bot re-reads edits while a report is still pending.
- To have a report removed from the tracker, or your name hidden from a public page, email contact@harpisles.com from the Discord account that made the report (or tell a Lead Tester in the server).
- Exploit and security reports are hidden from the public site by default.
Children
Harp Isles is played by people of many ages. We collect nothing beyond what Discord already shows in the server, and we do not ask for or store real names, addresses, or contact details. Parents or guardians who want a child's report removed can email the address above.
Cookies
The website sets one cookie, and only for staff who sign in: a session cookie so the dashboard knows who you are. Visitors who only browse get no cookies.
Changes
If this policy changes in a meaningful way we will update the date at the top and post a note in the Harp Isles Discord.