Privacy Policy

1. What services we use and provide (free of charge, we do not make money)

Third-party services we use:

• Cloudflare Browser Insights
• Cloudflare CDN
• Cloudflare Stream
• Cloudflare Rocket Loader
• Cloudflare Bot Management
• Cloudflare Turnstile
• Cloudflare Workers and Cloudflare Pages
• GitHub Pages (GitHub, Inc. / Microsoft) – hosting of jiron.dev and of this privacy policy
• Google Hosted Libraries (ajax.googleapis.com) – JavaScript library delivery
• MongoDB Atlas (MongoDB, Inc.) – database hosting for InterLink
• Discord (Discord Inc.) – the platform our bot and applications run on

Services we provide ourselves:

• Jiron.dev (https://www.jiron.dev)
• DiscordDevTools website (https://www.discorddevtools.xyz)
• DiscordDevTools API, including the Welcome Image Generator (https://api.discorddevtools.xyz)
• InterLink – Discord bot, web call panel and Discord Activity (https://www.interlink.gg, https://calls.interlink.gg)

2. Contact Information

If you have any questions or concerns about our protection of your data, you can always reach us by email at contact@jiron.dev. Responsible for data processing done through this website is:

Manassés Zähnler
Switzerland

Data protection officer:

Manassés Zähnler
Switzerland

3. General principles

3.1 What data we collect from you and from whom we receive this data

First and foremost, we process personal data that you provide to us or that we collect when operating our website. We may also receive personal data about you from third parties. These may be the following categories:

• Contact information, if you choose to send it to us (e.g. the email address you write to us from, and the content of your message);
• Online identifiers (e.g. cookie identifiers, IP addresses, session identifiers, request identifiers);
• Technical and traffic data (browser and operating system details, referring page, requested URL, date and time of the request, response status, approximate location derived from the IP address);
• Discord account data (your Discord user ID, username, display name and profile picture, and the IDs and names of Discord servers and channels you use our services in);
• Content you submit to us yourself (e.g. text, colours, image links and other parameters you pass to the Welcome Image Generator);
• Sound recordings and live audio (your speech in a Discord voice channel, but only if you have switched the "Allow Voice Transfer" setting of InterLink on – see section 4.10);
• Your settings and preferences for our services (for example which InterLink features you have enabled, and whether you have accepted the terms).

We do not ask for and do not knowingly process: payment or account details (our services are free of charge and we do not take payments), health data, biometric identifiers, government identification numbers, or the contents of your private Discord messages.

3.2 Under what conditions do we process your data?

We process your data in good faith and for the purposes set out in this privacy policy. In doing so, we ensure transparent and proportionate processing.

If, in exceptional cases, we are unable to comply with these principles, the data processing may still be lawful because there is a justification. A justification reason may be in particular:

• Your consent;
• the execution of a contract or pre-contractual measures;
• our legitimate interests, unless your interests are overridden.

Where the EU/EEA General Data Protection Regulation (GDPR) or the UK GDPR applies to you, the legal bases we rely on are the following:

• Consent (Art. 6(1)(a) GDPR): transferring and, where applicable, recording your voice through InterLink; displaying your Discord username, display name or profile picture on our call panel. Each of these is off by default and is only switched on by you through the bot's /settings command, and you can switch it off again at any time.
• Performance of a contract or pre-contractual measures (Art. 6(1)(b) GDPR): providing the services you ask us for – connecting and maintaining a call, storing your service settings, generating an image you requested, and keeping you logged in to the web call panel.
• Legitimate interests (Art. 6(1)(f) GDPR): keeping our servers and services available and secure, preventing abuse and attacks, rate limiting, writing server and request log files, and diagnosing faults. Our interest is in operating a functioning and secure service; we balance it against your interest in not being monitored more than necessary by keeping the data minimal and the retention short.
• Legal obligations (Art. 6(1)(c) GDPR): where we are required by law to retain or disclose data.

3.3 How can you withdraw your consent?

If you have given us consent to process your personal data for specific purposes, we will process your data within the scope of this consent unless we have another justification.

You can revoke your consent at any time by sending an e-mail to contact@jiron.dev (see section 2). Where the consent concerns an InterLink setting, you can also simply switch that setting off again with the bot's /settings command, which takes effect immediately. Data processing that has already taken place is not affected by this.

3.4 In which cases can we share your data with third parties?

a. Principle

We may need to rely on the services of third parties or affiliates and engage them to process your data (known as processors). Categories of recipients are namely:

• IT service provider (web hosting, support, cloud services, content delivery, database hosting, etc.);
• Consulting firms (legal, tax, etc.), if we ever need advice on a specific matter.

Concretely, the following recipients currently receive personal data when you use our services. Each of them acts as our processor or, where they determine their own purposes, as an independent controller:

• Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA – content delivery, security, bot protection, performance measurement and hosting (see sections 4.2 to 4.8);
• GitHub, Inc. (Microsoft Corporation), 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA – hosting of https://www.jiron.dev and of this privacy policy on GitHub Pages (see section 4.13);
• Google LLC / Google Ireland Ltd. – delivery of a JavaScript library from ajax.googleapis.com on the DiscordDevTools website (see section 4.12);
• MongoDB, Inc., 1633 Broadway, New York, NY 10019, USA – database hosting for InterLink settings on MongoDB Atlas (see section 4.11);
• Discord Inc., 444 De Haro Street #200, San Francisco, CA 94107, USA – the platform our bot, web panel login and Activity run on (see section 4.14);
• Our hosting provider for the servers on which the DiscordDevTools API and the InterLink bot run.

We do not sell your personal data, we do not share it for advertising purposes, and we do not use it for advertising profiling. We ensure that these third parties and our affiliates comply with the requirements of data protection and treat your personal data confidentially.

We may also be required to disclose your personal information to government authorities.

b. Visiting our social media channels and other external links

We may have embedded links to our social media channels on our website. This is apparent to you in each case (typically via corresponding icons). If you click on the icons, you will be redirected to our social media channels.

In this case, the social media providers learn that you are accessing their platform from our website. The social media providers can use the data collected in this way for their own purposes. We would like to point out that we have no knowledge of the content of the transmitted data or its use by the operators.

The external links currently present on our websites lead to: Discord (our support server), GitHub, LinkedIn, Buy Me a Coffee (voluntary donations, operated by Buy Me a Coffee), and Flaticon (attribution for icons we use). These are plain links – nothing is loaded from those providers until you click, and we receive no data back from them. If you donate through Buy Me a Coffee, the payment is handled entirely by that provider under its own privacy policy; we never see your payment details.

c. Transfer abroad

Under certain circumstances, your personal data may be transferred to companies abroad in the course of order processing. These companies are obligated to data protection to the same extent as we are. The transfer may take place worldwide.

If the level of data protection does not correspond to that in Switzerland, we carry out a prior risk assessment and ensure contractually that the same level of protection is guaranteed as in Switzerland (for example, by means of the new standard contractual clauses of the EU Commission or other legally prescribed measures). If our risk assessment is negative, we take additional technical measures to protect your data. You can access the EU Commission's standard contractual clauses at the following link. https://commission.europa.eu/publications/standard-contractual-clauses-controllers-and-processors-eueea_de

In practice, personal data is currently transferred to the United States of America (Cloudflare, GitHub, MongoDB, Discord and, where the library is loaded, Google) and may be processed in any country in which those providers operate infrastructure. For the United States we rely on the EU-U.S. Data Privacy Framework where the provider is certified under it, and otherwise on the EU Commission's standard contractual clauses together with the technical measures described in section 3.6. Cloudflare and MongoDB Atlas allow data to be kept in specific regions; where we have that choice we prefer European or Swiss locations.

3.5 How long do we keep your data?

We store personal data only for as long as is necessary to fulfill the individual purposes for which the data was collected. The periods below apply to the individual processing operations described in section 4:

• Server and request log files (including your IP address, the requested URL and your browser details): up to 12 months from the day the entry is written, after which the daily log file is deleted.
• Cloudflare edge logs and analytics: retained by Cloudflare according to its own retention periods, which are shorter than or equal to our own; we do not keep a separate copy.
• Welcome Image Generator cache (the parameters you passed in the URL and the rendered image): kept for as long as the entry stays in the cache. The cache holds the most recent 2000 entries; when it is full, the oldest entry and its image are deleted. You can prevent caching entirely for a request by passing cacheImage=false.
• InterLink settings (your Discord user ID, whether you accepted the terms, and which features you enabled): kept until you ask us to delete them, because they are what makes the service remember your choices.
• InterLink server settings (Discord server ID and that server's configuration): kept until the server asks us to delete them or the bot is removed.
• Live call audio: not stored. It is decoded, mixed and passed on in memory while the call runs and is gone when the call ends. The single exception is described in section 4.10.
• Discord OAuth login cookies for the web call panel: for the lifetime of the cookie, or until you log out or clear your browser's cookies.
• Emails you send us: for as long as needed to deal with your request, and afterwards where we are required to retain them.

Where legal regulations require us to store data for longer – in particular business communications and accounting records, which must be retained for up to 10 years – those periods take precedence. As far as we no longer need such data from you to perform the services, the data will be blocked and we will only use it for accounting and tax purposes.

3.6 How do we protect your data?

We will keep your information secure and take all reasonable steps to protect your information from loss, access, misuse or alteration.

Our contractual partners and employees who have access to your data are obliged to comply with data protection regulations. In some cases, it will be necessary for us to pass on your requests to companies affiliated with us. In these cases, too, your data will be treated confidentially.

Within our website, we use the SSL (Secure Socket Layer) procedure in conjunction with the highest encryption level supported by your browser.

3.7 What rights do you have?

a. Right to information

You can request information about the data we have stored about you at any time. We ask you to send your request for information together with proof of identity to contact@jiron.dev.

You also have the right to receive your data in a common file format if we process your data automatically and if:

• you have given your consent for the processing of this data; or
• you have disclosed data in connection with the conclusion or performance of a contract.

We may restrict or refuse to provide information or data if this conflicts with our legal obligations, our own legitimate interests, public interests or the interests of a third party.

The processing of your request is subject to the statutory processing period of 30 days. However, we may extend this period due to a high volume of requests, for legal or technical reasons, or because we need more detailed information from you. You will be informed of the extension of the deadline in good time, at least in text form.

b. Deletion and correction

You have the option of requesting the deletion or correction of your data at any time. We may reject the request if statutory provisions oblige us to store the data for a longer period or to retain it unchanged or if your request conflicts with a legal requirement.

Please note that exercising your rights may be in conflict with contractual agreements and may have corresponding effects on the performance of the contract (e.g. premature termination of the contract or cost consequences).

c. Legal process

If you are affected by the processing of personal data, you have the right to enforce your rights in court or to file a complaint with the competent supervisory authority. The competent supervisory authority in Switzerland is the Federal Data Protection and Information Commissioner: https://www.edoeb.admin.ch

If you are in the EU or the EEA, you may instead lodge a complaint with the supervisory authority of the member state in which you live, work, or in which you believe the infringement took place. A list of the national authorities is available at https://www.edpb.europa.eu/about-edpb/about-edpb/members_en. If you are in the United Kingdom, the competent authority is the Information Commissioner's Office (https://ico.org.uk).

3.8 Changes to the privacy policy

We may change this privacy policy at any time. The changes will be published on https://jiron.github.io/privacy/privacy.html, you will not be informed separately.

3.9 Cookies and similar technologies

A cookie is a small text file that a website asks your browser to store. We use only cookies that are necessary for our services to work. We do not use advertising cookies, we do not use cross-site tracking cookies, and we do not embed third-party advertising or analytics trackers beyond what is described in this policy.

The following cookies may be set:

• Cloudflare security cookies (for example __cf_bm and cf_clearance), set by Cloudflare on our domains to tell human visitors from bots and to keep a successful security check valid. These are necessary for the security of the service. Cloudflare defines their lifetime, which is typically between 30 minutes and one year.
• access_token and refresh_token, set by the InterLink web call panel (https://calls.interlink.gg) after you log in with Discord. They contain the tokens Discord issues for your session so we can show you the call panel for a server you are actually in. They are set as HttpOnly, which means page scripts cannot read them, and they are never shared with third parties.
• guildid_view_attempt, set by the InterLink web call panel to remember which server's call panel you were trying to open, so that you land on the right page after logging in with Discord.

Because these cookies are strictly necessary to deliver a service you have asked for, we do not ask for consent for them; we are required to inform you about them, which is what this section does. You can delete cookies at any time in your browser settings and refuse them entirely, but the web call panel cannot log you in without them.

The InterLink call panel and the Discord Activity also keep a real-time connection (WebSocket via Socket.IO) open to our server while you have them open, so that speaking indicators and participants update live. This connection carries the data described in section 4.10 and is closed when you close the page.

3.10 Children and minimum age

Our services are not directed at children. Because our services are built around Discord, you must meet Discord's own minimum age requirement to use them – at least 13 years, or the higher minimum age that applies in your country. We do not knowingly collect personal data from children below that age. If you believe that a child has provided us with personal data, please contact us at contact@jiron.dev and we will delete it without undue delay.

3.11 Automated decision-making

We do not carry out automated decision-making that produces legal effects concerning you or similarly significantly affects you, and we do not carry out profiling for advertising purposes. Our security systems do take automated measures – Cloudflare Bot Management and our own rate limiting may slow down, challenge or temporarily block a request that looks automated or abusive. These measures affect a request, not a person, and if you are blocked in error you can contact us at contact@jiron.dev.

4. Individual data processing operations

4.1 Providing the website and creating log files

What information do we receive and how do we use it?

By visiting https://www.jiron.dev, https://www.discorddevtools.xyz, https://api.discorddevtools.xyz, https://www.interlink.gg, https://calls.interlink.gg, https://jiron.github.io/privacy/ (and any subpage or other missing subdomains of any of those domains), or by using the InterLink Discord Activity, certain data is automatically stored on our servers or on servers of services and products that we obtain and / or have installed, for purposes of system administration, for statistical or backup purposes or for tracking purposes. These are:

• the name of your Internet service provider;
• Your IP address (in some circumstances);
• the version of your browser software;
• the operating system of the computer with which the URL is accessed;
• the date and time of access;
• the web page from which you are visiting URL;
• the search words you used to find the URL.

How these log files are written and what exactly they contain

Our own servers for the DiscordDevTools API (https://api.discorddevtools.xyz) and the Welcome Image Generator write one entry per request into a plain text file. A new file is started every day and the files are grouped into one folder per month. Each entry contains:

• the date and time of the request, to the millisecond;
• your IP address, and separately the address of the proxy the request arrived through (this is normally Cloudflare), so that a forged address can be recognised;
• the HTTP method, the full requested URL including all query parameters you passed, the response status code, the response size and how long the request took;
• the host name you addressed, your browser's user-agent string, and the referring page;
• a randomly generated request identifier, used only to match up lines belonging to the same request;
• on the Welcome Image Generator, additionally the request headers and up to the first 2048 bytes of the request body.

Fields that typically carry credentials are never written to these files. Authorization headers, cookies, API keys and any body field named like a password, secret, token or session are replaced with [redacted] before the entry is written. The log folder and files are readable only by the account that runs the server.

Requests that are malformed enough that they never reach the application are logged too, with the address they came from, because that is the shape most scanner traffic takes.

Why may we process this data?

The log files are stored in order to guarantee the functionality of our services, to investigate faults, to recognise and defend against attacks and abuse, and to ensure the security of our information technology systems. This is our legitimate interest (Art. 6(1)(f) GDPR).

Please note that, unlike what a shorter statement might suggest, an IP address in combination with a timestamp can under some circumstances be traced back to you, and we therefore treat these log files as personal data throughout.

How long are they kept and how can you prevent data collection?

Log entries are kept for up to 12 months from the day they are written and the daily file is then deleted. Writing them is mandatory for the secure operation of our services, so you have no possibility to object to the logging as such. You can of course limit what ends up in the URL line: everything you pass as a query parameter to our API is written to the log, so do not pass anything there that you would not want stored (see also section 4.9).

4.2 Cloudflare Browser Insights

Our website uses the "Cloudflare Browser Insights" service provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). This service collects and analyzes data about the performance and use of our website from the perspective of the end user.

When you visit our website, various data, including your IP address, information about the browser you are using, website loading times, site interactions, and other technical information, is transmitted to Cloudflare. This data is used by Cloudflare to provide us with detailed reports about the performance of our website and user behavior.

4.3 Cloudflare CDN

Our website uses the Content Delivery Network (CDN) service provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). A CDN helps deliver content from our website faster by distributing copies of the content to a network of fast loading servers.

When you visit our website, your IP address is transmitted to Cloudflare and cookies may be set in your browser, which are necessary for the optimization and security of the service. Cloudflare uses this data to speed up traffic between our web server and your end device and to protect our website from attacks.

4.4 Cloudflare Stream

Our website uses the "Cloudflare Stream" service provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). Cloudflare Stream is a video streaming platform that allows us to efficiently host, stream and monetize videos.

When you watch videos on our website that are provided via Cloudflare Stream, various data, including your IP address, information about the browser you are using, date and time of access, and interaction data with the video, are transmitted to and stored by Cloudflare. This data is used to enable video streaming, monitor performance and improve the user experience.

4.5 Cloudflare Rocket Loader

Our website uses the "Cloudflare Rocket Loader" service provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). Rocket Loader optimizes the loading times of web pages by accelerating the delivery of JavaScript resources.

When you visit our website, technical information, including your IP address and information about the browser you are using, is transmitted to Cloudflare. This data is used by Cloudflare to provide the Rocket Loader service and to improve the performance of our website.

4.6 Cloudflare Bot Management

Our website uses the "Cloudflare Bot Management" service provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). This service helps us detect and control automated, non-human (bot-based) traffic to ensure the security of our website and improve the quality of the user experience.

When you visit our website, various data, including your IP address, information about the browser you are using, behavior on the website, and other technical characteristics, are transmitted to Cloudflare. Cloudflare analyzes this data to determine whether it is human or bot-based traffic and takes appropriate measures to block or control harmful bots.

4.7 Cloudflare Turnstile

Our website uses "Cloudflare Turnstile", a service provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). Cloudflare Turnstile is a security service that helps us distinguish human traffic from automated traffic and thus protect our website from misuse.

Turnstile does not ask you for any information about yourself and does not require you to solve a puzzle; it decides in the background whether the request looks human. It does not use your data for advertising purposes.

When you fill out forms on our website or perform certain actions that require verification, Cloudflare Turnstile may be used to ensure that you are a human and not a bot. In doing so, various data, including your IP address and information about your interaction with the Cloudflare Turnstile widget, is transmitted to and processed by Cloudflare.

4.8 Cloudflare Workers and Cloudflare Pages

We use "Cloudflare Workers" and "Cloudflare Pages", services provided by Cloudflare, Inc, 101 Townsend St, San Francisco, CA 94107, USA ("Cloudflare"). They allow pages to be delivered, and code to run, on Cloudflare's network close to you instead of on a single central server.

When you call up a page delivered this way, your request – including your IP address, the requested address, your browser details and the time of the request – is processed on Cloudflare's infrastructure so that the response can be produced and returned to you. Cloudflare processes this data on our behalf in order to deliver the page, and keeps its own operational and security logs about it.

4.9 DiscordDevTools API and Welcome Image Generator

Our website (https://www.discorddevtools.xyz/) offers a free API intended for developers, reachable at https://api.discorddevtools.xyz. When you use this API we process technical data (your IP address, browser details, request timestamps – see section 4.1) and, in addition, everything you yourself put into the request.

The Welcome Image Generator (https://api.discorddevtools.xyz/welcome-image-generator/generate.png) is driven entirely by URL parameters. Those parameters typically contain a username and a title and greeting text, and may contain a link to a profile picture and to a background image. This is personal data of the person the image is about – and that person is usually not you, but a member of the Discord server you are generating the image for.

What happens with it:

• The parameters are used to render the image you asked for.
• If you pass an image link, our server fetches that image from the address you gave so it can be drawn into the result. The address must be a public one; we refuse links that point into private or internal networks.
• Unless you pass cacheImage=false, the full parameter string and the rendered image are stored in our cache so the same request does not have to be rendered again. The cache keeps the most recent 2000 entries; when it is full, the oldest entry and its image file are deleted.
• The full request URL, including those parameters, is also written to the request log described in section 4.1 and kept for up to 12 months.

If you build on our API, you are responsible for the data you send us. If you pass other people's personal data to our API, you need your own legal basis for doing so, and you should pass only what the image actually needs. Do not send us anything sensitive, and do not put credentials or tokens into the URL.

We apply rate limits per IP address to keep the service available; this means we count recent requests per address for a short rolling period.

If you wish to request deletion of data submitted to the API, please contact us at contact@jiron.dev with as much information as possible – ideally including the full GET request URL used during submission, so that we can find the cache entry and the log lines. We do not share API data with third parties, and the data is only processed on infrastructure under our control.

4.10 InterLink (Discord bot, web call panel and Discord Activity)

InterLink is a free Discord bot that connects the voice channels of two different Discord servers so that their members can talk to each other, together with a web call panel (https://calls.interlink.gg) and a Discord Activity that show who is in the call. The following describes what InterLink processes. The bot's own terms, which you accept before you can set it up, are available at https://calls.interlink.gg/terms and at the same address on our other InterLink domains; where they and this policy differ, section 6 applies.

a. What we store in our database

We store the following in our database (see section 4.11 for where that database lives):

• Per user: your Discord user ID, whether you have accepted the terms of service and privacy policy, and the on/off state of each of your settings (voice transfer, show profile picture, show display name, show username). A record is created the first time the bot has to look you up.
• Per Discord server: the server's ID, which other servers it has blocked, the channel chosen for messages, and whether calls, the randomizer and the phone book listing are enabled.

We do not store your username, display name or profile picture in our database. Those are fetched from Discord while a call is running and are kept only in the memory of the running server for as long as the call lasts.

b. Voice and the "Allow Voice Transfer" setting

This setting is off by default. It only becomes active when you switch it on yourself using the bot's /settings command, and switching it off again withdraws your consent for the future.

While it is on, and while you are in a voice channel that is part of a call, our bot receives the audio you send to that voice channel, decodes it, mixes it with the audio of the other participants and plays it into the connected voice channel on the other Discord server. That is what makes the call work. The audio is handled in memory for the duration of the call and is not written to disk; when the call ends, it is gone.

We also receive and pass on your speaking state (whether you are currently talking, shown as a green ring on the call panel) and your mute and deafen state.

Recording: we reserve the right to record the mixed audio output of participants who have this setting enabled, solely so that a moderator can check a report of abuse. Any such recording is deleted at the latest 24 hours after the end of the call and is not backed up, and it is only ever looked at in response to a report, or where we are legally required to or are directed to by Discord. If you do not want to be recorded under any circumstances, do not enable this setting – the rest of the bot works without it.

Please also be aware that anyone else in the call can hear you, and that we cannot prevent a participant from recording a call on their own device.

c. The display settings

"Allow To Display Profile Picture", "Allow To Display Display Name" and "Allow To Display Username" are likewise off by default. Only if you switch one on do we retrieve that item from Discord and show it to the other participants on the call panel and in the Activity; otherwise a placeholder is shown instead. These items are shown live and are not stored by us. Please note that these settings govern your name and picture on the call panel only – see d. below for what is shown about you regardless of them.

d. What the other server and its members can see

The point of InterLink is to connect two different Discord servers, so some data necessarily crosses from one to the other. Please read this carefully, because the settings in b. and c. do not cover all of it:

• When you place a call with /call, your Discord display name is posted into a text channel of the server you are calling, together with the name and ID of the server you are calling from, so that the people there can decide whether to accept. This happens regardless of the "Allow To Display Display Name" setting, which governs the call panel and not the call notification. If you do not want your display name shown to a server you are calling, ask someone else on your server to place the call.
• Your Discord user ID is visible to everyone who opens the call panel or the Activity for a call you are in, including members of the other server, because it is used to identify your tile on the page. The display settings in c. control your name and picture; they do not hide your user ID, and a Discord user ID can be used to look an account up.
• The names and IDs of both servers and your speaking, mute and deafen state are shown to everyone in the call.
• Your audio, if you have enabled voice transfer, is heard by everyone in the connected voice channel on the other server.

Separately, the /phonebook command shows a list of the servers that can be called, with each server's name and ID, to anyone who runs it in any server the bot is in. A server is listed by default. Anyone who administers a server can take it off that list through the bot's settings, and can also block individual servers or switch off calls entirely.

e. Logging in to the web call panel and the Activity

To open the call panel for a server, you log in with Discord (OAuth2). Discord asks you to authorise this and then sends us an access token and a refresh token, which we place in your browser as HttpOnly cookies (see section 3.9) and use to ask Discord who you are, so that we can check that you are actually in the call you are trying to view. We request only the "identify" and "guilds" permissions, and we do not receive your Discord password. During this, we process your Discord user ID, and the ID and name of the server and the voice channel concerned.

The Discord Activity works the same way, except that Discord itself performs the authorisation inside your Discord client and the resulting token is passed on to the page in the address of the embedded view. We do not store these tokens on our servers; they live in your browser session and expire.

f. Your rights, specifically for InterLink

To obtain a copy of, correct or delete what we store about you in InterLink, write to contact@jiron.dev and include your Discord user ID (in Discord: Settings → Advanced → Developer Mode, then right-click your name → Copy User ID), so that we can identify the right record. Deleting your record resets your settings; the bot will create a fresh, empty record with everything switched off the next time it encounters you. For settings of a Discord server, the request should come from someone who administers that server.

4.11 MongoDB Atlas

The InterLink settings described in section 4.10 a. are stored in a database hosted on "MongoDB Atlas", a service of MongoDB, Inc, 1633 Broadway, 38th Floor, New York, NY 10019, USA ("MongoDB"). MongoDB operates the database infrastructure on our behalf as our processor and does not use the content for its own purposes. The connection between our servers and the database is encrypted, and access is restricted to our own credentials. Depending on the cluster region, the data may be processed outside Switzerland and the EEA; section 3.4 c applies to such transfers.

4.12 Google Hosted Libraries

Pages of the DiscordDevTools website (https://www.discorddevtools.xyz) load the jQuery JavaScript library from Google Hosted Libraries at ajax.googleapis.com, a service of Google LLC, 1600 Amphitheatre Parkway, Mountain View, CA 94043, USA, represented in the EEA by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland ("Google").

This means your browser establishes a connection to a Google server when you open such a page, and in doing so transmits your IP address, your user-agent string and the address of the page you are on to Google. This happens automatically as the page loads. We have no influence over what Google does with this data, and Google may process it in the United States. We use this service only to deliver a standard JavaScript library quickly; we do not receive any data back from Google and we do not use it for analytics or advertising. The legal basis is our legitimate interest in reliable delivery of our website (Art. 6(1)(f) GDPR). Further information: https://policies.google.com/privacy

If you do not want this connection to be made, you can prevent it with a browser extension that blocks third-party scripts, at the price of some interactive elements of the page no longer working.

4.13 GitHub Pages

Our website https://www.jiron.dev and this privacy policy (https://jiron.github.io/privacy/privacy.html) are hosted on "GitHub Pages", a service of GitHub, Inc, 88 Colin P. Kelly Jr. Street, San Francisco, CA 94107, USA, a subsidiary of Microsoft Corporation ("GitHub"). When you open one of these pages, your browser transmits your IP address, your browser details, the requested address and the time of the request to GitHub, which processes and logs this data in order to deliver the page and to secure its service. Further information: https://docs.github.com/site-policy/privacy-policies/github-general-privacy-statement

These pages are static: they contain no forms, no tracking scripts and no analytics, and they set no cookies of their own.

4.14 Discord

Our bot and our applications run on the Discord platform, operated by Discord Inc, 444 De Haro Street, Suite 200, San Francisco, CA 94107, USA, represented in the EEA by Discord Netherlands BV ("Discord"). We are not affiliated with Discord (see also section 5).

Discord is the source of most of the data we process about you: your Discord user ID, username, display name and profile picture, the servers and voice channels you are in, your speaking, mute and deafen state, and the audio you send to a voice channel all reach us through Discord's interfaces. Equally, everything our bot sends – messages, embeds and call audio – passes through Discord's infrastructure.

Your use of Discord itself is governed by Discord's own privacy policy (https://discord.com/privacy) and terms (https://discord.com/terms), over which we have no influence. We process data received from Discord only for the purposes described in this policy, and we adhere to the Discord Developer Terms of Service and Developer Policy.

5. Additional note for Discord

We are in no way affiliated to Discord (https://discord.com). DiscordDevTools is purely a hobby project made to help out other developers that want to create apps/bots or other fun projects on Discord. If there are any concerns regarding the name and/or domain of DiscordDevTools, we are happy to adjust based on Discord's needs. We do not want any legal problems, we just want to get more users to go on Discord and try out developing too. For legal concerns in this matter, please contact us at contact@jiron.dev or text us on Discord (the developer's username is "jirondev").

6. Legal Priority

If any website which a button that leads to this page also contains a privacy policy page, the information on https://jiron.github.io/privacy/privacy.html has priority. If there's missing information on the original page but is not missing on https://jiron.github.io/privacy/privacy.html, you must assume that the information on https://jiron.github.io/privacy/privacy.html is an addition to the original page so both sites are relevant. You always automatically accept this privacy policy when using our websites. Our websites include, but are not limited to, the websites written right under "What information do we receive and how do we use it?" on this page under chapter 4.1.

The pages this currently applies to are:

• https://www.discorddevtools.xyz/privacy-policy and https://www.discorddevtools.xyz/terms-of-use;
• the InterLink terms of service and privacy policy at https://calls.interlink.gg/terms (and at /terms on our other InterLink domains), which you accept in the bot before you can set it up.

Those pages remain in force for everything they say that this policy does not contradict – in particular the InterLink terms describe the individual bot settings, and the DiscordDevTools terms of use govern the use of that website. Where they are shorter, less specific or older than this policy, this policy is the one that counts.