Privacy and data handling.
Last updated:
LSAS Platform, Inc., a Delaware C-Corporation, operates this website and its evaluation sandbox. This page describes the application data flows visible in the implementation. Agreements for a particular customer deployment may impose additional requirements; the website notice and terms remain subject to legal review.
Data handling varies by surface. Review the actual provider, connector, retention, and hosting configuration before supplying sensitive information.
Website and contact information
- The contact form accepts your name, work email, company, optional role, phone and timeline, and your message. Submitted details are stored for responding to LSAS Platform inquiries.
- When configured, the email delivery service receives contact details to send the inquiry and a confirmation. Hosting and database service providers process information required to operate the site.
- The practitioner feedback form separately collects your name and email, optional role, feedback and conversation preference, and an approved source page and invitation context. A submission reference prevents duplicate retries. These records are retained with contact information for reviewing feedback; they are classified as practitioner discovery, not sales-qualified opportunities. When configured, an internal email notification includes the submitted details. This form does not send an automatic email to the submitter or enroll them in marketing or sales sequences.
- Optional public website analytics start only after you accept analytics. Your preference is stored in a first-party cookie for up to 180 days. You can reject analytics or change your choice through Cookie preferences in the footer; the website remains usable.
- With acceptance, we measure public page visits, link and resource requests, animation engagement, search topics, Regulatory Pulse interactions and inquiry submission outcomes. Existing first-party engagement reports use random event IDs. Raw search text, form contents and sandbox inputs are not sent in these analytics events.
- The same choice controls Google Analytics and optional first-party engagement measurement. Google Analytics is provided by Google and uses analytics cookies and device/browser information to measure visits and engagement. Advertising features are disabled by this integration. Authentication and console routes and sensitive-link URLs are excluded from optional website analytics. Campaign labels on incoming links may be used for attribution; arbitrary page query strings are not included in our event payloads.
- Rejecting analytics prevents optional measurement. Withdrawing a previous acceptance stops further collection, removes accessible Google Analytics cookies and reloads the current page to stop the loaded tag. It does not erase data already collected. Essential session and security functions operate independently.
Accounts and administrative activity
- Account records include identity and membership information, password hashes, sessions, and invitations. Session cookies support sign-in and access control.
- Developer Evaluation operations record verification requests and their mail-processing outcomes, verified workspace creation, API key issuance, evaluation-file response counts, and governed decisions. These operational records support delivery, troubleshooting, and account usage reporting independently of optional website analytics consent.
- Durable verification history uses a normalized email digest rather than a second copy of the email address. A digest is pseudonymous, not anonymous. File counts are associated with the evaluation account and identify the requested file and UTC day; they do not establish that a file was saved or executed. These new operational records do not contain verification tokens, passwords, full API keys, request payloads, IP addresses, or browser fingerprints. Platform-admin reports show aggregates without individual addresses or digests.
- Protected changes produce audit records with relevant actor, tenant, version, and action context. These records can contain personal identifiers needed for accountability.
- Tenant-scoped access and assigned review roles restrict application access. Platform administration has separate privileges; a tenant boundary is not a promise that infrastructure operators cannot access stored data.
Runtime and assessment content
- Model decision telemetry normally records derived findings and outcomes. Run Engine inputs, evidence, reports, workflow artifacts, and connector records can include supplied content.
- The output-review profile stores the exact held artifact in encrypted form for authorized inspection and release. Encryption does not make that artifact anonymous.
- Pattern redaction is limited to the implemented checks and transformations. It does not guarantee removal of all personal information from every stored field or log.
Providers and deployment boundaries
- A model or connector request transmits the permitted payload to its configured destination. The destination provider has its own processing and retention terms.
- The public site is a hosted evaluation service. Customer-hosted, private-cloud, and on-premise arrangements require deployment work and verification; they are not automatically provisioned by this application.
- Residency, backup storage, network access, TLS, encryption at rest, and service-provider agreements depend on the hosting configuration. This code review does not establish those external controls.
Retention and requests
- Configured retention policies and legal holds govern supported worker cleanup. Running the worker is required; a saved setting alone does not delete records.
- Expired verification-link records can be removed separately from durable operational history. Evaluation enrollment history and download counters remain for operational accounting until an authorized retention or account-decommissioning process removes them; automatic age-based deletion of that history is not provided. Evaluation expiry does not reset usage history. Privacy requests follow the contact process below.
- Database backups, infrastructure logs, external provider records, and contact records have separate lifecycles that must be included in the operator’s retention policy.
- Contact LSAS Platform through the contact page for questions about information submitted to this site or requests relating to it. Applicable obligations and customer instructions require case-specific review.
Public sandbox
- Use synthetic or approved public sandbox data. The Epic demonstration uses dedicated sandbox patient read/search flows and intentionally shows baseline and governed results.
- Published homepage counts are aggregate activity for an explicitly configured demo application. Simulated override activity is separate from authoritative protected approvals.
- Demo content may be throttled, reset, retained for evaluation, or removed. Do not use the public sandbox to submit real patient data, payment credentials, private keys, or confidential production content.