Your privacy at Awescroll.
Awescroll is a publication, not a platform. There is no account, no advertising, no cookie and no tracking across sites. This page says what little is kept, by whom, for how long, what you are asked before anything is counted, and what you can ask for, in plain words.
Who is responsible
Awescroll is made and published by Denis Milanov, who is the controller of the data described here under the GDPR. For anything on this page, write to hello@awescroll.com.
Cookies and storage
The site sets no cookies and writes nothing to your browser on its own. The one thing it ever keeps there is your own answer to the one question it asks (below): yes or no, one word, kept so that you are not asked again, and changed or removed here whenever you like. The transitions between pages carry a one-word flag in the page address for the length of that page change and wipe it the moment the next page starts; nothing is stored for them. Whether the opening sequence on the cover plays is decided from what your browser already knows about how you arrived (a step back, a reload, or a link from one of our own pages); nothing is written for that either. The private statistics page the editor uses keeps its own access key for that tab; it exists only on that page, for the publisher, and is not part of reading Awescroll.
Reading
To know whether stories are worth making, the site counts how far they are read: a story was shown, started, reached a quarter, a half, three quarters, the end; the sources were looked at, and one was opened; a share button was pressed; the three questions at the end were answered, and how many were right; the next story was opened; an address was added to the list. Each count is an event name with the story, the page address and, for the questions, the number right out of three. Nothing is read from your device for it: no screen size, no browser name, no clock. It is sent once to this site's own address and written to Cloudflare Workers Analytics Engine, which keeps it for three months. No IP address, cookie, identifier or browser fingerprint is stored with it: the site assigns no visitor identifier and builds no profile across visits, so the counts say how many, never who. Nothing is sent until you say so. The first story you open asks, once, in one line at the foot of the screen, whether it may count how far you read. Yes sends the counts from then on, including the ones from the minutes before you answered, which the page holds in its memory until then; no, or no answer, sends nothing, ever, and the page forgets what it held when you leave it. If your browser sends a Do Not Track or Global Privacy Control signal, you are not asked and nothing is sent. Your answer is kept in this browser so that you are not asked again, and you can give it or change it here:
You have not answered in this browser, so nothing is sent. The first story you open asks once; you can also answer here.
One more count is made where a page request arrives, on the server, before the page reaches you: which page was asked for and, if your browser says so, the name of the site the link was on (instagram.com, x.com, a search engine; the name only, never the page you were reading there, and nothing when there was none). It is a plain count of requests, like any server's log, with no address, no browser detail and no identifier, kept in the same place for the same three months, so the publisher knows which channel readers come through. It reads nothing from your browser and stores nothing in it, which is why your answer above does not cover it; a Do Not Track or Global Privacy Control signal does stop it. Search engines and link previews are not counted.
The reading counts are made on the basis of your consent, given by answering yes, and only after it; withdrawing it is the No button above. The arrival count is made on the publisher's legitimate interest in knowing which channels bring readers, as a plain count of requests to the server that stores nothing on your device and reads nothing from it; to the extent it touches personal data at all, you may object by writing to hello@awescroll.com.
Cloudflare, the company that hosts this site, offers its own traffic measurement, Cloudflare Web Analytics, a script it can add to every page. It ran here until 13 September 2026. It no longer does: the site's security policy now blocks that script and the address it reports to, so it cannot run even if the setting is left on by mistake. Cloudflare keeps what it collected for that period in aggregated form for about six months, and it reaches the editor only as those aggregates.
The newsletter
If you enter an email address, the address, the time, the page you were on and the version of this notice are stored in Cloudflare's key-value store and used for one thing: to tell you when a new story is ready. The basis is your consent, given by entering the address for that stated purpose; you may withdraw it at any time. It is never shared or sold, and no one else is sent it. Today, nothing is mailed: the list is being gathered before the second story exists. When mailings begin, every one will carry a link that removes you at once, and the first mailing may ask you to confirm you want them. The address is kept until you ask to be removed or the list is closed. To be removed now, write to hello@awescroll.com from that address; it is deleted the same day. To slow down abuse, the site counts attempts from each connection address for one minute and then forgets it; that count is never stored with your address.
Sharing
SHARE opens your device's own share sheet or copies a link; the story record is drawn on your device and saved or shared as a file from there. Nothing about it is uploaded.
Hosting and where the data goes
The site is served by Cloudflare, Inc., which processes connection data (such as IP addresses) to deliver pages and protect against abuse, under its own privacy policy. Cloudflare is the only company that handles this site's data: it hosts the pages and keeps the newsletter list and the reading counts, processing that data for Awescroll under Cloudflare's customer terms; for the connection and security data of its own network it acts under its own privacy policy. Cloudflare's network also asks browsers to report failed connections to it (Network Error Logging, a policy the browser keeps for seven days); that is Cloudflare's own monitoring, contains no personal data by its account, and the publisher is asking for it to be switched off for this site. It is a US company operating a worldwide network; transfers outside the EU are covered by its standard contractual clauses and its certification under the EU-US Data Privacy Framework, as described in its policy. Awescroll's fonts, images, media and application code are all served from awescroll.com itself; the site's security policy allows scripts from nowhere else. No advertising and no cross-site behavioural tracking are used.
Your rights
You may ask what is held about you, ask for it to be corrected or deleted, ask for its use to be restricted while a question about it is settled, receive the newsletter address you gave in a plain copy to take elsewhere, object to its use, or withdraw the consent you gave for the newsletter, by writing to hello@awescroll.com. Reading counts hold nothing that identifies you, so there is nothing about you in them to find; the newsletter address is the one thing that is yours, and it is removed on request. If a reply does not satisfy you, you may complain to the Bulgarian Commission for Personal Data Protection (cpdp.bg), where the publisher is based, or to the data protection authority of the country you live in.
This page changes only when what is kept changes. Last change: 13 September 2026 (this version is recorded with each newsletter address).