Privacy Policy

Last updated: 30 October 2026. This notice explains how gioyous.it handles information when you browse the site, use its tools and games, contact us, create an account, comment, participate in the forum, or interact with advertising and embedded services. It covers services currently enabled as well as optional functionality installed on the site but not currently active. A feature described as optional or inactive does not necessarily collect data while it is disabled.

1. Who is responsible for your data

The website is gioyous.it, an independent technology collective and studio. The operator of gioyous.it is the data controller for processing carried out for the operation of this website, unless this notice identifies a third party as an independent controller for its own service. You can contact the site operator through the Contact page. Please do not send passwords, payment-card details, identity documents, or other unnecessary sensitive information through the contact form.

This notice applies to https://www.gioyous.it and its subdomains, pages, tools, games, forum, APIs and related website services that link to this notice. Some third-party services have their own privacy notices and act as separate controllers for their own processing.

2. Information we may collect

Depending on the feature you use, information may include:

  • Technical and log information: IP address, date and time of a request, requested URL, referring page, browser and device details, operating system, language, response status, and security or diagnostic events.
  • Account and profile information: username, display name, email address, password hash, profile fields, role, account preferences, and authentication or security records.
  • Content you submit: comments, forum topics and replies, contact-form messages, survey answers, chatbot prompts, feedback, uploaded media, and other information you choose to provide.
  • Usage and interaction information: pages viewed, navigation events, clicks, scrolling, game or tool interactions, ad impressions, recommendation-block views and clicks, and performance events, where the relevant analytics or feature is enabled.
  • Consent and preference information: cookie choices, consent status, timestamp, banner or policy version, and related technical identifiers used to remember your choices.
  • Transaction or donation information: information necessary to process a donation or other payment if a payment feature is made available. Payment credentials should be handled by the relevant payment provider; we do not intend to store full payment-card numbers or security codes on this website.

3. Why we use information and legal bases

We use information to operate and secure the site; provide pages, accounts, forum functions, games, tools and APIs; answer enquiries; prevent spam, abuse and fraud; maintain backups; understand site performance; remember privacy choices; display and measure advertising where enabled; and comply with legal obligations.

Under the GDPR, the legal basis depends on the specific activity. It may be: your consent (Article 6(1)(a)), performance of a contract or steps requested before entering one (Article 6(1)(b)), compliance with a legal obligation (Article 6(1)(c)), or our legitimate interests in operating, protecting, maintaining and improving the website (Article 6(1)(f)), where those interests are not overridden by your rights. Non-essential cookies, behavioural analytics, personalised advertising and similar tracking are used only where the required consent has been obtained. You can withdraw consent at any time; withdrawal does not affect processing already carried out lawfully.

4. Hosting, server logs, security and backups

The site is hosted using Aruba infrastructure. The hosting environment and web server may process IP addresses, request details, timestamps, user-agent information and error or security logs to deliver pages, diagnose faults, prevent attacks, rate-limit abusive traffic and maintain service availability. Aruba may act as a data processor for hosting operations and may use its own subprocessors. Aruba HiSpeed Cache and related performance services may temporarily store or cache page and technical data to deliver the site efficiently.

Security tools, login protection, anti-spam services, firewalls and diagnostic tools may process IP addresses, login attempts, browser details, request metadata and security events. Really Simple Security, LoginPress, Akismet and other security or anti-spam components may be involved depending on the feature and configuration. Backups and migration tools, including Duplicator and JetBackup, may copy databases and website files that contain personal data. Backup copies are retained according to the relevant backup rotation and operational requirements and may remain temporarily after information is changed or deleted from the live site.

5. Accounts, login, comments and the forum

If you register or sign in, WordPress and related account components process the account information you submit and technical information needed to authenticate you, maintain your session, protect the account and apply permissions. Login cookies and other session identifiers may be necessary for these functions. Optional two-factor authentication, if enabled, may process authentication secrets, one-time codes, recovery codes or email verification information.

If you leave a comment, we process the information shown in the comment form, the comment itself, the time of submission, your IP address and browser user-agent information for moderation and spam prevention. Comments and their metadata may remain publicly visible and may be retained for as long as the discussion remains useful or necessary. WordPress may provide an anonymised hash of your email address to Gravatar to check whether you use that service; if a profile image is displayed, it is supplied by Gravatar. See Automattic’s privacy notice.

The site operates a wpForo forum. If you register, post, reply, react, report content or use forum features, the forum may process your username, email address, profile details, posts, replies, timestamps, moderation records, IP address and related account or session information. Public posts and profile details may be visible to other visitors, indexed by search engines, quoted, copied or retained in third-party caches. Do not publish personal or confidential information in public forum areas. Forum content may be retained to preserve discussion context, moderation history and site integrity.

6. Contact forms, feedback, surveys and email

The Contact form currently asks for your name, email address, subject and message. These details are used to receive, review and respond to your enquiry. The form is configured to send a notification to the site’s administrator email address, with your submitted email address used as the reply-to address. Form submissions may be processed by WPForms and stored in the WordPress environment or its database according to the form’s settings. Spam-prevention checks, including timing and anti-spam mechanisms, may also process technical information. Do not include special-category data or sensitive documents unless we specifically request them through an appropriate channel.

UserFeedback may be used to collect optional survey responses or feedback about the website. If you respond, we process the answers and any information you choose to include, along with technical metadata that the survey service collects. WP Mail SMTP is used to support the delivery of website email; email providers and mail servers may process sender and recipient addresses, message contents, timestamps and delivery metadata while transmitting or storing messages.

7. Analytics, measurement and session replay

Google Analytics and MonsterInsights: Google Analytics may be connected through Site Kit by Google and/or MonsterInsights. If enabled and configured, these tools can collect page views, events, referral information, device and browser details, approximate location, interaction and performance data, and online identifiers. Google may process this information on its own infrastructure and use cookies or similar technologies depending on the configuration and your consent choices. See Google’s Privacy Policy.

Microsoft Clarity: Microsoft Clarity is installed and active. When its tracking is enabled and permitted by your consent choices, it may collect interaction and diagnostic information such as pages viewed, clicks, pointer movement, scrolling, navigation, device and browser details, and session identifiers. Clarity can create session-replay animations from page content and user interactions; these are not ordinary camera or screen video recordings. Form fields and sensitive content should be masked or excluded from recording. Clarity may use cookies and other identifiers and may process information on Microsoft’s systems. See Microsoft’s Privacy Statement and Clarity’s FAQ.

Other measurement: Post Views Counter and similar features may count views or interactions. Traffman may process the page URL being viewed, recommendation or advertising-block impressions, clicks on recommendations, and technical request information, potentially including IP address and browser details, to operate its content traffic-exchange network. These activities may involve Traffman and other participating websites or network partners. Micro Sponsors and other sponsorship or trust-badge integrations may also involve third-party content or measurement when displayed.

Site Kit may connect the site to Google services such as Analytics, Search Console, AdSense or other Google products. The exact services and data flows depend on which services are connected and enabled in the Site Kit dashboard. Search Console primarily provides site owners with search-performance and indexing reports; it is not the same as a visitor analytics tracker.

8. Advertising, AdSense and traffic exchange

Advertising and sponsorship functionality may be provided through Google AdSense, Traffman, Micro Sponsors or other advertising partners when configured and displayed. Google AdSense may use cookies, local storage, advertising identifiers, IP addresses, device and browser information, page context, ad impressions, clicks and related signals to deliver, limit, personalise or measure advertisements, detect invalid traffic and prevent fraud. Depending on your choices and the ad configuration, ads may be personalised or non-personalised. Third-party advertising technology providers may receive or access information through ad requests, tags, pixels or similar technologies.

Google’s advertising partners and technology providers may include entities other than Google. The providers actually used depend on the AdSense settings and the consent framework in effect at the time. Their identities and privacy information should be made available through the applicable advertising consent interface and Google’s published vendor information. See How Google uses information from sites or apps that use its services and Google’s publisher CMP requirements.

For visitors in the European Economic Area, the United Kingdom and Switzerland, Google requires publishers serving personalised ads to use a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework. The site currently has CookieAdmin, WPConsent and the WP Consent API installed. Their presence alone does not establish that the site’s advertising consent configuration is valid, certified or correctly connected to every advertising and analytics tag. The site operator must ensure that the active consent mechanism blocks non-essential technologies until the required consent is obtained, passes consent signals to Google and Microsoft where required, and provides a way to change or withdraw choices.

9. Cookies, local storage and consent choices

Cookies and similar technologies may be set by WordPress, the forum, login and security components, consent tools, analytics services, advertising partners, embedded content and other features. They may be session-based or persistent and may be first-party or third-party. They can remember login state, form preferences, consent choices, language or display preferences, measure usage, support advertising, prevent fraud or preserve functionality.

  • Strictly necessary technologies support functions you request, such as login sessions, security, load balancing, consent storage and basic site operation.
  • Preference technologies remember choices such as language or display settings.
  • Analytics technologies measure traffic, performance and interactions, including Google Analytics, MonsterInsights and Microsoft Clarity where enabled.
  • Advertising and marketing technologies may support ad delivery, frequency control, personalisation, measurement, attribution, sponsorships and traffic exchange, including Google advertising and Traffman where enabled.

Cookie names, providers, purposes and expiry periods can change when plugins, services or settings change. We therefore do not treat the list above as a fixed technical cookie inventory. Use the consent or cookie-preferences interface displayed on the site to review or change your choices. You can also control cookies through your browser settings, although blocking necessary cookies may affect login, forum, form or other site functions. Deleting cookies may remove your saved consent choice, causing the banner to appear again.

Where consent is required, non-essential analytics, advertising and similar tracking should not run before consent. You can withdraw or change consent through the site’s cookie-preferences interface. A browser-level block or deletion is separate from a withdrawal request and may not communicate your choice to every third-party service.

10. Games, tools, Wordle, APIs and external content

gioyous.it provides browser-based tools, games, Wordle-related pages and API endpoints. Some tools process the text or files you enter locally in your browser; where a tool states that processing is local, the input is intended to remain on your device unless you separately submit it or the tool requires a network request. Other features may send requests to our server or an external provider to retrieve content, validate data, load game assets, retrieve Wordle source data, obtain software-release information or provide a requested result. Those requests may expose your IP address, requested URL, timestamps, browser details and any data included in the request. Avoid entering secrets, passwords or confidential personal information into public tools.

Pages may contain embedded or linked content from third parties, including video, social networks, maps, review services, Trustpilot, PCrisk, Internet Archive, GitHub or other external services. When an embedded item loads, the third party may receive your IP address, browser information, the page URL and information about your interaction, and may set cookies or use other tracking technologies. A normal link generally sends information to the destination only when you follow it. Third-party services are governed by their own privacy notices and terms.

11. AI assistants, chatbots and automated services

The site has chatbot and assistant-related components, including HumanChatbot Network and Site Assistant. If a chatbot or AI assistant is made available, the text of your prompt, conversation, page context and technical request information may be processed by the site and by the external AI or hosting provider configured for that feature. Do not submit passwords, payment information, confidential source code, sensitive personal data or other secrets to a chatbot. The external provider, model, storage and retention settings depend on the specific integration and must be reviewed in that feature before it is enabled.

The Attendant AI search/chatbot plugin is currently installed but inactive. If activated, it may send visitors’ search questions and relevant site content to the configured AI provider, such as Google Gemini or OpenAI, to generate answers. It is not described as currently operating while disabled. Any future activation should be accompanied by an updated provider-specific disclosure and consent review where required.

12. Donations and payment features

The Charitable donation plugin is installed and active. If donation campaigns or payment methods are published, the information needed to make and administer a donation may include donor name, email address, donation amount, campaign, transaction reference, payment status and information required by the selected payment gateway. The payment gateway may independently collect payment credentials and transaction metadata under its own privacy notice. No particular payment processor or live donation workflow is confirmed by this notice; the actual provider and fields must be disclosed on the relevant donation form before donations are accepted.

13. Social sharing, external accounts and publication integrations

Social publishing, sharing or login integrations, including ZASP and any connected social platforms, may transmit post text, links, media, account identifiers, authentication tokens or publication metadata to the platform you choose. If you follow an external social link, the destination platform may collect information about your visit. The platform’s own privacy notice applies to its processing. We do not receive your social-platform password through a normal share link.

14. Optional plugins installed but currently inactive

The WordPress installation also contains the following plugins marked inactive in the plugin inventory checked on 30 October 2026. They are listed for transparency because they may be enabled later. Their mere installation while inactive does not mean their visitor-facing functions are currently running or collecting information:

  • Attendant – Free AI Site Search & Chatbot: if enabled, visitor queries and relevant page context may be sent to its configured AI provider, such as Gemini or OpenAI.
  • BarterBanner: if enabled, banner views, clicks, referral information and traffic-exchange activity may be processed by BarterBanner and participating sites.
  • Two Factor: if enabled, authentication secrets, one-time codes, recovery codes or email verification details may be processed for account security.
  • Elementor: if enabled for visitor-facing content, embedded widgets or third-party integrations added through it may load external resources or process interaction data.
  • All in One SEO: currently inactive; its ordinary search-engine metadata functions are not, by themselves, a visitor tracking service.
  • Block-a-saurus: currently inactive; if enabled, the embedded game may process gameplay locally and generate ordinary server requests for page and game assets.
  • Blogger Importer and RSS Importer: currently inactive import tools; if used by an administrator, they may retrieve content and metadata from external feeds or accounts. They are not currently described as visitor-facing collection tools.
  • GopherPress: currently inactive; if enabled, it could expose site content through the Gopher protocol and generate server request logs.
  • Interactions: currently inactive; if enabled, configured interactive effects may process browser interaction events and load related assets.
  • KineticHub Page Loader: currently inactive; if enabled, it may load scripts and assets needed for page transitions or loading effects.
  • Silica: currently inactive; if enabled, its visual components may load scripts, styles or external resources configured by the site operator.
  • Ultimate Cursor: currently inactive; if enabled, cursor and background effects may process pointer or browser interaction events.

Other inactive plugins may be present for administration, migration, design or content management. We review this inventory when site functionality changes. If an inactive plugin is activated in a way that introduces a new recipient, tracking purpose, AI provider, payment service or other material processing activity, this notice and the consent configuration should be updated before the feature is made available.

15. Who may receive information

Depending on the feature and configuration, information may be made available to: Aruba as hosting and infrastructure provider; WordPress and plugin service providers; Google services including Analytics, Site Kit and AdSense; Microsoft Clarity; Traffman and its traffic-exchange partners; Automattic/Gravatar and Akismet; email delivery providers; anti-spam and security providers; AI providers configured for chatbot features; donation/payment providers if enabled; and external platforms whose content or widgets you choose to load. We do not sell personal information as a standalone data-broker business. Advertising and analytics integrations may nevertheless disclose information to their providers for the purposes described above.

16. International transfers

Some providers may process information outside Italy or the European Economic Area, including in countries that may have different data-protection laws. Where GDPR applies, transfers must rely on an applicable legal mechanism, such as an adequacy decision, an approved certification framework where applicable, or standard contractual clauses with any supplementary measures required by the circumstances. The applicable provider’s privacy documentation explains its transfer arrangements.

17. How long information is kept

We keep personal information only for as long as reasonably necessary for the purpose for which it was collected, including account operation, responding to enquiries, maintaining discussions, security, legal compliance and resolving disputes. Account data is generally retained while the account remains active and for a reasonable period afterwards where needed for security or legal purposes. Comments and public forum contributions may remain for the life of the relevant discussion or account record. Contact messages and form entries are kept for as long as needed to handle the enquiry and maintain appropriate records. Security logs, analytics records, cookies, session recordings and backups may have separate retention periods controlled by the relevant service or configuration. Exact retention periods vary and should be checked in the settings and contracts of each provider; we do not claim a single fixed retention period for all systems.

18. Your rights

Where the GDPR applies, you may have the right to request access to your personal data, correction of inaccurate data, erasure, restriction of processing, data portability, and to object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it at any time. You may also object to direct marketing where applicable. These rights are subject to legal conditions and exceptions.

To exercise a right, contact us through the Contact page and describe your request. We may need to verify your identity before acting. You also have the right to lodge a complaint with the Italian Data Protection Authority (Garante per la protezione dei dati personali) or another competent supervisory authority. The Italian Authority’s website is garanteprivacy.it.

19. Children’s privacy

The site is not intended to knowingly collect personal information from children in circumstances where parental authorisation is required. If you believe a child has provided personal information inappropriately, contact us so we can review and, where appropriate, remove it. Public forums and interactive features should not be used to disclose a child’s personal details.

20. Changes to this notice

We may update this notice when the site, its plugins, services, legal requirements or data practices change. The latest revision date appears at the top of this page. Material changes may also be communicated through the site or the relevant consent interface where appropriate. Please review this page periodically.

21. Important configuration note

This notice describes the site’s observed plugin inventory and the categories of processing that its active or optional features can perform. The precise cookies, connected Google products, advertising vendors, AI providers, consent signals, recording exclusions and retention periods depend on settings that can change independently of this page. The site operator should keep the cookie inventory and vendor list synchronized with the live configuration, and should not activate a new tracking, advertising, AI or payment integration until its privacy information and consent behaviour have been checked.

Verified by MonsterInsights