Effective July 28, 2026 · Product prototype

Privacy notice

This notice explains what Greenlit collects, why it is needed, which providers process it, and how long each category is retained. The public walkthrough uses synthetic data and creates no retained customer record.

Data you provide

SOW input: synthetic or expressly non-confidential text selected for analysis. Greenlit does not upload the original document to its database or evidence store. To prevent loss during sign-in or reload, the extracted text and unfinished draft are saved in this browser’s local storage until you choose New import or clear site data.
Business record: agency, client, project, milestone value, confirmed criteria, target build, verification results, and evidence metadata.
Reviewer record: reviewer name, business email, optional note, approval or change request, consent statements, and decision time.
Agency account: business email, account identifier, owned milestone records, in-app notifications, and review-link controls.
Optional invoicing: billing name and email, due terms, invoice memo, Stripe account/customer/invoice identifiers, hosted-invoice links, amounts, status, and timestamps. Greenlit does not receive or store card or bank-account details.
Optional product-research request: your name, business email, agency, role, agency size and location, milestone volume, typical approval delay, staging model, requested next step, current approval process, consent record, and request status. Greenlit uses this information only to evaluate fit and respond to the request.
Prototype operations: feedback, page path, service errors, capacity counters, and privacy requests needed to operate and improve the build.
Security context: country code and a keyed, one-way hash derived from request metadata. The beta does not intentionally retain a raw IP address in its transaction record.

Gemini provider notice

When Gemini’s unpaid API tier is used, Google’s current terms permit Google to use submitted content and generated responses to provide, improve, and develop its services, and human reviewers may process that content. Do not submit confidential, proprietary, sensitive, regulated, or personal information. In regions where Google requires paid API service, Greenlit uses its local source-grounded fallback instead. See Google’s Gemini API terms.

Purposes and providers

Data is used only to evaluate and respond to optional product-research requests, draft acceptance criteria, run confirmed checks, produce evidence, create a review packet, record a decision, optionally create and reconcile an agency-authorized invoice, prevent abuse, and maintain a reproducible audit trail. Infrastructure providers are Google (AI when eligible), Vercel (web hosting), Cloudflare (configured queued browser verification), Supabase (database and private evidence storage), and Stripe when an agency enables invoicing (customer, invoice, hosted payment, and payment-status processing). Decision notices remain in-app, and new requests remain in the operator queue, unless a disclosed notification provider is configured. Each provider receives only the data needed for its role.

Synthetic walkthrough

The guided walkthrough uses only the included synthetic SOW and seeded outcomes. It does not call the Cloudflare browser runner, create evidence artifacts, append transaction events, send its sample decision to the server, or create a downloadable transaction export. A reviewer name and email entered in that walkthrough remain only in local browser storage for the sample receipt.

Retention

Original SOW contentNot retained server-side; unfinished extracted text remains in local browser storage until New import or site-data deletion

Recipient-bound review invitationOne-time link plus a separately shared code; 72 hours by default, with a 14-day hard limit

Reviewer receipt session30 days after a final decision; the original review bearer link still expires

Screenshot evidence90 days unless a legal hold applies

Approval and audit recordFour years by default, configurable when a different legal or contractual period applies

Invoice metadata and audit eventsWith the related approval record for four years by default; the agency’s Stripe account may retain the underlying invoice under its own settings and obligations

Stripe OAuth credentialsEncrypted while connected; cleared when the agency disconnects or the account is deleted

Optional product-research request12 months from submission, or earlier after a verified deletion request

Privacy-request record24 months, then purged even if the workflow was not closed unless an active legal hold or retained correction record still requires it

Privacy email verificationA verification-only account is queued for cleanup when created and becomes eligible for deletion when the 30-minute link expires if it is never used; the minimized cleanup receipt is purged seven days after completion

Account-deletion receiptThe plaintext email is erased when Auth deletion completes, and the minimized operational receipt is purged after 30 days

Removed beta-access tombstoneOperator context is minimized after 30 days; the normalized email is retained only to prevent accidental re-admission for up to four years, then purged

Beta feedback / operational events24 months for feedback; 90 days for operational events; account notifications up to 180 days

Greenlit applies data minimization and does not retain information longer than reasonably necessary for the disclosed purpose. A legal hold may suspend deletion for a specific dispute or legal obligation.

Your choices

You may request access, export, correction, or deletion through the privacy request form. A deletion request may be limited where retention is necessary to complete a transaction, protect security, comply with law, or establish or defend legal claims. Greenlit does not sell or share personal information for cross-context behavioral advertising, so Global Privacy Control and Do Not Track do not change that practice.

Security and limits

Greenlit uses TLS, private storage, server-only credentials, AES-256-GCM encryption for Stripe OAuth tokens, signed Stripe webhooks, HMAC-authenticated runner callbacks, expiring review sessions, restrictive browser headers, and append-only hash-chained audit events. No service can guarantee absolute security. Do not use this beta for health, financial-account, government-identifier, child, employment, or other regulated data.

Scope and changes

The public walkthrough is available without an account and uses synthetic data. Separate source-import, retained-project, and product-research features are directed to adults acting for a business. Material changes will update the effective date and be presented before new collection where required.

Operator and contact

Use the privacy request form for privacy or data questions.