Who Owns What You Build: The 100% IP Ownership Policy, Explained

Who Actually Owns the Schema SangAEO Builds?

You do. Every JSON-LD entity graph, every llms.txt file, every edge snippet SangAEO generates for a client's domain is 100% that client's property, during the subscription and after it. SangTech makes no licensing claim, no royalty, no residual usage right. The output is built from your site's real content, and it stays yours the same way a document you wrote yourself would.

This isn't a marketing line bolted onto a pricing page. It's a structural decision about how the product works, and it matters more than it sounds like at first read.

Why Does an IP Policy Need Explaining At All?

Because most SaaS and agency tooling doesn't work this way. Configuration, custom code, and generated assets frequently sit inside a vendor's platform under a license, meaning access stops the day you cancel. SangAEO does the opposite: the JSON-LD, the llms.txt file, and the deployment snippet are handed to you as plain artifacts you can read, move, and reuse anywhere, with or without SangTech.

The practical reason this is possible: SangAEO doesn't invent anything about your business. It scans your actual domain, real robots.txt rules, real schema coverage, real HTML rendering, and generates structured data strictly from what's already true on your site. There's no proprietary dataset or black-box model output to protect. The artifact is a reflection of your content, so treating it as your property isn't a concession, it's the only honest position.

What Happens to the Setup If You Cancel?

Nothing breaks by design. If the schema and llms.txt were deployed at the Cloudflare edge, they keep running unless you remove them. If they were delivered as a paste-ready snippet in your CMS, the code stays exactly where you put it. SangAEO's ongoing role is the scheduled re-scan and the monthly plain-English brief on what changed on your site. Cancel that, and the structured data you already have doesn't get clawed back or disabled.

This is also why onboarding avoids sales calls. The 4-step setup, confirm business details, grant read access, run a live verification against the domain, activate, happens entirely in text chat and interactive staging links. Every step leaves a timestamped record of exactly what was built and when, which is the paper trail that makes an ownership claim actually verifiable instead of just asserted.

Why This Connects Back to How SangAEO Is Actually Run

SangTech is one founder, Tumisang, not an engineering team, and SangAEO is a single $99/mo product with no enterprise tier and no sales process. There's no incentive structure built around locking clients into a platform they can't leave cleanly, because there's no long sales cycle or contract renewal team whose job depends on retention friction.

The core mechanism SangAEO exists to fix, AI retrieval scrapers enforcing fetch timeouts and skipping client-rendered content, only matters if the structured data actually lives on your site, in your control, permanently. An ownership policy that expired at cancellation would undercut the entire premise. So it doesn't.