SmythOS
SmythOS · Agent platform · US · smythos.com
services/smythos.yamlVendor data-handling terms
The no-training statements are the Google API Limited Use wording. Data passed through agents built on the platform is not addressed.
“We affirm that Google Workspace APIs are not used to develop, improve, or train generalized AI and/or ML models. / We do not transfer any Google user data to third-party AI tools for the purpose of developing, improving, or training generalized or non-personalized AI/ML models.”
“The Company retains your personal information to the extent necessary to reasonably serve customer relations, to meet our compliance and legal obligations, to enhance security and fraud prevention, and for audit purposes. / For example, we may retain your information during the time in which you have an account to use our Site or Services and for a reasonable period of time afterward.”
“The Services are operated in the United States. / If you are located in another jurisdiction, please be aware that information you provide to us will be transferred to and processed in the United States.”
Domains and endpoints
observed means seen in Unseen deployments; vendor-documented means listed by the vendor. Vendors do not publish complete lists.
| Host | Role | Source |
|---|---|---|
| smythos.com | app | observed |
Assessment
Reasoning: A low-code agent builder that connects to many SaaS APIs. The policy covers Google data and account data but says nothing about what happens to the data agents move between systems, and everything runs in the US. The exposure is in the connectors the builder is given, not in the policy.
Flags: Training-use of agent data not stated · US processing only · Agents hold credentials for connected systems · Assessed 2026-09-16. The assessment is Unseen's; the terms above are the vendor's.
Changelog
- 2026-09-16Documented. Google API, retention and transfer terms verified against the SmythOS privacy policy.
- 2026-09-15Listed from the Unseen catalogue with observed domains.
Corrections
Pull request on GitHub, or the form below. Changes are reviewed and recorded in the changelog.