Skip to content

Trust center · Security

Security practices for the AI systems we build

What happens to the data and access you share with us, layer by layer. We are a small, founder-led studio: this page lists the practices we follow on every project, and it is plain about the certifications we do not hold.

Defence in depth as nested layers: a glowing data core inside five frosted shells that drift apart, one shell per practice. An illustration, not a certification.
  1. Your data, used only for your project
  2. Accounts registered in your business’s name
  3. Least-privilege access for named people
  4. Secrets kept out of code
  5. No training on your data for other clients
  6. Access removed when the engagement ends

Controls

How it works in practice

Each control names the mechanism and where it applies. These are our working practices, not a certification.

Core: your data

  • Your data, used only for your project

    We ask only for the data the work needs and build and test with samples or de-identified data where that is enough. Your data stays in your own systems wherever possible, and on our side only the people working on your project can open it.

    Scope: Every project: the data you share with us and the data your system processes.

  • No training on your data for other clients

    We never reuse your business data to train systems we build for anyone else. For the AI providers your system calls, we choose the setting that keeps API data out of model training wherever the provider offers one.

    Scope: Our own work, and the provider settings we control. Each provider’s terms still apply, and your proposal names them.

Middle: accounts and access

  • Accounts in your business’s name

    AI model, telephony, messaging, automation and hosting accounts are registered to your business wherever possible, and API keys are issued from them. You hold the admin rights and pay the provider directly.

    Scope: Every provider that offers business accounts. Any exception is named in your proposal before work starts.

  • Least-privilege access for named people

    We ask to be added as a named user with the narrowest role that does the job, not for shared logins. You can see who has access and revoke ours at any time, without asking us first.

    Scope: Your systems, your SaaS tools and the provider accounts above.

  • Secrets kept out of code

    API keys and passwords live in each platform’s secret or environment settings, never in code repositories, so a copied folder or a shared repository cannot leak them.

    Scope: Every credential a build uses, from test keys to production keys.

Outer: the end of an engagement

  • Access removed when the engagement ends

    At handover we pass admin control to you and remove our access. On a monthly plan we keep only what the plan needs. Project data we hold is returned or deleted if you ask, unless the law requires us to keep it.

    Scope: One-off projects at handover; monthly plans when you cancel.

How we handle your data

The safest data is data we never receive. Most of what we build reads from your systems in place: a chatbot answers from your published pages, an automation moves a record between your tools. When we need a copy to build or test, we start from samples or de-identified data and ask for real records only when the work cannot be checked without them.

Access and accounts in practice

Accounts in your name are the layer that protects you from us. If we stop working together, or if anything about our own setup were ever compromised, your system keeps running on your accounts and your keys, and you can remove our access yourself. We recommend multi-factor authentication on every account involved, and we tell you promptly if we suspect something has gone wrong.

AI providers and model training

  • Your system sends data to the AI providers named in your proposal, under each provider’s terms, which you can review before you accept.
  • Where a provider offers a setting that keeps API data out of model training, we choose it. Where reduced or zero data retention is available to your account, we can configure it.
  • If data must not leave your environment, a self-hosted model or an on-premise deployment can be scoped as an Enterprise build.

Healthcare and other regulated data

When a project involves health information, we build HIPAA-aware:

  • the AI sees only the minimum information each task needs;
  • protected health information stays in systems you control, or with providers that will sign a business associate agreement (BAA) with you;
  • we can build and test with synthetic or de-identified data until your agreements are in place;
  • before launch, you get a written data-flow description for your compliance advisor.

HIPAA-aware is a design approach, not a certification. Whether a system meets HIPAA, GDPR or another regulation depends on your policies, agreements and risk assessment, which we support but cannot sign off for you.

How we run our own site

miniailabs.in follows the same habits. It is served over HTTPS only, with strict transport security, and its response headers stop content-type sniffing, limit the referrer data sent to other sites, switch off camera, microphone and location access, and stop other sites from framing our pages. No API key reaches your browser: the chat assistant and every form call our own server functions, which validate what they receive and apply per-visitor rate limits. The assistant removes card numbers, ID numbers and passwords from messages before anything is stored or sent to a model, and it treats retrieved text as data, never as instructions.

If something goes wrong

  1. We tell you promptly when we suspect a security incident affecting data we handle for your project, without waiting for the full picture.
  2. We explain what happened, which data and systems were involved, and what we are doing about it.
  3. We give you the information you need for your own notification duties, for example under India’s Digital Personal Data Protection Act, 2023 or the GDPR.
  4. Because your accounts are in your name, you can revoke our access or rotate a key yourself at any moment, without waiting for us.

Responsible disclosure

Think you have found a vulnerability in miniailabs.in or a system we operate? Email hello@miniailabs.in with the subject “Security”, describing what you found and how to reproduce it. A person replies as soon as we can. The same contact is published in machine-readable form at /.well-known/security.txt, following RFC 9116.

Please give us reasonable time to fix the issue before telling anyone else, do not access or change data that is not yours, and do not run denial-of-service, spam or social-engineering tests. We do not run a bug bounty and cannot offer payment for reports.

Certifications we do not hold

We hold no SOC 2 report and no ISO 27001 certificate, we do not claim HIPAA compliance or GDPR certification, and we do not offer standard availability guarantees; a custom SLA is available on Enterprise builds. The trust center overview explains how we support your review without them.

FAQ

Frequently asked questions

Which security certifications does MiniAI Labs hold?

None today. We have no SOC 2 report and no ISO 27001 certificate, and we say so on security questionnaires. What we give you instead is a written description of how data moves through your system, which providers it touches and who has access, so your team can assess the actual design. If certification is a firm requirement for your vendors, tell us on the first call so you can decide before any work starts.

Does anything we share with you end up training AI models?

Not through us. Your data is used only for your project and never to train systems we build for other clients. For the AI providers your system calls, we pick settings that keep your data out of model training wherever the provider offers that option, and your proposal names every provider so you can read its terms before you accept.

How do you treat patient or other health information?

We build HIPAA-aware. The AI sees only what each task needs, health data stays in systems you control or with providers under your own agreements, and we can build and test with de-identified data until those agreements are signed. Before launch you get a written data-flow description. Your compliance advisor makes the final call on whether the setup meets your obligations.

Will you sign our NDA, data processing agreement or business associate agreement?

On request, reviewed case by case. Send the agreement before work starts so we can review it and, if we agree it, reflect it in your proposal. We only sign commitments we can actually meet, so we may ask to change a clause that assumes a large security team or a certification we do not hold.

Do you need admin rights to our systems?

Usually not. We ask for the narrowest role that lets us build and test, and we explain why if a step genuinely needs more, for example creating an API key in an account we set up for you. Where a platform supports it, a temporary elevated role that you grant and then remove is better than a standing admin login.

How do I report a vulnerability in miniailabs.in?

Email hello@miniailabs.in with “Security” in the subject line, with what you found and how to reproduce it. A person replies as soon as we can, and we ask for reasonable time to fix the issue before it is shared. We do not run a bug bounty, so we cannot pay for reports.

Questions about this page

Send your security questionnaire, vendor-assessment form or a question about this page to hello@miniailabs.in. We answer as things stand today, including “no” where that is the true answer.

hello@miniailabs.inSend an RFP or security questionnaire

Next step

Have a workflow in mind? Let’s scope it together.

Book a free 30-minute strategy call. Bring one process you want to automate and we will talk through scope, integrations and a sensible first step.

Free 30-minute call · no commitment

Send an RFP or security questionnaire