# Corporate Security, Risk, Change and ESG Policy

Version 1.0 · Last reviewed 2026-10-26 · Owner: Delora Legal (security@deloralegal.com)

Status: Draft v1.0. Describes controls in place today. Adoption date to be set.

## Purpose

This policy sets out how Delora Legal keeps track of what it owns and runs, classifies and handles information, assesses risk, changes its software safely, trains and guides the people who work on it, protects the places where its systems live, and conducts itself as a business. It combines the corporate governance rules that sit around the technical security policies.

## Scope

It applies to everyone who works on Delora (employees, contractors, advisers), to every asset used to deliver the service (laptops, cloud accounts, source code, data), and to Delora's business conduct. No server of Delora's own runs the service; a build and test machine in the owner's office holds no customer data. Delora is run today by its owner, who holds every role in this policy. The roles are written separately so the policy works when the team grows.

## Roles and responsibilities

| Role | Responsibility | Held by today |
|---|---|---|
| Security owner | Owns this policy, the asset inventory, the risk register, exceptions and the yearly review | The owner |
| Risk owner | Accepts, mitigates or transfers each identified risk | The owner |
| Engineers | Follow the change process and the project's written engineering rules; write tests with each change | The owner |
| Everyone | Complete training, follow the code of conduct, report concerns and incidents | The owner |

## Policy

### Asset management

1. Delora must keep an inventory of hardware, software and cloud assets, with a named owner for each, and review it at least yearly and when an asset is added or retired.
2. Every laptop used for Delora work must be enrolled with the Vanta Agent so the device inventory and its protection status are maintained automatically.
3. Every page, route handler and server action in the application must be listed in the application inventory with the access it enforces. A change that adds or removes one without updating the list must fail the build.
4. Assets must be returned or wiped and their access removed when a person leaves.

### Data classification and handling

5. All information must be assigned one of four classes: Restricted, Confidential, Internal or Public, and handled according to the table below.
6. Restricted identifiers must be sealed with AES-256-GCM before storage, shown masked, decrypted only when a USCIS form is filled, and never logged or sent to any AI service.
7. Real client data must exist only in production. Development, tests, staging, demos and the repository must use synthetic data only.
8. Personal data must never appear in application logs, tickets, screenshots or chat. Logs carry ids, not names, email addresses or identifiers.

### Risk assessment

9. The Security owner must carry out a risk assessment at least yearly, and after a major change, an incident or the addition of a vendor. It must cover risks to customer data and to the service, including fraud and insider risk, vendor risk, and legal and regulatory risk.
10. Each risk must be scored on likelihood and impact, given a treatment (mitigate, transfer, accept or avoid) with an owner and date, and recorded in the risk register in Vanta. High risks must be reviewed quarterly.
11. A risk may be accepted only in writing by the Risk owner, with the reason recorded.

### Change management

12. Every change to production must go through a pull request with the required automated checks passing, and the author or reviewer must read the full diff before merge.
13. Changes with security, data or migration impact must run on staging, with synthetic data, before they reach production.
14. Database changes must be versioned migrations, applied by the production build under a separate migration role before the new code serves traffic. Migrations must be idempotent, and a destructive migration must have a restore point noted in its pull request.
15. Secrets and configuration must be changed only in the hosting environment and password manager, never in the repository.
16. An emergency change is allowed only to stop an active incident. It must still be a pull request with passing checks. Review may follow within one business day, and the incident record must link to it.
17. Vulnerabilities must be fixed or mitigated within these proposed times from discovery: critical within 7 days, high within 30 days, medium within 90 days. Lower findings are fixed in planned work or accepted in the risk register.
18. An independent penetration test must be carried out at least yearly and after major architecture changes, against staging.

### Personnel conduct, privacy and training

19. Everyone with access must accept this policy and the security policies before access is granted, and yearly after.
20. Everyone must follow the code of conduct below.
21. Everyone must complete security awareness training at joining and yearly. Engineers must also complete secure development training. Completion must be tracked in Vanta.
22. A background check must be completed, where the law allows, before a person receives access to production or customer data.

### Physical and cloud environment

23. Delora must not operate offices, data centers or servers. Customer data must be processed only on infrastructure run by named vendors listed on the public subprocessors page.
24. Physical security of that infrastructure is inherited from the vendors. Delora must collect and review each high-risk vendor's current SOC 2 report at least yearly and confirm it operates the user entity controls the report lists.
25. Where people work from home or elsewhere, the home-office rules below must be followed.
26. Production and staging must remain separate: their own database, secrets and data, with production secrets scoped to the Production environment.

### Environmental, social and governance conduct

27. Delora must act in line with the modern slavery, community and inclusive hiring commitments in this policy, and must not publish statements about them that it cannot support.

## Asset classification and inventory

### Hardware

Hardware is limited to the laptops and phones used by people who work on Delora. Each is recorded with its owner, operating system, encryption status, screen lock, update status and last check-in. The Vanta Agent supplies this on laptops (installation is an open owner step), and phones used for MFA are listed in Vanta's people records. Devices must meet the endpoint standard in the Access, endpoint and network security policy. Delora owns no servers or network equipment.

### Software and cloud services

| Asset type | Where it is tracked | Notes |
|---|---|---|
| Source code and CI | GitHub repository and automated checks | Dependencies are pinned and updated through reviewed pull requests |
| Hosting | Vercel production and staging environments | Production and staging use separate secrets |
| Database | Neon projects for production and for staging | Production holds all firm content; staging holds synthetic data only |
| Cloud account | AWS (S3, SES, IAM) | S3 is for documents once document upload goes live; it is not live yet and no production bucket exists |
| AI provider | Anthropic account, separate keys for production and staging | Intake only |
| Other services | Resend, Stripe, Better Stack, SonarCloud, Vanta, Google Workspace, domain registrar | Customer-facing subprocessors are listed on the public subprocessors page |
| Secrets | Hosting environment variables and the password manager | Never in the repository |

The full vendor list, with risk ratings and the evidence to collect from each, is in the vendor management policy.

### Application assets

The application inventory is generated, not hand-kept. It lists every page, route handler and server action with the access each one enforces, and automated tests fail when the application gains or loses an entry that is not matched in it, including end-to-end probes that try each entry signed out, with the wrong role, and with another firm's identifiers. The commands and check names are in the internal detail document, available under NDA.

## Data classification, access and impact

| Class | Examples | Handling rules | Who may access | Impact if exposed |
|---|---|---|---|---|
| Restricted | SSN, A-Number, passport or travel document number, USCIS online account number | Sealed with AES-256-GCM, bound to the firm; shown masked; decrypted only when a USCIS form is filled; never logged; never sent to any AI | No person reads raw values in the application | High: severe harm to individuals and to the firm |
| Confidential | Client and case data, intake transcripts, documents (when upload is live), generated forms, firm user accounts, secrets, API keys | Tenant-isolated by row-level security; production only; synthetic copies elsewhere; no PII in logs; TLS in transit | Members of the owning firm according to their role (admin, attorney, paralegal). Delora staff do not sign in to customer firms | High |
| Internal | Source code, runbooks, internal documents, metrics without personal data, audit-log ids | Company systems only; not published unless intentionally | Delora personnel | Low to moderate |
| Public | Marketing site, Academy content, published policies, the subprocessors list | None beyond accuracy review; counsel reviews privacy and terms wording | Anyone | None |

Handling rules that apply to every class: data is classified when created; the highest class in a record sets the handling of the whole record; downloading Confidential or Restricted data to a laptop, pasting it into personal tools or into any AI tool other than the application's approved integration is not allowed; and disposal follows the retention schedule in the data retention policy.

## Risk assessment

The Security owner lists risks once a year using the process in the risk management policy. Each is scored from 1 to 5 on likelihood and on impact; the score is the product. Scores are grouped as high, medium and low. The treatment is mitigate (with an owner and a date), transfer (insurance or contract), accept (signed off in writing) or avoid.

A starter register of fifteen risks is drafted and is entered into Vanta as the first register. The current top risks and their treatments are in the internal detail document, available under NDA.

The draft register suggests considering cyber liability insurance. No policy is claimed here; whether to buy one is a question for the yearly assessment.

## Change management and restrictions

### Pipeline

Every change opens a pull request and runs automated checks: type checking, linting, unit and form-filling tests, end-to-end tests and dependency and secret scanning. Changes go to a staging environment with its own database, secrets and synthetic data before production. Production builds apply database migrations first, under a separate migration role, and dependency updates arrive as pull requests. The check names, scripts and branch rules are in the internal detail document, available under NDA.

### Restrictions

- Changes to the protected branches go through pull requests with required checks. Protection is in place on the production branch; extending it to every branch and adding further required checks is still to do.
- Required approvals are proposed at one reviewer once a second engineer joins. While there is one engineer, the compensating control is that every change is a pull request with automated tests and security scans, and the owner reviews the full diff before merging. This is recorded as an approved exception.
- Staging and previews must never use production data or production secrets.
- Model and prompt changes to the AI intake must keep prompts static, keep the Claude history append-only, and keep the safety evaluations passing.

### Emergency changes

1. Confirm the change is needed to stop an active incident, and note it in the incident record.
2. Make the change as a pull request. Required checks still run; if the automation is unavailable, run the documented local fallback and record the result.
3. Merge once checks pass. Review of the diff may follow within one business day.
4. Link the pull request to the incident record and include the change in the post-incident review.

### Vulnerability fixes and penetration testing

The proposed fix times are 7 days for critical, 30 for high and 90 for medium findings. Findings come from automated scanning, penetration tests and vulnerability reports, and are tracked until closed. The scope for an external penetration test (staging only, synthetic data) is written. The test is planned and has not yet taken place.

## Code of conduct

Everyone who works on Delora must:

1. Act honestly and respectfully with customers, colleagues, vendors and researchers.
2. Protect client confidentiality. Immigration clients are vulnerable; their information is handled as if it were their own.
3. Never misstate Delora's security or compliance status. SOC 2 is described as a target, never as an achievement, until a report exists.
4. Keep a human in the loop: AI output is a draft, nothing reaches a client or USCIS without attorney approval, and the product never gives legal advice.
5. Use synthetic data in every place except production, and report accidental exposures at once.
6. Declare conflicts of interest, and not accept gifts or payments that could influence a vendor or customer decision.
7. Raise concerns without fear of retaliation. Concerns are raised to the owner or, if they concern the owner, to an adviser named in Vanta (proposed).

Breaches of the code are handled under "Enforcement".

## Training

| Training | Who | When | State |
|---|---|---|---|
| Security awareness (Vanta's built-in course) | Everyone with access | At joining and yearly | Planned; completion tracked in Vanta |
| Employee privacy: handling client personal data, sealed identifiers, no PII in logs or chat, synthetic data only, routing data subject requests to the firm, reporting incidents | Everyone with access | At joining and yearly, within the awareness course or a short briefing | Proposed; to be recorded with the awareness course |
| Secure development: the written engineering rules, tenancy guide and forms guide read and acknowledged; a yearly refresher on web application security, multi-tenant isolation, secrets handling and the risks of AI prompts and outputs | Engineers | At joining and yearly | The reading is the existing onboarding rule; the formal yearly refresher is proposed |
| Incident response tabletop | Incident commander and anyone with a role | Yearly | Planned |

Background checks use Vanta's background-check integrations, for everyone with access to production or customer data.

## Physical and cloud environment security

Delora has no offices, data centers or servers. Customer data is held by:

- Vercel (hosting, in transit only for customer data),
- Neon (the database, in US East),
- Amazon Web Services (S3 for documents, and SES for email), and
- Anthropic (intake messages, with SSNs removed and A-numbers masked).

The physical security of these data centers (access control, environmental protection, redundant power) is inherited from those vendors. Delora's evidence is their independent SOC 2 reports, which are being collected into Vanta as owner steps; until they are filed, Delora cannot show them to a customer. The reports carve these vendors out as subservice organizations, and Delora reviews each report yearly for exceptions and for the controls it must operate itself.

**Cloud environment rules.**

1. Production secrets must be marked sensitive and scoped to production only; staging uses different values (the scoping is an owner step to be evidenced).
2. Preview deployments must be protected by sign-in (the owner confirms the setting).
3. The database role used by the application is restricted (no superuser, no BYPASSRLS; checked at start-up), and a separate schema owner role is used only for migrations and restores.
4. Document upload is not live and no production bucket exists yet. When it goes live, the bucket must keep default encryption, versioning and public access blocked, and the application's cloud identity must be limited to the access it needs; confirming those settings will be an open owner step.
5. The AWS root user must not be used after setup, and AWS console access must use named identities with MFA (an open owner step).

**Home-office and mobile working rules.**

1. Lock the screen whenever you step away, and set it to lock automatically after five minutes or less.
2. Work on Delora systems only on a device that meets the endpoint standard, not on shared or public computers.
3. In public places, position the screen so others cannot read it, use a privacy filter where practical, and do not discuss customer matters aloud.
4. Avoid administrative work on untrusted networks; use a personal hotspot rather than an open public network.
5. Do not print customer data or keep paper copies of secrets.
6. Report a lost or stolen device at once to security@deloralegal.com.

## ESG commitments

### Modern slavery statement

Delora Legal is a small software company. It has no factories, no physical supply chain, no recruitment agencies and no labour-hire arrangements. Its suppliers are software and cloud services listed in the vendor management policy and, for customer-data processors, on the public subprocessors page. Delora is run by its owner today and has no employees.

The UK Modern Slavery Act 2015 requires an annual statement only from commercial organisations that carry on business in the UK and meet a turnover threshold of £36 million. Delora is a one-person United States company and does not meet it, so no statement is legally required. Delora publishes this one voluntarily.

Delora commits to:

1. Not knowingly engage a supplier, contractor or recruiter that uses forced labour, child labour or human trafficking.
2. Ask about modern slavery as part of the due diligence on any new vendor that provides labour or services in person, and to review the supplier's published statements where they exist.
3. Pay contractors and staff fairly and on time, under written agreements, and never withhold identity documents.
4. Act on any concern raised about a supplier or about Delora, by reviewing it, ending the relationship if it is confirmed, and recording the outcome.
5. Review this statement every year with this policy.

Concerns can be sent to legal@deloralegal.com.

### Community

Delora has no community or charitable program today, and does not claim one. It commits to:

1. Keep the client-facing intake available in English and Spanish, and write product text in plain language.
2. Credit security researchers who report issues in good faith, with their consent.
3. Decide at each yearly review whether it can responsibly adopt a community program, and publish any program only once it exists.

### Diversity, equity and inclusion

Delora has no employees today, so it has no workforce statistics and publishes none. As it hires, it commits to:

1. Recruit on skills and ability to do the work, using written job descriptions and the same structured questions for each candidate for a role.
2. Not discriminate on race, colour, national origin or immigration status where lawful, religion, sex, gender identity, sexual orientation, age, disability, pregnancy, veteran status or any other characteristic protected by federal, state or local law.
3. Provide reasonable accommodations in the hiring process and at work, and keep the hiring process accessible.
4. Advertise roles widely and in plain language, and keep pay and role requirements clear.
5. Respect the many communities Delora's customers and their clients come from, including by keeping its product and copy respectful of people in the immigration process.
6. Review the hiring process for fairness each time it is used and record what it changes.

## Current implementation

| Control | State |
|---|---|
| Application route and action inventory | In place and enforced by tests and end-to-end probes |
| Hardware inventory via the Vanta Agent | Planned: owner step |
| Vendor inventory with risk ratings | Drafted; collection of vendor reports is in progress |
| Data classification | Drafted; sealed identifiers and masking enforced in code |
| Synthetic data outside production | In place; a repository test fails on SSN-like and A-number-like values |
| Annual risk assessment and register | Starter register drafted; first assessment planned |
| Pull requests with CI, staging, migrations by migration role, Dependabot | In place |
| Branch protection and required reviews | Required checks in place on the production branch; required reviews not in place (single engineer) |
| Emergency change procedure | Written, adopted with this policy |
| Fix times for vulnerabilities (7, 30, 90 days) | Proposed |
| Penetration test | Not yet performed; scope written; planned |
| Code of conduct | Drafted and adopted with this policy |
| Security awareness training and background checks | Planned |
| Vendor SOC 2 reports for physical security | Being collected (owner step) |
| Home-office rules | Adopted with this policy |
| Modern slavery, community, DEI commitments | Published as commitments only; no programs or statistics claimed |

## Exceptions

Exceptions must be requested in writing to the Security owner with the risk, the compensating control and an end date, and are recorded in Vanta and reviewed at least quarterly. Open exceptions today: required pull-request approvals (single engineer, compensated by green checks and the owner's review of every diff), some required checks and protections not yet in place, and no recorded penetration test. The detail is in the internal detail document, available under NDA.

## Enforcement

Breaking this policy may lead to loss of access and, for employees and contractors, disciplinary action up to termination of employment or contract. Breaches of the code of conduct are reviewed by the owner, or by the named adviser if the concern is about the owner. Vendors that break contract terms on security or conduct may be removed.

## Review

The Security owner reviews this policy at least once a year, and after a major change, incident or new vendor, and records the review in Vanta. Owner: Delora Legal (security@deloralegal.com). Next review due by 2027-10-26.

## Related documents

- Product and application security policy
- Data security and privacy policy
- AI governance policy
- Access, endpoint and network security policy (available on request from the Trust Center)
- Incident Response Plan, and Business Continuity and Disaster Recovery Plan (available on request from the Trust Center)
- Internal policy drafts, available on request: information security; risk management; change management and secure development; personnel security and acceptable use; data classification, retention and disposal; vendor and subprocessor management
- Corporate security, risk, change and ESG policy: internal detail (available under NDA)
- [Trust Center](https://deloralegal.com/trust) and [Subprocessor list](https://deloralegal.com/subprocessors)
