AIOS is a developer platform that connects to databases and systems you already own, discovers their structure, and lets your agents query and operate them through one API. Doing that means we hold three sensitive things on your behalf: your account, your connection credentials, and a description of your data estate. This page explains exactly what we hold, why, where it lives, and how long we keep it.
Sections marked [[FILL: …]] are not yet complete. They cover facts only the operator of this service can state — legal entity, registered address, governing law, and contact routes. Until every marker is replaced and the document has been reviewed by counsel, treat this page as informational.
AIOS (“AIOS”, “the Service”) is operated by [[FILL: full legal entity name]], trading as Swan Create, registered at [[FILL: registered business address]] ([[FILL: company / registration number, if any]]). In this policy, “we”, “us” and “our” mean that entity. “You” means the person or organisation holding an AIOS account.
For the personal data described here we act as the controller in respect of your account and billing records, and as a processor in respect of the contents of the systems you connect to AIOS.
This policy covers aios.swancreate.com, the AIOS REST and MCP APIs, the
AIOS dashboard, and the marketing pages on the same domain. It does not cover the
third-party databases, SaaS products, or model providers you choose to connect —
those remain governed by their own agreements with you.
Payments are processed by Stripe. Card numbers never reach our servers — card details are collected directly by Stripe in your browser. We store the Stripe customer and subscription identifiers, your plan, its status, and invoice metadata so we can apply the right quotas and show your billing history. [[FILL: confirm whether billing address / VAT ID is also stored]]
To do its job, AIOS stores the credentials you register for your own databases and third-party licences (connection strings, API keys, service secrets). These are encrypted at rest with AES-256-GCM under a key held outside the application database, and are decrypted only at the moment a request that is entitled to them is served. Secrets are never returned in list responses, never written to application logs, and never displayed back in the dashboard once saved.
When you connect a database, AIOS crawls its structure and stores a description of it: database, schema, table and column names, data types, keys, relationships, row counts, and derived artefacts such as the knowledge graph and search embeddings. To make that description useful to an agent, AIOS also stores a very small number of sample rows per table, with values it identifies as personal or sensitive redacted.
You control this. Sampling can be limited or disabled per data source, and specific tables or columns can be excluded from discovery. If a table must never be described or sampled, exclude it before connecting the source. [[FILL: link to the exclusion / settings doc once written]]
Messages you send to the AIOS Brain, documents you upload to a document store, support requests, and anything you type into a form on this site.
| Purpose | Data used | Basis |
|---|---|---|
| Provide the Service: authenticate you, run queries, serve context to agents | Account data, credentials, schema metadata | Performance of the contract |
| Bill you and manage subscriptions | Account and billing data | Performance of the contract |
| Enforce plan quotas and rate limits | Usage logs | Performance of the contract |
| Security, fraud prevention, and abuse investigation | Audit and server logs | Legitimate interests |
| Diagnose faults and improve reliability | Error traces, bug reports | Legitimate interests |
| Service notices about outages, security, and changes | Email address | Legitimate interests / contract |
| Marketing email, where you have opted in | Email address | Consent — withdrawable at any time |
We do not use your Customer Data to train models offered to other customers, and we do not use it to build a general-purpose dataset.
AIOS is designed so an agent never has to hold a long-lived secret. When an agent needs access it asks AIOS for a specific handle — a database, a licence, a document store — and receives either a short-lived broker token or an instruction to proxy the call through AIOS. Issued tokens expire after fifteen minutes, and every issue is written to the audit log.
The practical consequences: a leaked agent transcript does not leak a standing password; a revoked key stops working everywhere at once; and you can see, per credential, exactly which agent used it and when.
Conversational features and natural-language querying use large language models hosted on Microsoft Azure OpenAI inside our own Azure subscription. To answer a question, the prompt and the relevant context — which may include schema metadata, sample rows, and query results — are sent to that model endpoint.
AIOS runs entirely on Microsoft Azure. Application data lives in Azure SQL; secrets and keys are held in Azure Key Vault; compute runs on Azure virtual machines. Primary region: [[FILL: Azure region(s), e.g. East US]].
| Subprocessor | Purpose | Data reached |
|---|---|---|
| Microsoft Azure (incl. Azure SQL, Key Vault, Azure OpenAI) | Hosting, storage, key management, model inference | All categories |
| Stripe | Payment processing and subscription billing | Name, email, payment details (collected by Stripe directly) |
| Mailgun | Transactional and service email delivery | Email address, message content |
| [[FILL: verify this list is complete before publishing]] | — | — |
We will give notice before adding a subprocessor that processes personal data. [[FILL: notice period, and where the current list will be published]]
Every record AIOS stores carries a tenant identifier, and tenancy is enforced at several layers — on the authenticated key, in the service layer, in every query, and at the row level in the database. Your schemas, credentials, agents, documents, and logs are not visible to another tenant, and a query issued under your key cannot reach another tenant’s data source.
No system is perfectly secure. If we become aware of a breach affecting your personal data we will notify you and, where required, the relevant supervisory authority. [[FILL: breach-notification commitment, e.g. “without undue delay and within 72 hours”]]
To report a vulnerability, write to [[FILL: security contact address]]. We will not pursue good-faith research that respects customer data and does not degrade the service.
| Category | Retained for |
|---|---|
| Account and tenant records | Life of the account, then [[FILL: grace period]] before deletion |
| Stored credentials | Until you delete them, or until the account is closed |
| Schema metadata, samples, embeddings | Until the data source is disconnected, then removed on the next maintenance run |
| Audit log | 18 months by default |
| Usage and request logs | [[FILL: usage-log retention]] |
| Billing records | As long as tax and accounting law requires [[FILL: statutory period]] |
| Support correspondence | [[FILL: support-mail retention]] |
You can delete a connected source, a credential, a document, or a conversation at any time from the dashboard or the API. To delete an entire account and everything attached to it, contact us at the address in section 16; we will confirm when it is done. Backups are cycled out on their own schedule, so deleted data may persist in encrypted backups for a short period after removal from the live system.
Depending on where you live you may have the right to access, correct, export, delete, or restrict processing of your personal data, to object to processing based on legitimate interests, and to withdraw consent. Exercise any of them by writing to the contact address below; we will respond within [[FILL: response window, e.g. 30 days]], and we will not charge you or degrade your service for asking.
Where we hold data as a processor on behalf of a customer — for example personal data inside a database that customer connected — we will refer your request to them and assist them in answering it.
[[FILL: supervisory authority / regulator you can complain to, and how]]
Data is stored in the Azure region named in section 8. If we transfer personal data out of the region where you are located, we rely on [[FILL: transfer mechanism, e.g. Standard Contractual Clauses]]. A Data Processing Addendum is available on request: [[FILL: DPA request address or link]].
AIOS is a business tool and is not directed at children. We do not knowingly collect personal data from anyone under [[FILL: minimum age — 16 in the EEA/UK, 13 in the US]]. If you believe a child has given us personal data, tell us and we will delete it.
We update this page when the way we handle data changes. Material changes are announced by email to account holders and reflected in the effective date at the top. Continuing to use AIOS after a change takes effect means you accept the updated policy. [[FILL: whether prior versions will be archived, and where]]
Privacy questions, rights requests, and DPA requests: [[FILL: privacy contact email address]].
Postal address for legal notices: [[FILL: postal address]].
[[FILL: named data protection officer or EU/UK representative, if one is required — delete this line if not]]