The short version
- We collect what we need to run your account and servers: your email, what you build, usage counts and billing status.
- Our servers and database are in the EU. No advertising trackers, and our website sets no cookies.
- We don't sell your data, and we don't use it or your customers' data to train AI models.
- Payments are handled by Creem. We never see your card details.
- You can ask for a copy of your data or have it deleted at any time: support@saywire.dev.
1Who we are
Saywire is run by Saywire Ltd, a company in the United Kingdom, 11 Biscayne Avenue, London E14 9BE. For the personal data described in this policy we are the controller under the UK General Data Protection Regulation (UK GDPR), the Data Protection Act 2018 and, for people in the European Economic Area, the EU General Data Protection Regulation (EU GDPR).
For any privacy question or request, email support@saywire.dev. This policy covers saywire.dev, the dashboard at app.saywire.dev, our API and the MCP servers we host.
2What we collect
Data you give us
- Account data: your email address and a password (stored only as a secure hash), or the basic profile your sign-in provider shares if you use GitHub or Google (email, name, avatar and account id).
- What you build: server names, the descriptions you write, tool configurations and their version history, API specifications you import, and connection settings.
- Secrets: API keys, tokens and database connection strings for the services you connect. We store them encrypted; our dashboard and API can't read them back, and only the gateway that runs your tools can decrypt them.
- Support messages: what you write when you email us.
Data created when you use Saywire
- Usage records: monthly tool-call counts per workspace and per server, and a log of each call with the tool name, status, timing, sizes and error code. By default the log doesn't contain call inputs or outputs.
- AI generation records: which model was used and how many tokens, so we can apply plan limits and track costs.
- Build chat conversations: what you write to the assistant, its answers, and the results of the read-only lookups it made (schema, column statistics and, only if you allow it for an integration, sample rows). Kept with the server so you can continue later.
- API key records: a hash and short prefix of each Saywire API key, and when it was last used. We never store keys in plain text.
- Product analytics (dashboard only): which pages and features are used, for example "server deployed" or "sign-up completed". These events contain ids, counts and categories only and are linked to your user id, not your email. We also record sessions in the dashboard to find usability problems; every text field and anything showing keys, secrets, configurations or tool results is hidden from these recordings.
- Security and server logs: IP address, browser type, and times of sign-ins and requests, used to keep accounts and the Service secure.
Data from others
- Creem, our payment provider, tells us your Creem customer and subscription ids, your plan, subscription status and renewal date. We don't receive your card details.
- GitHub or Google, if you sign in with them, share the profile data listed above.
3How we use it and our legal bases
| Purpose | Data | Legal basis |
|---|---|---|
| Create and run your account, build and host your servers, run tool calls | Account data, what you build, secrets, usage records | Contract (to provide the Service you signed up for) |
| Generate tools with AI from your description, and the build chat | Your messages, service and database metadata (schemas, column statistics); sample rows and API responses only from integrations where you turned on "Let the assistant read sample rows", with personal-looking fields masked. Never secrets | Contract |
| Apply plan limits, take payment through Creem, manage your subscription | Usage records, billing status, email | Contract |
| Send service emails (sign-up confirmation, password reset, billing, security and important changes) | Contract; legitimate interests for security notices | |
| Answer support requests | Support messages, account data | Contract; legitimate interests |
| Keep the Service secure, prevent abuse and fraud, debug problems | Security and server logs, usage records | Legitimate interests (protecting you, us and other customers) |
| Understand and improve the product | Product analytics (pseudonymous) | Legitimate interests (improving a product you use); you can object at any time |
| Keep business and tax records, meet legal obligations | Billing records | Legal obligation |
We'll only send marketing emails if you've opted in, and every one will have an unsubscribe link. We don't make decisions about you based solely on automated processing that have legal or similarly significant effects.
4What we never do
- We don't sell or rent personal data.
- We don't use advertising trackers or share data with advertisers.
- We don't use your data, or data that passes through your servers, to train AI models, and our AI provider doesn't either under its commercial terms.
- We don't send secrets, API keys, tool inputs or outputs, prompts or configuration contents to our analytics provider.
5Data that passes through your servers
When an AI client calls one of your tools, the request and the response from your API or database pass through our gateway. For that data you are the controller and we act as your processor: we handle it only to run your tools, under the data processing terms in section 9 of our Terms of Service. If you're an individual whose data is held by one of our customers, please contact that customer; we'll help them answer your request.
By default we don't keep the contents of tool calls. Call logs record metadata only (tool, status, timing, sizes) and are deleted after your plan's log period.
The build chat is the exception you control: if you allow the assistant to read sample rows from an integration, up to 20 rows per lookup (personal-looking fields masked) are sent to our AI provider and stored in the conversation. We blank those results after 30 days. Without that permission the assistant sees only schemas, statistics and the shape of results.
6Who we share it with
We use a small number of service providers (sub-processors) to run Saywire. Each one gets only the data it needs and is bound by a contract to protect it. We may also share data if the law requires it, to protect people's safety or our legal rights, or with a successor if the Service is transferred (we'd tell you first).
| Provider | What for | Data | Where |
|---|---|---|---|
| Contabo GmbH | Servers that run our API, gateway and database | All data stored by the Service | EU (Germany) |
| Cloudflare, Inc. | DNS, website and dashboard hosting, network security, email forwarding, encrypted backups | IP addresses and request data; database backups (encrypted) | Global network; EU-focused storage where available |
| Anthropic PBC | AI that generates tool configurations and runs the build chat | Your messages and service metadata; sample rows and API responses only from integrations where you allowed it (masked). No secrets | USA |
| PostHog Inc. | Product analytics and feature flags (dashboard) | Pseudonymous usage events, masked session recordings | EU (PostHog EU Cloud, Germany) |
| Resend (Plus Five Five, Inc.) | Sending account and service emails | Email address, email content | EU (Ireland) sending region; USA company |
| Google LLC | Support inbox (Gmail); Google sign-in if you choose it | Support messages; sign-in profile | USA / global |
| GitHub, Inc. | GitHub sign-in if you choose it | Sign-in profile | USA |
Creem (Armitage Labs OÜ, Estonia) is our merchant of record. It sells you the plan, so it is an independent controller for your payment and tax data under its own privacy policy. We share your email and user id with Creem when you start a checkout.
We'll update this list before adding a new provider. Customers are notified of new sub-processors as set out in our Terms.
7International transfers
Our servers and database are in the EU. Some providers above are based in, or may access data from, the United States or other countries. When personal data leaves the UK or EEA, we rely on an adequacy decision (such as the EU-US Data Privacy Framework and its UK Extension, for certified providers) or on Standard Contractual Clauses approved by the European Commission, with the UK International Data Transfer Addendum. You can ask us for a copy of the relevant safeguards.
8How long we keep it
| Data | Kept for |
|---|---|
| Account data, what you build, secrets, usage counts, AI generation records | While your account is open; deleted within 30 days of closing it |
| Tool call logs | 7 days (Free) or 30 days (paid plans) |
| Data the build chat read from your systems (sample rows, API responses) | 30 days, then blanked; the rest of the conversation is kept with the server |
| Database backups | Up to 60 days, then overwritten |
| Security and server logs (incl. IP addresses) | Up to 90 days |
| Product analytics events | Up to 12 months; session recordings up to 30 days |
| Billing records (Creem ids, plan changes) | Up to 6 years after the end of the tax year, as UK tax law requires |
| Support emails | Up to 2 years after the conversation ends |
We may keep data longer if we need it to resolve a dispute, enforce our terms or meet a legal obligation, and only for as long as needed.
9Cookies and local storage
- This website (saywire.dev) sets no cookies and loads no third-party trackers. Our fonts are served from our own domain.
- The dashboard (app.saywire.dev) uses your browser's local storage for things that are strictly necessary or that you ask for: keeping you signed in, your theme, sidebar state and your last sign-in method. Our analytics keep no cookies or local storage and run only while the tab is open.
- Creem's checkout, on Creem's own domain, may use cookies needed for payment and fraud prevention, as described in Creem's privacy policy.
Because we only use strictly necessary storage, we don't show a cookie banner. If that changes, we'll ask for your consent first.
10Security
We protect data with encryption in transit (HTTPS), encryption of stored secrets with a key held only by the gateway, hashed API keys and passwords, row-level access controls in the database, an egress guard that blocks calls to private networks, restricted administrator access and regular updates. No system is perfectly secure; if a breach puts your data at risk, we'll tell you and the regulator as the law requires.
11Your rights
Under the UK GDPR and EU GDPR you have the right to:
- access the personal data we hold about you and get a copy;
- correct data that is wrong or incomplete;
- delete your data ("right to be forgotten");
- restrict how we use it;
- port it: receive it in a machine-readable format, or have it sent to another provider;
- object to processing based on legitimate interests, including product analytics, and to direct marketing at any time;
- withdraw consent where we rely on it, without affecting what happened before.
To use any of these rights, email support@saywire.dev from the address on your account. We'll reply within one month (we may extend this by two months for complex requests and will tell you if so). It's free, unless a request is clearly unfounded or excessive. We may ask you to confirm your identity.
If you're unhappy with how we handle your data, please tell us first so we can put it right. You can also complain to the UK Information Commissioner's Office (ico.org.uk) or, if you're in the EEA, to the data protection authority in the country where you live or work.
12Children
Saywire is for people aged 18 and over and isn't directed at children. We don't knowingly collect data from children; if you think a child has given us personal data, contact us and we'll delete it.
13Changes to this policy
We'll update this policy when our practices or providers change, and show the date at the top. If a change materially affects how we use your data, we'll email you before it applies.
14Contact
Saywire Ltd
11 Biscayne Avenue, London E14 9BE
support@saywire.dev