Warrant Canary

At Vixen Team, we value our privacy greatly. We know that you value your privacy too. That's why we make it a core tenet of our development practices - all of our projects must be developed with standard privacy practices in mind.

However, we need to uphold and enforce our Terms of Use, as well as Discord's Terms of Use. On occasion, we may receive a report from an nMarkov user about a potential breach of our Terms of Use, or a notification from Discord about a potential breach of their Terms of Use. In either of these events, we may need to access user data to investigate the report.

We think it's important to be open with our users, especially when their data is involved. So if we receive a report and data has to be accessed, we will publish information on this page about the scope of the data that was accessed, and the consequences of the breach.

p.s. We know this isn't a warrant canary by the true definition, but it mostly serves the same purpose.

This page was last updated on 30th December, 2023.

2023

December

• 30th December
  • Report concerning a breach of nMarkov's Terms of Use and Discord's Terms of Use/Community Guidelines
  • Specifically, it was reported that nMarkov was being used for the spreading of CSAM and PII obtained via doxxing
  • Scope of access:
    • All messages sent by two specific users were retrieved
    • Due to the nature of the report, all messages sent in any server shared by nMarkov and these users were retrieved
  • Result:
    • An instance of doxxing had been established; the offending user was banned from using the bot, and has been reported to Discord Trust and Safety.
    • Messages containing CSAM or any content involving minors could not be found.
    • Other messages containing content of a graphic nature were found; the offending server(s) were banned from using the bot and applicable messages have been reported to Discord Trust and Safety.
    • The reporting user engaged in threatening and obscene behaviour during the submission of their report and was banned from using the bot.

January

• 23rd January
  • Continuing on from canary entries dated 2022-11-04 and 2022-10-12
  • Discord Trust and Safety has neglected to respond to our report and has closed our ticket. If action has been taken by them, we have not been told about it; as such we consider the matter closed with no action taken on our side.
  • No additional data was collected from this server since the last update.

2022

November

• 4th November
  • Continuing on from canary entry dated 12th October 2022
  • Scope of access:
    • Messages were gathered from the same server to provide an updated archive. This updated archive has been forwarded to Discord Trust and Safety in our original ticket to them

October

• 12th October
  • Report concerning breach of nMarkov's Terms of Use and Discord's Terms of Use/Community Guidelines; further specifics will be provided in the future
  • Scope of access:
    • Messages were gathered from one server
  • Result:
    • The server was reported to Discord Trust and Safety on 13th October; awaiting response
    • No action has been taken by Vixen Team as of 4th November

August

• 11th August
  • Report concerning malicious use of nMarkov; specifically targeted harassment of specific users
  • Scope of access:
    • Messages were gathered from one user, as well as messages from one server
  • Result:
    • The user was banned from using nMarkov services
    • The server was banned from using nMarkov services