Skip to content
tycho löke
MeWorkExpertiseWritingConnect
Follow your curiosity

Where would you like to go?

10 places to explore

Reading pathsThree questions to explore in the journalSectionMeet TychoThe person behind the platformSectionMy workTechnology, partners, and product marketingSectionMy journeyFrom help desk to product marketingSectionExplore expertiseMicrosoft cloud, MSPs, security, and AISectionThe journalLonger reads and shorter observationsPageConversationsPublic sessions and webinarsSectionGet in touchContinue the conversationSectionPrivacy policyData, privacy, and deletion requestsPageTerms of useThe ground rules for websites and applicationsPage
↑ ↓ to explore to openesc to close
Connect
Back to top
Website & applications

Privacy policy

A clear overview of the information used to run this website and my personal bots and applications, and the choices you have.

Effective and last updated: 26 October 2026

Privacy policyTerms of use
On this page
  1. Who is responsible and what this covers
  2. Information the services process
  3. Why information is used
  4. Legal bases
  5. Who receives information
  6. How long information is kept
  7. Your rights and deletion requests
  8. Cookies and browser storage
  9. Security and international processing
  10. Age requirements
  11. Changes and contact
Questions, support, or data deletion?

Contact [email protected]. For a bot, include its name and your Discord user ID so I can find the right records.

01Who is responsible and what this covers

Tycho Löke is responsible for the personal data described in this policy. Contact [email protected] for privacy questions or requests. This policy covers tycholoke.com and Discord bots and other applications operated by Tycho Löke that explicitly link to it (the “services”). These are personal projects, independent of AvePoint and Discord.

A service may provide a more specific privacy notice explaining its features, providers, and data practices. Read that notice alongside this policy. This policy does not cover unrelated third-party bots, websites, or services.

02Information the services process

  • Website requests: technical information such as IP address, browser and device information, requested pages, timestamps, and error or security events may be processed by the hosting infrastructure to deliver and protect the website.
  • Messages you send me: your email address, name if supplied, the content of your enquiry, and information needed to respond.
  • Discord interactions: depending on the bot’s stated features and granted permissions, Discord user, server, channel, role, and message identifiers; profile details supplied by Discord; commands and their inputs; interaction timestamps; and settings needed to provide the requested feature.
  • Content submitted to a bot: command text, messages, or attachments that you deliberately provide, or that a clearly described feature needs to process with the relevant Discord permissions. Receiving content to execute a command does not by itself mean a complete message history is stored.
  • Operational records: settings, feature-specific records, errors, and limited diagnostic or abuse-prevention information needed to keep a service working.

The information available to a bot depends on its configuration, Discord permissions, and the features you use. A service must explain any additional collection or use before it begins. Do not submit passwords, access tokens, payment details, or sensitive personal information through bot commands or support messages.

03Why information is used

Information is used to deliver website pages, respond to commands and enquiries, remember service settings, provide the features described by each application, troubleshoot errors, prevent misuse, and meet legal obligations. Discord API data is used only as necessary for a bot’s stated functionality; improvements using that data must use aggregated or de-identified information.

Personal data is not sold. Discord API data is not used for advertising, user profiling, or training AI or machine-learning models. Any feature that sends user content to an external AI or other content-processing provider requires a specific disclosure identifying that provider and explaining the processing before you use it.

04Legal bases

Where the GDPR or similar rules apply, processing relies on performing a contract when needed to deliver a service you request; legitimate interests in operating, securing, and maintaining the services and answering enquiries, balanced against your rights; compliance with legal obligations; or consent where required. You can withdraw consent at any time without affecting earlier lawful processing. Installing a bot does not replace any consent required by law.

05Who receives information

Cloudflare provides this website’s hosting, delivery, security, and storage infrastructure. Discord processes the information needed to operate its platform and provide bot interactions under its own privacy policy. Hosting, storage, and email providers may process information on my behalf as needed to operate a service or answer an enquiry. A bot’s specific notice will identify additional providers where applicable.

Command results may be visible to other people in the channel where you use a bot, depending on the feature. Server administrators control server settings and permissions; check where you are posting before submitting personal information.

Information may also be disclosed where legally required or necessary to protect legal rights and safety. Discord API data is shared only with service providers acting on my behalf, when required by law, or when a user expressly directs an allowed disclosure, in accordance with Discord’s developer terms.

06How long information is kept

Data is kept only for as long as needed for the purpose described. Command inputs are processed to complete the interaction; any persistent storage of content or feature records must be explained in that service’s notice. Settings and records needed for an ongoing feature may remain while that feature is in use. Support correspondence and diagnostic records are retained only as needed to resolve enquiries, investigate faults or abuse, and meet applicable obligations.

Discord API data is deleted promptly when no longer necessary for the bot’s stated functionality, when a valid deletion request is received, when Discord requires deletion, or when the application stops operating, unless law requires retention. Any legally required retention is limited to that obligation. Backup copies, where used, expire through their normal rotation and are not used to resume ordinary processing of deleted data.

Removing a bot stops its future access to that server but may not immediately remove records already stored. To request deletion of existing data, use the contact method below.

07Your rights and deletion requests

Email [email protected] with the subject “Privacy request” or “Data deletion request”. Include the bot or service name and, for Discord requests, your user ID and relevant server ID if available. Describe what you want accessed, corrected, exported, or deleted. Only information reasonably necessary to verify your identity or authority will be requested; never send your Discord password or token.

Depending on applicable law, you may have rights to access, correct, erase, restrict, or receive a portable copy of your personal data, object to processing based on legitimate interests, and withdraw consent. Requests are handled without undue delay and within the applicable legal period, generally one month under the GDPR; you will be told if a lawful extension or exception applies.

You can stop using a bot, remove it from a server you manage, or revoke authorised application access in your Discord settings. Deleting data held by these services does not delete content or records independently held by Discord or other server members. You can also complain to your local data protection authority, including the Dutch Autoriteit Persoonsgegevens.

08Cookies and browser storage

This website uses local browser storage to remember your colour-theme preference. The private writing studio also uses local draft storage and an authentication cookie for its operator. Cloudflare may use necessary security technologies to protect and deliver the site. The current website does not include advertising trackers or optional analytics scripts. You can clear browser storage or control cookies through your browser settings; some preferences or authenticated features may stop working.

09Security and international processing

Reasonable technical and organisational measures are used to limit access and protect information, including encrypted connections and access controls. No system can guarantee absolute security. If a personal-data breach occurs, affected users, Discord, and authorities will be notified where required.

Infrastructure providers may process information outside your country, including outside the European Economic Area. Where required, transfers must use an adequacy decision or appropriate safeguards such as standard contractual clauses. Contact [email protected] for information about safeguards relevant to a particular service.

10Age requirements

Discord bots covered by this policy are not directed at children under 13 or anyone below the minimum age required to use Discord in their country, if higher. If you believe information has been collected from someone below that age, contact [email protected] so it can be investigated and deleted as appropriate.

11Changes and contact

This policy may be updated as the services change. The date above identifies the current version. Material changes will be communicated through the affected service where appropriate, and consent will be requested where required. For any privacy question, contact [email protected].

← Return to tycholoke.com

Let’s connect

Technology. Business. People.
A continuing conversation.

Choose the conversation you’d like to start.

For AvePoint, channel conversations, and speaking enquiries.

[email protected]
Email Tycho

tycho löke
Privacy policyTerms of useLinkedIn Back to top
Personal perspectives. Not an official AvePoint publication.© 2026 Tycho Löke