Built so your security review is a formality, not a blocker.
Laand is standalone B2B hiring infrastructure engineered to protect enterprise assets, eliminate candidate bias, and secure data workflows. By decoupling talent identity from data processing and running on zero-data-retention infrastructure, we structurally remove the legal and security liabilities that come with a legacy ATS.
- Candidate PII anonymized by default
- Zero LLM training on your data
- PCI-DSS Level 1 payments via Stripe
- 2-hour session timeout
- AWS SOC 2 Type II / ISO 27001 infrastructure
Last updated: August 2026
The six questions your security team will ask
Do you store candidate PII we'd be liable for?
Not during sourcing or evaluation. Profiles stay pseudonymized until your team explicitly unlocks one.
Is our hiring data used to train AI models?
No. We use enterprise-tier providers under zero-data-retention terms. Prompts are processed in memory.
Who owns the work candidates submit?
The candidate, until a valid Unlock Event transfers it to you in full. Your problem definitions are always yours.
How are recruiter accounts protected?
12-character minimum passwords, bcrypt hashing, brute-force lockout, and a 2-hour inactivity timeout.
Do you touch our card or bank details?
Never. Stripe Connect handles every transaction. No card or bank number reaches a Laand server.
Where does our data actually live?
Redundant AWS data centres, with daily snapshots and a 30-day point-in-time recovery window.
Zero-trust candidate anonymization & data minimization
Traditional ATS platforms force your company to absorb immediate regulatory liability for storing thousands of unvetted candidate resumes. Laand removes that exposure at the architecture level.
- Cryptographic pseudonymization. All talent profiles, multi-chain LLM fit scores, and High-Agency Assessments (HAAs) are anonymized across the platform by default.
- Consent-based PII disclosure. Candidate Personally Identifiable Information stays anonymous until the candidate completes the Micro-Projects Escrow Sandbox phase and your hiring team explicitly unlocks the profile.
- Global regulatory alignment. By withholding candidate PII during sourcing and evaluation, Laand natively helps your company meet US CCPA, UK GDPR, and EU GDPR data minimization mandates.
Multi-chain LLM API security & data privacy
Our multi-chain LLM backends process resume data to generate Fit Scores, strategic Fit Analyses, and Job Application Kits (JAKs) under strict isolation controls.
- Named providers, not a black box. The chain runs on Google Gemini and OpenAI for analysis and generation, and Perplexity for live company and market research. No other model provider processes your data. The full list, and exactly what each one sees, is in Section 9.
- Zero LLM training on your data. Laand partners strictly with enterprise-tier LLM providers and enforces zero-data-retention APIs. Customer hiring data, resume profiles, and strategic project evaluations are never used to train public or proprietary models.
- Research is separated from candidate data. The research chain that studies your company, competitors, and market receives company and role identifiers from the public web only. Candidate profiles are never included in those requests.
- Data transience. Prompt payloads sent to LLM chains are processed entirely in memory and structurally isolated from other tenants.
Intellectual property & sandbox security
Because Laand uses real-world company problems to evaluate talent, we enforce a strict Dual-Protection IP Framework that protects corporate trade secrets and candidate effort at the same time.
- Company IP protection. All proprietary problem definitions, company context, and operational challenges initiated by the hiring company remain the exclusive intellectual property of that company.
- Talent sandbox isolation. Candidate-submitted code, designs, and strategy artifacts uploaded during a Talent Hunt are sandboxed logic-side, isolated by tenant keys, and accessible only to authorized reviewers inside your workspace.
- IP transfer mechanics. Rights in a candidate's solution are governed by our Terms of Service and transfer cleanly to the hiring company only upon a successful payout milestone or profile Unlock Event.
The full contractual mechanics — definitions, the licence that applies before an unlock, the automatic assignment on unlock, and what happens when a company declines a submission — are set out in Section 8 of our Terms of Service. Send that section to your legal team; it is written for them.
Authentication, session governance & password mandates
Laand enforces strict identity boundaries for both talent and enterprise users, to close credential-theft and unauthorized access vectors.
- Talent authentication. Candidates authenticate exclusively through the Google OAuth secure handshake. Laand does not accept, process, or maintain candidate passwords.
- Enterprise-grade password mandates. Corporate recruiter and manager accounts require a minimum of 12 characters with uppercase and lowercase letters and a special character, enforced at both the interface and the server.
- Cryptographic salting & hashing. Corporate passwords are never stored in plain text and never written to logs. Credentials are hashed with bcrypt — a one-way adaptive function — at cost factor 12, with a unique cryptographic salt generated per credential.
- Automated session timeouts. Recruiter and manager sessions expire automatically after 2 hours of inactivity, protecting corporate dashboards from unattended terminals. Expiry is enforced server-side — the session is destroyed, not merely hidden — so an intercepted session cookie cannot be replayed after it lapses.
- Credential lifecycle. A password reset revokes every active session on the account. A password change from inside the dashboard requires the current password and signs out every other device. Both trigger a security notification email that cannot be unsubscribed from.
Encryption & platform defences
- Encryption in transit. All traffic to and from the platform, and between the platform and its sub-processors, is served exclusively over TLS. Session cookies are issued
HttpOnly,Secure, and same-site-restricted, so they are unreadable to JavaScript and not sent cross-site. - Encryption at rest. Databases, automated snapshots, and uploaded assets are encrypted at rest by the underlying AWS storage layer.
- Brute-force and abuse resistance. Authentication endpoints are rate-limited per client, and five failed sign-in attempts against an address lock it for 15 minutes.
- No account enumeration. Sign-in, sign-up, and password-reset all return responses that are identical whether or not an address is registered — including response timing, so the difference cannot be measured with a stopwatch. Nobody can use Laand to work out which companies are our customers.
- Verified corporate identity. Company accounts must confirm ownership of their work email before they can sign in, and signups from disposable-email domains are rejected.
Financial data isolation via Stripe Connect
Laand offloads financial risk entirely by separating subscription billing and escrow payments from our primary database infrastructure.
- Zero-retention financial storage. Stripe Connect handles all candidate escrow payouts and corporate transfers.
- Compliant processing. Credit card numbers, bank account details, and corporate tax identifiers are never transmitted to, stored on, or processed by Laand's servers. All payment handling inherits Stripe's PCI-DSS Level 1 certification.
Infrastructure & managed backend integrity
Laand's entire application layer, database system, and processing endpoints run on scalable, secure backend systems hosted on AWS through Floot.
- Inherited controls. Our underlying cloud architecture inherits the physical security, environmental protections, and network mitigations certified under SOC 2 Type II and ISO 27001.
- Global availability. Data is hosted in secure, redundant AWS data centres with automated network-layer DDoS protection, targeting 99.9% uptime.
- Disaster recovery. Automated daily snapshots of our isolated database architecture provide a 30-day point-in-time recovery window for business continuity.
Compliance posture: what we inherit, what we operate
Security pages are easy to write and hard to trust. Here is the honest split between the certifications our infrastructure providers hold and the controls Laand implements itself.
Inherited from our providers
- AWS — SOC 2 Type II, ISO 27001
- AWS — physical & environmental data-centre controls
- AWS — network-layer DDoS mitigation
- Stripe — PCI-DSS Level 1
- Google — OAuth identity assurance
Operated by Laand
- Candidate pseudonymization & consent-gated unlocking
- Tenant isolation of sandbox submissions
- Password hashing, session governance, timeouts
- Rate limiting, lockout, enumeration resistance
- Zero-retention terms with LLM providers
- Backup and recovery configuration
To state it plainly: Laand (VEC, LLC) does not currently hold its own SOC 2 Type II or ISO 27001 certification. The certifications above belong to the infrastructure we run on. We are an early-stage company and we would rather tell you that than let a badge imply otherwise. Every control described on this page is implemented today and can be evidenced on request; an independent audit of Laand itself is on our roadmap as our enterprise base grows. If your procurement process requires a completed security questionnaire in the meantime, we will fill one out.
Sub-processors & data processing agreements
These are the third parties that may process customer or candidate data on our behalf, current as of August 2026.
| Sub-processor | Purpose | Data involved |
|---|---|---|
| Amazon Web Services (via Floot) | Application hosting, database, backups | All platform data at rest and in processing |
| Stripe / Stripe Connect | Subscription billing, escrow, candidate payouts | Payment and payout identity data — held by Stripe, never by Laand |
| Google (Gemini API) | Fit Scores, Fit Analyses, Job Application Kits, structured extraction | Resume and profile content, in memory, zero retention |
| OpenAI | Multi-chain job analysis and career-plan generation | Resume and profile content, in memory, zero retention |
| Perplexity | Live company, market, and role research from the public web | Company, role, and public-web identifiers only — no candidate data is sent |
| TheirStack | Periodic job-listing sync into the Laand job board | Inbound only — no customer or candidate data leaves Laand |
| Google (OAuth) | Talent authentication | Email address and basic profile — no password ever reaches us |
| Emailit | Transactional and notification email | Name and email address |
| Mixpanel | Product analytics | Pseudonymous usage events |
Need a Data Processing Agreement, a countersigned sub-processor list, or answers to a specific standard (SIG, CAIQ, or your own questionnaire)? Email [email protected] and we will turn it around rather than send you to a form.
Incident response & breach notification
- Notification. If we confirm a breach of personal data affecting your workspace or your candidates, we will notify you without undue delay — and within 72 hours of becoming aware of it where the GDPR or UK GDPR applies.
- What the notice contains. What happened, which data categories were involved, what we have done to contain it, and what — if anything — you need to do.
- Containment. Our first actions on a credential or session compromise are to revoke affected sessions, force credential rotation, and preserve logs for investigation. Every authenticated request resolves through a single session gateway, so revocation is immediate and global rather than endpoint-by-endpoint.
- Afterwards. Affected customers receive a written post-incident summary, including the root cause and the changes made to prevent recurrence.
Reporting a vulnerability
If you have found a security issue in Laand, we want to hear about it before anyone else does.
- Email [email protected] with steps to reproduce. We acknowledge reports within 3 business days.
- Safe harbour. We will not pursue or support legal action against good-faith research that respects the boundaries below, and we are happy to credit you once the issue is resolved.
- Please do not access, modify, or exfiltrate data belonging to other users, degrade service for others, run high-volume automated scans against production, or disclose the issue publicly before we have had a reasonable chance to fix it.
Testing against a live hiring platform touches real people's job applications. If you need an account or a safe target to test against, ask us first — we would rather set one up for you.
Governance & regulatory inquiries
For detailed frameworks covering candidate data deletion rights, system-of-record permanence, and our legal terms, see the Laand Privacy Policy and the Laand Terms of Service. For enterprise security questionnaires or specific compliance inquiries, contact our risk assessment team directly.
Still have questions? Ask a person.
Security questionnaires, DPAs, architecture calls, penetration-test summaries — send them to a human who can actually answer, not a ticket queue.
[email protected]