Public position: Seitiate is open infrastructure. Using the engine does not transfer ownership of your content or useful exported context to the platform, and portability is a core design goal. This page describes current public commitments, architectural direction, and areas that still depend on the deployment you choose.
1. The Seitiate.com Website
The marketing and documentation site at seitiate.com is a public website operated by Agent-C LLC. We do not use advertising pixels or third-party marketing trackers on this site. Like most websites, the hosting layer may create standard operational logs for security, performance, and abuse prevention.
If you contact us directly, we will receive the information you choose to send us, such as your email address or message contents.
2. Self-Hosted Engine Posture
If you run Seitiate yourself, the engine runs in the environment you control. In a normal self-hosted setup, Agent-C LLC does not automatically receive your projects, memory, exported context, or routine usage data simply because you are using the engine.
That said, your actual privacy and security posture depend on how you deploy it. If you run Seitiate on your own machine, server, or cloud environment, you are responsible for the infrastructure choices, access controls, and data handling in that deployment.
3. Current Public Commitments
These commitments describe the current public doctrine around Seitiate and products built on it.
3.1 Ownership of Content and Context
We believe users retain ownership of the content they create and the useful durable context derived from their work. Paying for hosting, compute, storage, governance, or product experience does not mean the platform should own the person or their accumulated context.
3.2 Portability and Exit
We reject lock-in through inaccessible derived context. Exporting content matters, but exporting the useful form of remembered context matters too. Exact export mechanics depend on the version and deployment, but the architectural direction is clear: users should be able to leave with the substance of their work intact.
3.3 Anti-Harvesting Direction
Seitiate is not meant to justify harvesting user work as platform property. Hosted products built on the engine may charge for service and experience, but that should not become a pretext for claiming ownership of user content, silently training on it without clear permission, or trapping valuable context behind permanent payment.
4. Security and Encryption Language
Security matters, but this page should not overstate what every deployment already guarantees.
- Self-hosted deployments: your privacy and security depend heavily on how you run the system and what safeguards you put around it.
- Hosted products: may use encryption in transit, encryption at rest, access controls, and operational safeguards, but the exact implementation depends on the specific product and deployment.
- Not a current blanket claim: this page does not promise full user-held end-to-end encryption for all hosted data, and it does not claim that operators can never access hosted data under any circumstances.
Where a product offers stronger guarantees, those guarantees should be documented in that product's own security and privacy materials rather than assumed from this page.
5. Current Reality vs. Direction
Some ideas associated with Seitiate are still architectural direction rather than universal present-day guarantees. Depending on the deployment, those may include stronger cryptographic isolation, more complete portability tooling, or richer provenance and publication controls.
When a feature is not yet fully implemented across deployments, it should be understood as direction rather than contract. The authoritative source for the current state of the engine remains the codebase and product-specific documentation.
6. Contact
If you have questions about privacy, ownership, portability, or responsible hosted-product boundaries, contact hello@seitiate.com.