Trust Center
Our approach to security starts with a different question than most vendors answer. Instead of asking “who is allowed to see this data,” we ask “does anyone need to see it at all.” For most of what Nera does, the answer is no, not even us.
This page covers what our security and privacy posture actually looks like today: what’s certified, what’s architectural, and what’s still in progress. We’d rather tell you exactly where we stand than round up. Reviewing Nera for a bank or credit union? See what we provide for your review.
Certifications & Compliance
Working With Regulated Data
What’s in scope, what isn’t, and what we need from you before regulated data reaches Nera.
Covered under a signed agreement
The Nera ChatApp, the Excel add-in, and API/SDK access are covered by our BAA and DPA. A signed BAA must be in place before any protected health information is submitted to Nera, and a DPA before personal data subject to GDPR is submitted. We provide our standard BAA and DPA; email info@nera.systems to start.
Not covered
Support channels, email correspondence, and any trial or sandbox environment are not covered, so please don’t send regulated data through them. Third-party tools you connect to Nera are governed by your agreement with that provider, not by ours, and you’re responsible for evaluating them.
Your side of the arrangement. Enforce SSO and multi-factor authentication for your users, keep your encryption keys under your own control, remove access promptly when people leave, and confirm that your intended use is permitted under the regulations that apply to you. Nera’s output is advisory and reviewed by a person; it should not be the system of record for regulated data, and it should not be used for automated decisions about individuals.
For Banks and Credit Unions
How Nera fits the information security and third-party reviews that community banks and credit unions run, and what we provide for yours.
The question your examiner will ask. Bank and credit union examiners now ask, as a routine part of exams, which AI tools are in use, what customer or member data each vendor receives, and who can read it when it arrives. For most AI tools, the honest answer is a vendor contract: the provider receives readable data and promises to handle it well.
With Nera, the answer is a data path. Customer and member data is encrypted with keys your institution holds before it leaves your environment. The AI model receives the question and the structure of the data, never the values. Neither Nera nor the model provider can read your data at any point. If you shut Nera off, there is nothing readable to claw back, because none was ever held.
| Framework you are examined under | Who it applies to | How Nera supports your file |
|---|---|---|
| Interagency Guidelines Establishing Information Security Standards (GLBA, 12 CFR Part 30, Appendix B) | Banks | Treat Nera as a service provider and document it. We provide architecture and data-flow documentation showing customer information is never readable by Nera or the model provider, plus our DPA and subprocessor list. |
| Interagency Guidance on Third-Party Relationships: Risk Management (Fed, FDIC, OCC, June 2023) | Banks | Our due diligence package (below) covers the information security review the guidance describes, and our security team is available to your reviewers directly. |
| NCUA Part 748 and Appendix A (GLBA safeguards for member information) | Credit unions | Member data stays encrypted with your keys and is never readable by Nera or the model provider, which you can document as a data path rather than a vendor promise. |
| NCUA Letters 07-CU-13 and 01-CU-20 (third-party due diligence) | Credit unions | NCUA cannot examine technology vendors directly, so your own file carries the weight. We provide the documentation that file needs: how the product works, what it receives, and our safeguards and controls. |
| Computer-Security Incident Notification Rule (OCC, Fed, FDIC, 2021): banks notify their regulator within 36 hours | Banks | Nera notifies you within 24 hours of a confirmed incident affecting your data, or sooner if your agreement requires, so you can meet your 36-hour window. |
| NCUA Part 748 cyber incident notification (72 hours) | Credit unions | Nera notifies you within 24 hours of a confirmed incident affecting your data, or sooner if your agreement requires, inside your 72-hour window. |
| CSBS AI Supervisory Framework (state examiners, September 2026) | State-chartered banks | The framework places use cases involving sensitive personal data in its highest risk tier. Nera's architecture keeps that data unreadable to the AI, and we document it for your risk-tiering worksheet. |
Nera supports your compliance program; it does not make your institution compliant. Each institution remains responsible for its own program and for confirming that its intended use is permitted.
Your due diligence package
Available under NDA to banks and credit unions evaluating Nera:
- System architecture and data-flow documentation
- Our policy set: access control, incident response, data retention and related policies
- Subprocessor list and Data Privacy Addendum
- Completed vendor questionnaire, in your format or the SIG Lite
- Current SOC 2 Type II and penetration test status and timeline
- A call between your security team and ours
Where we stand today
- Data residency: United States regions only, on Google Cloud and Microsoft Azure
- Model training: never on your data, by contract and by architecture
- Model providers: US-based only (Anthropic, Google, OpenAI), or your own API keys
- Encryption keys: held by your institution
- Deployment: cloud today, with on-premises or hybrid deployment available
- SOC 2 Type II: in progress
- Independent penetration test: planned, alongside SOC 2
- Business continuity and disaster recovery plan: being formalized, with defined recovery objectives
Starting with Nera. Banks and credit unions start with a paid pilot on one workflow, so your risk and IT teams can review the data path on a real use case before wider rollout. Talk to us about a pilot.
The Architecture Behind the Claims
Most security pages describe controls: who can access what, how access is logged, how breaches are handled. Those controls matter, and we have them. But they’re not the reason Nera is different.
The reason is architectural: customer data is encrypted before it ever leaves your environment, using keys you hold. The AI model receives your question and the structure of your data, never the underlying values. Computation happens on encrypted data. Results come back encrypted and are decrypted with your key.
Neither the model provider (Anthropic, Google, OpenAI) nor Nera itself ever has access to your data in a readable form, at any point in the process. That’s not a policy we’ve committed to. It’s a property of how the system works.
The practical consequence: if Nera’s infrastructure were compromised, there’s nothing in it for an attacker to read. Your data was never there in a form anyone could use.
What This Means Day to Day
Encryption
Your data is encrypted client-side, in your environment, before it’s transmitted. AES-256 at rest, TLS 1.2+ in transit.
No training on your data
Your data is never used to train or improve any model, Nera’s or a third party’s. This is both a contractual commitment and an architectural fact, since we can’t train on data we can’t read.
Model choice, your control
Nera works with Anthropic Claude, Google Gemini, and OpenAI GPT models today, with support for switching models mid-conversation. You can also supply your own model API keys.
Data residency
All production data is currently hosted in United States regions, with no replication elsewhere by default.
Access control
Multi-factor authentication is enforced across all infrastructure. Production access is role-based and limited to named engineering staff.
Track record
Nera has experienced no information security breach and no non-minor security incident since founding in November 2023.
Where We’re Early, and Where We’re Not
Nera is a young company, and we think the honest version of that fact serves you better than a page full of green checkmarks.
What’s mature
The core architectural guarantee, encryption, and the fact that customer data is never readable by Nera or by the model provider. This isn’t a roadmap item. It’s how the system has worked since day one.
What’s in progress
Formal third-party attestation (SOC 2 Type II), independent penetration testing, and a fully documented business continuity and disaster recovery program. These are standard expectations for enterprise procurement, and we’re building toward them on a committed timeline rather than claiming them early.
We’d rather have this conversation directly with your security team than leave it to a badge to answer. If you’re evaluating Nera for a regulated use case, we’re glad to walk through our data flow design, our compliance roadmap and timeline, and answer your team’s specific questions.
Subprocessors
Nera uses a deliberately small set of subprocessors:
| Subprocessor | Purpose | Data Involved |
|---|---|---|
| Google Cloud Platform | Cloud infrastructure, hosting | Encrypted customer content, operational metadata |
| Microsoft Azure | Cloud infrastructure (secondary), hosting | Encrypted customer content, operational metadata |
| Anthropic (Claude) | AI model provider | Question and data structure only, never underlying values |
| Google (Gemini) | AI model provider | Question and data structure only, never underlying values |
| OpenAI (GPT) | AI model provider | Question and data structure only, never underlying values |
| Stripe | Payment processing | Billing and transaction data |
We’ll notify customers before adding a new subprocessor with access to their data. Full details are in our DPA.
Infrastructure
Nera runs on Google Cloud Platform (primary) and Microsoft Azure (secondary), both of which maintain SOC 2 Type II and ISO 27001 certification at the infrastructure layer under their own published data processing addenda:
Google Cloud Data Processing Addendum
Microsoft Products and Services Data Protection Addendum
All production data is hosted in United States regions, with no replication elsewhere by default. Nera has no owned data centers or physical infrastructure; physical security is inherited from these providers’ published certifications.
Documents
The policies and agreements that govern how Nera handles your data, and the answers your security team will want first.
Security & Privacy FAQs
Answers to the questions security and compliance teams ask most about how Nera handles data.
Privacy Policy
What personal information we collect, how we use it, and the choices and rights you have.
Data Privacy Addendum
Our commitments as a processor: security measures, subprocessors, deletion, audits, and international transfers.
Terms of Service
The agreement governing use of the Nera platform, including data ownership and the no-training commitment.
Website Terms of Use
The terms that govern browsing nera.systems, separate from the Terms of Service for the product itself.
Available on Request
Under NDA: system architecture and data-flow documentation, our current policy set (access control, incident response, data retention, and related policies), our subprocessor list, and a completed vendor questionnaire in your format or the SIG Lite.
Questions?
Reach out to your Nera contact, or email us directly to get your security team connected with ours. We’re glad to walk through the architecture, the compliance roadmap, and your team’s specific questions.
Contact usThis page is provided for informational purposes only and does not constitute legal or compliance advice. Please consult your own advisors about your obligations.
Last updated: November 2026