Now taking on new projects · Free call, AI Roadmap, Build, SupportSee services & pricing
Trust center

Your data, your accounts, your control

Everything about how we handle your information, systems and access, in one place and in plain terms. If something you need is not here, ask, and we answer in writing.

§01At a glance

Six commitments, every engagement

These hold for every system we build, whatever the size of the project.

  • 01

    Your accounts

    We build and run systems in accounts your business owns. Billing, data and control stay with you.

  • 02

    Least access

    Separate, revocable credentials with only the permissions each task needs, removed when the work ends.

  • 03

    A person approves

    Sending, deleting or changing key records waits for a named person, unless you ask us in writing to let an agent post routine items itself. Payments and bank details always wait for a person.

  • 04

    Full audit trail

    Inputs, outputs and actions are logged, so you can see what happened and why.

  • 05

    Provider terms reviewed

    We review the AI provider's current business terms with you before any of your data is processed.

  • 06

    NDA and DPA on request

    We sign them before any of your information is shared, if you want them.

§02Architecture

Built inside your environment

Where possible, every part of the system lives in accounts your business owns. The one thing that usually leaves is the text a model needs to read, and only the part the task requires.

Your environment · your accounts
Your systemsCRM · ERP · drives · email
Scoped credentialsseparate, revocable
Agent or workflowruns in your account
Approvalsfor consequential actions
Audit loginputs, outputs, actions
Test setyour real cases
AI model providerbusiness or API terms, chosen and approved by you
Diagram: the agent, your systems, credentials, approvals, audit log and test set all sit inside your own environment and accounts. Only the data a task needs is sent to an AI model provider that you have approved.
§03Principles

Applied to every engagement

You own the accounts

We build and run systems in accounts registered to your business: your cloud, your automation platform, your AI provider account.

Ownership001

Least privilege

Each system gets only the permissions its task needs: read-only where reading is enough, limited to specific folders, mailboxes or records.

Access002

Data minimization

Only the information a task needs is sent to an AI model. Where practical, personal or sensitive details are removed or masked first.

Data003

Human approval

Actions with real consequences, like sending to customers, moving money or changing important records, can require a person's approval.

Oversight004

Logging

Inputs, outputs and actions recorded at a level agreed with you, while keeping logs free of unnecessary sensitive data.

Audit005

Testing first

We test systems against real examples, including awkward and adversarial ones, before they're used for real work.

Quality006
§04Data

How we handle your data

Your data stays in your systems. An agent reads what a task needs, when it needs it, through the same kind of access a person would use.

  • Only what the task needs. The text a model has to read is sent to the model provider you approved, and only that part.
  • Business terms that exclude training. Systems use providers' business or API services, whose terms say customer data isn't used for training by default; we review those terms with you before any data is processed. Where a provider offers reduced or zero data retention for your use, we consider it in the design.
  • Copies kept to a minimum. Logs and test sets are stored in your accounts, and you decide how long they are kept.
  • Sensitive data handled deliberately. Health, financial and personal data shape which providers and designs are acceptable. Your privacy and legal advisers approve the approach; we do not give legal advice.
§05Access

Access to your systems

  • Requested in writing. Every access request says what it is for and what it allows.
  • Least privilege. Read-only wherever possible. Agents get their own credentials, never a person's login.
  • Test first. Work starts in test environments or with sample data where your systems allow it.
  • Protected. Credentials live in your secret store or password manager, with multi-factor sign-in where offered.
  • Removed at the end. Access is revoked when the work ends, and the handover includes a full access list.
§06Where it runs

Where your systems run

In accounts your business owns: your cloud account, your automation platform, your workspace. The billing is in your name, so there is nothing to migrate if you change suppliers and nothing that stops working if we stop working with you.

The security architecture above shows what lives in your environment, what leaves it, and the controls on each step.

§07Model providers

AI model providers and their terms

You choose the provider, with a recommendation for your case. These are the public pages where each major provider describes how it handles business data.

AI model providers and their public data terms
ProviderWhere its data terms are published
OpenAI (API and business plans)Enterprise privacy
Anthropic (API and business plans)Commercial terms · Privacy center
Google (Gemini on Google Cloud)Data retention and governance
Microsoft (Azure OpenAI models in Microsoft Foundry)Data, privacy and security
Amazon Web Services (Amazon Bedrock)Data protection
Open-weight models on your own infrastructureNo third-party model provider: the model runs in your environment

Provider terms change. We review the current terms of the provider chosen for your project with you before any of your data is processed. These links are for reference and are not a summary of those terms.

§08Contracts

Agreements in writing

  • A written agreement for every engagement, with the scope, deliverables and price.
  • We sign NDAs and data processing agreements on request, before any of your information is shared.
  • We do the work ourselves. If a project needs a specialist, they are brought in only with your written approval, under the same terms.
  • The legal fine print for this website is in the terms of use and the privacy policy.
§09AI-specific risks

Risks that come with AI, and how designs account for them

No design removes these risks completely. The aim is to reduce them to a level you're comfortable with, and to make problems visible when they happen.

AI-specific risks and their mitigations
RiskWhat it looks likeHow designs respond
Wrong or invented answersConfident output that is incorrectAnswers grounded in your documents with citations, outputs checked against your data, human review where accuracy matters
Manipulated inputsText in an email or document trying to steer the system (“prompt injection”)Tight limits on what the system may do, instructions kept separate from content, approval for sensitive actions
Data leaking between usersAn assistant revealing something a person couldn't otherwise seeYour existing permissions respected rather than pooling everything together
Behavior changing over timeModel updates or new kinds of input changing resultsA saved test set re-run after changes, and monitoring of real use
§10Compliance

Working within your obligations

If you work under rules such as GDPR, HIPAA, financial services regulation or professional confidentiality duties, those requirements shape the design from the first conversation: which data may be used, which providers are acceptable, what must be logged and what needs human review.

We are not a law firm and don't give legal advice. For regulated data, your legal or compliance advisers should confirm the approach meets your obligations, and the design documentation is written to make that review straightforward.

Questions about a specific project? Email info@georgyconsulting.ai.

§11Incidents

If something goes wrong

AI systems can make mistakes, and any system can fail. What matters is how fast we catch it and how we handle it.

  1. 01

    Contain

    We pause the agent or revoke its credentials. We build every system so it can be stopped without stopping your business.

  2. 02

    Tell you

    We tell you promptly and in writing: what happened, what was affected and what we are doing about it.

  3. 03

    Investigate

    The audit trail shows the inputs, outputs and actions involved, so we find the cause rather than guess it.

  4. 04

    Fix and re-test

    We test the fix on the case that failed and the existing test set before the system goes back into use, and add the case to the test set.

§12AI usage policy

How we use AI tools ourselves

  • Client information never goes into consumer AI tools. We use only business or API services with reviewed terms, and only where you have agreed to it.
  • Your data is not used for training. Client information goes only to services whose terms exclude training on it, and we train no models of our own on it.
  • A person checks the work. We review code, documents and recommendations drafted with AI assistance before they reach you.
  • Mistakes are planned for. We test every system on your own examples, with approval points where an error would matter.
§13Next step

Find your first AI win

Book a free 20-minute call. You'll leave knowing exactly where AI pays off in your business, and what to do first.