iAlpha Talk to us

SECURITY & OWNERSHIP

Your infrastructure. Your data. Your IP.

The same boundary applies to all three. This page says where the agents run, where your data goes, who touches your systems, and what you own when we are finished.

One boundary, and it is yours, not ours.

Agents run inside your environment. Your data stays inside it. What we build crosses the boundary once, at handover, in your direction. Nothing production-facing sits with us, and no part of our revenue depends on which model or platform you choose.

Outside, scoped and approved

iAlpha Delivery Devs

Your environment

The agents

Your data

Your systems

At handover

Code, prompts, configuration and documentation become yours.

Where do the agents actually run?

  • Agents run in your environment, or in a sandbox you approve. Nothing production-facing sits with us.
  • Each agent holds scoped, short-lived credentials. No shared keys, no standing admin rights.
  • Access is limited to the systems the workflow needs, and it is approved before the build.

During a pilot we may run the work on our own infrastructure so we can move quickly, on data and under a boundary you have approved in advance. At production it moves to yours.

What happens to our data?

  • Your data stays inside your boundary. We name the provider, the region and the retention term before anything moves.
  • Enterprise API terms exclude your data from model training.
  • Retention is 30 days by default. Where your data class requires zero retention, we arrange it with the provider before the build starts.
  • We design to local data-transfer limits from the start, rather than discovering them at review.

Who else can see it?

Two organisations, and we would rather you heard it here than found it later.

  • iAlpha. The founders. We specify the work, review it with your team, build the pilot and sign it off.
  • Delivery Devs. Our engineering partner, who take the pilot into your systems and engineer it for production. Production is where agents fail, and it deserves engineers who do nothing else.

They work under the same access rules we do: scoped credentials, only the systems the workflow needs, approved before the build. They are named in your engagement letter as a subprocessor and bound by the same terms we are.

Nobody else. We do not staff your operations, and we do not bring in contractors you have not been told about.

What do we own at the end?

  • Code, prompts, configurations, evaluation sets and documentation are assigned to you at handover.
  • Assignment is express, not work-made-for-hire alone, because AI-generated material may not be copyrightable, and a doctrine that assumes an author cannot transfer what has none.
  • We keep only our pre-existing components, licensed to you perpetually and royalty-free.
  • The system runs under your certifications, not ours. Your audit requirements are scoped with you at Triage, before anything is built to them.

What happens when we stop working together?

  • Access and credentials are revoked within five working days.
  • Any copies of your data on our systems, or our partner's, are deleted within 30 days, and we confirm the deletion in writing.
  • You keep the code, the runbook and the documentation. Nothing you need to run the system depends on us still being there.

If we are still required in year two, the transfer failed.

What we build in, by default.

This is the standard we design to. What a given build carries is set with you at Triage, and written down before anything is built.

Approval before it acts

Anything an agent cannot undo waits for a person to approve it first.

Tamper-evident logs

Every action and every tool call recorded, so changes to the record are detectable.

Validated agent memory

What an agent stores is checked, so a bad input cannot become a standing instruction.

A stop switch you own

You can halt any agent yourself, at any time, without calling us first.

Built against the OWASP Top 10 for Agentic Applications (2026) and the NIST AI Risk Management Framework. EU AI Act Article 50 transparency obligations apply from 2 August 2026.

Send this page to whoever has to sign it off. If they need something it does not answer, ask us, we would rather write it down than leave it to a call.

One of the founders reads your message. Not a coordinator. You’ll hear back within two working days.

  • We will answer a security questionnaire.
  • We will sign your NDA before the first call if you prefer.
  • We work globally, from the United States and Pakistan.

Or reach us however is easiest: