Terms of use
Greenlit is a product prototype for demonstrating evidence-backed milestone approval. The public walkthrough uses synthetic data and creates no retained customer record.
Eligibility and authority
The public walkthrough requires no account and uses only included synthetic material. Separate source import, retained project, and product-research features are for adults acting for a business who have authority to submit the material and represent the organization they identify. Those features are not offered for consumer, medical, financial, employment, government, or child-directed use.
Your data and Gemini
Submit only material you are authorized to process and never submit secrets or regulated data. You authorize the disclosed processing needed to provide the Service. Gemini’s unpaid API tier may allow Google to use inputs and outputs to improve its services and permit human review; only synthetic or explicitly non-confidential, non-personal material is allowed. The analysis screen requires a separate acknowledgment before anything is sent.
Human control and verification
AI suggestions are drafts. You are responsible for reviewing source quotes, measurable outcomes, check mappings, and results. Browser evidence reflects only the recorded build, time, and typed checks and does not prove facts outside that scope.
Approval record, not a legal signature
The client decision is a business approval record. It is not a payment guarantee, accounting or tax ledger, notarization, certification, or substitute for a contract or formal electronic-signature product where one is required. Do not use Greenlit for documents excluded from electronic-transaction laws or requiring special signatures, witnessing, or notarization.
Optional Stripe invoicing
An agency may authorize Greenlit to create an invoice in its own connected Stripe account after approval. Automatic sending must be configured before client review and is disclosed to the reviewer; approval never charges a payment method by itself. In test mode, Greenlit creates only a Stripe test invoice and does not email the client. A live-mode deployment may email the invoice after approval when the operator has explicitly enabled live access. Stripe, not Greenlit, hosts payment collection. The agency is the merchant, owns the Stripe customer and invoice, and remains responsible for prices, taxes, refunds, disputes, invoice terms, accounting, and compliance. Disconnecting Greenlit does not cancel invoices already created in Stripe.
Guided walkthrough
The synthetic walkthrough is not a transaction-record service. Its seeded outcomes and local sample decision are for demonstration only and are not retained, hash-chained, exported, or represented as browser evidence.
Electronic records
Reviewers must affirm their intent, consent to receive and retain the record electronically, and provide their name and business email. Records can be viewed in a modern browser and printed or saved as PDF. Transaction events are timestamped and hash-chained to make later alteration detectable.
Acceptable use
Do not probe third-party sites without authorization, upload secrets or regulated data, bypass origin verification, falsify identity or authority, interfere with the Service, or use generated evidence to mislead another person. Custom verification is limited to public HTTPS staging origins whose one-time ownership token has been verified for the signed-in agency. Potential form mutations require a separate authorization.
Availability and responsibility
The prototype is provided as-is and may be changed or withdrawn. You remain responsible for contracts, invoice accuracy and delivery, payments, refunds, disputes, taxes, accessibility compliance, legal notices, and decisions made from the output. To the maximum extent permitted by law, the Service disclaims implied warranties and liability for indirect or consequential losses.
Account access removal
Account-based project access may be removed at any time. Removing access ends active agency sessions, blocks owner-only routes, revokes undecided client-review links, and cancels work that has not completed; it does not silently delete retained transaction records or legally held evidence. The retention and deletion rules in the Records policy continue to apply, and a former user may still submit a request through the public privacy-request form.
Privacy and requests
The Privacy Notice describes collection, providers, security, and retention. Submit data-rights requests through the privacy request form.
Governing law and venue
The public walkthrough is a synthetic demonstration and creates no retained approval transaction. Separate account-based product access is not offered under incomplete governing-law terms.
Operator and contact
Use the privacy request form for privacy or data questions.
