Privacy policy
Last updated: 2026-11-14
This policy explains what oculus (the Discord bot and oculus.rocks) collects, why, and how long we keep it. By using oculus you agree to it. Found a mistake? Email [email protected].
What we collect
- User data: User IDs, usernames, nicknames and avatars as Discord shows them.
- Server data: Server IDs and names, and the settings your staff configure (prefix, roles, channels, modules, templates).
- IDs and timestamps: Channel, role and message IDs, and message timestamps.
- Command input: What you type into commands.
- Moderation and security records: The action, reason, moderator ID, target ID and time of moderation actions and security events.
- Verification signals: When you verify in a server that uses it, the result and time, plus checks used to spot alts, raids and bots:
- A scrambled code made from your Discord email (a one way hash; we never store or see the email itself in our systems, and the server's staff never see it). It only tells us whether two accounts share an email.
- Scrambled codes made from your IP address and your network range (one way hashes, never the address itself), to spot accounts on the same network.
- A scrambled code made from your browser and device setup (like screen, graphics and fonts), to spot the same device on several accounts. No cookies are used for this.
- Your network provider's name and number, country, and whether the connection looks like a VPN, proxy, hosting provider or Tor.
- Signs of automated browsers or private browsing, and the bot check result.
- Account details used to spot raids (account age, default avatar, join time).
- Shared flags: If verification finds a likely alt or blocks someone, oculus notes the user ID, the reason and the time. Other servers that use oculus verification see that note when the same account verifies there, so they can spot alts and raiders. The note never includes your email, IP or device details.
- Server backups: A copy of each server's roles, channels, permissions and which members had which roles, so anti-nuke and staff can restore them.
- Messages, only where a feature needs them:
- Tickets: messages inside a ticket. When it closes, a text transcript is sent to the server's ticket log channel and to the person who opened it.
- Starboard, reminders, autoresponders and welcome templates: the message or text the feature uses.
- Message logs: in servers that turn on message logs, oculus keeps a copy of recent messages (text and attachment links) for up to 7 days, so it can show what an edited or deleted message said in that server's log channel.
- Filters check messages as they arrive without saving them.
- Snipe: the last deleted and edited messages and removed reactions in a channel stay in memory for 2 hours so members can use snipe, then they are gone. They are never written to disk.
- AFK: your away message and the links to messages that mentioned you, in memory until you come back.
- Feature data: Levels and leaderboard points, giveaway entries, counters, confessions (stored without showing who sent them, but kept linked to the sender so staff can act on abuse), tags and who made them, reaction triggers and who made them, timers, tic-tac-toe and juul stats, the last member to bump the server, and members who recently stopped boosting.
- Last seen: The time you last sent a message in each server, for the seen and highlight commands.
- Emoji stats: How often each of a server's emojis is used, without who used them.
- Highlights: The words you ask to be told about and what you ignore. When one is said, oculus sends you a DM with that message.
- Birthdays and timezones: Only if you set them, your birthday (month and day, no year) and the timezone and place you chose. Members of servers you share with oculus can see them in the birthday and timezone lists.
- Watch lists: Fortnite items you watch, and crypto transactions you subscribe to (the hash, until it confirms or for 2 days).
- Social feeds: The public accounts a server follows (YouTube, Twitch, Kick, SoundCloud, Reddit, Pinterest), the channel, and which posts were already sent.
- Activity stats: Per server and per day, how many messages and reactions each channel got, total voice time, and how many members were active, for the server's dashboard. Which user IDs were active is kept only until the day after, then only the count stays.
- AI: Questions sent to ask, and messages checked by AI chat watch in servers that turn it on, are processed by oculus's own AI node and are not kept after the answer. Flagged messages are posted to the server's alert channel. The AI is never trained on your messages.
- Downloads: The link you give download and the file it returns pass through oculus's own download node and are not kept. The reposter does the same for links posted in servers that turn it on.
- Media: Images, videos and audio you give to media, OCR, transcribe, shazam and text to speech commands are processed on oculus's own media node and are not kept. To recognize a song, shazam sends an audio fingerprint to Shazam.
- Lookups and searches: Search and lookup commands send only what you type to the service that answers it, like Bing, Wikipedia, AniList, Open Library, TVmaze, Steam, Roblox, CoinGecko, Blockchair, Fortnite API, iTunes, Discogs, LRCLIB, Telegram, TikTok, X, Snapchat or wikiHow. Screenshot sends the website address to thum.io, and run sends your code to Wandbox to run it. Translate, tone and homework answers use oculus's own AI node and are not kept.
- Roleplay: How many times you used each roleplay action on another user, shown on the card.
- Name history: The last 25 usernames oculus saw you use, and your last 25 nicknames in each server, for the names and gnames commands. You can clear them yourself with clearnames and cleargnames.
- Music: What you request and who requested it, for the current session.
- Linked accounts: Only if you add them yourself: your Last.fm username and your fm settings (look, reactions, color), and your Discogs username. Album artwork you submit and your votes are kept with your user ID.
- Website: Our verification page and site sit behind a security and delivery network that checks your browser and IP address to block bots and attacks. We do not store your IP address in our own systems. The site has no tracking or ad cookies; the verification page and the dashboard each set one session cookie, only to keep you signed in.
- Technical logs: Command names, errors and timings, used to fix bugs and keep oculus fast.
Why we use it
- To run commands and features you or your server turned on.
- To protect servers with anti-nuke, anti-raid and verification.
- To fix bugs and keep oculus fast and secure.
Automatic actions
Some features act on their own, using rules the server's staff set: anti-raid and verification can kick, ban or hold back new members (for example very new accounts or accounts spamming the same message), and anti-nuke can remove roles from or ban staff who break the server's limits. If an automatic action affected you, contact the server's staff. You can also email us and we will check whether oculus worked as configured.
How long we keep it
| Data | Kept for |
|---|---|
| Server settings and templates | While oculus is in the server, then 30 days |
| Moderation and security records | Up to 1 year; servers can delete them sooner |
| Verification signals (hashes and checks) | While you are in the server, then 30 days |
| Verification sessions on the website | 1 hour |
| Shared flags | 90 days |
| Activity stats | About 13 months; active user IDs only until the next day |
| AI questions and checked messages | not kept |
| Roleplay counts | Until you ask us to delete them |
| Name history | Until you clear it or ask us to delete it |
| Last seen times and emoji stats | While oculus is in the server, then 30 days |
| Highlights, birthdays and timezones | Until you remove them or ask us to delete them |
| Crypto transaction subscriptions | Until confirmed, at most 2 days |
| Media, OCR, transcripts, lookups and searches | not kept |
| Server backups (roles, channels, role members) | The 4 newest automatic ones and up to 10 manual ones |
| Snipe history | 2 hours |
| Message copies for message logs | 7 days |
| Tickets and transcripts | Until the server deletes them, at most 1 year after closing |
| Starboard, reminders, giveaways, counters, confessions | While the feature is on, then 30 days |
| Levels and leaderboards | While the feature is on, then 30 days |
| Music requests | Until the session ends |
| Linked accounts and their sessions | Until you unlink, or after 6 months without use |
| Technical logs | 14 days |
| Our own system backups | 30 days, then deleted |
Sharing
We do not sell or rent your data, and we do not use it for ads. We only share it:
- With Discord, because oculus runs on Discord.
- With services that host and run oculus for us (servers, storage, the web security and delivery network), only what they need to do that.
- With services you link yourself, like Last.fm or Discogs.
- With the service a lookup or search command asks, only the text you typed.
- When the law requires it.
Your rights
- Delete: Email [email protected] with what you want removed and proof that the account is yours. Done within 14 days, and gone from backups within 30 days after that.
- Access: Email us for a copy of your data. Sent within 7 days.
- Unlink: Remove your links any time with
,lastfm unlinkor,discog logout, or email us. - Clear: Remove your highlights with
,highlight reset, and your name history with,clearnames. - Object: Email us if you disagree with how we process your data, including automatic actions.
Moderation records that a server keeps for its own safety can stay until that server deletes them or the 1 year limit is reached.
Changes
We may update this policy at any time. The date at the top shows the latest version. Using oculus after a change means you accept it.