OFFLAW
Zaloguj się

Privacy Policy

Version 1.2 · Effective July 9, 2026 · Updated October 28, 2026

Dokumenty OFFLAW są dostępne po rosyjsku i angielsku; tutaj — wersja angielska.

This Privacy Policy explains what data OFFLAW collects, uses, stores, and protects when you use the Discord bot, the website, the dashboard, support, subscriptions, and related digital services.

By using OFFLAW — adding the bot to a Discord server, signing in through Discord OAuth, setting up a server, paying for a subscription, or contacting support — the user agrees to this Privacy Policy.

A user who does not agree with this Policy should not use the Service.

1. Who we are

OFFLAW is a Discord bot and web service for managing Discord communities, including applications, profiles, reputation, contracts, leave, reports, bonuses, logs, and server settings.

OFFLAW is not a product of Discord Inc., is not affiliated with Discord Inc., and is not endorsed by Discord Inc.

OFFLAW contacts: Support email: yt1dante@gmail.com · Discord support server: discord.gg/Wb27bwmDt5

2. What data we collect

OFFLAW collects only the data needed to run, secure, support, and improve the Service.

2.1. Discord account data

When you sign in through Discord OAuth, OFFLAW may receive:

  • the Discord user ID;
  • the username and display name;
  • the avatar;
  • public Discord profile information;
  • the list of servers available through Discord OAuth;
  • the user's permissions on servers.

OFFLAW never asks for or stores the password of the user's Discord account.

2.2. Discord server data

For the bot to work, OFFLAW may store:

  • the server ID;
  • the server name;
  • channel IDs;
  • role IDs;
  • category IDs;
  • thread IDs;
  • module settings;
  • access permissions;
  • log configuration;
  • settings for applications, contracts, leave, reports, and other features.

2.3. Server member data

Depending on the features enabled, OFFLAW may process:

  • the Discord user ID;
  • the username and display name;
  • the avatar;
  • the member's roles;
  • rank;
  • reputation;
  • the member profile;
  • age, Static, or other data the user entered in a form themselves;
  • the number of contracts, applications, and leave requests;
  • reports, appeals, and moderators' decisions;
  • activity logs within the OFFLAW system.

2.4. Data entered by users

Users and server administrators may enter data through forms, modals, commands, the dashboard, or support tickets. This may include: application texts; form answers; reasons for leave; evidence for reports; links to screenshots or videos; moderators' comments; bug descriptions; support requests.

The user is responsible for making sure that the data they enter into OFFLAW does not violate the law, the rights of third parties, Discord's rules, or community rules.

2.5. Payment data

If the user takes out a subscription, OFFLAW may store: the selected plan and paid add-ons; the currency, date, and amount of the transaction; the billing period; renewal dates; the subscription and payment status; the Stripe identifiers needed to process payment, manage the subscription, confirm Stripe notifications, and reconcile transactions; the history of changes, cancellations, refunds, and payment disputes.

Payment details are entered in Stripe's secure form and processed by Stripe and the available payment providers. OFFLAW does not receive or store the full bank card or bank account number. Which data Stripe processes depends on the payment method chosen; see the Stripe Privacy Policy.

2.6. Technical data and security

When the website, the dashboard, and the API are used, OFFLAW may automatically collect: the IP address; browser and device data; the session ID; cookie identifiers; sign-in time; security logs; request logs; API errors; actions in the dashboard; changes to settings.

This data is used for security, preventing abuse, diagnosing errors, limiting suspicious activity, and protecting the Service.

2.7. Server copies and data transfer

On the Pro and Max plans, OFFLAW makes a copy of the server on behalf of the server owner — automatically once a day and when a server manager (the owner or a member with the “Manage Server” permission) requests one. The copy is used to restore the server's structure (on the same server or a new one) and to give members their roles back when they rejoin. A copy contains:

  • roles, categories, and channels with their access permissions, including private channels the bot can see;
  • forum posts: title, tags, and the text of the first message — without its author or the rest of the conversation;
  • emoji, stickers, sounds, role icons, and server images;
  • server settings, AutoMod rules, and onboarding;
  • bans: Discord ID and the reason for the ban;
  • member roles: the member's Discord ID and their roles.

A copy does not contain channel conversations.

Only the Discord owner of the server being restored can restore it from a copy, and only from a copy taken while they owned the copied server. If Discord shows that the copied server has a different owner, it cannot be restored. After a restore, the bot gives members their roles from the copy when they join the server. Roles with moderation or management permissions and roles with access to the OFFLAW dashboard are given only after the server owner confirms them; the decisions are recorded in the change log.

The server owner can transfer OFFLAW settings and data to another server they own: module settings, profiles, application forms, reputation, contracts, absences, logs, and history, including ticket conversations. A transfer is a copy: nothing changes on the previous server. If the previous server is unavailable (deleted or without the bot), only the person who was its owner according to OFFLAW's latest records can transfer its data. The transferred data is visible to the new server's team under that server's access rules.

3. How we use data

OFFLAW uses data for the following purposes:

  • providing the Discord bot's features and running the dashboard;
  • authorization through Discord OAuth and checking the user's permissions on a server;
  • showing available servers and saving server settings;
  • processing applications, contracts, leave, reports, and profiles;
  • keeping action logs;
  • activating and checking the subscription;
  • handling support requests;
  • preventing spam, fraud, DDoS, and abuse;
  • detecting suspicious sign-ins;
  • improving the stability and security of the Service;
  • meeting legal obligations;
  • protecting the rights of OFFLAW, users, and third parties.

4. Discord OAuth

Sign-in to OFFLAW is done through Discord OAuth. During authorization, Discord may show which permissions OFFLAW requests. The user can decline authorization if they do not agree with the requested permissions.

OFFLAW uses Discord OAuth to: identify the user; obtain the Discord user ID; check the user's servers; check the user's permissions on a server; protect the dashboard from unauthorized access.

OFFLAW does not receive the Discord password and cannot sign in to the user's Discord account on their behalf.

5. Cookies and sessions

The OFFLAW website may use cookies, session tokens, and similar technologies to: keep you signed in; protect the session; run the dashboard; prevent CSRF attacks; protect against abuse; analyze stability and errors.

OFFLAW may use secure cookies (the Secure, HttpOnly, and SameSite attributes) to protect sessions. The user can restrict cookies in the browser settings, but some features of the website may then stop working correctly.

6. Action and security logs

OFFLAW may record actions in the dashboard and within the bot, including: who changed a setting; which server was changed; what the value was before and after the change; the time of the action; the IP address; the Discord user ID; the server ID; the type of action.

This is needed for security, auditing, restoring settings, investigating abuse, and protecting server owners.

A sign-in from a new device or a new network, or suspicious activity, may be recorded in security logs. Important actions may require signing in through Discord again.

7. How we share data

OFFLAW does not sell users' personal data. OFFLAW may share data only in limited cases:

  • Discord — for the bot and Discord OAuth to work;
  • hosting providers — to host the website, the API, the database, and the bot;
  • Stripe and the available payment providers — to process and verify payment;
  • protection and infrastructure providers — for example CDN, DDoS protection, rate limiting, monitoring;
  • contractors or developers — if they help maintain OFFLAW and are bound by confidentiality;
  • law enforcement, courts, or government authorities — if the law requires it.

OFFLAW may disclose data if it considers this necessary to comply with the law, protect the rights of OFFLAW, prevent fraud, investigate violations, keep users safe, or respond to a court request.

8. Data retention

OFFLAW keeps data only as long as needed for the purposes described in this Policy. Recommended retention periods:

  • server settings — while the bot is used on the server or until the data is deleted;
  • profiles and statistics — while the feature is active or until the server asks for deletion;
  • action logs — up to 12 months;
  • security logs — up to 24 months;
  • payment data — up to 7 years, if needed for accounting, taxes, disputes, or protecting the rights of OFFLAW;
  • support tickets — up to 12 months;
  • server copies (Section 2.7) — 14 days from when the copy is taken, and a copy being used for a restore — until the restore ends;
  • files from server copies — together with the last copy that contains them;
  • the list of member roles to give back and the queue for confirming them — 30 days from the restore, and a member joining does not extend this period;
  • if a server leaves the Pro or Max plan or the bot is removed, no new copies are made, and existing copies are deleted when their period ends;
  • transferred data — as data of the new server, and logs — according to the new server's plan, counted from the date of the original event;
  • after a plan is moved to another server, the previous server's logs — 30 more days at the previous plan's depth, so that they can be transferred;
  • OFFLAW database backups for recovery from failures (these are not the server copies from Section 2.7) — up to 90 days.

OFFLAW may keep some data longer if needed for legal obligations, resolving disputes, preventing fraud, security, complying with Discord's rules, or protecting the rights of OFFLAW.

9. Data deletion

The user can ask for deletion of data related to their Discord account or server by contacting support:

OFFLAW may ask the user to confirm their identity or their rights on the server before deleting data. Once the request is confirmed, OFFLAW will delete or anonymize the data unless keeping it is required for legal obligations, security, fraud prevention, resolving disputes, accounting, protecting the rights of OFFLAW, or complying with the law.

Data disappears from database backups when those backups' period ends (Section 8); if the database ever has to be restored from such a backup, deletions made after it was taken are carried out again.

Deleting a server's data also deletes its copies and the list of roles to give back. Data already transferred to another server becomes that server's data and is deleted under its rules. If a member's data is deleted on request, OFFLAW also deletes it from server copies and the list of roles: a restore from an earlier copy or a transfer will not bring it back.

10. Data security

OFFLAW takes reasonable technical and organizational measures to protect data, including: Discord OAuth; restricted access to the database; secure cookies (Secure, HttpOnly, SameSite); API rate limiting; protection against frequent requests; security logs; restricted access for staff and developers; backups; error monitoring; DDoS protection and CDN.

Server copies are stored in the OFFLAW database at a hosting provider (Section 7); the database is encrypted at rest. Database backups are also stored encrypted. The right to restore a server from a copy is checked at the start and at every step of the restore.

However, no digital service can guarantee absolute security. The user uses the Service understanding that transmitting and storing data on the internet always carries some risk.

11. Children's data

OFFLAW is not intended for children under 13. OFFLAW does not knowingly collect personal data of children under 13. If a user believes that a child under 13 has provided data to OFFLAW, they should contact support, and OFFLAW will take reasonable steps to delete that data.

If the user's Discord server is aimed at minors, the user is responsible for complying with applicable laws, Discord's rules, and the requirements for informing members.

12. Users' rights

Depending on the jurisdiction, the user may have the right to: request access to their data; request correction of the data; request deletion of the data; request restriction of processing; object to processing; receive a copy of the data; withdraw consent where processing is based on consent.

To make a request, the user can contact OFFLAW: yt1dante@gmail.com · discord.gg/Wb27bwmDt5. OFFLAW may ask for additional information to confirm the user's identity and right to access the data.

13. Notice to California residents

If the user is a California resident, they may have rights under the California Consumer Privacy Act / California Privacy Rights Act, if these laws apply to OFFLAW. OFFLAW does not sell users' personal data.

Categories of data OFFLAW may collect: identifiers (Discord ID, username, IP address, session identifiers); internet activity (sign-in logs, actions in the dashboard, API logs); commercial information (plan, subscription status, payment transaction identifiers); user content (applications, reports, comments, tickets); technical information (browser, device, and their technical parameters).

Categories of sources: the user directly; Discord OAuth; the Discord API; the user's Discord server; the user's browser or device; Stripe and the available payment provider.

Purposes of processing: providing the Service; security; support; payment; logging; fraud prevention; compliance with the law.

To exercise their rights, the user can contact OFFLAW using the contacts above. OFFLAW will not discriminate against the user for exercising their privacy rights.

14. International users

OFFLAW may use servers, hosting, databases, and services located in the United States or other countries. By using the Service, the user understands that their data may be processed and stored outside their country of residence, where data protection laws may differ.

15. Links to third-party websites

The Service may contain links to Discord, Stripe, other payment services, image and video hosting, documentation, or other third-party websites. OFFLAW does not control how third-party websites process personal data, their security, or their content. The use of third-party services is governed by their own terms and policies.

16. Changes to this Privacy Policy

OFFLAW may update this Privacy Policy from time to time. The current version is published on the OFFLAW website with the date of the last update. Continuing to use the Service after the updated Policy is published means the user agrees to the changes.

If the changes are material, OFFLAW may notify users through the website, the dashboard, the Discord support server, or another available channel.

17. Contacts

For questions about privacy, data deletion, security, payment, or data processing, the user can contact OFFLAW:

See also the Terms of Service.