Trust & Procurement
The facts a security or legal reviewer usually asks for.
A concise, evidence-based procurement view of Lexsentra's current service boundaries, data handling, access controls and external providers. This page describes implemented capabilities, not roadmap claims.
Least-privilege runtimeTenant-scoped RBACPlan-aware retentionControlled evidence sharing
Service scope
What Lexsentra does
Lexsentra performs regulatory QA on public digital surfaces, stores bounded technical evidence, supports human evidence review, and continuously monitors configured properties for material regressions.
- Service operator: Bokhonko Zhanna, individual / sole proprietorship established in Ukraine (Terms)
- Primary current scope: UK iGaming regulatory QA
- Execution: public HTTP/HTTPS and isolated browser scanning
- Evidence: findings, screenshots and sanitized network observations where applicable
- Human control: append-only evidence review before external sharing
Data minimisation
What the evidence layer does not collect
The scanner is designed to reduce unnecessary sensitive data collection while preserving enough technical context for review.
- Query strings and URL fragments removed from stored request URLs
- Request and response bodies not collected in network evidence
- Request and response headers not collected in network manifest
- Internal filesystem evidence paths not exposed through scan metadata
- Evidence responses use private, no-store cache controls
Identity & tenancy
Access model
Customer access is organization/workspace scoped with explicit permissions and audit-oriented controls.
- Owner, Admin, Compliance, Analyst, Developer and Viewer roles
- Tenant-scoped workspace authorization checks
- Hashed session bearer tokens and session revocation
- CSRF protection on cookie-authenticated state changes
- Append-only review and access audit events where implemented
Evidence lifecycle
Retention and external handoff
Evidence lifecycle is explicit in the product rather than implied by a generic storage policy.
- Plan-aware evidence retention with scheduled deletion enforcement
- Expired evidence is blocked at the read path before physical purge
- Workspace shows evidence approaching its retention boundary
- External evidence links are separate, expiring tokens
- Only approved evidence may be shared externally; review downgrade revokes active links
Data lifecycle
Where customer data enters, moves and leaves the current service.
The current production flow is deliberately bounded: account and workspace records are stored in PostgreSQL on the production host; configured public or explicitly authorised targets are fetched by isolated HTTP/browser workers; screenshots and minimized network evidence are written to the configured evidence store; approved evidence can be exported or shared through a separate controlled token; transactional email is sent through Resend; billing checkout is handled by Paddle as Merchant of Record. Verified organization owners can submit a non-destructive data-exit or deletion-review request and track its bounded status in the product. For a verified customer exit request, Lexsentra can generate an operator-assisted, tenant-scoped read-only JSON return package covering core workspace/product records while filtering authentication secrets, credential ciphertext and internal evidence filesystem paths. This request/status workflow is not a self-service deletion API, and retained financial/audit/provider-side records still require documented treatment. Retention rules make expired evidence unavailable before scheduled physical purge. Current database backups are local to the production host, so Lexsentra does not describe the existing backup setup as off-site disaster recovery. End-to-end hosting residency is not promised until provider contract/location facts and any future off-site storage are confirmed.
External providers
Purpose-limited third parties
Publicly disclosed providers are used for narrow operational functions rather than broad access to scan evidence.
- Paddle: subscription checkout and payment processing as Merchant of Record; Lexsentra does not receive card details
- Resend: verification, invitation and alert email delivery
- Scanned public targets: receive ordinary browser or HTTP requests from the isolated scanner
Operational boundaries
Least-privilege service design
Security-sensitive execution paths are separated into narrowly scoped services and database roles.
- Current production delivery model: managed multi-tenant SaaS
- Single-tenant, on-premises and air-gapped deployment are not currently offered as shipped capabilities
- Browser worker has no Paddle or database credentials
- Webhook delivery is isolated behind HTTPS-only egress controls
- Specialized billing, retention, monitoring and delivery database roles
- Runtime PostgreSQL role cannot perform schema DDL
- Systemd services use no-new-privileges and empty capability sets where configured
Current assurance status
No certification is implied.
Lexsentra does not currently claim SOC 2, ISO 27001, PCI DSS certification, UKGC approval, or any other third-party security or regulatory certification. Product findings and review states are technical QA evidence and internal governance signals, not a legal compliance determination or regulator certification.
Documents already public
Review before sending a questionnaire
Available through review
Questions not answered publicly
For security questionnaires, detailed deployment questions, contractual security requirements or information not stated on this page, request a security review. Lexsentra will answer based on the current implemented environment rather than pre-claiming controls.
- No public DPA, SLA or independent audit report is claimed here
- No unsupported data-residency guarantee is stated
- No confidential architecture or credentials are exposed publicly