Trust and security
Security, privacy and accessibility go in the foundation. Here's what that means in practice.
Genbays hosts client data in India by default and in another region on request, sends it to an AI provider only when your agreement names one, builds to WCAG 2.1 AA, and delivers software ready for India's DPDP Act. This page says what we do, what stays in your control, and how to report a problem.
Where your data lives
- India by default
- Mumbai region on the cloud providers we use. Forms on this site go to a Mumbai database.
- Your region on request
- Other regions are available for client builds on request. The choice is written into the DPA.
Your data and AI assistants
If we build you an assistant, these are the rules we start from. The details of each, such as how long data is kept and how much a person checks, are written into your agreement.
Nothing is sent without your say
Before an assistant reads anything, your agreement names the AI provider, the region it runs in, and exactly which data it sees. If any of that changes, we ask you again, in writing.
No training on your data
Your agreement only allows AI providers whose contracts say your data isn't used to train their models. We'll show you the clause on request.
It sees only what the job needs
Your agreement lists the fields it can use. Anything else, such as Aadhaar numbers or full bank account numbers, is removed before anything is sent.
You choose where records are kept
The documents, what the assistant made of them and the log of what it did are kept where your agreement says: in India by default, or in your own cloud account on request.
Only your team can instruct it
Text inside a bill, an email or a WhatsApp message is treated as data, so it can't change what the assistant does. The actions it's allowed to take are listed in your agreement.
It's tested on your documents first
Before go-live we score it on your own documents, including ones it never saw while we built it. The bar it has to clear is agreed with you and written into your agreement.
A person checks its work
Anything that fails a check, or that it isn't sure of, goes to a person. How much else a person checks, and for how long, is set in your agreement. With the improvement retainer, we also re-check a sample of what it did alone.
Every action is logged
What it read, what it did, how sure it was and who checked it. Your admin can read the log, and we'll export it for you on request.
You can switch it off
Your admin can hand the work back to your team at any time. The limits that switch it off on its own, such as a spending cap, are set in your agreement.
Deleted on your schedule
Documents held for processing are deleted on the schedule your agreement sets, and your own records rules come first. If you try an assistant and don't go ahead, the trial data is deleted, with written confirmation on request.
What we do on every build
- Access
- Named accounts, roles, and least privilege on every system we build and every system we touch. Access is logged.
- Secrets and keys
- Never in code. Managed by the hosting provider's secret store, rotated on staff change.
- Backups
- Daily, encrypted, in the same region as the data, restore-tested before go-live.
- Encryption
- In transit everywhere. At rest by default on every hosting provider we use.
- Dependencies
- Pinned, scanned, and updated on a schedule as part of the retainer.
- Staff
- Small team, direct accountability. Confidentiality agreements. Client data stays on client systems, not laptops.
- Incidents
- A written playbook. You hear from us first, within the windows in your DPA.
Compliance readiness
Readiness is a capability we build in, not a badge we've bought. Where a law needs a document, it's on the legal pages.
India · DPDP Act 2023
Consent records, purpose limitation, retention rules and Data Principal rights built into what we deliver.
Accessibility
WCAG 2.1 AA is a requirement on everything we build, per the RPwD Act 2016 and GIGW. Our statement for this site is on the legal pages.
Reporting a problem
- Security disclosure
- Found something? Email [email protected] with the subject Security disclosure. We reply within two business days and we don't take action against good-faith reports.
- Support commitments
- Response times by severity are agreed in the retainer and written into it. Documents for procurement: DPA, sub-processors, accessibility statement.
Questions people ask us
Can our data stay in our own cloud account?
Yes. We can build into an account you own, so the data never leaves your control and you can revoke our access on the day the contract ends.
Do you sign NDAs before the workflow review?
Yes, yours or ours, before we see anything.
Do you send our data to AI services?
Only if we're building you an assistant, and only to the provider your agreement names, in the region it names, with the data it names. That provider's contract says your data isn't used to train its models. Without that agreement in writing, none of your data goes to an AI service.
What if the assistant gets something wrong?
Anything that fails a check, or that it isn't sure of, goes to a person before it's saved. With the improvement retainer, we check its accuracy on the schedule the retainer sets. If it's slipping, the fields affected go back to being checked by a person, and we tell you.
Can we stop using the assistant?
At any time. Your admin switches it off and the work goes back to your team's queue, with nothing lost. What you own at the end, such as the code, the test documents and the log, is set in your statement of work.
Tell us what's slowing you down.
Forty-five minutes, no charge, no pushy follow-up. You'll talk to someone who builds software, not someone who sells it. You keep the workflow map either way.