Trust Center
Where your data goes, who can see it, and what we are not.
Written for the security reviewer: hosting, encryption, identity, credentials, AI providers, sub-processors and regulatory status — including the certifications we don't have.
Last reviewed October 20, 2026.
Status at a glance
SOC 2 Type II
CurrentAnnual audit; report under NDA.
GDPR
DPA on requestUS hosting; SCCs; EU residency via on-prem.
EU AI Act
DocumentedTransparency duties since Aug 2026; high-risk obligations 2 Dec 2027.
LGPD · Ley 21.719
DocumentedBrazil in force; Chile from 1 Dec 2026. On-prem available.
HIPAA
Not certifiedWe do not sign BAAs or accept PHI.
ISO 27001
Not certifiedOn the certification roadmap; no date committed.
Where it runs
Where the cloud platform runs
Microsoft Azure, United States. One production environment for all regions after the 2026 region unification; portal URLs may still carry a regional prefix. There is no EU or Latin American cloud region today — customers with residency requirements use Sovereign Suite, the whole platform on their own infrastructure.
What runs on your machines
Studio (the bot IDE) and Bot Runner are Windows applications. Bots execute on your machines or VMs; the runner opens an outbound connection to the orchestrator and needs no inbound ports from the internet. Screen data processed by a bot stays on the machine unless a step sends it somewhere.
Encryption
TLS 1.2 or higher in transit (HTTPS and WSS); AES-256 at rest in the cloud platform. Sessions use short-lived JWTs.
Backups and continuity
Daily backups of the cloud platform within Azure; recovery procedures are part of the SOC 2 scope and described in the report. We do not publish RPO/RTO figures outside it.
Identity and access
Single sign-on
Google Workspace and Microsoft Entra ID. Multi-factor authentication is enforced by your identity provider; a native portal MFA is on the roadmap.
Roles
Portal roles: Owner, Admin, Security Admin, Member, Billing Contact, Guest. Orchestrator roles: Admin, Analyst, Developer and Operator (the last two with the Advanced Access Management add-on).
Security Groups
Scope orchestrators, workflows and Bot Runners per team or per client — the isolation an agency uses between its customers' tenants.
Audit logs
Owner and Security Admin can filter and export audit logs (CSV) for up to 60 months. Every workflow run keeps a step-by-step log; RPA launches keep console logs and run history.
Credentials and run data
Bot credentials
Stored in Windows Credential Manager on the machine where the bot runs, retrieved by activities at run time. They are not uploaded to the cloud. There is no central cloud vault for RPA credentials and no CyberArk or HashiCorp Vault integration today.
App connections and AI keys
AI Workflows connections, AI provider keys and Variables are encrypted server-side, cannot be read back after saving (only replaced) and are masked in logs.
Run data
AI Workflows keeps run data for 30 days; a flow paused for an approval cannot resume after that window. IntelliDocs stores nothing after a document is processed and the result is returned.
AI providers and your data
Your model, your contract
Bring your own key for OpenAI, Anthropic, Google Gemini, Azure OpenAI, OpenRouter, Cloudflare AI Gateway or any OpenAI-compatible endpoint, including self-hosted models. Those calls are governed by your provider agreement; ElectroNeek sees counts, not content.
Included document and Easley AI credits
Document intelligence (IntelliDocs) and Easley AI run through our provider accounts under API terms that exclude training on customer data: the OpenAI API, with Google Cloud Vision for OCR. Agents and AI Workflows use your own key.
No training, no retention by us
ElectroNeek does not train models and has no models of its own. Prompts and documents are sent to the provider for the request and not stored by us afterwards; provider-side retention follows their API terms, and zero-retention options are available on enterprise request.
On-prem with the model
Sovereign Suite installs the platform and an LLM inside your network, so neither documents nor prompts leave it.
Sub-processors
The DPA is the authoritative list and we notify DPA signatories of changes. This is the current set for the cloud platform; on-prem deployments have none of these except the support tools you choose to use.
| Provider | Purpose | Region |
|---|---|---|
| Microsoft Azure | Cloud hosting of the platform (US) | United States |
| OpenAI | Document intelligence (IntelliDocs) and Easley AI credits | United States |
| Google Cloud | OCR (Cloud Vision) for scanned documents | United States |
| Your AI provider | Only if you connect your own key | Per your contract |
| Zendesk | Support tickets | United States |
| HubSpot | Website forms, CRM and email | United States / EU |
Regulation, honestly
EU AI Act
ElectroNeek is a general-purpose automation platform; whether a deployment is high-risk depends on your use case. Transparency obligations apply since August 2026; high-risk obligations now start 2 December 2027 after the Digital Omnibus (Reg. 2026/1744). We provide model cards for included models, a human-oversight description, and the audit-log specification your DPO will ask for.
GDPR
The cloud platform is US-hosted; transfers rely on Standard Contractual Clauses in our DPA. Customers who cannot transfer personal data outside the EU run Sovereign Suite on EU infrastructure, where ElectroNeek is typically not a processor at all.
LGPD (Brazil) and Ley 21.719 (Chile)
Both permit international transfer with safeguards; both are satisfied most simply by on-prem for regulated sectors. Our team and partners in Latin America support DPO questions in Spanish and Portuguese.
HIPAA (US)
ElectroNeek is not HIPAA certified, does not sign Business Associate Agreements and must not be used to process protected health information. We say this wherever it matters, and we decline healthcare deals that need it.
Responsible disclosure
Found something? Tell us.
Email security@electroneek.com with reproduction steps. We acknowledge within one business day and keep you informed until the fix ships. The same contact is published at /.well-known/security.txt.
In scope: *.electroneek.com, the cloud platform, Studio and Bot Runner. Out of scope: social engineering, denial of service, third-party services.
Safe harbor: good-faith research under this policy is authorized and we will not pursue legal action against researchers who follow it.
Questions security reviewers ask
Yes, under NDA, through the form on this page. The report covers the cloud platform and the processes around it.
In Microsoft Azure in the United States for the cloud platform. Bot execution data stays on your machines. If US storage is not acceptable, Sovereign Suite runs everything on your infrastructure.
No. Calls go through API terms that exclude training. ElectroNeek does not train models. If you bring your own key, your provider contract governs retention.
No. We do not sign BAAs and PHI must not be processed on the platform.
They live in Windows Credential Manager on the runner machine and are never uploaded to the cloud. Treat the runner machine as you would any server holding credentials.
SSO with Google and Microsoft; MFA is enforced by your identity provider. A native portal MFA is planned.
Yes. Request it through the form; it lists the sub-processors above and the Standard Contractual Clauses for transfers.
Email security@electroneek.com (also published at /.well-known/security.txt). We acknowledge within one business day and work with researchers in good faith.
Request the SOC 2 report, a DPA or a questionnaire answer
Say what you need in the message; we reply within one business day, NDA first where required.