Data and Privacy

Crom is made up of a lot of moving parts that collect, store, and display data. I've worked to make Crom as privacy-friendly as possible, only storing what it needs to keep things running. This page keeps track of what data Crom stores, why it needs to store it, and how to request deletion.

Last updated: 06 Nov 2020.

Discord bot (CROM#5028)

Server preferences Reason: Features Retention: Indefinite

Crom has various settings you can tweak to customize its behavior on a per-server level. You can see what data is stored for your server by running crom info. Crom stores the following data from your server.

  • Discord server ID Visibility: Secret
  • Server preferences Visibility: Server members only

You can ask for your data to be deleted on Crom's discord server .

Patreon benefits Reason: Features Retention: Indefinite

For past members of the Crom Patreon, Crom offered additional benefits such as a custom embed color for articles associated with their wiki username. You can see what data is stored for you by saying crom info in a direct message to Crom. Crom may store the following data for you.

  • Discord user ID Visibility: Secret
  • Patreon user ID Visibility: Secret
  • Patreon pledge amount Visibility: Secret
  • Linked wiki user name Visibility: Patreon member only
  • User preferences (i.e. embed color) Visibility: Patreon member only

Keep in mind that patreon benefits are public by nature and linked to your wiki name. You can ask for your data to be deleted on Crom's discord server .

Logging Reason: Diagnostics Retention: < 90 days Visibility: Secret

When Crom encounters problems (e.g. API error, high latency), Crom logs some information about the call so that the root cause could be determined quicker. When Crom encounters an issue, it logs the following data.

  • Discord server (to trace commands to server preferences)
  • Command user (since some commands like lc depend on the discord username)
  • Command string

All logs are deleted within 90 days. Crom will only log messages if they are valid Crom commands that resulted in an unexpected error or delay.

Reddit bot (u/The-Paranoid-Android)

Logging Reason: Diagnostics Retention: < 90 days Visibility: Secret

To make sure parsing logic is working as expected, Crom logs whenever it finds a reddit comment or submission that it can reply to.

  • Extracted SCP numbers and search strings
  • Parent comment/submission permalink
  • Crom reply permalink

None of this is private information. Regardless, all logs are deleted within 90 days.

Crom Backend (https://api.crom.avn.sh )

Wiki crawler Reason: Features Retention: Depends on data Visibility: Public

Crom works by crawling pages on the internet and storing them internally. Since this is publicly accessibly information, there are no privacy controls on this data. In high-level terms, Crom stores the following data.

  • Page information (e.g. title, rating, creation date)
  • Wikidot user info (e.g. user name, user id)
  • Structured page data (e.g. author page listings, attribution metadata pages)

Under normal circumstances, data removed from the source page will cause it to be completely deleted from Crom in a few hours. But because of the complexity of the data expiry system, I cannot guarantee this. Under emergency situations, you can ask for your data to be deleted early on Crom's discord server . Keep in mind that this data is based on publicly available information, and if it's not removed at the source, it will re-appear in Crom's backend.

Logging Reason: Diagnostics Retention: < 90 days Visibility: Secret

For diagnostic and security reasons, Crom keeps request logs. For better privacy, query details and variables are not stored.

  • Source IP address
  • Authenticated user (if authenticated)
  • GraphQL query metadata

All logs are deleted within 90 days.

Crom website

There are no analytics or tracking cookies on this website.