PRIVACY POLICY Effective: August 17, 2026 IMPORTANT NOTE ON LANGUAGE This English translation is provided for convenience only and is not legally binding. The legally binding version is exclusively the current complete German version of this Privacy Policy, including all supplements related to the Digital Services Act (DSA). ### Summary (not legally binding) ### MessageDrop is a privacy-focused web app for publishing user-generated content, private communication, and location-based organization of information. The service can be used without a user account. Certain features require the creation of a user account. Login is performed locally via a PIN; the PIN is not transmitted to the server. Only the pseudonymous user ID, public keys, and status data are stored on the server in the user account. Use of MessageDrop is permitted only after reaching the age of 16. Persons who have reached the age of 16 but have not yet reached the age of 18 may use the service only with the consent of their parents or legal guardians. Legally binding declarations that go beyond the ordinary use of the service are generally only possible upon reaching the age of 18. A large portion of the data is intentionally stored primarily locally on the user’s device (e.g., in the browser or app storage) to ensure data minimization and a high standard of data protection. Control over this locally stored data generally lies with the user. Loss or deletion of local data is possible at any time. For the translation function, the user may optionally store their own DeepL API key in the encrypted local user record on the device. When the translation function or the key validation function is used, the key is transmitted for the respective request to our backend and for use with DeepL, but is not stored permanently on the server. The optional read-aloud feature uses the browser’s or operating system’s speech synthesis. For this purpose, the text selected by the user is passed to the speech component of the device or platform. Depending on the browser, operating system, device, and selected voice, processing may take place locally on the device or via components of the platform provider. Without a previously created backup, it is not possible to restore locally deleted data. Public content, comments, and publicly discoverable SecretDrops are created by users and may be reported, reviewed, and moderated in accordance with the provisions of the Digital Services Act (DSA). Content for which DSA proceedings are initiated will be temporarily hidden from public view. Personal information must not be published publicly—neither about oneself nor about other individuals. Potentially illegal public content, including publicly discoverable SecretDrops, can be reported via the reporting function within the service or through the DSA contact point listed in the legal notice. Affected users may—to the extent provided by law—file internal complaints against moderation decisions. MessageDrop does not use a personalized recommendation or ranking system. Public content is not algorithmically filtered or prioritized, but is displayed exclusively based on the geographical area being viewed and the time of publication. Private chat messages are transmitted with end-to-end encryption and are generally not visible to us in plain text. External content (e.g., YouTube, TikTok, Pinterest, Spotify, Tenor, Klipy, Unsplash, Wikipedia, and Viator) is loaded only after the user has actively enabled the respective provider. Blanket consent for all providers is not available. This is separate from external functional services (e.g., Open-Meteo, OpenStreetMap/Nominatim, SkedGo/TripGo, and DeepL), which are used when the respective function is actively used and are not enabled via the external content toggle. When Unsplash images are selected, image files can be loaded, downloaded to the device, and stored locally. Consent granted for external content may be revoked at any time with future effect (e.g., by deactivating the respective provider in the settings). System messages (e.g., notices regarding DSA proceedings or scheduled maintenance) are generated exclusively by authorized administrative systems and displayed in the user’s frontend. System messages are always active; users can delete them in the frontend without this necessarily affecting internal records. Profiles (name/avatar) can be used locally for easier identification. When initiating contact, a user may optionally request profile sharing; the other user must actively consent. For technical delivery of the profile sharing function, requests and response status are stored temporarily on our server; if consent is granted, the shared profile name and avatar are stored there only in encrypted form for delivery. After delivery or expiry, these temporary records are deleted; the current period is 7 days. Once delivered, the name and avatar are stored locally on the contact’s device. Places can be followed; where technically possible and supported by the device, the user may receive push notifications when new public content appears at a followed place. Technically required push tokens are processed solely for delivery. There is no entitlement to the delivery of push notifications. MessageDrop offers optional Usage Time Protection (self-restriction or parental mode) with a daily limit and optional time windows. A parental PIN is processed exclusively as a cryptographic hash; the plaintext PIN is not stored. MessageDrop does not provide access to emergency services. Only the current, complete German version of this Privacy Policy, including the additions relating to the Digital Services Act (DSA), is authoritative. ### Complete Version ### ### Glossary ### User A natural person who uses MessageDrop, regardless of whether a user account has been created. User Account A technical, pseudonymous access unit that a user may voluntarily create and that is identified by a User ID. User ID Technical identifier of a user account. The User ID is pseudonymous and, on its own, does not allow for the direct identification of a person. Visitor A user who uses MessageDrop without creating a user account. Public Content Content created by users (e.g., public messages, comments, and publicly discoverable SecretDrops) that is generally publicly visible or discoverable unless it has been restricted or removed. Private Communication Communication between users that is transmitted in encrypted form (e.g., private chats). External Content / Third-Party Providers Content provided by third-party providers and integrated only after an active decision by the user (e.g., iframes/oEmbed). Upon activation, data is transmitted to the respective provider. System Messages Internal messages generated exclusively by authorized administrative systems and displayed in the frontend (e.g., regarding DSA proceedings or maintenance work). System messages do not constitute an email inbox. DSA Proceedings Proceedings under the Digital Services Act (DSA), in particular notices and appeals in connection with public content, including publicly discoverable SecretDrops. Public Case Page A publicly accessible page relating to DSA proceedings on which only anonymized or non-personal information is published. Push Notifications / Push Tokens Technical feature for delivering notifications to a device. Push tokens are technical identifiers that may be required for delivery. Local Storage Storage of data on the user’s device (e.g., IndexedDB, app storage, cache). This data can be deleted by the user or due to technical circumstances. Read-Aloud Function Optional feature that allows selected text to be read aloud using the browser’s or operating system’s text-to-speech synthesis. Which voices are available and whether processing occurs locally or on the platform depends on the browser, operating system, device, and selected voice. Usage Time Protection Optional feature for limiting usage time (in “self” or “parental” mode) with a daily limit and optional time windows. Parent PIN Hash Cryptographic hash value of a parent PIN set by the user in the parental mode of Usage Time Protection. The plaintext PIN is not stored. ### 1. Data Controller under the GDPR ### The data controller pursuant to Article 4(7) of the GDPR is: JackTools.Net UG (limited liability) Im Kirchfeld 27 38304 Wolfenbüttel Germany Represented by the Managing Director: Christian Wagner, Dipl.-Inform. (FH) Email: jacktoolsnet@gmail.com Phone: +49 (0) 176 / 41 23 57 74 (hereinafter “we,” “us,” or “Provider”) This Privacy Policy applies to MessageDrop (messagedrop.de), related mobile applications, Progressive Web Apps (PWA), and internal admin and moderation interfaces. This Privacy Policy governs only the processing of personal data; liability and warranty issues are governed by the Disclaimer. ### 2. Use as a Visitor (without a User Account) ### ### 2.1 General Use ### MessageDrop can be used without creating a user account. In particular, public content can be viewed, provided it is available. ### 2.2 Technical Data Processing ### When using the service as a visitor, technically necessary data is processed, in particular: - IP address, - timestamp, - technical header information (e.g., user agent in server logs, to the extent technically transmitted), - request metadata, if applicable, for the delivery and security of the service. The purpose of the processing is the technical delivery of the service, system security, the prevention of misuse and fraud, as well as error analysis and stability. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in secure and stable operation). ### 2.3 External Content and Third-Party Providers ### MessageDrop allows for the optional integration of external content from third-party providers (e.g., videos, music, animated content, or embedded media). External content is disabled by default. Instead of the external content, a notice is displayed informing the user that third-party content is available, together with an active option (e.g., a toggle) that allows the respective provider to be explicitly enabled. Blanket consent for all external providers is not provided; the decision is made separately for each provider. This provider-specific decision applies to the embedding of external content. External functional services (e.g., Open-Meteo, Nominatim / OpenStreetMap, and DeepL) are described in Section 2.6. External content is embedded only after the user has deliberately and voluntarily enabled it. Depending on the provider, integration is carried out using techniques such as iframes or oEmbed as well as API and media requests. Content may be loaded directly from the servers of the respective third-party provider. We have no influence over the nature, scope, and purpose of data processing by these providers. By activating an external content provider, the following data in particular may be transmitted to the respective provider: - IP address, - technical device and browser information (e.g., user agent, language settings), - time of access, - referrer information (if transmitted by the browser), - any other technically necessary request information. At the same time, for technical reasons, the respective provider may transmit data to the user’s device or store data there, in particular: - cookies or comparable identifiers (e.g., local storage, session storage), - pixels, tracking technologies, or measurement technologies (to the extent used by the provider and technically possible), - cache data or other technically necessary content for delivering the embedding. We have no influence over the nature, scope, or purpose of this data processing by the external provider. Processing is carried out exclusively under the responsibility of the respective third-party provider. The privacy policy and terms of use of the respective provider apply. The external providers integrated at the time this Privacy Policy was prepared are listed below: YouTube (Google Ireland Limited) Privacy Policy: https://policies.google.com/privacy Legal Notice / Contact: https://www.google.com/about/company/ TikTok (TikTok Technology Limited / TikTok Information Technologies UK Limited) Privacy Policy: https://www.tiktok.com/legal/page/eea/privacy-policy/de Legal Notice / Contact: https://www.tiktok.com/legal/page/global/impressum Pinterest (Pinterest Europe Ltd.) Privacy Policy: https://policy.pinterest.com/de/privacy-policy Contact: https://help.pinterest.com/de/contact Spotify (Spotify AB) Privacy Policy: https://www.spotify.com/de/legal/privacy-policy/ Legal Notice: https://www.spotify.com/de/legal/imprint/ Tenor (Google Ireland Limited) Privacy Policy: https://policies.google.com/privacy Legal Notice / Contact: https://www.google.com/about/company/ Klipy / KLIPY.COM (KIKLIKO, Inc.) Privacy Policy: https://klipy.com/support/privacy-policy Terms of Service: https://klipy.com/support/terms-services Contact: KIKLIKO, Inc., 505 Montgomery St. Ste 1100, San Francisco, CA, 94111, USA Unsplash (Unsplash B.V.) Privacy Policy: https://unsplash.com/privacy Terms of Use: https://unsplash.com/terms Wikipedia / Wikimedia projects (Wikimedia Foundation, Inc.) Privacy Policy: https://foundation.wikimedia.org/wiki/Policy:Privacy_policy Terms of Use: https://foundation.wikimedia.org/wiki/Policy:Terms_of_Use Wikipedia searches are performed only if they are enabled in the search settings and the required map zoom level has been reached. Searches for articles within the visible geographic area are sent to the Wikimedia services through the MessageDrop backend. When a Wikipedia pin is opened, article information is loaded and displayed only after Wikipedia has been enabled in the external content settings. This may include retrieving article text, license and creator information, and images from Wikimedia services. If media is loaded directly by the user's device or Wikipedia links are opened, Wikimedia receives the technical request data required for delivery, in particular the IP address and browser information. The Wikimedia Foundation is based in the United States and operates servers and data centers there. When Wikimedia services are used, particularly when media is retrieved directly or Wikipedia or Wikimedia pages are opened, personal data may therefore be transferred to, processed, and stored in the United States. The level of data protection in the United States may differ from that in the European Union. Further information about processing and possible international data transfers is available in the Wikimedia Foundation Privacy Policy linked above. Viator (Viator, Inc.) Privacy Policy: https://www.viator.com/support/privacyPolicy Terms and Conditions: https://www.viator.com/support/termsAndConditions Viator content and experience searches are loaded only after Viator has been enabled in the external content settings. In particular, search terms, language and country settings, destination and location parameters, date and price filters, and product and media data may be processed. API communication takes place through the MessageDrop backend. Product images may be loaded directly from media servers used by Viator; the respective operator then receives the connection data technically required for delivery, in particular the IP address and browser information. When a Viator offer is opened, the user leaves MessageDrop. Flaticon / Freepik (Freepik Company S.L.U.) Privacy Policy: https://www.freepik.com/legal/privacy/ Terms of Use: https://www.flaticon.com/legal The links listed above are provided for information purposes only. We have no control over the content, whether the external pages remain up to date, their availability, or any changes to them, and we assume no responsibility or liability in this regard. The list of external providers may be expanded or modified for technical reasons. If new providers are integrated, the list will be updated in an amended version of this Privacy Policy. The legal basis is Art. 6(1)(a) GDPR (consent). Consent may be revoked at any time with future effect, in particular by deactivating the respective provider in the settings. ### 2.4 Local Profiles Without a User Account (Optional) ### When using the service without a user account, the user may optionally create local profiles for better organization and identification. Such a profile may consist, in particular, of a freely chosen name and an avatar (image). These profiles are stored exclusively locally on the device and are visible only to the respective user. No data is transferred to our servers or made public to other users. The legal basis is Art. 6(1)(f) GDPR (legitimate interest in a user-friendly display) or Art. 6(1)(b) GDPR (provision of a function used by the user), insofar as processing is necessary to provide that function. ### 2.5 Read-Aloud Function / Speech Synthesis ### MessageDrop may provide an optional read-aloud function, insofar as this is supported by the browser and device. This function is used only after being actively triggered by the user. For the read-aloud function, the text selected by the user is passed to the browser’s or operating system’s speech synthesis. We do not receive any additional content data on our servers through the use of this function unless such data is already being processed as part of the relevant MessageDrop feature. Whether speech synthesis takes place entirely locally on the device or whether components of the browser, operating system, or platform provider are involved depends on the specific technical environment, in particular on: - browser, - operating system, - device, - installed language packs, - selected voice. We have no influence over the technical design or any data processing by browser, operating system, or platform providers in connection with their speech synthesis. To the extent that such providers supply their own components, processing is carried out under the sole responsibility of the respective provider. The legal basis is Art. 6(1)(b) GDPR (provision of the function requested by the user) and, where necessary, Art. 6(1)(f) GDPR (legitimate interest in accessible and user-friendly functions). ### 2.6 External Functional and Information Services ### For certain functions, MessageDrop uses external information and API services that do not necessarily appear as embedded content, in particular: - Open-Meteo (weather and air quality data), - DeepL (translations), - Nominatim / OpenStreetMap (search, geocoding, map reference), - SkedGo / TripGo (route, stop, timetable, and real-time information), - Flaticon / Freepik Company S.L.U. (licensed stickers and comparable graphic elements). When using these functions, depending on the specific use case, search terms, language and country settings, destination/location parameters, technical connection data, and, where applicable, reference URLs may be processed. Communication with third-party providers takes place, where technically implemented, via our servers or directly from the device. For the translation function, the user may choose either the DeepL access provided by us or their own DeepL API key. A user-provided DeepL API key is stored locally in the encrypted user record on the device. When the user performs a translation or validates the key, that key is transmitted to our backend for processing of the respective request and used with DeepL. According to the current technical design, a user-provided DeepL API key is not stored permanently on the server. There is no separate external content toggle for these functional services. They are only used when the user actively uses the respective function. According to the current technical design, the OpenStreetMap map tiles displayed in the app are requested directly by the device from `https://tile.openstreetmap.org/`. The OpenStreetMap tile server therefore receives the technically required connection data, in particular the IP address, time, browser information, and identifiers of the requested map tiles. The requested tiles may reveal the geographic map area being displayed. The OpenStreetMap Foundation processes this data as an independent controller in accordance with its own privacy policy. Place searches through Nominatim are performed only when the corresponding search function is used. In particular, the search term or geographic search parameters may be processed. POI data displayed in MessageDrop is instead delivered from a geodata database operated by MessageDrop. The underlying OpenStreetMap country extracts are obtained server-side through the Geofabrik GmbH download service, filtered, and updated regularly. Merely displaying or retrieving a POI therefore does not cause an additional request to Geofabrik or OpenStreetMap. MessageDrop processes the requested map area, selected POI categories, and the usual technical connection and log data for this purpose. Geofabrik is used solely for server-side retrieval of OpenStreetMap extracts. No user search requests, locations, or other personal user data are transmitted to Geofabrik. When the routing feature is actively used, MessageDrop transmits the data required for the request through its own TripGo service to the TripGo API provided by SkedGo Pty Limited. This includes, in particular, start and destination coordinates, requested transport modes, requested departure or arrival time, language and, where applicable, stop, line, and connection identifiers. A location determined on the device is used for a route request only when the user invokes the corresponding function. Communication with SkedGo takes place through the MessageDrop server. SkedGo processes the technically required connection and request data in accordance with its own privacy policy. Processing outside the European Economic Area, in particular in Australia or other countries used by SkedGo or participating transport data providers, cannot be excluded. To reduce external API requests and provide stable operation, route and transport information is cached for limited periods. Routes are currently cached only briefly in memory for approximately 15 seconds. Stop and line information is normally stored for up to 7 days and may be used as stale data for up to 30 days during temporary failures of the external service. Entries in the persistent stop cache that are no longer required are currently removed after 30 days. Region information may currently be cached for up to 6 hours. These periods may be adjusted in the future for technical or operational reasons. According to the current technical design, stickers and comparable graphic elements from Flaticon / Freepik are not loaded as external Flaticon embeds on the user’s device, but are delivered via the MessageDrop sticker function and our systems. The technical data required for use is processed by MessageDrop. If Flaticon / Freepik source pages, license information, or external links are accessed in an individual case, Flaticon / Freepik may process data under its own responsibility. If the user has activated the provider Unsplash in accordance with Section 2.3, depending on the function, image files may be downloaded in addition to retrieving metadata (e.g., for avatar/background images). In this process, image files may be downloaded to the device and stored locally. In addition, technical proof of download may be transmitted to Unsplash. Further information about the providers is available on their respective websites, for example: - Open-Meteo: https://open-meteo.com/ - DeepL: https://www.deepl.com/ - OpenStreetMap / Nominatim: https://www.openstreetmap.org/ - OpenStreetMap license information: https://www.openstreetmap.org/copyright - OpenStreetMap Foundation Privacy Policy: https://osmfoundation.org/wiki/Privacy_Policy - Geofabrik download service: https://download.geofabrik.de/ - SkedGo / TripGo: https://developer.tripgo.com/ - SkedGo Privacy Policy: https://skedgo.com/privacy-policy/ - SkedGo Terms of Use: https://skedgo.com/home/terms-of-use/ - Unsplash: https://unsplash.com/ - Flaticon: https://www.flaticon.com/ - Flaticon Terms of Use: https://www.flaticon.com/legal - Freepik / Flaticon Privacy Policy: https://www.freepik.com/legal/privacy/ The legal basis is Art. 6(1)(b) GDPR (provision of the function requested by the user) and Art. 6(1)(f) GDPR (legitimate interest in user-friendly, functional provision). ### 3. Use with a User Account ### ### 3.1 Creating a User Account ### Creating a user account is voluntary and occurs solely by assigning a PIN. The server initially creates only a pseudonymous user ID. Cryptographic key pairs for encryption and signing are generated on the device. The public keys are stored in the user account on the server; private keys remain exclusively on the device. The following are stored on the server: - the pseudonymous user ID, - public signature and encryption keys, - a user status (e.g., enabled or disabled), - the date of the last login, as well as technically necessary status or metadata. All other user data is stored exclusively in encrypted form locally on the device. This may also include a user’s voluntarily stored personal DeepL API key for the translation function. The legal basis is Art. 6(1)(b) GDPR (performance of a contract or implementation of pre-contractual measures at the user’s request). ### 3.2 Login and Authentication ### For login, the PIN is used exclusively locally to decrypt the encrypted user data record on the device. The device then requests a one-time verification challenge from the server. This challenge is signed with the local private signature key. The server verifies the signature and, if the verification is successful, provides a technical access token for subsequent communication. The PIN and the decrypted user data record are not transmitted to the server. The legal basis is Art. 6(1)(b) GDPR (performance of the login and authentication process). ### 3.2.1 Security Reset (Key Regeneration) ### Users can generate new key pairs for security reasons (security reset). In this process, the public keys in the user account are updated; private keys remain stored locally. During the security reset, the chat history is deleted, but contacts are retained. Contacts who are online receive the new public keys immediately; other contacts receive them upon the next update. ### 3.3 Deletion and Inactivity ### User accounts that have not been logged into for a period of 90 days are removed from the backend without warning. Upon removal of the user account, all associated server-side data records are deleted, in particular: - the user ID, - the user status, - login and activity information, - other uniquely identifiable server-side references. The deletion is final unless a previously created backup of the user’s data exists. Regardless of this, the user may delete their user account independently via the app at any time. In this case, all server-side and local data records will be deleted immediately and permanently, subject to statutory retention or evidentiary obligations (e.g., in connection with DSA proceedings). The legal basis is Art. 6(1)(b) GDPR (provision, administration, and deletion of the user account) as well as Art. 6(1)(c) GDPR (compliance with legal obligations), to the extent that legal obligations require further processing. ### 3.4 Public Content, Comments, and SecretDrops ### Users may post public messages, public comments, and publicly discoverable SecretDrops. Public content must not contain any personal information, regardless of whether it pertains to the user or others. Such content may be moderated, hidden, or removed. SecretDrops are encrypted on the client side. The secret content is generally not readable by MessageDrop without the corresponding PIN. However, the metadata required for provision, discoverability, status, moderation, and DSA proceedings is processed, as well as content or information provided in the context of a report or after decryption by users. This content is processed for the following purposes: - Provision and display within the service, - Moderation and enforcement of usage rules, - Prevention of abuse and fraud, - Compliance with legal obligations, in particular under the DSA. To support moderation, content (including hashtags) may be analyzed automatically. If technically necessary, an external AI moderation service may be involved. This may involve the transmission of content data and technical metadata to the respective service provider. We use the results exclusively to support moderation and to fulfill legal obligations. Public messages, public comments, and publicly discoverable SecretDrops are generally deleted after 30 days unless a shorter validity period, prior consumption, or a legal or technical exception applies. There is no entitlement to permanent availability, archiving, or restoration. Public content may be rated (e.g., like/dislike). There is no entitlement to any particular reach, visibility, or rating outcome. The legal basis is Art. 6(1)(b) GDPR (provision and processing of public content, comments, and publicly discoverable SecretDrops) as well as Art. 6(1)(f) GDPR (legitimate interest in operation, security, and prevention of misuse) as well as Art. 6(1)(c) GDPR (compliance with legal obligations), to the extent that legal obligations apply. ### 3.5 Private Communication ### Private chat messages are transmitted using end-to-end encryption. Read private messages are generally deleted automatically after 7 days. There is no entitlement to availability, archiving, or restoration. The users involved are solely responsible for the content of private communications. There is no prior review of content or ongoing monitoring. However, procedural measures (e.g., blocking/removal) may result from legal obligations, to the extent necessary in individual cases. The legal basis is Art. 6(1)(b) GDPR (provision and operation of private communication) as well as—to the extent that procedural measures are necessary to fulfill legal obligations—Art. 6(1)(c) GDPR (compliance with legal obligations). ### 3.6 Local Data Storage on the Device ### MessageDrop follows a privacy-oriented approach in which the majority of data is primarily stored locally on the user’s device. This includes, in particular: - local user data, - settings and preferences, - optionally stored third-party access credentials for individual functions (e.g., a personal DeepL API key for translations), - contacts and links, - locally cached content, - cryptographic keys, - temporary working data. Depending on the platform, storage occurs primarily via the browser’s IndexedDB, local app storage, and cache mechanisms of the operating system or browser. Locally stored data is not automatically synchronized with other devices or a cloud. Control over locally stored data lies with the user. The user can delete this data at any time, in particular by using the corresponding functions within the app, deleting app or browser data, uninstalling the app or the installed web app, or resetting the browser or device. Without the user’s involvement, we have no access to locally stored data and no way to view, back up, or subsequently restore this locally stored data. If locally stored data is deleted by the user or due to technical circumstances, this may result in the loss of content, settings, or access. We cannot restore this data without a backup previously created by the user. The responsibility for backing up, preserving, and managing locally stored data lies exclusively with the user. ### 3.6.1 Backup and Restore Function (optional) ### To reduce the risk of data loss, MessageDrop provides an optional backup and restore function. As part of the backup function, the user selects a local storage location and a personal PIN. The backup is stored in encrypted form. The PIN used is known exclusively to the user and is neither stored by us nor recoverable by us. If the PIN is lost or forgotten, it is technically impossible to restore the backup. The data contained in the backup corresponds to the data assigned to the user and stored locally and on the server at the time the backup is created. When restoring a backup, any existing user account is permanently deleted both locally and on the server. All associated data is removed and then restored based on the backup. There is no merging of existing and restored data. As part of the restore process, the data contained in the backup is transferred back to the server and—where technically implemented—created or restored there. Discrepancies between the original state and the state after the restore are possible. Backups are tied to the key state at the time of creation. After a security reset, older backups may be considered obsolete and may not be restorable. The legal basis is Art. 6(1)(b) GDPR (provision and use of the backup/restore function at the user’s request). ### 3.7 Local Profile, Profile Sharing, and Contact Profiles ### The user can create a local profile (e.g., name and avatar) for their own user account. This profile is generally stored exclusively locally on the device. Within the context of the contact function, a user can actively request profile sharing with a contact. The contact must actively confirm the profile sharing (e.g., via a pop-up) before a transfer takes place. For technical delivery of the profile sharing function, including cases where one party is temporarily offline, the request data and the response status are stored temporarily on our server. If consent is granted, the shared profile name and avatar are stored there only in encrypted form for delivery to the requesting contact. These temporary records are deleted after successful delivery/processing by the requesting contact or upon expiry if delivery does not occur in time. The current period is 7 days. For technical or operational reasons, deletion may be delayed in individual cases, so shared profile information may exceptionally remain retrievable for longer. Once delivered, the profile name and avatar are transferred to the contact’s device and stored locally there. Note: After the transfer, there is no technical way to retrieve or delete the profile information already transferred from the contact’s device. The locally stored data can only be deleted by the receiving contact on their device. In addition, each user can independently set their own local profile entries for contacts (e.g., their own display name, their own avatar). This information is only visible locally. The legal basis is Art. 6(1)(b) GDPR (provision of the contact function) and—to the extent that profile sharing is based on voluntary, active consent—Art. 6(1)(a) GDPR (consent of the data subject to the processing of personal data concerning them). ### 3.8 System Messages ### MessageDrop provides users with system messages. System messages are internal communications generated exclusively by authorized administrative systems (in particular via the admin and moderation system) and transmitted to the user’s frontend via the MessageDrop backend. System messages serve in particular to: - provide information regarding proceedings under the Digital Services Act (DSA), - communicate decisions, procedural statuses, or measures, - provide information regarding technical or organizational processes (e.g., scheduled maintenance, security-related notices, or system-related restrictions). System messages are always active and cannot be disabled. In the context of system messages, we process in particular: - User ID, - content of the message, - times of creation, provision, and delivery of the message, - delivery and read status (to the extent technically implemented). Users can delete system messages in the frontend. Deletion affects only the display or local availability in the user’s frontend. Legally required or documentation-mandated records (e.g., in the context of DSA proceedings) may remain unaffected by this. The legal basis is Art. 6(1)(b) GDPR (provision of system messages in connection with the use of the service) and Art. 6(1)(c) GDPR (compliance with legal obligations), to the extent that system messages are required for this purpose (e.g., DSA). ### 3.9 Following Places and Push Notifications ### Users can follow places or stop following them. Where technically possible and supported by the device, users can receive push notifications when new public content is posted at a place they follow. For push notifications, technically necessary tokens/identifiers are processed depending on the platform so that messages can be delivered to the device (e.g., push tokens). These tokens are processed for delivery purposes and are not used by us for profiling or tracking purposes. Push notifications may be delayed, restricted, or not delivered for technical, system-related, or user-specific reasons; there is no entitlement to delivery. The legal basis is Art. 6(1)(b) GDPR (the “Follow” function) as well as Art. 6(1)(a) GDPR (consent of the data subject to the processing of personal data concerning them), provided that the use of push notifications is designed to be consent-based or requires system-level authorization on the device. ### 3.10 Usage Time Protection (Self-Restriction / Parental Mode) ### MessageDrop offers optional Usage Time Protection with the following basic functions: - “Off” mode (deactivated), - “Self” mode (self-restriction with daily limit and configurable self-extension), - “Parental” mode (daily limit and configurable extension via parent PIN). The following data is processed for this purpose in particular: - Usage Time Protection settings (mode, daily limit, time slots per weekday, extension duration, and allowed number of extensions), - Local daily status (date, usage seconds consumed, and number of self- and parent-initiated extensions already used), - Optionally, a parent PIN hash (no plaintext PIN). The parent PIN is exclusively hashed locally (cryptographic hash) and is not stored in plain text. For logged-in user accounts, settings and status data for Usage Time Protection can be transferred to the backend for synchronization. The legal basis is Art. 6(1)(b) GDPR (provision of the requested protection feature) and Art. 6(1)(f) GDPR (legitimate interest in youth protection-oriented and responsible use). ### 4. Digital Services Act (DSA) ### ### 4.1 DSA Proceedings ### To the extent that the legal requirements of the Digital Services Act (DSA) apply to MessageDrop, proceedings may be initiated in relation to public content, comments, and publicly discoverable SecretDrops, in particular through notices or appeals. Notices may be submitted via the reporting function within the service or through the DSA contact point listed in the legal notice. To facilitate prompt processing, a notice should be as specific as possible (e.g., link/ID of the content, brief explanation, and optional supporting evidence). In this context, we process in particular: - User ID (if available), - information about the person submitting the notice, to the extent voluntarily provided (e.g., email address), - information about the reported content, - timestamps relating to the proceedings (e.g., receipt of the notice, processing, decision, notification, and conclusion of the proceedings), - status of the proceedings, - decisions taken and reasons given, - information from internal complaints against moderation decisions (to the extent provided for by law). Additionally, the reporting person may voluntarily provide evidence as part of a DSA procedure, in particular: - file uploads (e.g., screenshots or documents), - external links as evidence. File uploads are stored on our servers. External links are stored in our database. This evidence is processed exclusively for the purpose of reviewing the reported facts and for documentation in accordance with legal obligations and is not made publicly available. As part of moderation decisions, we also process data to notify affected users (e.g., regarding the status of the proceedings, measures taken, key reasons for the decision, and, where applicable, the involvement of automated processes, to the extent legally permissible and technically feasible). Data regarding obviously abusive reports or complaints (e.g., serial reports without factual basis) may be processed for the purpose of preventing abuse. The legal basis is Art. 6(1)(c) GDPR (legal obligation) and Art. 6(1)(f) GDPR (legitimate interest in enforcing rights, preventing abuse, and retaining evidence). ### 4.2 Public Case Page ### A publicly accessible case page may be provided for DSA-related proceedings. This page contains only anonymized or non-personal information, specifically the status of the proceedings, the nature of the reported content, decisions made, and legal justifications in accordance with the DSA. No personal data is published. Publication is solely for the purpose of fulfilling legal transparency obligations. ### 4.3 Public DSA Statistics ### MessageDrop can provide publicly accessible, aggregated statistics showing the number of proceedings initiated, the nature of the decisions, and the ratio of notices to measures taken. The statistics do not contain any personal data and do not allow for any conclusions to be drawn about individual users. ### 4.4 Storage and Disclosure ### DSA-related moderation, decision, and procedural data are stored to the extent necessary to fulfill legal documentation, evidence, and accountability obligations. Unless administrative or judicial proceedings are pending, DSA-related procedural data (e.g., notices, decisions, and associated metadata) will be deleted no later than six months after the conclusion of the respective proceeding. Evidence (files and external links) voluntarily provided in the context of a DSA proceeding is stored only for as long as it is necessary for the conduct of the proceeding and for statutory verification and documentation obligations, and is also deleted no later than six months after the conclusion of the proceeding, unless further retention is required. If administrative or judicial proceedings are initiated in connection with a DSA proceeding, or if such proceedings are foreseeable, the relevant data may be stored for the duration of those proceedings and beyond within the legally permissible scope (so-called Legal Hold). In this case, deletion shall occur immediately once the reason for retention no longer applies. Disclosure to competent authorities, courts, or other authorized bodies shall take place exclusively within the legally required and permissible scope. The legal basis is Art. 6(1)(c) GDPR (fulfillment of legal documentation, evidence, transparency, and disclosure obligations) as well as Art. 6(1)(f) GDPR (legitimate interest in maintaining evidence and in the assertion, exercise, or defense of legal claims), to the extent that storage or disclosure is necessary beyond the immediate legal obligation. To the extent that, in individual cases within the scope of a DSA proceeding, special categories of personal data within the meaning of Art. 9 GDPR or personal data relating to criminal convictions and offenses within the meaning of Art. 10 GDPR are included, their processing shall take place exclusively to the extent that this is legally permissible and necessary for the conduct, documentation, or disclosure of the proceeding. ### 5. Retention Period ### Personal data is stored only for as long as necessary for the respective purpose or as required by law. This does not apply to DSA procedural data (including necessary evidence/supporting documents), which may be subject to statutory retention obligations or documentation-related requirements. In particular, the following principles apply: - Visitor/server logs: storage as necessary for security and operation (Art. 6(1)(f) GDPR (legitimate interest in security and operation)), - User account metadata (user ID, status, last login): until the user account is deleted, subject to legal obligations, - Usage Time Protection (settings/status, including parent PIN hash): until modified/deleted by the user or until the user account is deleted, - public content including publicly discoverable SecretDrops: deletion after 30 days unless a shorter validity period, prior consumption, or a legal or technical exception applies, - read private messages: deletion after 7 days, - temporary records for profile sharing with contacts: deletion after delivery/processing or, at the latest, upon expiry; the current period is 7 days, - locally stored data: deletion by the user or due to technical circumstances is possible. ### 6. Data Security ### We implement appropriate technical and organizational measures to protect personal data from loss, misuse, or unauthorized access. However, complete protection cannot be guaranteed. ### 7. Rights of Data Subjects ### You have the right to access (Art. 15 GDPR), rectification (Art. 16 GDPR), erasure (Art. 17 GDPR), restriction of processing (Art. 18 GDPR), data portability (Art. 20 GDPR), and objection (Art. 21 GDPR). Consent that has been given may be withdrawn at any time with future effect. To exercise your rights, you may contact the controller (see Section 1). In addition, you have the right to lodge a complaint with a data protection supervisory authority (Art. 77 GDPR). ### 8. Minimum Age ### The service is not intended for persons under the age of 16 (Art. 8 GDPR). If we become aware that the service is being used by persons under the age of 16, we reserve the right to deactivate or delete such user accounts. Persons who have reached the age of 16 but have not yet reached the age of 18 may use the service only with the consent of their parents or legal guardians. Legally binding declarations or obligations that go beyond the ordinary use of the service are generally only possible upon reaching the age of 18. ### 9. No Emergency Services ### The service is not a substitute for emergency services and does not provide access to such services. ### 10. Changes to the Privacy Policy ### We reserve the right to amend this Privacy Policy. Changes take effect upon publication of the updated version, unless a later date is specified. In the event of significant changes, we will provide appropriate notice within the service before they take effect, to the extent that this is legally and technically feasible. To the extent that consent is required for specific processing activities, renewed consent may be required in the event of significant changes.