Privacy Policy

Last updated: August 2026

This Privacy Policy explains how Just a Side Project (the "Blog," "we," "us") handles information when you visit justasideproject.blogspot.com.

1. Information We Don't Collect Directly

We don't operate user accounts, and we don't ask visitors to submit personal information to read the Blog. Any information referenced below is collected automatically by the platform and services we use, not by us directly.

2. Cookies and Third-Party Services

This Blog is hosted on Google's Blogger platform and may display advertising through Google AdSense. As part of that, Google and its partners may use cookies (including the DoubleClick DART cookie) to serve ads based on your prior visits to this site and other sites on the internet.

Google's use of advertising cookies enables it and its partners to serve ads based on your visit to this site and/or other sites. You can opt out of personalized advertising by visiting Google Ads Settings.

We may also use Google Analytics or similar tools to understand aggregate visitor behavior (e.g., which pages are popular). This data is anonymized/aggregated and is not used to personally identify visitors.

3. Third-Party Privacy Policies

This Privacy Policy does not apply to other advertisers or websites linked from this Blog. We encourage you to review the privacy policies of any third-party ad servers, including Google's own policy at policies.google.com/privacy.

4. Children's Privacy

This Blog is not directed at children under 13, and we do not knowingly collect personal information from children under 13.

5. Your Choices

Most browsers let you refuse or delete cookies. Disabling cookies may affect how ads are displayed but will not prevent you from reading the Blog's content.

6. Changes to This Policy

We may update this policy from time to time. Changes will be posted on this page with an updated "Last updated" date.

7. Contact

Questions about this policy can be sent via the Contact page.

Comments

Post a Comment

Popular posts from this blog

I Tried to Build a Free AI Shorts Channel. Here's Why I Pivoted to Writing Instead.

I wanted one thing: a fully automated, zero-cost pipeline that could turn an idea into a YouTube Short, start to finish, using nothing but free tools and an AI coding assistant. No stock footage subscriptions, no editing software, no manual screen recording. Just a script in, a video out. I got closer than I expected. Then I hit a wall that had nothing to do with code. What actually got built Over one long session, the pipeline came together piece by piece: Text-to-speech via Google Cloud's free tier (WaveNet/Neural2 voices, a few million free characters a month — far more than a couple of Shorts a week would ever use) Visuals generated entirely in code (Python + Pillow): chat-bubble mockups, file-browser mockups, "results" grids, all procedurally drawn, no stock assets Assembly via ffmpeg, stitching narration, captions, and generated slides into a finished vertical video One orchestration script tying it all together, so a new video was just: drop in a scr...
Read more

I Compared the Free Tiers of Google Flow, Kling AI, and Hailuo So You Don't Have To

In my last post , I mentioned pivoting away from AI-generated video after digging into the free tiers of the big three tools. Here's the actual digging — what each one gives you for free, and where the fine print gets in the way. I'm not affiliated with any of these tools. I just wanted a straight answer to "can I use this for a monetized channel without paying," and it took longer to find than it should have. The short version Tool Free credits Renewal Max clip length (free) Watermark Commercial use on free tier Google Flow (Veo 3.1) ~50 Daily 8 seconds "Made with Veo" visible Unclear — see below Kling AI ~66 Daily ~5 seconds per generation Visible Explicitly excluded Hailuo / MiniMax 200 One-time (new account bonus) ~6 seconds (768p) Visible Explicitly excluded Google Flow (Veo 3.1) Flow bundles Veo 3.1 (video), an image model, and a music model into one workspace. The free allotment is roughly 50 credits a day, n...
Read more

How I Wired Up Fully-Automated Cross-Posting Between Blogger and dev.to (With Working Code)

The last two posts on this blog went out through a pipeline I built specifically so I wouldn't have to manually copy-paste content between platforms. Here's the actual setup, in case you're trying to do the same thing. The goal One command, two platforms: publish to Blogger (where this blog actually lives) and have it show up on dev.to at the same time, without dev.to's copy counting against the original for search ranking purposes. Piece 1: Blogger, via its own API Blogger still has a working API (v3), authenticated through standard OAuth — no service-account keys needed, which matters if your Google Cloud project has an org policy blocking those (mine did). A one-time browser login gets you a refresh token; after that, a script can call posts().insert() or posts().update() and posts().publish() without touching a browser again. Piece 2: dev.to, via its API dev.to exposes a simple REST API gated by a personal API key (generate one under Settings → Extension...
Read more