Know the data path before you upload.
Pastlight is currently an invite-only private pilot. This page describes controls implemented in the application and the boundaries customers should understand.
Organization-scoped application access.
Analysts authenticate by email. Tenant-owned records carry organization and review linkage, and database row-level security uses organization membership to limit which records an authenticated user can access. Server routes verify access before serving private artifacts.
The production pilot does not provide public self-service signup. Access is provisioned for invited analysts, and review, evidence, export, and administration routes are private application surfaces.
Private objects, not public file links.
Original uploads, extracted document text, raw archived HTML, screenshots, evidence bundles, and report exports are stored in a private Supabase Storage bucket. The application records artifact hashes and storage paths, and authorized download routes verify the stored bytes against the recorded digest before serving supported materials.
Pastlight does not intentionally create permanent public object URLs for customer materials or generated reviews. Private application and report routes are excluded from the public sitemap and are configured for no indexing.
Only the services needed for the review.
Pastlight uses Vercel to run the web application and workflows, Supabase for authentication, database, and private object storage, Resend for configured email delivery, and the Internet Archive for historical web discovery and replay.
When optional model assistance is enabled, relevant text may be sent to OpenAI for structured claim extraction or finding-language review. Deterministic identifiers and evidence validation remain authoritative. Customers should not assume material stays solely within Pastlight’s infrastructure; applicable providers process data needed to deliver their part of the service.
Provider terms and data-processing commitments can change. Contact us before upload if a deal requires a specific contractual control, region, model-processing restriction, or subprocessor review.
Measure the run without recording the source.
Application operational events are designed to contain content-free review and organization identifiers, hashes, counts, duration, status classes, token usage, and estimated cost. They are not designed to contain uploaded text, extracted passages, quotations, filenames, source URLs, email addresses, magic links, access tokens, or raw provider errors.
Demand-validation events use fixed categories such as entry page, campaign token, material type, and funnel step. They do not accept document content, claims, filenames, target domains, or management notes.
A short pilot retention window with explicit removal paths.
The pilot sets a 30-day retention deadline after terminal completion or the last recorded activity for a nonterminal review. A scheduled retention process removes eligible reviews after active workflow and storage state are safely reconciled.
Authorized job deletion removes private objects below the organization and review prefix before deleting database rows, then verifies the storage prefix is empty. Organization deletion follows the same storage-first approach and removes the related organization access records. Content-free deletion and reconciliation records may remain for up to 90 days.
Deletion may wait while an active workflow or storage write cannot yet be proven terminal; this fail-closed behavior avoids removing data mid-write. Contact jbench1234@gmail.com to request help with deletion or retention questions.
Use only material you are authorized to process.
Customers are responsible for ensuring they have the right to upload and analyze the material, for limiting access to the appropriate organization members, and for avoiding highly sensitive personal data that is unnecessary for the historical review. Pastlight is not a general-purpose data room.
Security descriptions are summaries of the current private-pilot implementation, not a certification or warranty. Review the privacy notice and pilot terms, and contact us when your obligations require a written agreement or control not described here.
Put the current story against the dated record.
Begin with the material you already have. An analyst controls which claims proceed and which findings appear in the final brief.