DATA USE
Dramanota keeps its launch data model deliberately small. This page describes what the current shipped product actually stores and sends.
Runtime-based notice · updated 24 Sep 2026My Shelf, viewing state, episode progress, your chosen platform, the identifier for your latest explicit decision on a saved drama when available, and any optional structured outcome feedback are stored in this browser’s local storage. Your interface language uses a first-party preference cookie. A random anonymous session ID lives in session storage for the current browser session.
Dramanota records first-party product events such as search, identity confirmation, decision-card views, explicit next-step choices that you submit, watch clicks, shelf changes, resume clicks, and optional structured outcome feedback that you explicitly submit. Events may include a drama or listing ID, the random session ID, locale, counts, booleans, and — when you explicitly submit an outcome — the structured outcome choices shown in the product. If My Shelf carries the identifier for a recent explicit decision on the same drama, the server verifies that it belongs to that drama and links the outcome to the verified decision. If that decision record is no longer retained, the outcome remains unlinked rather than being guessed. This outcome flow does not collect free-text reviews. Raw search text is not included in analytics event metadata.
A watch or resume action opens a verified legal destination when one is available. Dramanota records the click, but a click is not treated as your explicit next-step decision or as proof that you watched, paid, or completed anything. The destination platform’s own privacy terms apply after you leave Dramanota.
You can clear My Shelf from the Shelf page. This removes the current and legacy Dramanota shelf records from this browser, including locally stored decision identifiers and outcome feedback. Closing the browser session ends the current session-storage identifier. Browser settings can also clear Dramanota’s language preference cookie.
Behavior-event rows older than 30 days are automatically pruned when the Dramanota server starts and by a daily maintenance sweep. This applies to first-party analytics (including submitted outcome events), clickout, and decision-event rows; source evidence, offer snapshots, platform records, and correction history are separate product-provenance data.