Datenschutzerklärung

Wody is developed and operated by Păcurar Ancuța-Narcisa, an individual based in Romania, European Union (the “Operator”). The Operator acts as the data controller for processing activities for which Wody determines the purposes and means of processing. You can contact the Operator at privacy@wody.online. This Privacy Policy explains what personal data Wody processes through the Discord bot and web dashboard, why it is processed, where it is stored, how long it is kept, and how you can exercise your rights. Where Wody processes information entered into a server by a server owner or authorised administrator, the server owner or administrator may also have responsibilities as a controller for that processing, depending on the feature and the applicable law.

Wody uses Discord OAuth2 for dashboard login. After you authorize the application, Wody receives:

• Your Discord user ID, username, global display name, discriminator and avatar identifier.
• An OAuth access token and refresh token issued by Discord. These are stored only on the server and are used to access the Discord resources required by the dashboard.

The dashboard also requests your Discord server list from Discord when it needs to determine which servers you can manage. The server list is fetched from Discord using your access token and is not stored as part of your Wody session record.

Wody does not receive or store your Discord password. The Discord tokens and profile data are not stored in your browser cookies. Your browser receives only a random session identifier with a cryptographic signature. The corresponding session record is stored server side in the sessions collection in MongoDB. The access token and refresh token are used only from the server when the dashboard needs to access Discord resources permitted by the OAuth2 authorization.

To provide Wody's modules and features, Wody stores information associated with Discord servers, channels, roles and members. The homepage currently presents 20 modules, including moderation, automod, welcome and goodbye messages, auto role, tickets, reaction roles, captcha verification, giveaways, levels, suggestions, auto responses, custom commands, embed building, scheduled messages, forums and logging. including Pools. Depending on the features used, the stored data includes:

• Server configuration and settings created through Discord or the dashboard.
• Welcome and goodbye messages, custom commands and automatic responses.
• Moderation records such as warnings, bans, kicks and timeouts, including the Discord IDs needed to identify the affected member and moderator.
• Level and XP information.
• Suggestions and their moderation status.
• Ticket information, ticket reviews and closed ticket transcripts where the ticket feature is used.
• Giveaway entries and results.
• Captcha verification records, such as which member verified and when, where the Captcha feature is used. To verify, a member must log in with Discord on the verification page. This login shares basic Discord account information with Wody, including the Discord user ID, username and the list of servers linked to that account, so Wody can confirm the member actually belongs to the server before granting the configured role. Wody does not receive the member's email address or password through this process.
• Scheduled message content and scheduling settings.
• Forum channel automation settings, such as default tags and post cooldowns, where the forums feature is used.
• Premium server configuration backups where the backup feature is enabled.
• YouTube channel subscriptions and notification channel settings where the YouTube Notifications feature is enabled.
• Your lifetime Wody vote total associated with your Discord user ID, where the voting feature is used.
• Audit records for relevant settings changes and Premium administration, including the Discord user ID of the person who made the change where recorded.
• Premium key and activation records needed to issue, validate, limit or revoke Premium access.
• Pool configuration, answer options, scheduled closing times, votes and results where the Pools feature is used.
• Image scam detection, where a server administrator turns it on: pictures attached to messages in that server are analysed automatically, in memory, by comparing image fingerprints with reference images chosen by the Wody team and, where text recognition is available, by reading the text in the picture to look for scam indicators. The picture itself is not kept by Wody. A log entry posted in the server's own log channel may show the picture, a short excerpt of the text read from it, the links found and the details of the message. The reference images registered by the Wody team, with their fingerprints, are stored.
• Message logs, where the Logging module is turned on: when a message is deleted, its log entry in the server's log channel can include the message's pictures, which Wody downloads from Discord and posts again in that channel. Wody does not keep its own copy.

Wody does not store general Discord chat history as a separate archive. Message content is stored only where a feature requires it, such as configured messages, scheduled messages or ticket transcripts. Wody does not use analytics, advertising or behavioral profiling, and the dashboard does not use third-party tracking cookies.

Wody stores its application and bot data in MongoDB Atlas. This includes the server configuration, feature data and server-side dashboard sessions. The dashboard application is hosted on Vercel. Authentication cookies are stored in your browser. Discord separately processes data on Discord's own systems when you use Discord or complete the OAuth2 login process. Wody does not use analytics, advertising, behavioral profiling or third-party tracking cookies on the dashboard.

The dashboard uses a server side session. The wody_session cookie does not contain your Discord access token, refresh token or profile. It contains a random session identifier and a cryptographic signature used to detect tampering.

The session record containing your cached profile, Discord access token, refresh token and expiry time is stored in the sessions collection in MongoDB. The browser cookie can remain for up to 7 days, but the server-side session is not necessarily valid for the full 7 days. Its expiry is calculated from the Discord access token lifetime and is set 60 seconds before that token expires. When the server-side expiry is reached, the session is rejected; when that expired session is checked, its database record is removed. Logging out removes the session record and the session cookie immediately. The current implementation stores the refresh token but does not use it to refresh an expired access token.

Dashboard authentication cookies are HttpOnly, so normal page JavaScript cannot read them. They are marked Secure and are sent only over HTTPS. They use SameSite=Lax to reduce cross site request risks. The cookie values are cryptographically signed and a modified value is rejected. OAuth login also uses a separate short lived state value to verify that the login response corresponds to a login started by the same browser.

Access to server settings is checked against the permissions returned by Discord. A user must be the server owner or have Administrator or Manage Server permission for the server being managed.

We process this information to authenticate dashboard users, determine which Discord servers they can manage, operate the bot features requested by server owners and members, keep dashboard changes synchronized with the bot, maintain configuration and moderation records, provide Premium functionality, prevent unauthorized access and keep the service secure and operational. Depending on the processing activity, the legal basis may be the performance of a contract or steps requested before entering into a contract (Article 6(1)(b) GDPR), compliance with a legal obligation (Article 6(1)(c) GDPR), or the Operator's legitimate interests in operating, securing and protecting the service (Article 6(1)(f) GDPR). Where consent is required by law for a particular processing activity, Wody will rely on consent instead.

Wody does not sell your personal data, use it for advertising or behavioral profiling, or use analytics on the dashboard. The service relies on the following providers:

• Discord, for authentication and access to Discord resources through its API.
• MongoDB Atlas, for the database used by the dashboard and bot.
• Vercel, for hosting and delivering the dashboard.

These providers may process information under their own terms and privacy documentation. Depending on the service and the processing involved, a provider may act as a processor or as an independent controller. Discord remains an independent controller for the data it processes on its own platform.

Independent third-party Discord bots and applications that share a server with Wody process information under their own privacy policies and arrangements. Wody does not control that processing and is not responsible for the independent processing carried out by unrelated providers. This does not reduce Wody's own responsibility for processing that Wody controls, or any obligation that applicable data protection law places on Wody. See Section 20 of the Terms.

The wody_session browser cookie has a maximum lifetime of 7 days. This is the lifetime of the browser cookie, not a guarantee that the server-side session or Discord tokens remain valid for 7 days. The server-side dashboard session has its own expiry based on the Discord access token lifetime and is normally set to expire 60 seconds before that token. An expired session is rejected and its database record is removed when the session is checked. The wody_oauth_state cookie expires after 10 minutes and is removed immediately after the OAuth2 response is checked. Bot configuration and feature data are kept while they are needed to operate the relevant server features. Server owners can request deletion of applicable records by contacting us. Some records may need to be retained where required by law, necessary to establish or defend legal claims, or reasonably necessary for security, moderation history or Premium validation.

Where applicable under GDPR and other data protection law, you may have the right to request access, correction, deletion, restriction of processing, objection to processing and data portability. Where processing is based on consent, you may withdraw that consent at any time without affecting the lawfulness of processing carried out before withdrawal.

To exercise your rights or ask what information is associated with your Discord account, contact privacy@wody.online. We may ask you to verify your Discord identity before providing account information or processing a request. You may also lodge a complaint with the competent data protection authority, including ANSPDCP in Romania.

If you use Wody as a server owner or authorised staff member, the dashboard and bot may display or store information about other members when required by the features you use, such as moderation records, levels, tickets, suggestions or giveaways. This information may come from Discord, from the member directly, or from the server owner or staff using Wody. Server owners and staff are responsible for using that information lawfully and only for appropriate server management purposes. Depending on the feature, the server owner may be the controller for member data entered or managed through Wody, while Wody may process that data on the owner's behalf.

Discord, MongoDB Atlas and Vercel may process information in countries outside Romania or the European Economic Area. Where a transfer to a third country is subject to GDPR Chapter V, the transfer is made only where an applicable legal mechanism is available, such as an adequacy decision or appropriate safeguards including standard contractual clauses, where applicable. Information about the relevant safeguards can be requested from the Operator at the contact address above.

Personal data may be obtained directly from you, from Discord when you authorise the Wody application, or from server owners and authorised staff when they configure and use Wody. Wody does not use your personal data for automated decision-making or profiling that produces legal effects or similarly significant effects on you.

Wody provides YouTube Notifications to detect and deliver notifications about new content from configured YouTube channels. WebSub is the primary notification method. WebSub callbacks are received over HTTPS and, where provided by the service, the callback signature is verified before processing.

If a notification cannot be obtained or processed through WebSub, Wody may use the official YouTube Data API as a fallback. Wody does not scrape YouTube, use browser automation, or parse YouTube pages to obtain video information.

For this feature, Wody may process and temporarily store channel identifiers, video identifiers, video URLs, titles and other metadata returned by YouTube services, notification timestamps, delivery and processing status, deduplication identifiers, and limited technical information required to validate, queue, retry, or troubleshoot notifications. WebSub notifications may be retained temporarily while awaiting processing or retry.

Wody uses identifiers and processing records to prevent duplicate notifications. Video content itself is not downloaded or re-hosted by Wody.

Wody does not collect YouTube passwords or other YouTube account credentials through YouTube Notifications. This feature does not give Wody permission to like, subscribe, comment, generate views, or modify videos on behalf of users.

Where Wody uses YouTube API Services, use of the feature is also subject to the applicable YouTube Terms of Service and Google Privacy Policy.

The homepage displays a rotating selection of Discord servers that use Wody, under the “Servers already using Wody” heading. A server is included there automatically once the bot is a member of it and its member count exceeds a threshold we configure (currently more than 5 members), with no separate opt-in step required from the server owner. Only information Discord already makes publicly available through its own API is shown: the server's name, its icon, and an approximate member count. No member list, message content, channel names or any other server data is displayed. When more servers qualify than fit on screen, a random subset is shown and rotates periodically rather than displaying every qualifying server at once. If you are a server owner and would prefer your server not appear in this showcase, contact privacy@wody.online and we will exclude it.

When Premium Economy or Wody Games (Slots, Coinflip, Dice and Blackjack) is used in a server, Wody stores, per server, the Discord user ID and server ID together with the data needed for the game: virtual balances (wallet, bank, savings, gems, Blackjack chips), inventory, pets, businesses, farm plots, job, quests, achievements, statistics, daily reward timestamps and streaks, market listings and trades, and Blackjack sessions and hand history.

Economy and Blackjack use virtual currency only. It has no real-world value, cannot be bought, sold or withdrawn through Wody, and is not connected to real money. Balances are separate for every server and are not shared between servers.

Transactions and administrative actions (action, amount, member, administrator) are kept in server logs so that disputes and abuse can be reviewed. Administrators with access to the dashboard or the admin tools can see these logs and can reset economy data. Retention: admin and economy logs 365 days, closed trades 30 days, Blackjack hand history 90 days, settled Blackjack sessions 7 days. Other game data is kept until a server administrator resets it or you ask us to delete it.

Global economy leaderboard. Wody publishes a ranking of the 100 richest members across all servers where Wody Economy is used, on Discord (command /globalleaderboard) and on the website (page /leaderboard). For each ranked member it shows the Discord display name, the avatar, the total net worth (the sum of the member's balances on every server) and the number of servers. The ranking is calculated from economy data the bot already stores, refreshed about every 5 minutes and kept as one snapshot in the database. Bots are not ranked. Any member can leave the ranking at any time with the Hide me button under /globalleaderboard and come back with Show me; the choice is stored as the member's Discord user ID in a list of hidden members and removes the member from the snapshot immediately. Avatars on the website are loaded through Wody's own servers, so visitors' browsers do not contact Discord or other third parties and no cookies are set.

Birthdays is free and independent from Economy. A member sets a birthday with /birthday. Wody then stores the Discord user ID and server ID, the day and month, an optional birth year, a privacy level (public, community or private), an optional time zone and an on or off switch. Birth year is optional and is never required.

Privacy levels: public shows the date to the server; community uses the birthday for features such as announcements and reminders while keeping the exact date hidden from other members; private is never listed, announced or shown to other members. Age is displayed only when the server enables it, a birth year was provided and the birthday is not private.

Server administrators with dashboard access can see and manage all entries of their own server in the administration list, including private ones, but private birthdays are never shown in the calendar, in public boards or in announcements. A short history is kept of each celebration (date, whether it was announced, whether the birthday role was added and removed, and any delivery error). You can remove your birthday at any time with /birthday, and administrators can remove entries. Data is kept until it is removed.

Stream Notifications is a Premium feature. For Twitch, Wody stores the public Twitch login, ID, display name and avatar of each streamer an administrator adds, the Discord channel and message settings, and technical subscription data for Twitch EventSub. Incoming Twitch events are processed to post the alert; event records are kept for 7 days and delivery records for 30 days to prevent duplicate messages.

For TikTok, an administrator can connect their own TikTok account through the official TikTok Login Kit. After consent, Wody stores the TikTok open ID, username, display name and avatar and the access and refresh tokens. The tokens are encrypted on the server (AES-256-GCM), are never shown in the dashboard and are never sent to your browser. Wody uses the scopes you approve to read only the connected creator's own video list (video ID, title, description, creation time, cover image, link and duration) to announce new videos. Wody does not post to TikTok, does not read private messages and does not use TikTok data for advertising or sell it. A server owner who already linked their own TikTok account on the TikTok page can add that same account to a server with one click; Wody then stores an encrypted copy of the same connection for that server, and removing the account from the server deletes that copy only.

You can disconnect a TikTok account at any time in the dashboard. Wody then revokes the token and deletes the stored connection. You can also remove access in your TikTok settings. Wody does not offer alerts for TikTok creators who have not connected their own account. Twitch and TikTok are independent services with their own privacy policies.

Requests made from the dashboard to the bot (for example test messages) are stored temporarily and deleted after 24 hours.

Wody Creator Link (the TikTok page on wody.online): a signed-in Wody user can link their own TikTok account with TikTok Login Kit to see their TikTok profile and latest videos inside Wody. Wody stores the TikTok open ID, username, display name, avatar and the encrypted tokens, only for that user, only read access, and deletes them when the user unlinks the account on the page. Wody does not post to TikTok and does not use this data for advertising.

Wody Human Check (the "I'm not a robot" box used on verification and Collab forms): it uses no cookies, no local storage and no outside service. A short browser challenge and how the box was ticked (such as pointer movement and timing) are sent once to Wody, scored in memory and not stored. Only a one-time token marker is kept for a few minutes to stop reuse.

Community Discovery lets the owner of a Discord server publish a public profile for it at wody.online/{prefix}/{name}. A profile is shown only after a person on the Wody team has reviewed and approved it. The address prefix is chosen by Wody and may change; older addresses keep redirecting.

What we store. The profile content you enter (name, descriptions, category, tags, languages, invite code, social links, chosen colors and images, the Discord roles you choose to show publicly), the Discord server ID and public statistics read through the Discord bot (member count, online count, voice count, boosts, icon, creation date), your Discord user ID as the listing owner, the people you add as managers, the submission history, review decisions and messages, and the date you accepted the Terms and the Privacy Policy when submitting.

Visitors. Favorites, reviews and reports are linked to the Discord account that made them. A review shows the reviewer's Discord name and avatar after moderation, and only members of the server can review it. Wody staff can see who wrote a review or report. Internal moderation notes are never shown to listing owners.

Analytics. Profile views, invite clicks and unique visitors are counted without cookies. A unique visitor is estimated from a one way daily hash of the IP address and browser string with a secret salt that changes every day. The raw IP address and browser string are not stored with the count, and the short lived technical records used for de-duplication are deleted after 2 days. Invite clicks only show that the Join button was pressed, not that someone joined.

Retention. Notifications are deleted after 90 days. When a listing is deleted by its owner or by Wody, the listing, its versions, reviews, favorites, reports, managers, images and notifications are removed and the public address becomes available again. A short audit entry (listing name, address, who deleted it and when) is kept for moderation and legal reasons. Suspended and unpublished listings are kept until deleted.

Legal basis and sharing. Profile content is published at your request (contract) and moderation is carried out under our legitimate interest in keeping the directory safe. We do not sell this data. Public profile content, including the invite you provide, can be seen by anyone and may be indexed by search engines while the listing is published. Unpublished, suspended and unapproved listings are not indexed.

Rules. What may be listed and what is stored about listed servers is also summarised in the Community Guidelines.

Invite Tracking is free and is off until a server administrator turns it on. When it is on, Wody reads the list of invites of the server (this needs the Manage Server permission) and compares the use counters before and after each join to work out which invite a member used.

What we store, per server. For every join: the Discord user ID of the member, the Discord user ID of the inviter, the invite code, the time of the join, whether the match was certain, and whether the member later left. For every invite: its code, the creator's Discord user ID, the use counter and its limits. The server's settings for the module (log and notice channels, messages, who can see statistics, the fake account threshold) are stored too. When Wody cannot be sure, the join is stored as unknown with the reason and nobody is credited.

Why and who can see it. The data is used only to show invite statistics, leaderboards, join logs and the inviter variables of the welcome message in that server. Members can see statistics with the commands, unless the server limits them to staff. Server administrators with dashboard access can see the recent joins and the leaderboard of their own server. Data of one server is never shown in another.

Deletion. Administrators can delete all invite statistics, or those of one member, from the dashboard or with /invite-reset. If Wody is removed from a server, the data of that server is deleted after 30 days. Invite Tracking never deletes the data of other modules.

When Wody is added to a server, it records the server ID, the server name and the time it joined, and when it is removed it records the same with the time it left. These records are kept so the Operator can see which servers use Wody and handle returns and bans, until deletion is requested (see Section 9). At the same time Wody posts a report to a private Discord channel controlled by the Operator. The report contains information Discord makes available to the bot: the server name, ID, icon and banner, the server owner's Discord name and ID, the account that added the bot when the bot is allowed to read the audit log, the member count, creation date, language, boost level, verification level, the number of channels, roles, emojis and stickers, the vanity link, description, the name of the rules channel and the server features, plus whether the server is banned or has Premium. A second private message shows only aggregate totals and counts about the bot and the website. The purpose is to operate, secure and support the service, detect abuse and enforce bans (legitimate interest). The report does not include messages or member lists.

When someone claims a passport with /claimpassport, Wody keeps a small record for the Discord account: the Discord user ID, a passport number generated by Wody (the first 1000 passports also carry a Genesis number from 1 to 1000, given in the order they were claimed), the date it was claimed, and one counter: how many times other members displayed the passport (one count per viewer per hour). Wody does not count the commands you use or the days you are active. Wody does not store the display name or avatar for the passport; they are read from Discord when a card is drawn, and a finished card image is only kept briefly in the memory of the running bot.

To show the number of server bans, Wody stores pairs of Discord user ID and server ID for servers that use Wody where the account is banned. They are learned from ban and unban events and from a check of the servers where Wody may see the ban list, made when a passport is claimed and then at most once a day when its owner displays it. A pair is removed when the ban is lifted or when Wody is removed from the server. Only the number appears on the card, never the names of the servers or the reasons. Earlier versions kept a list of servers the account was a member of; those records have been deleted. A short-lived keyed hash is kept for one hour to avoid counting the same view twice. The purpose is to provide the feature the user requested (legitimate interest and, for the feature itself, the performance of the service). The passport record is kept while the feature is available; you can ask for it to be deleted by contacting us, subject to the exceptions in Section 9.

Access to the Owner Panel is limited to the Operator and to people the Operator explicitly authorises for the community management part, for a limited time. Wody stores the Discord user ID, display name and avatar link of those authorised people, who granted the access, and when it expires. Sign-ins and actions in the Owner Panel are recorded in an audit log with the Discord user ID, display name, action, result, time, and a short one-way tag derived from the IP address (not the address itself). The audit log is kept for up to one year and each entry is also posted to a private Discord channel used by the Operator. The purpose is the security of the service and accountability for administrative actions.

Reports and moderation decisions in the official Wody Discord community, and reports sent to the Operator by email, are handled by the Operator and the community staff. They may include the reporter's and the reported person's Discord identifiers, the content reported, and the decision taken. This information is used to protect users and the service and to defend legal claims, is shared only with those who need it to handle the report, and may be disclosed where required by law. Absolute confidentiality cannot be promised because a report may need to be reviewed in order to be investigated. See the Community Guidelines for how to report.

WODY Collab stores what you put into it, tied to your Discord user ID: your collabs (text, category, tags, optional links and up to three images, with every version you submitted), the result of the automatic check and any moderation decision, reports made about a collab, your applications, and the messages exchanged between authors and applicants. Your Discord display name and avatar hash are copied into each collab and application so the other person can see who wrote it; a collab shows the author's Discord name and picture and, when the author has a public profile, a link to it (the profile is visible to signed in members only). When a visitor uses the optional contact form of a collab, the name, reply contact and message the visitor types are stored in the author's inbox, and no network address is stored with the message. Abuse is limited with the Wody Human Check and with per-collab limits instead.

Your Collab profile stores your preferences (categories, tags and language used for the For you section and for notifications), the social links you add (only addresses of the offered platforms, saved as canonical https links), the setting that decides whether the authors of collabs you apply to can see those links (off by default), and your notification settings. The social links are shown on your profile. Your Discord username, display name and avatar hash are copied into your Collab profile so that it can be opened by your username; they are refreshed from Discord each time you open your profile and cannot be edited here. Your profile is public: every signed in member can open it at wody.online/profile/{username} and see your name, picture, username, join date, vacation status and the number of your live collabs. If you connect your TikTok account on the TikTok page, your TikTok username is added to your profile automatically as a link to your TikTok profile (read from the account you linked, never typed in). You can hide the TikTok link with its own switch, and you can turn off the sharing of all your social links at any time; hidden links are not shown to anyone. Only signed in members can see a profile; visitors who are not signed in are sent to the login. Notifications are stored for 90 days and, if you leave them enabled, are also sent as a Discord direct message in your language. Notices about moderation of your own collab are always recorded in the profile; only their Discord message can be turned off.

To enforce the rule against prices and payment details, the text of a collab, an application or a message may be analysed by automatic rules and, when the operator has configured one, by an AI service. If the analysis fails, the collab is held for a person to review. Wody staff see reports, detected payment terms and the moderation history. Collab does not make decisions that produce legal effects about you by solely automated means: an automatic hold or suspension is placed in a queue for a person at Wody to review.

The purpose is to provide the feature you requested and to keep the board safe (legitimate interest and the performance of the service). Drafts and live collabs are kept while the feature is available. When you delete a collab it is hidden at once, its images are erased and its open applications are closed; its versions, checks, decisions and reports are kept as a moderation record, as described in Section 24. Applications and messages are kept while the collab exists and as long as needed for moderation. You can ask for deletion of your Collab data by contacting us, subject to the exceptions in Section 9. See also the Terms.

When you add an image to a collab by link, our server downloads that address once, checks that the file really is a PNG, JPEG or WebP image and stores a copy with your other collab images. Only a short file name taken from the address is kept, nothing that identifies you is sent to the other site (no cookies and no referrer), and visitors only ever load our copy. Your optional vacation status (an on/off switch, a short note of up to 120 characters and an optional end date) is stored in your Collab profile. While it is on, it is shown on your profile and to people who open your collabs or read your applications; it switches off by itself after the end date.

Server owners can create their own Collab categories for their server in the Dashboard. For each category Wody stores the server ID, the name the owner chose, who may post in it (everyone in the server, members with chosen Discord roles, or only the server staff), the IDs of the chosen roles, who created it and when. A category belongs to one server only: other servers cannot see it or use it, and two servers can use the same name. To decide whether you may post in a restricted category, Wody reads your roles in that server from Discord at the moment you post; those roles are not stored. The Collab settings a server owner chooses in the Dashboard (approval and announcement channel) are stored with the server ID.

To prevent abuse of posting, Collab keeps short lived records of when you posted and deleted collabs (your Discord user ID, the server ID and a time). They are used for the posting cooldown, the daily limit per server and temporary pauses, and the database removes them automatically after 24 hours.

This Policy may be updated when the service or its data processing practices change. The revision date shown above identifies the current version. Material changes may also be announced through the official Wody community channels where appropriate.

For privacy, legal, or data protection questions, contact Păcurar Ancuța-Narcisa, the Operator, at privacy@wody.online.

Wody may also use the optional wody_language preference cookie to remember a language you actively choose. It is not created or updated unless you consent to Preferences, and the language selector remains hidden until that consent exists. Your cookie choice is recorded using the strictly necessary wody_cookie_consent cookie. You can change or withdraw the optional preference at any time in the Cookie Policy.