Privacy Policy

Your privacy is important to us. It is JARVIS' policy to respect your privacy and comply with any applicable law and regulation regarding any personal information we may collect about you through our JARVIS bot.

This policy is effective as of 20 March 2022 and was last updated on 4 November 2026.

For a changelog, please see the commit history for this file located here

Information We Collect

Information we collect includes both information you knowingly and actively provide us when using or participating in any of our services and promotions, and any information automatically sent by your devices in the course of accessing our products and services.

Log Data

When you use our JARVIS services, if opted in to usage data collection services, we may collect data in certain cicumstances:

• Administrative activity (i.e. ban, warn, mute)
  • User ID (either as admin or as the recipient of the activity)
  • Guild ID of activity origin
  • Discriminator at time of activity (bans only)
  • Username at time of activity (bans only)
• Admin commands
  • User ID of admin who executes admin command
• Reminders
  • User ID
  • The guild in which the command originated
  • The channel in which the command originated
  • Private text entered via the command
• Roleping
  • User ID for user bypasses
• Pinboard
  • Message ID of pinned message
  • Channel ID of pinned message
  • Guild ID of origin guild
• Tags
  • User ID of creator
  • User ID of editor
  • Guild ID of origin guild
• Temprole
  • User ID of user given role
  • Uesr ID of admin who gave user role
• User Settings
  • Per-user settings for commands (currently not in use)
• Captchas
  • Verification captchas (currently not in use)
• Website audit trail
  • User ID of the admin who changed a server's settings or rules on the website
  • Guild ID, what changed (setting names with old and new values) and when
  • Deleted automatically after one year
• Ban appeals (website)
  • User ID of the person appealing, the guild, the message they wrote and when
  • The decision, any note, and the User ID of the moderator who decided
  • Deleted when the person deletes their data; the moderator's ID is handed to JARVIS
  • When an appeal is made, the server's moderators are told in its mod-log channel that someone appealed (without what was written); the person is sent a message with the decision
• Website moderation requests
  • User ID of the admin who asked for an action (warn, kick, mute, unmute, ban, unban) on the website
  • User ID (or channel) of the target, the reason, any options (such as purge filters), and the outcome
  • Deleted automatically after 90 days
• Automated activity logging
  • We store no information about users who edit nicknames, join/leave servers, or other related activities. However, this information, if configured by server admins, is relayed into a Discord channel and is not automatically deleted, nor do we have control over this information.
    • This information is also stored by Discord via their Audit Log, which we also have no control over. Please contact Discord for their own privacy policy and asking about your rights on their platform.

Message Content

While JARVIS does not store message content, it does read all messages sent in a server for the following reasons:

• Anti-phish and anti-malware
  • Phishing and malware URLs are automatically scanned and the origin message deleted
• Anti-invite
  • Deletes Discord server invites
• Raid and spam alerts
  • Only if a server turns them on. For about a minute, JARVIS keeps in memory (never in the database, and lost on restart) who posted in which channel, a fingerprint of the text, and who joined, to notice raids and spam runs
  • When one is noticed, a short excerpt of the message, the user and channel IDs, and links to the messages are posted in the server's chosen alerts channel. JARVIS never acts on its own because of an alert
• Filters
  • Deletion of messages based on custom regex filters

Website and Dashboard

JARVIS also has a website where you can sign in with Discord to manage your reminders, delete your data, and (if you have the right permissions) manage the settings of servers that use JARVIS. Using the website is optional.

• Sign-in uses Discord's OAuth2 with only the identify and guilds permissions. We never see your Discord password.
• When you sign in, we store a session containing your user ID, display name, avatar, and the list of servers you share with JARVIS along with your permissions in each. Your Discord access token is used once during sign-in and is not kept.
• Sessions expire automatically (7 days by default) and are deleted when you sign out or delete your data.
• The website sets only the cookies it needs to work, and no others:
  • jarvis_session: keeps you signed in (HttpOnly, SameSite=Lax, and Secure over HTTPS)
  • jarvis_oauth and jarvis_next: protect the sign-in process and remember where to send you afterwards; they expire after 10 minutes
• The website has no analytics, advertising, or third-party trackers, and its fonts and scripts are served by the site itself. Web servers and reverse proxies in front of the site may log technical request details, such as IP addresses and paths, for security and troubleshooting.
• Changes you make on the website are stored the same way as changes made with commands, and are covered by the rest of this policy.

Operator Access

The few people who run JARVIS have a private area of the website, separate from the server pages, to keep the service healthy. It covers every server JARVIS is in. Through it, operators can see:

• Counts and trends: how many messages JARVIS has seen (never what they said), how many members, channels, and servers joined or left, and how quickly JARVIS is responding
• Server names, IDs, member counts, and how each server has configured JARVIS
• Whether JARVIS and its background services are running, and the state of the website's action queue
• JARVIS' own error and warning logs, kept briefly in a size-limited store, which can contain user, channel, and server IDs but never message content
• Look-ups by user ID of which servers someone shares with JARVIS, and the counts of what is stored about them (reminders, appeals, sessions), not the contents of private records
• Which accounts are signed in to the website, with the sign-in and expiry times. Operators can end a sign-in; the sign-in secret itself is never shown

Operators use this to find problems, remove duplicate or leftover data, and carry out deletion requests. They can also stop JARVIS from answering a particular user, or make it leave and avoid a particular server, for example after abuse reports. A block stores the ID, the reason the operator gave and who set it, until it is lifted or expires. Changes made there are recorded in an audit trail kept for a year, and the warning and error logs are deleted after 7 days. Operators cannot read your messages through it, because JARVIS does not store them.

Use of Information

We use the information we collect to provide, maintain, and improve our services. Common uses where this data may be used includes sending reminders, helping administrate Discord servers, and providing extra utilities into Discord based on user content. What we do not do is sell your information, ever.

Security of Your Personal Information

Although we will do our best to protect the personal information you provide to us, we advise that no method of electronic transmission or storage is 100% secure, and no one can guarantee absolute data security. We will comply with laws applicable to us in respect of any data breach.

How Long We Keep Your Personal Information

We keep your personal information only for as long as we need to. This time period may depend on what we are using your information for, in accordance with this privacy policy. If your personal information is no longer required, we will delete it or make it anonymous by removing all details that identify you.

Your Rights and Controlling Your Personal Information

You may request access to your personal information, and change what you are okay with us collecting from you. You may also request that we delete your personal identifying information. There are multiple ways to remove your data:

• Run the /data export command in any guild, or use My data on the website, to download a copy of your data
• Run the /data delete command in any guild, or use My data on the website, to delete it
• Contanct @zevaryx on Discord
• Join the help server at https://discord.gg/4TuFvW5n and ask in a help forum thread

Limits of Our Policy

Our website and Discord bot may link to external sites that are not operated by us (ie. discord.com). Please be aware that we have no control over the content and policies of those sites, and cannot accept responsibility or liability for their respective privacy practices.

Changes to This Policy

At our discretion, we may change our privacy policy to reflect updates to our business processes, current acceptable practices, or legislative or regulatory changes. If we decide to change this privacy policy, we will post the changes here at the same link by which you are accessing this privacy policy.

Contact Us

For any questions or concerns regarding your privacy, you may contact us using the following details:

Discord

@zevaryx

https://discord.gg/4TuFvW5n