Skip to main content
Trust CenterRetention derived from the codeThe scope of the MSIoU networkReporting vulnerabilities

What this system really does with data — with the periods, the tables and the place in the code

This page is not a summary of the privacy policy. It carries what policies usually leave out: which tables hold the data, after how many days and by what mechanism it is deleted, on what terms data leaves the server it arose on, and how to file a request and what happens to it next.

Data matters

privacy@venon-sec.xyz

We answer without undue delay, and at the latest within a month (Article 12(3) GDPR).

Reporting vulnerabilities

security@venon-sec.xyz

Document last reviewed: 5 August 2026.

Compliance state

What is in place

Every entry leads somewhere it can be checked. The list carries nothing unbacked — a “ready” without an address to verify it would be handing ourselves a certificate.

Data categories

What is stored, what for and on what basis

Every category names its source file. If the code changes and this description does not, the discrepancy will be visible.

Server configuration

Example tables
GuildConfig, VenonSecConfig, AntiFakeConfig, LevelingConfig, PowerRole, ApplicationConfig and the remaining module settings
Purpose
Remembering how the administrator set the bot up: protection thresholds, channels, roles, panel content.
Legal basis
Article 6(1)(b) GDPR — performance of the service contract.
Retention period
For as long as the bot is on the server. After the bot is removed — deleted following a 30-day grace period.

src/db/guildDataPolicy.js (kategoria configuration)

Module operating data

Example tables
TempBan, TempMute, TemporaryRole, AfkStatus, Giveaway, Application, TempVoice, Invite, game states
Purpose
Keeping the state of running features: timed penalties counting down, giveaways in progress, open applications, temporary channels.
Legal basis
Article 6(1)(b) GDPR — performance of the contract; Article 6(1)(f) — the server administrator's legitimate interest in moderation.
Retention period
Until the event ends, and at the latest 30 days after the bot is removed from the server.

src/db/guildDataPolicy.js (kategoria operational)

Members' personal data

Example tables
Profile, UserSettings, LevelSystem, LevelPath, SocialBond, OnlineTime, OnlineSession, UserDailyStat, ActivitySpy, CustomQuote, MemberDataRequest
Purpose
Levels and activity paths, time spent in voice channels, daily statistics, personal settings and a member's own notes.
Legal basis
Article 6(1)(f) GDPR — legitimate interest; optional features (the MSIoU passport, for instance) rest solely on Article 6(1)(a) — consent.
Retention period
30 days after the bot is removed from the server; the deletion strips the Discord identifiers (anonymization: delete_discord_identifiers).

src/db/guildDataPolicy.js (kategoria personal_data)

Moderation and audit records

Example tables
Case, Warn, SecurityIncident, SecuritySignal, SecurityAction, ShieldSession, AntiFakeEvent, LockdownLog, ActivityLog, Report, ReputationLog, MsiouLookupLog, MsiouAlert, GuildBackup
Purpose
Evidence of who took a moderation action and why; raid and abuse detection; the ability to appeal a decision.
Legal basis
Article 6(1)(f) GDPR — legitimate interest in the security of the server and in the accountability of moderation decisions.
Retention period
Longer than the other categories: 90 days after the bot is removed, after which the server record itself is deleted too.

src/db/guildDataPolicy.js (kategoria audit_log) + src/db/guildLifecycle.js

Panel sessions

Example tables
DashboardSession
Purpose
Keeping an administrator signed in to the web panel after logging in through Discord OAuth2.
Legal basis
Article 6(1)(b) GDPR — necessary to make the panel available.
Retention period
Until the session expires or is signed out.

prisma/schema.prisma (model DashboardSession)

Service status samples

Example tables
StatusSample, StatusDay
Purpose
The availability and latency charts on the /status page. Contains no user identifiers.
Legal basis
Article 6(1)(f) GDPR — running the service and keeping it transparent.
Retention period
Raw samples: 7 days (deleted on a cycle). The daily aggregate: the 90-day uptime window.

src/services/StatusMonitor.js — RAW_RETENTION_MS, UPTIME_DAYS

Retention

When the data disappears

Deletion is triggered by removing the bot from the server, not by the age of a record. While the bot works, moderation records are kept — that is what they are for. Writing “we delete the logs after 90 days” would be untrue, so we do not write it.
  1. The bot is removed from the server

    The server is marked as departed

    `Guild.departedAt` is set. From that moment the grace period runs — the data is still there, so that removing the bot by accident does not wipe a year's worth of configuration.

  2. 30 days after the bot is removed

    Configuration, operating data and members' personal data — deleted

    Every category with a retention of 30 days or less is deleted. Only the audit records remain, so the basis for a moderation decision can still be reconstructed.

  3. 90 days after the bot is removed

    Audit records and the server record — deleted

    The rest of the data tied to the server is deleted, and finally the `Guild` record itself. After this stage nothing that could be attributed to that server remains.

  4. On a cycle, regardless of the bot's presence

    Raw status samples — deleted after 7 days

    The status monitor deletes samples older than 7 days on every measurement cycle.

The deletion is carried out by the scheduler GuildLifecycleScheduler which runs every 6 hours. The grace period is 30 days, the retention of audit records — 90 days. The operation runs in a transaction: either the server is cleared entirely, or it is not touched at all.

src/schedulers/GuildLifecycleScheduler.js, src/db/guildLifecycle.js

The MSIoU network

The only flow that carries data beyond the server

MSIoU lets an administrator see a person's disciplinary history gathered on other servers in the network. It is the most sensitive feature in the whole product, so 9 hard rules govern it — every one enforced in the code, not in the terms.

Your own server always, the network only for its members

An administrator sees their own server's data unconditionally. From other servers they get confirmed sanction entries only — and only when their server belongs to the network and receives (`enabled && receive`), and only from servers that publish to it (`enabled && publish`). A server outside the network has no view into it.

src/modules/msiou/dataPolicy.js — resolveReadableGuildIds

A failure takes access away, it never grants it

Any error while reading the network configuration narrows the scope to your own server (fail-closed). There is no path in which a fault widens the visibility of data. A failed read of entries shows up in the dossier as “no data”, not as zero entries.

src/modules/msiou/dataPolicy.js, src/modules/msiou/dossier.js

No rating of the person and no revoked sanctions

The dossier and the alert give no score and no “clean” label — they state the number of confirmed entries in the available data. A sanction revoked at the source is not counted as an entry: the revocation is a correction, and only the number of such revocations is given. No entries means only that there are none in the available data.

src/modules/msiou/networkRecords.js — networkCaseWhere

The source of an entry is a pseudonym

Another server sees the source of an entry as a stable pseudonym (e.g. “Source 4F2A9C1B”) — without the server ID, its icon or the moderator who issued the sanction. It sees the server's name only if the publishing server turned that on itself (`revealName`).

src/modules/msiou/networkRecords.js — describeSource

An objection (opt-out) narrows the scope to a single server

An entry in `MsiouUserOptOut` stops the dossier from showing entries from the network and limits it to the server where the question was asked, and the person's sanctions are not sent out in network alerts. Opting out removes someone from the NETWORK, not from the records of the server they are actually on — those belong to that server's administrator.

src/modules/msiou/dossier.js, src/modules/msiou/dataPolicy.js, src/utils/msiou.js

The passport runs on consent, not by default

A positive record (tenure, activity, no penalties) leaves the server only after the person concerned turns the passport on themselves. The very existence of an `MsiouPassport` row is the consent; withdrawing it deletes the row. The passport shows aggregate numbers only — server names never leave it under any configuration.

src/modules/msiou/passport.js, prisma/schema.prisma — MsiouPassport

Every lookup is recorded

Looking someone up in the dossier goes into `MsiouLookupLog` along with who asked and from where (a command, the panel, the API). The person asking is accountable too — that is the safeguard against using the dossier for surveillance.

prisma/schema.prisma — MsiouLookupLog, src/utils/msiouLookupLog.js

Alert inbox: 90 days, the assessment stays with the recipient

An alert is an entry in the receiving server's inbox: what arrived and how it was assessed (reviewed, dismissed, disputed). The assessment never goes back to the source. The sanction's content is read live from the source — a sanction revoked at the source turns the alert into “withdrawn”, and deleting the source server's data removes the content. Alerts older than 90 days are deleted.

src/modules/msiou/alerts.js — ALERT_RETENTION_DAYS

Activity comes from this server only

Activity, reputation and reports in the dossier come only from the server where the question was asked — they never go to the network. Activity is aggregate numbers (all-time and for the last 30 days), with no message content or history.

src/modules/msiou/dossier.js — collectActivity, ACTIVITY_WINDOW_DAYS

Your rights

Access, rectification, erasure — how it works in practice

Requests do not end at an email address. Each one lands in a register tied to the server, moves through statuses and requires a decision with reasons.

ACCESS

Access to data (Article 15 GDPR)

A summary of what the server holds about a person: cases, activity, applications, incidents.

CORRECTION

Rectification (Article 16 GDPR)

Correcting an incorrect entry — a warning issued by mistake, say, or assigned to the wrong person.

DELETION

Erasure (Article 17 GDPR)

A request to delete the data. Moderation records may be kept where they are necessary to defend against claims — a refusal has to carry its reasons in the decision field.

APPLICATION_APPEAL

Appeal against an application decision

Created automatically when someone appeals a rejected application. It ties the request to a specific submission (`submissionId`).

1. Submission

The request goes to the administrator of the server where the data arose, or to the contact address given in the policy. It lands in the `MemberDataRequest` register tied to that server.

2. Review

The request moves through the statuses OPEN → IN_REVIEW → RESOLVED or REJECTED. The panel records who decided it (`resolvedById`) and when (`resolvedAt`).

3. A decision with reasons

Every closure requires the text of the decision (`resolution`). A refusal without reasons is not possible in this register — that is the condition for being able to challenge it.

4. Appeal

A decision may be appealed to the President of the Personal Data Protection Office, ul. Stawki 2, 00-193 Warsaw, Poland. We would rather you got in touch first — most matters are settled faster that way.

Roles

Who the data controller is

For the data of a given server's members, the controller is that Discord server's administrator. The service provider acts as a processor and follows their instructions within the bot's configuration.