Privacy

Scope and controller

This notice describes dryyyve. Other dryyyve apps have their own privacy pages. Last updated: 13 September 2026.

Charles Walczynski
Breidenbacherstraße 25
55116 Mainz, Germany
Email: charles@dryyyve.com

This portfolio stores the appearance and language preferences described below and loads the like counts. The other sections document the existing dryyyve services, including the previous device interface, accounts and earlier feedback forms.

Hosting and requests

This website is hosted by ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany. Delivering the site involves processing your IP address, request time, requested URL and technical browser/request information. A data processing agreement is in place with the hosting provider. In this hosting account, website access logs and access statistics are disabled. Technical request data still have to be processed to deliver the site and maintain its security (Article 6(1)(f) GDPR). This setting does not rule out separate operational or security processing by the hosting provider.

Passive usage counts

We count requests for this site’s start page directly while delivering it, as daily totals only. Repeated requests, bots and cache downloads may be included; offline use is not counted. These counters store no IP addresses, browser characteristics, cookies, visitor identifiers, referrers, campaign parameters or app content, and cause no additional browser requests. Their purpose is to understand and improve operation of the dryyyve services (Article 6(1)(f) GDPR). Daily totals are retained for 90 days and older rows are removed on the next counter request. Private copies are created when the owner opens the dashboard; after a successful daily copy, copies older than seven days are removed. Failed backups preserve existing copies until recovery. The copies are on the same hosting server. Only the owner can read the aggregated overview through a protected connection.

Data used by this app

This studio stores your chosen appearance under dryyyve-studio-theme and your chosen language under dryyyve-studio-language in this browser. Without a saved choice, it uses your browser language (German or English; other languages fall back to English). The start page requests shared like counts when it loads; these legal pages make no like or account requests. The linked apps have their own privacy pages explaining their storage and features.

The retained device interface stores appearance under dryyyve-theme, sound under dryyyve-sound and language under dryyyve-language. These preferences remain separate from the portfolio. Your existing account settings remain available here:

Open account settings

DRYYYVE account

The account service at accounts.dryyyve.com stores your verified email address, chosen username, a random account ID, password hash, creation time and security version on our ALL-INKL server. Your password is never shared with an app. Verification and recovery emails are sent only when needed for account access. Creating an account does not subscribe you to marketing or a newsletter.

The device on dryyyve.com checks your session with accounts.dryyyve.com when the page opens and when you return to it, so it can greet you and show your account settings. Registration, login, username and password changes are sent directly to that service. Your password and account tokens are not stored in browser local storage. A necessary, host-only, HttpOnly session cookie on accounts.dryyyve.com supports sign-in for up to 30 days. Security counters use secret-keyed identifiers for the account or connection IP; raw IP addresses are not stored in the account database. Verification and reset links expire after 30 minutes; their tokens are stored hashed. Expired database tokens and counters are cleaned up on subsequent requests. Server session files are subject to expiry and hosting session cleanup.

When you explicitly sign in to Words or Opus, the selected app receives your stable DRYYYVE ID and verified email address over its server connection. Opus uses the ID to link its own profile and does not retain the email address in its app database. Passwords are never shared. Hashed app-specific session tokens last up to 30 days; authorization codes expire after one minute. Account access and the requested app connection use Article 6(1)(b) GDPR; proportionate abuse prevention uses Article 6(1)(f). Necessary session storage is covered by Section 25(2) TDDDG.

You can export or delete your central identity in its account settings. First export or delete any Opus profile in Opus: deleting the central identity removes its only sign-in route, but does not erase the Opus profile. In Words, manage or delete the separate profile there; establish a separate Words password first if you want to keep accessing it after central deletion. Central export contains identity data, not the content stored by these apps. Existing guest data are never uploaded automatically. If central deletion has already happened, contact Charles for help with the app profile; ownership must be verified before access or deletion. A saved central account export can help identify the profile but does not by itself prove ownership.

Central deletion invalidates connected sessions when the app next verifies them (Words: on the next protected request once its 60-second verification cache has expired; Opus: on each protected request). Daily central database copies are normally kept for seven days and cleaned up after a successful snapshot on a subsequent request. Failed snapshots preserve existing recovery copies until the failure is resolved. These copies may temporarily contain deleted account records. They are private and on the same host, so they do not protect against loss of that host. Provider backups have separate retention. Contact Charles for account corrections or assistance.

The private owner dashboard shows existing central accounts and new registrations. For account administration, corrections and support, only the operator can view each existing account’s verified email address, chosen username and registration time (Article 6(1)(b) GDPR for requested account services and Article 6(1)(f) for proportionate account administration). The list is read directly from the account database, is not retained as a separate list and is not linked with page counts or usage histories. Deleting an account removes it from this view and the recalculated totals; the account backup periods described above still apply.

Prototype welcome

Closing the welcome panel stores dryyyve-prototype-welcome-v1 in this browser so it is not shown on every visit. This preference is not uploaded or shared with other apps.

Changelog

Opening the changelog stores a compact identifier of its current content under dryyyve-changelog-seen-v1 in this browser. The indicator returns when new changes are added, including additions to an existing daily entry. This preference is not uploaded and is independent of your account.

Product feedback

Feedback is now sent by email to charles@dryyyve.com. Clicking this link opens your email application; this website does not send a message for you. See Contact and your rights below for email handling.

Previously submitted form feedback

The previous form and its submission endpoint are retired; new submissions are no longer accepted. Previously submitted feedback contains your selected app, message, submission time and, only if you provided it, your email address on our hosting server. This is used to understand suggestions, improve the prototypes and optionally reply. It does not subscribe you to a newsletter, create an account or publish your message. Please do not include passwords, sensitive information or other people’s private data.

The intended retention period for old form feedback is 90 days. The former implementation removed expired entries and 15-minute abuse counters only on a subsequent valid form submission. The retired endpoint no longer opens this database, so it cannot trigger deletion. A separate operator cleanup is being prepared; regular execution and removal of any old entries have not yet been verified. There is no public inbox or message-reading API.

For abuse prevention, the server briefly processes the connection IP address to compute a secret-keyed marker that changes every 15 minutes. The raw IP address is not stored in the feedback database, and the marker is not attached to your message. Previously collected request counters expired at the end of their 15-minute window; any remaining counters need the separate operator cleanup described above. These markers are pseudonymous, not anonymous. Feedback handling and proportionate abuse prevention serve our legitimate interest in maintaining and improving these independent apps (Article 6(1)(f) GDPR). You can contact Charles about access, correction, deletion or an objection using the address above. Hosting-provider backups, if present, are separate from this application cleanup.

Optional Rainwave radio

The optional radio connects directly to relay.rainwave.cc only after you open the radio panel, read the provider notice and press “Connect to Rainwave”. Opening this website, waking the device or opening the radio panel does not preload audio or contact the radio provider. No persistent radio permission or listening history is stored by dryyyve.

While connected, Rainwave receives your IP address and technical request details. Our site sends no referring-page address. Existing provider cookies or credentials may be included according to browser settings. Provider processing locations and retention periods have not been verified; stopping playback does not delete provider records. The connection is optional and is initiated only for the playback you request. We do not claim a complete provider or international-transfer assessment.

Switching the radio off, switching the device to standby or leaving the page ends the stream connection. Muting only silences playback. After stopping, a new connection requires the connection button again. Audio comes directly from Rainwave; dryyyve does not proxy or store it.

App likes

The portfolio start page requests shared app like counts when it loads. When you first like an app, we set the random dryyyve-likes cookie to remember your choices and let you undo a like. It is restricted to this website, inaccessible to JavaScript, and expires after 365 days without renewal. On our hosting server, we store a hash of that random identifier, your selected apps, its expiry and short request-limit counters. We do not store your IP address or browser details in the likes database. This association is used only to provide your requested like function; it is not used for advertising or tracking across websites.

You can remove an individual like by pressing its heart again. Expired device associations are removed on a subsequent request; anonymous totals remain. Clearing cookies removes this browser's ability to undo its earlier likes. Counts are informal feedback and cannot guarantee one vote per person.

Browser storage and your choices

Appearance and sound preferences stay in this browser and are not uploaded to a dryyyve account. Likes use the separate server storage described above. Persistent browser storage remains until you reset it, clear the site's browser data or the browser removes it. Temporary sessionStorage ends with the browsing session. You can remove site data in your browser settings; this also removes saved progress. HTTP and HTTPS, different devices and different subdomains have separate storage.

Storage supporting the function you request is used for that function; the applicable exception for strictly necessary device storage is Section 25(2) TDDDG. Where stored information is personal data, processing to provide the requested function is based on Article 6(1)(b) GDPR; optional appearance preferences support convenient operation under Article 6(1)(f). No analytics or advertising storage is used.

External resources and links

Fonts, scripts, icons and game resources are served from this website. No analytics, advertising or external font/CDN requests are initiated by this version. Following an external link or using your device's sharing service opens a service with its own privacy policy.

The support link opens Buy Me a Coffee only when you follow it. There is no embedded payment widget. Details: Buy Me a Coffee privacy policy.

Contact and your rights

If you email me, I process your contact details and message to respond (Article 6(1)(f) GDPR, or Article 6(1)(b) for a contractual request). Messages are retained for the correspondence and any applicable legal retention obligations. Depending on the processing, you may request access, correction, erasure, restriction or portability, and object to processing based on legitimate interests. Contact the email above. You can also complain to the data protection authority of Rhineland-Palatinate or another competent authority.

App privacy notices

• Opus
• Mixtape
• Stacks
• 37
• Brew
• words
• Murmel
• Spacebar
• HExplore
• Lightweight

naext is not publicly available yet; its local notice describes its different storage and AI features.