Privacy

Last updated: 18 September 2026. This notice describes Stacks at stacks.dryyyve.com.

Controller and hosting

Charles Walczynski, Breidenbacherstraße 25, 55116 Mainz, Germany; stacks@dryyyve.com.

ALL-INKL.COM – Neue Medien Münnich, Hauptstraße 68, 02742 Friedersdorf, Germany hosts this app. Delivering requests requires your IP address, requested URL, time and technical connection information. Hosting and proportionate security measures support operation of this app (Article 6(1)(f) GDPR). This notice does not assert a provider log-retention period.

Your library stays in your browser

Books, shelves, locations, tags, notes, reading status, Read next and appearance settings are stored in IndexedDB (stacks-library) on this browser and origin. Stacks has no account or cloud sync. These library records are not sent to our server. Clearing website data or browser eviction may remove them. Export a JSON backup in Settings to keep a separate copy or transfer the library to a different device or address. Importing a backup requires your choice and confirmation. CSV export is also available. The library reset in Settings deletes books, personal shelves, notes, loans and the Read next list after two confirmations. Appearance and language preferences are kept. Downloaded backups remain separate files.

The app-local language preference is stored as stacks-language. Layout and read-only example-library visibility preferences use stacks-library-layout and stacks-example-library-visible. They remain in this browser and are separate from your library; the example library is read-only and is not merged into or synced with your books.

With the optional own-AI import, you photograph books and use an external AI service of your choice. Stacks does not receive the photos or contact an AI service. The prompt is copied locally, and the returned JSON is read and reviewed in your browser. Opening the preview sends ISBNs to Open Library to look up missing covers and loads supplied supported cover links. Manually supplied book links use the existing book-link lookup. Only selected books are added to your existing library; cover requests follow the rules below. Your chosen AI service handles the photos and research under its own terms and privacy policy.

Photo workshop

Photo workshop projects contain shelf photos, inventory drafts, review answers and progress history. On the public site these are stored only in a separate browser database (stacks-photo-workshop). The optional local workshop service stores saved projects on your own computer, where your active Codex task can read and update them. It does not contact an AI API or keep an agent running. Photos and projects are not uploaded to the public Stacks server. Delete project removes the selected local project; exported files and copies on other addresses remain separate. Library reset does not delete workshop projects. New uploads preserve the original photo bytes and any embedded metadata without resizing. A project export includes its photos; a library export contains only accepted book records without the photos.

Book links and metadata

When you submit a supported book link, the Stacks server receives that link and requests the public book page. It may consult Bookchor using the matching ISBN to fill missing public book details. Requests use a limited host list and do not forward your browser cookies, passwords or other login information. The provider receives our server connection and the requested public page. No login or CAPTCHA is bypassed.

Successful public metadata responses may be cached privately on the server for up to 15 minutes, with a maximum of 100 entries. The cache is separate from your local library. It stores no user account, note or location. We do not add application logs of request bodies or submitted links.

ISBN/title search and enrichment contact Open Library directly from your browser, using the requested ISBN, title or related public catalog identifiers. Open Library receives your connection information and query. Books are saved to the local library only after your review.

Recommendations and covers

Suggestions from your own library are calculated locally. External suggestions load only when you select Find recommendations. They send selected public author/genre terms to Open Library, not private notes, tags, locations or your full collection. Source links open Open Library; Find on Amazon opens a title/author search on Amazon. There are no affiliate parameters or claims about price or availability. Those providers have their own privacy policies.

Displayed Open Library covers may load directly from covers.openlibrary.org. Covers from the other supported hosts are fetched through the restricted Stacks cover endpoint. Providers receive the relevant image request and connection information; Stacks does not share your library. An optional local cover cache holds at most 200 images, each up to 2 MB. The JSON backup contains source URLs, not a separate image library.

Offline storage and choices

A service worker caches the app, local fonts and legal pages for offline use after a successful first visit. Updates can be applied in Settings. Library storage and the optional cover cache are separate from this app cache. Browser data generally stays until you remove it or your browser clears it; we cannot recover a lost local library. Storage needed for the functions you request is used under Section 25(2) TDDDG. Where requested processing involves personal data, Article 6(1)(b) GDPR covers providing those functions; optional preferences and maintaining this prototype rely on Article 6(1)(f).

Fonts and app code are hosted locally. Stacks contains no advertising or analytics trackers. External requests described above occur for the functions you use. We send no referrer when loading external resources.

We manage email correspondence with Google Workspace, provided by Google Cloud EMEA Limited, 70 Sir John Rogerson’s Quay, Dublin 2, Ireland, under the Google Cloud Data Processing Addendum. The service processes email addresses, message content, attachments and delivery metadata to receive and answer your request. ALL-INKL also processes messages where existing mailboxes or forwarding routes are involved during the transition. Processing outside the EU/EEA may occur under an applicable adequacy decision or contractual safeguards, including EU standard contractual clauses. This does not transfer your locally stored app data to Google.

Contact and your rights

If you email Charles, your address and message are used to respond, on the basis of Article 6(1)(f) GDPR or Article 6(1)(b) for a contractual request. Correspondence is kept for its purpose and applicable retention obligations. You may request access, correction, deletion, restriction or portability where applicable, and object to processing based on legitimate interests. You can complain to the data protection authority of Rhineland-Palatinate or another competent authority. Your locally held library can be exported or removed using your browser and the app's existing controls.

Passive daily counters

We count only existing server GET deliveries per Europe/Berlin day, including bots, reloads and cache requests. No IP addresses, browser identifiers, referrers, campaigns, IDs or content are stored; offline and local browser activity is not counted. Daily totals older than 90 calendar days are removed on the next access to the counter database and can remain longer while it is inactive. Private snapshots are created only when the protected dashboard is read; snapshots older than 7 calendar days are removed during a successful backup. Existing snapshots can remain longer during inactivity or if a backup fails. The legal basis is Article 6(1)(f) GDPR for reliable product operation. There is no browser tracking, cookie, consent interface or third-party analytics service.