Privacy Policy

Last updated: August 2026

This Privacy Policy explains how Broke It With AI ("we", "this site") collects, uses, and shares information when you visit.

Information We Collect

We use Google Analytics and Google AdSense, which automatically collect certain information such as your IP address, browser type, device type, pages visited, referring site, and time spent on the site, typically through cookies and similar technologies. We do not otherwise collect personal information unless you voluntarily provide it (for example, by emailing us).

Cookies and Advertising

Third-party vendors, including Google, use cookies to serve ads based on your prior visits to this and other websites. Google's use of advertising cookies enables it and its partners to serve ads based on your visits to this site and/or other sites on the Internet. You can learn more about how Google uses information from sites that use its services at policies.google.com/technologies/partner-sites, and you may opt out of personalized advertising by visiting Google Ads Settings or optout.aboutads.info.

Your Privacy Rights (California / CCPA)

If you are a California resident, the California Consumer Privacy Act (CCPA) gives you the right to know what personal information is collected about you, to request deletion of that information, and to opt out of the "sale" or "sharing" of personal information (which, under CCPA's broad definition, can include certain advertising cookie activity). We do not sell personal information in the traditional sense. To exercise these rights or ask questions, contact us at the email below. You can also manage ad-related data sharing directly through Google's Ads Settings.

EU/EEA and UK Visitors (GDPR)

If you are visiting from the European Union, European Economic Area, or United Kingdom, Google requires us to inform you that this site uses Google services (Analytics, AdSense) that collect, share, and use data as described in Google's own policies, and to obtain consent where required by law. You can review and manage Google's data practices at policies.google.com/technologies/partner-sites.

Children's Privacy (COPPA)

This site is not directed at children under 13, and we do not knowingly collect personal information from children under 13. We do not use interest-based advertising or remarketing to target users known to be under 13.

Your Rights and Choices

You can ask us what information (if any) we hold about you, request correction or deletion of it, or ask questions about this policy, by emailing us at the address below. You can also disable cookies generally through your browser settings, though some site features may not work as intended if you do.

Third-Party Links

This site links to official government sources (.gov domains) and, occasionally, other resources. We are not responsible for the privacy practices of external sites, and we encourage you to review their privacy policies separately.

Changes to This Policy

We may update this Privacy Policy from time to time. The "Last updated" date at the top reflects the most recent revision.

Contact

Questions about this policy, or requests regarding your personal information, can be sent to asadaleg@gmail.com.

Comments

Post a Comment

Popular posts from this blog

I thought my pipeline retried 6 times. It was making up to 48 billed calls.

Image
My publishing pipeline had a retry limit. MAX_TOPIC_ATTEMPTS = 6 . If a draft failed validation — too short, dead link, too similar to an existing post — it would throw the topic away and try a different one, up to six times, then give up. Six attempts. That was the mental model. Six is a small number, so I never thought about it again. That last part is the actual mistake. I set the constant myself, I picked the value deliberately, and having picked it I stopped treating it as a question. A number you chose feels known in a way a number you inherited does not — which is backwards, because the one you chose is the one nobody else has checked. What made me look was a day where the schedule ran and nothing appeared on the blog. No post, no error I'd been alerted about, just an empty run. I went into the logs expecting a crash and found the opposite: the pipeline had worked perfectly, generated draft after draft, rejected every one of them on validation, exhausted its attempts, and...
Read more

I let AI run two blogs for a month. Google indexed 1 post out of 81.

Image
I built two fully automated blog pipelines. Pick a topic, research it, write the body, generate the images, publish — no human in the loop. One was WordPress on its own domain, the other was Blogspot. WordPress ran from July 23 to August 23 and shipped 44 posts. Blogspot started August 8 and stopped on the same day the other one did, so 37 posts in 15 days. Eighty-one posts total. Both pipelines ran on a schedule with no approval step. A run would ground itself against official sources, draft the body, generate three to five images, run a mechanical validation pass (word count, live-link checks, duplicate detection against previous posts, required-field checks), retry on failure, and publish. If validation failed too many times, the run gave up and logged it. That was the entire loop. It worked, in the sense that posts appeared on a schedule and none of them were broken. Today I measured what Google actually did with them. One post is indexed. Out of 81. The one that made it is a ...
Read more

I had another AI review my trading bot. It found three ways my books were wrong.

Image
I wrote a trading bot with AI assistance, tested it, and ran it. Then I did something I had not done before: I handed the whole file to a different model, cold, with no context about how it was built, and asked it to look for accounting errors. It came back with three. All of them were in code I had read many times. None of them crashed anything. That is the part worth writing down. The three 1. The bot recorded the size it asked for, not the size it got. market_fill() returned the fill price and nothing else. So open_position() , add_in() , and close_out() all took the requested quantity and wrote that into state as if it were fact. Exchanges do not always give you what you asked for. Contract counts get rounded. A single order can be truncated by the venue max market order size. When either happens, the exchange position and the bot idea of the position drift apart, silently, with no error anywhere, because from the bot perspective the order succeeded. The fix was to widen...
Read more