most analytics installs ask for a plugin, a plan, and an afternoon of configuration. mine asks for one line. i'm om yaduvanshi, 18, an applied ai developer. i built cloudline, a cookieless analytics tool. day 33 now, eight days past launch, and the install page has taught me more than the dashboard has. ## the install itself one script tag. under 2 kb. you paste it in, with your site id, and it installs in under a minute. single-page apps work automatically. no dashboard to configure first. if you ever want it gone, you delete that one line. that is the whole uninstall. ## the same line, four frameworks next.js takes it in the root layout, with next/script and afterInteractive. wordpress takes it through the WPCode plugin, or straight into header.php before the closing head tag. webflow and framer take it as custom code in the head. same tag everywhere. the framework changes where it lives, not what it does. ## what breaks most often first, check the realtime view. if a visit lands there, the install works, and the problem is somewhere else in how you are reading the dashboard. if nothing lands, the usual suspects are short. a content security policy blocking the script or the connection. an ad blocker on your own browser, hiding your own visits from you. a localhost visit, which production refuses on purpose. a domain that does not match the site id. all four are on the install page. i put them there because i kept answering the same questions. ## button clicks, the same way a button gets tracked when you add a data attribute with a label, or call the track function with one. only the label you chose is stored. nothing about the person who pressed it. ## why the install stays this small a pageview stores page, referrer, screen size, time. nothing else. no cookies. no ip addresses. nothing stored on a visitor's device. there is nothing to configure because there is almost nothing being collected. **cloudline** is free while in early access. no card. https://trycloudline.space — om

29 days ago i started writing about a tool i was building. today you can install it. i'm om yaduvanshi, 18, an applied ai developer. i built cloudline, a cookieless analytics tool. this is day 30 of 90, and it's launch day. ## what ships today one script tag, under 2kb. no cookie banner, because there is nothing to consent to. a pageview stores four things: page, referrer, screen size, time. nothing else. top pages and traffic sources, with every ai chatbot grouped into one source. engaged time, scroll depth at 25, 50, 75 and 100 percent. button clicks per page. funnels with nothing to configure. live visitors on one screen. up to 50 sites in one dashboard. install takes under a minute. removing it takes one deleted line. ## what it never does no cookies. no ip addresses. nothing stored on a visitor's device. no user-agent storage, no fingerprinting. device type comes from screen width and nothing else. when cloudline can't collect something, the dashboard shows an error message instead of a made-up number. same rule as the demo badge and the labelled roadmap: if it isn't there, you see that it isn't there. ## what's not shipping revenue attribution is coming soon and stays coming soon. countries, operating systems and browsers, core web vitals, weekly email reports — all on the roadmap, none of them live. i'd rather ship a short honest list than a long invented one. ## 30 days later i wrote about this thing for 29 days before asking anyone to install it. the ad blockers block it, the troubleshooting page lists every way it can fail, and the demo wears its sample-data badge in public. that was the whole strategy. be honest about the missing parts and people stop worrying about the hidden ones. **cloudline** is free while in early access. no card. https://trycloudline.space — om

i want to know which button people click. i don't want to know who clicked it. most analytics tools treat those as the same question. they're not. i'm om yaduvanshi, 18, an applied ai developer. i build cloudline, a cookieless analytics tool. day 28 of 90, building in public. ## how click tracking usually works open any analytics tool's click feature. it's usually a session replay, or a heatmap of real cursors on your actual page. those need to follow one person around your site. that takes an identity: a cookie, a session id, something that says "this click and that scroll belong to the same visitor". the click count you see is built on top of that identity. ## how cloudline does it you put data-cloudline-track="signup" on a button. or you call Cloudline.track('click', {label}) from your own code. the label you chose gets stored. the page gets stored. the count goes up. nothing else. no cookies, no ip addresses, no user agents, no session ids. a click is a number attached to a page. no trail, no person. ## what i gave up i can't tell you if the same person clicked twice. i can't tie a click to the visitor who scrolled to 100% and then left. there is no heatmap of actual cursors, because there are no cursors to record. that's the trade, and i'd rather name it than hide it. ## why this is the shape i want the whole product works like this. a pageview stores four things: page, referrer, screen size, time. that's the entire row. clicks fit the same shape: label, page, count. funnels are built from these counts. pageviews and clicks in order, showing where people drop off. nothing in them knows who anyone is. ## the part that changed how i read this changed how i read other tools' privacy pages. "we don't track individuals" next to a feature called session replay. a replay needs a session. a session is an identity wearing a mask. i'm not naming anyone. but if a tool needs to recognise you to count you, the count is the smaller feature and the recognition is the bigger one. ## two days to launch day 30 of this plan was always launch day. it's two days away now. the click tracking you just read about is the kind of thing launching with it: small, named, and honest about what it doesn't do. day 28 of 90. still building. **cloudline** is free while in early access. no card. https://trycloudline.space — om

i run more than one website. every analytics tool i tried made me log in somewhere else for each one, or gave me one dashboard per property with no overview. i'm om yaduvanshi, 18, an applied ai developer. i build cloudline, a cookieless analytics tool. day 27 of 90, building in public. ## why one dashboard if you have one site, this feature is invisible. if you have five, it's the whole product. i keep a few projects alive. stores, side pages, landing pages for this campaign. checking them used to mean clicking between properties and losing the thread of what actually mattered. nobody checks analytics they have to hunt for. ## how it works cloudline lets you add up to 50 sites under one account. same login. one dashboard for every site you run. 50 is a ceiling, not a target. the point is that adding a new site is a one-line install, not a new decision. one script tag, data-site-id, done. deleting the line removes it. ## the part i dogfood my own sites run on it. that's how i notice what actually gets checked and what doesn't. real traffic finds your weak spots faster than sample data. (i wrote about labelled demo data last time. this is the other side of that.) ## the honest part the dashboard still doesn't show countries. or operating systems. or core web vitals. the roadmap lists them, they aren't shipped, and cloudline doesn't pretend otherwise. ## what i'd like to know if you run more than one site: do you actually check all of them? day 27 of 90. still building. **cloudline** is free while in early access. no card. https://trycloudline.space — om

your next hundred visitors might come from a chatbot. not from google. from a chat window where somebody asked a question and your page was the answer it picked. cloudline groups its traffic sources: search, social, newsletters, and one more row. "ai assistants." here is why it is grouped instead of listed per bot. every referrer you store is a little piece of somebody's browsing history that you now own. a pageview in cloudline stores exactly four things: page, referrer, screen size, time. nothing else, no user agents, no fingerprints. a per-bot breakdown would turn one useful number (how much of my traffic comes from ai) into a detail nobody needs and everybody stores. so the grouping is the default, and defaults are the product. "ai assistants" answers the question that changes decisions: a growing share of your visitors arrives pre-sold by something that quoted you. which exact bot did the quoting is trivia for most sites. i'm om yaduvanshi, 18, an applied ai developer building cloudline, a cookieless analytics tool. day 23 of 90, building in public. ## the part i like about grouped sources search tells you what people typed. social tells you who shared it. "ai assistants" tells you something new: your content is being read by machines on behalf of humans. the visitor skips your homepage and lands on the page that answered the question. docs or a specific feature page. that changes what "top pages" means. your most important page might be the one nobody browses to. ## the honest caveat grouping hides things some people genuinely want. if you are doing seo for ai search, per-bot numbers would be useful. i am not pretending one row fits everyone. it is the privacy-preserving default, and you can argue with defaults. some of you will, and that is fine. ## the question i don't have an answer to do visitors who arrive through a chatbot behave like search visitors, or like referrals from a friend who already explained the product? i don't have enough of them yet to say honestly. if you run a site with real ai-referred traffic, i would love to hear what yours do. genuinely asking. day 23 of 90. still building. **cloudline** is free while in early access. no card. https://trycloudline.space — om

most cookie policies are confessions written by lawyers. mine is a confession written by me. i’m om yaduvanshi, 18, an applied ai developer building **cloudline** , a cookieless analytics tool. day 22 of 90, building in public. ## the policy a cookieless product keeps anyway cloudline sets no cookies. stores no ip addresses. nothing gets saved on your visitors’ devices. a pageview stores exactly four things: page, referrer, screen size, time. so why does the site have a cookie policy page at all? because not having one looks like you forgot, and looking like you forgot is worse than overexplaining. ## what the policy actually says the short version: there are no cookies to declare, so it says what’s stored instead. four fields. pages stored as path and query only, no fragments, no domain. no user agents. no fingerprinting. there’s also a “what we’ll never do” list on the features page. it lives on the site, and it means more there than quoted in a blog post. ## why write it at all conventional wisdom says privacy pages exist to satisfy regulators. the honest alternative: for a small tool, the privacy page is the sales page. nobody trusts a one-person analytics product on vibes. they trust it because you wrote down exactly what you collect, in plain words, and there’s nothing surprising in the list. the page costs nothing to maintain. every time someone asks “but what do you actually store?” i send the link instead of typing the answer. ## the caveat none of this is legal advice. it’s only about my own product: cloudline itself sets no cookies and needs no consent banner for its analytics. i’m not telling you what the law requires anywhere. i write code, not disclaimers. what i will say: if your tool collects almost nothing, write the almost-nothing down. short and exact. say it plainly and move on. day 22 of 90. still building. free while in early access. no card. https://trycloudline.space — om

your dashboard's biggest traffic source is probably called direct. which is a polite way of saying nobody knows where it came from. i'm om yaduvanshi, 18, an applied ai developer building **cloudline** , a cookieless analytics tool. day 20 of 90, building in public. ## what "direct" actually is people hear "direct" and picture someone typing their url. a small slice is that. most of it is traffic the referrer system never identified. messaging apps that strip referrers. social apps opening links in in-app browsers. newsletters with no tracking tags. ai assistants that send people your way and never tell you. your biggest traffic source is a shrug with a name. ## the problem i ran into when i built cloudline's traffic-sources view, direct kept winning. top bucket on my own sites. and "direct" is analytics for "we don't know". a category that big and that vague looks like an answer. it's the absence of one. the tempting fix was guessing. split direct into confident-looking slices. a lot of tools do exactly this. i decided against it, because a wrong confident number costs more than an honest vague one. ## what i do instead cloudline groups the sources it can actually see. search, social, newsletters, ai assistants that pass a referrer. a pageview stores four things: page, referrer, screen size, time. no cookies, no IPs, no user agents. grouping happens on what the visit carried with it, not on who made it. the assistants sending you traffic deserve their own bucket now. people discover sites inside chatbots every day. if your analytics files all of that under "direct", you're blind to a whole discovery channel. when the referrer is there, it gets grouped. when it isn't, it stays in direct, labelled as it is. ## the honest limit anything that strips the referrer completely is still direct. no analytics tool can attribute what was never sent. cloudline doesn't pretend otherwise. that's the deal with the whole product. four data points in, honest buckets out. free while in early access. no card. https://trycloudline.space — om

bounce rate punished every reader who landed on your page, read the whole thing, and left happy. it calls your best pages your worst. i'm om yaduvanshi, 18, an applied ai developer building **cloudline** , a cookieless analytics tool. day 19 of 90, building in public. ## the metric that lies bounce rate counts a session as a bounce when it has one pageview. no second page. that's it. someone who read your entire post and closed the tab counts exactly the same as someone who landed, hated it, and left in two seconds. docs pages, blog posts, landing pages, any page that answers a question. the pages that did their job get the worst scores. i spent years optimizing a number that punished good pages. never again. ## what i measure instead engaged time, paired with scroll depth. 25, 50, 75, 100 percent, per page. a page with three minutes of engaged time and 80 percent scroll depth is a page that worked. a page with ten seconds and a 90 percent bounce rate could be either. that's the number i check first in the morning now, not the one i used to check. ## the part i stay honest about cloudline stores no IPs, sets no cookies, doesn't read user agents. a pageview is page, referrer, screen size, time. so there's no session stitching, no "this person came back thursday". engaged time is page-level, and same-visitor-twice counts twice. the trade is written down, not hidden. and revenue attribution is on the roadmap, not in the dashboard. said plainly because it matters. free while in early access. no card. https://trycloudline.space — om

A rare sight over central Alberta last week captured public attention as an autonomous solar-powered airship, measuring approximately 20 meters in length, was observed hovering near Rocky Mountain House. The airship, developed by Cloudline, a South African aerospace company, and operated by Canadian firm 3 Points in Space Media, conducted flight tests at the Rocky Mountain House Airport to evaluate its potential for inspecting pipeline corridors. The technology represents a modern revival of airship applications, which historically declined after the Hindenburg disaster in the 1930s. Sean Adams, CEO of 3 Points in Space Media, described the airship as 'essentially the same as a helium party balloon' but noted its advanced autonomous control systems. The airship's 40-kilogram payload capacity allows it to carry heavier sensors than conventional drones, enabling longer-distance surveys of pipelines, power lines, and infrastructure. TC Energy, a major energy company, participated in the trials, highlighting the potential for gathering multiple data types in a single flight. The airship's quiet operation and ability to function in remote areas were emphasized as key advantages over traditional aircraft. Local residents expressed surprise at the sight, with Rocky Mountain House Mayor Shane Boniface noting it was 'the first time he'd seen such a thing in his 65 years.' The project aims to enhance the airship's resilience for cold-weather operations, with upcoming tests planned in Northern Ontario. This initiative bridges historical airship technology with modern applications, celebrating the legacy of early airships like the Graf Zeppelin while advancing new surveying techniques.

Orbiting low at eighteen meters before spiraling toward the two-kilometer cloudline, Earthia One traces translucent avenues as the city broadcast rolls through 'No Search in the Mirror' into 'Feud Fever'. Paper Whales is an interconnected city of creative resonance where you drif

i'm om yaduvanshi, 18. i build ai agents, and my second project is cloudline — website analytics without cookies. the problem: i put GA4 on a side project, added the cookie banner the lawyers want, and watched a chunk of my visitors click “decline” and disappear from my stats forever. you're not measuring traffic. you're measuring consent. so i built the alternative: one script tag under 2kb, pasted from your dashboard. no cookies, no ip storage, no banner needed for the analytics itself. a pageview stores exactly four things: page, referrer, screen size, time. that's the whole list. what you get: top pages, traffic sources (search, social, newsletters, even ai assistants), scroll depth, button clicks, funnels, live visitor count. up to 50 sites in one dashboard. why this matters for you: if you've ever stared at a GA4 dashboard that felt built for a fortune 500 company, or delayed launching because the cookie banner copy wasn't ready — this is the tool that skips all of that. it's free while in early access, no card: trycloudline.space i'm posting about building this in public for the next 90 days. next up: how scroll depth tracking works without storing anything personal.