Your data, handled the way an engineer would want their own handled

What the AI sees

Only what a specific workflow needs. An automation that reads quote requests is given the quote request — not your whole inbox, not your accounting system, not your customer list. Each automation has a written list of the fields it reads and the fields it writes, and that list is part of the handover. Where a task doesn’t need AI at all, we build a plain automation and nothing is sent to a model.

Where your data lives

In accounts in your name: your cloud project, your database, your model API keys, your integrations. By default those run in US data-center regions. We hold the access we need while we work, and we hand it back. Nothing is stored on GainSolutions systems beyond working copies during an engagement, which we delete at the end.

No training on your data

The model providers we use offer business terms under which data sent through their APIs is not used to train their models. We use those terms, in your accounts, and we link to the current policies below so you can read them yourself. Separately: we never use one client’s data, prompts, or documents for another client, and we don’t build anything “trained on” your business data.

• OpenAI — enterprise privacy and API data usage
• Anthropic — commercial terms of service
• Vercel — security
• Supabase — security

Least-privilege access

We ask for the smallest access that gets the job done — view-only during an audit, a named account with a limited role during a build — and we prefer your admin to grant it rather than sharing passwords. We use multi-factor authentication on every account that supports it. At handover we rotate any keys we created and document what exists and who holds it.

You own the accounts, keys, and code

Everything we build is delivered to you on full payment: source code in a repository you control, prompts, configuration, the runbook, and the accounts themselves. There is no GainSolutions platform in the middle and no license from us to keep paying. If you later hire someone else, they can pick up where we left off.

When we stop working together

You get a handover document, we remove our access, and we delete our working copies of your data. What you built keeps running in your accounts. On request we confirm the deletion in writing.

What we don’t take on yet

Workflows that need HIPAA- or GLBA-grade handling, outbound AI messaging to consumers, and automated decisions about hiring, credit, or housing. Until those have had legal review, we say so on the fit call and point you elsewhere if that’s what you need.

Every AI that talks to your customers says it’s an AI

Any assistant we deploy on your site identifies itself as AI at the start of the conversation and always shows a path to a person. This is required in several states and, in our view, plain good manners.

This website

Forms on this site go to our inbox and, optionally, a private Slack channel. Analytics are cookieless and aggregated. Details in the privacy policy.

Reporting a concern

Found something that worries you? Email hello@gainsolutions.io and it goes straight to the engineer.