Orca Trust Center

Your numbers stay in your database

Orca turns your NetSuite data into management reports, budgets and month-end commentary. This page sets out how we protect that data. Your IT or security team can request any of our policies below.

Updated 25 October 2026

Our commitments

Incident notice
24 hours

We tell you within 24 hours of confirming an incident that affects your data.

Data residency
Canada

Your figures and personal data stay in Canada, in a database you own.

NetSuite access
Read-only

The connector reads from NetSuite through a role you control. It never writes.

Security checks
Every change

Access tests, a secret scan and a dependency audit must pass before any change ships.

Documents

Our policies are available to customers and prospective customers. Request one or all of them and we'll send them by email.

Architecture overview
Components, data flow, hosting and encryption.
Request
Information security policy
Accounts, devices, access and secrets.
Request
Privacy and data handling
What data Orca holds, where, and for how long.
Request
Incident response plan
Roles, steps and how we notify you.
Request
Vulnerability management
Scanning, fix times and exceptions.
Request
Security testing
Tests on every change, before go-live and yearly.
Request
Logging and monitoring
What is recorded, retention and alerts.
Request
Backup and recovery
Backups, restore targets and restore tests.
Request
Business continuity
How Orca keeps running if we are unavailable.
Request
Change management
How changes are reviewed, tested and released.
Request
AI tools
Which AI tools we use and what they can see.
Request
People security
Background checks, training and leaving.
Request
Subprocessor list
Every provider, what it touches and where.
Request

Controls

What is in place today, and what is planned with its date.

In placePlanned
Data protection
  • Encrypted connections (HTTPS) only
  • Database in your own cloud account, in Canada
  • Passwords stored salted and one-way hashed (scrypt)
  • Mail server password encrypted (AES-256)
  • Database public interface off, row-level security on
  • Admin console writes use bound parameters only
  • Daily database backups, kept 7 days
  • Timed restore testPlanned: December 2026
Access control
  • Roles limited by subsidiary and account
  • Hidden accounts filtered in the database
  • Sign in with Microsoft, with your multi-factor policy
  • Account locks after 5 failed attempts
  • Mail server changes need your password again
  • Sign-out after 30 minutes idle, 12 hours at most
  • Quarterly review of our own access
Product security
  • Access tests for every role on every change
  • More than 3,500 automated tests
  • Independent code scan: six high-severity findings closed
  • Secret scan of the full code history
  • Continuous dependency and code scanning
  • Protected main branch with four required checks
  • Authenticated security scan before each go-live
  • Independent penetration testPlanned: June 2027
Monitoring and response
  • Audit trail that cannot be changed or deleted
  • Every sign-in attempt recorded
  • Written incident response plan
  • Central logs and alerts in your Azure tenantPlanned: Before go-live
  • Sign-in records deleted after 13 months
Our company
  • Two-step sign-in on every work account
  • Firewall on, work folders private
  • Encrypted work devices
  • Written confidentiality obligations
  • Background check before access
  • Access limited to named, screened individuals
  • Remote locate and erase enabled
  • Yearly security training
  • Named backup contact for incidents
  • Policies reviewed every 12 months

How your data moves

Your NetSuite
Connector reads only

A scheduled script inside your NetSuite reads what changed since the last run, using a read-only role you control.

Orca
Passes it through

Each batch is checked against a key issued for your company only, then written to your database. Nothing is kept on the way.

Your database
You own it

A database in your own Azure tenant or your own Supabase organization, in Canada. Orca reads your reports from here.

Refreshed on a schedule you set, as often as every 15 minutes.

Subprocessors

The providers involved in running Orca. We give customers at least 30 days' notice before adding one that touches their data.

ProviderUsed forWhere
Microsoft AzureHosting and database, in your own tenantCanada Central
SupabaseDatabase, in your own organization (alternative to Azure)Canada Central
VercelRuns Orca where you choose our hostingMontréal
Microsoft Entra IDMicrosoft sign-in (optional)Your tenant
Your mail serverInvitations and password resetsYour choice
Azure OpenAIAI commentary, off unless you switch it onCanada
AnthropicAI commentary, off unless you switch it onUnited States
GitHubSource code (no client figures)United States
Aikido SecurityCode and dependency scanning (no client figures)United States

Common questions

Do you have SOC 2 or ISO 27001?

Not today. We are a small team, so instead we share our written policies, our test results and our answers to your security questionnaire, and we commit to an independent penetration test by June 2027.

Can Orca run in our own cloud?

Yes. Orca and its database can run in your own Azure tenant, built with your IT team or provider. Your administrators then control access, logs and keys.

What does the AI see?

AI commentary is off unless you switch it on. If you do, it drafts text from figures summarised by month and line, never from individual transactions. It never changes a number, and a person approves every draft.

Does Orca write to NetSuite?

Not unless you switch it on. The connector only reads. By default, budgets leave Orca as a file that a person imports into NetSuite. If you choose, Orca can send an approved budget straight to NetSuite, using a separate NetSuite token you control. You can also require a second person in Finance to approve each send.

What happens if we leave?

Your database stays yours, with all its history. Within 30 days we remove our access and confirm in writing what we deleted.

Report a vulnerability

Email security@voconsulting.ca. We acknowledge reports within two business days. Please don't test against a customer's environment or access anyone's data.