What changed in this version (2026-09-28): From this version on, a new version of these Terms applies if you keep using the Service after it takes effect (Section 17). We tell you before then, in the workspace and by email; a change such as fees still asks an owner to accept it first. This version asks an owner to accept it before it applies to your account. Adding or replacing a subprocessor is no longer a change to these Terms: we tell you before a new one receives your personal data, you may object, and the Service keeps running (Section 6.1, and Section 6.2 of the Data Processing Addendum). Section 4.1 now says Output is not an accessibility, legal, security, or regulatory audit. Section 4.3 now covers the buttons that open a pull request adding or updating a setup file, such as the preview workflow. Section 5.1 asks you to confirm you may let our browser use each Preview you connect. Section 6.1 now says we are responsible for our subprocessors as the Data Processing Addendum states. Section 15.1 now excludes from your indemnity only claims caused by our breach, gross negligence, or wilful misconduct, rather than any negligence or defect. We also removed pricing ideas from Section 8.2 and narrowed why we keep review records after you uninstall (Section 7.4). The Privacy Policy and the Data Processing Addendum change to match, and PostHog, our analytics provider, now records sessions only once you are signed in.
And in 2026-09-27, if you last accepted 2026-09-22: Section 6.1 adds three subprocessors: Anthropic, PBC and Cerebras Systems Inc. as AI model providers the Service may use alongside Google, and PostHog, Inc. for product analytics. Section 3.2 now permits recording how the Service is used, including recordings of the workspace, to operate, support, and improve it, and Section 10.1 refers to it. Sections 3.3 and 6.1 now say we send Customer Content to an AI provider only under terms that exclude training on it. The Privacy Policy and the Data Processing Addendum list the same providers, and the Data Processing Addendum now says that accepting a version that adds a subprocessor authorises it. The pre-release phase the 2026-09-22 Terms called the Alpha is now called the Closed Beta; what it means, including that it is free, is unchanged. The plain-language summary says the same. The previous versions are at /terms/2026-09-27 and /terms/2026-09-22.
These Terms of Service (the "Terms") are an agreement between Renaissance Geek, Inc. ("Renaissance Geek", "we", "us") and the organization or individual that installs or uses the Impeccable PRs service ("Customer", "you"). They govern the pre-release ("Closed Beta") version of the service. An owner of the GitHub account that installs the App accepts these Terms in the workspace on the account's behalf, and by doing so represents that they have authority to bind it. The Data Processing Addendum is part of these Terms. The Privacy Policy describes what we collect about the people who use the Service.
Plain-language summary (not a substitute for the Terms): This is an early closed beta. Features will change, and there is no uptime commitment. Its output is AI-generated advice that you must review before acting on. You keep your code and we keep it confidential; we process it to produce reviews and send it to our AI providers (listed in Section 6) to do so, never to train their models. We use PostHog to understand how the Service is used, including recordings of the workspace; the Privacy Policy says what it receives. Our browser will visit the preview URLs you connect and act like a user on them, so only connect previews that are safe to interact with. Images we post to GitHub are served from unguessable links, because GitHub fetches them without a login. The closed beta is free and may end whenever we decide; a paid phase starts only when an owner accepts new terms, and nothing from the closed beta is ever charged. Our liability is capped, as Section 14 states.
1. The Service
1.1 What it is. Impeccable PRs (the "Service") is a GitHub App and web workspace that reviews pull requests touching frontend code. For each qualifying pull request it may post a summary comment, inline comments and suggestions, and a check run; render a preview deployment in a headless browser; run simulated user visits ("persona visits") against that preview; and produce images, audio, and text describing what it found. The Service uses large language models and other automated analysis to do this.
1.2 Closed Beta status. The Service is provided as a pre-release closed beta for evaluation. It is not a finished product. Features may be incomplete, may change without notice, and may be removed. We may limit access, restrict which organizations may install the Service, throttle usage, or suspend or discontinue the Service at any time. We have no obligation to release a general-availability version or to migrate your data to one.
1.3 No service levels. We offer no uptime, latency, or response-time commitment during the Closed Beta. Support is best effort, by email to support@renaissance-geek.ai or in the shared Slack channel where we have set one up with you; there is no guaranteed response time.
1.4 Changes. We may modify the Service, including which pull requests qualify for review, how reviews are scored or tiered, what models are used, and what the output looks like.
2. Eligibility and accounts
2.1 Business use. The Service is offered to businesses and to individuals acting in a professional capacity. It is not offered to consumers.
2.2 GitHub installation. You install the Service on a GitHub account or organization you control. The permissions the App requests and the repositories it can see are governed by GitHub and by your installation settings. You are responsible for choosing which repositories to connect and for who in your organization can change that.
2.3 Workspace access. Access to the workspace follows GitHub: a person who can push to a connected repository may see that repository's reviews, and owners of the GitHub account may manage the installation. You are responsible for your organization's GitHub membership and permissions.
2.4 Third-party accounts. The Service depends on GitHub, on Cloudflare, and on the AI providers listed in Section 6. Your use of those services is subject to their terms. We are not responsible for their availability, changes, or conduct.
3. Your content
3.1 Ownership. You retain all rights in the repository contents, pull request text, design documents, configuration, preview deployments, and any other material you make available to the Service ("Customer Content"). We claim no ownership in it.
3.2 License to us. You grant us a non-exclusive, worldwide, royalty-free license to access, copy, store, transmit, render, analyze, and create derivative works of Customer Content solely to provide, secure, and support the Service for you, and to send Customer Content to the subprocessors in Section 6 for that purpose. We may also record how the Service is used, including recordings of the workspace that can show Customer Content and Output, through the product analytics provider in Section 6.1, and our personnel may review those records to operate, support, and improve the Service, under the confidentiality obligations in Section 10 and never to train models. Beyond that, improvement of the Service uses the aggregated, de-identified data described in Section 3.3. During the Closed Beta our personnel may also examine individual reviews and the Customer Content behind them to diagnose and fix defects in the Service, under the confidentiality obligations in Section 10, without copying Customer Content into any training set, and only by those who need it for that purpose. This license ends when the relevant Customer Content is deleted under Section 7, except for copies in backups pending expiry and material we must keep by law.
3.3 No model training. We do not use Customer Content to train or fine-tune machine-learning models. We send Customer Content to an AI provider only under terms that state it does not train on the content we send (see Section 6). We may use aggregated, de-identified usage and performance data that does not identify you or reveal Customer Content to operate and improve the Service.
3.4 Your responsibilities. You represent and warrant that you have all rights needed to grant the license in 3.2; that Customer Content does not infringe or misappropriate anyone's rights and does not violate law; and that connecting a repository or preview to the Service does not breach any agreement you have with a third party.
3.5 Sensitive data. Do not use the Service with repositories or previews that contain production personal data, protected health information, payment card data, government-classified data, or production credentials. The Service is not designed for that data and we accept no obligations specific to it. If your repositories contain credentials, rotate them; we treat everything the App can read as potentially reaching an AI provider. Sign-in details for a test account on a Preview, which you may give us so our browser can reach it, are the exception: we store them encrypted and use them only to sign in to that Preview, and they should never unlock real user data.
4. Review output
4.1 What output is. Comments, suggestions, check results, scores, screenshots, recordings, persona narratives, and any other material the Service generates ("Output") are produced automatically, largely by AI models, from Customer Content. Output is a starting point for human judgment, not a determination of fact. Output is not an accessibility (including WCAG or ADA), legal, security, or regulatory audit or certification.
4.2 Accuracy. Output may be wrong, incomplete, inconsistent between runs, or misleading. It may miss real problems and flag non-problems. It may reflect instructions hidden in repository content or preview pages (prompt injection) despite our mitigations. You are solely responsible for reviewing Output before relying on it, applying any suggestion, merging any pull request, or making any decision based on it.
4.3 Code changes. The Service posts suggestions; applying one is your change, under your review. The App holds write permission to repository contents, and writes only when a repository editor presses a button that asks it to: "Create test PR" during setup, which puts a one-line test change on a branch of the App's own; and the buttons that add or update a setup file, such as the preview workflow. Either way the change goes on a branch named impeccable/… and arrives as a pull request that you merge or close. The App never commits to your default branch or to any branch of yours, never merges, and never writes unless someone presses one of those buttons. If your organization has not approved the write permission, the App writes nothing: those buttons open the change in GitHub's editor, prefilled, for you to commit under your own identity.
4.4 Your license to Output. As between you and us, you may use Output for any lawful purpose. Because Output is machine-generated from your content, we make no representation about whether it is protectable by copyright or whether it is unique to you.
4.5 Merge gating. If you configure the check run to block merges, that is your decision. We are not responsible for pull requests blocked, delayed, or merged because of the Service's check status, including when the Service is unavailable.
5. Preview deployments and persona visits
5.1 Authorization to visit. By connecting a preview deployment, tunnel, or uploaded site (a "Preview"), you authorize the Service to load it in an automated browser, take screenshots and recordings, and interact with it as a user would: navigating, clicking, scrolling, entering text into forms, and submitting them. You confirm that you are allowed to let the Service do this on each Preview you connect.
5.2 Previews must be safe to interact with. You are responsible for ensuring that a connected Preview is a non-production environment and that automated interaction with it cannot cause harm: no real transactions, no emails or messages to real people, no changes to production data, no irreversible actions, and no exposure of real user data. We are not liable for anything a persona visit does on a Preview you connected.
5.3 Access tokens and gating. Where you use our preview hosting or tunnels, we issue short-lived credentials. You are responsible for keeping them within your CI and for not exposing them.
5.4 Right to refuse. We may refuse to visit any URL, host, or network, or may stop a visit, at our discretion, including for safety, abuse, or cost reasons.
6. AI providers and subprocessors
6.1 Subprocessors. To provide the Service we send, or may send, Customer Content to the subprocessors listed in the Privacy Policy (section "Who receives it"), who act on our behalf. At the effective date of these Terms they are: Cloudflare, Inc. (hosting, storage, workflows, browser rendering); Google LLC (Gemini API: review models, and related text-to-speech and image generation); Anthropic, PBC (Claude API: models that may read your repository to configure the Service and to review); Cerebras Systems Inc. (Cerebras Inference API: models that may run selected review steps); PostHog, Inc. (product analytics: how the Service is used, including recordings of the workspace; the permissions and data handling page describes what they include and mask); Stripe, Inc. (billing; receives account and payment data, not Customer Content). We send Customer Content to an AI provider only under API terms that state it is not used to train their models; we are responsible for our subprocessors as the Data Processing Addendum states, and beyond that make no warranty about their systems. We may add or replace subprocessors as the Data Processing Addendum describes: we tell you before a new one receives your personal data, you may object, and the Service keeps running.
6.2 Provider retention. The AI providers may retain prompts and outputs for a limited period for abuse monitoring under their own terms. We do not control that retention.
6.3 Personal data. If Customer Content includes personal data, you are the controller and we are the processor for that data. The Data Processing Addendum governs that processing, forms part of these Terms from the moment they are accepted, and needs no separate request or signature. Our Privacy Policy describes what we collect about the people who use the Service.
7. Storage, retention, and deletion
7.1 What we store. We store installation and repository metadata, review findings and Output, derived design profiles, screenshots, recordings, rendered preview archives, and model inputs and outputs needed to produce and display reviews.
7.2 Retention. During the Closed Beta, run artifacts (including screenshots, recordings, and raw model responses) are configured to expire 90 days after creation, and uploaded preview archives 30 days after creation. Review records (run metadata, findings, scores, and the derived design profiles and personas for your repositories) are retained while the installation is active and, after uninstall, for the purposes and period stated in the Privacy Policy. Expiry periods are configured targets, not guarantees; details are published at the address in Section 18.9.
7.3 Media shown on GitHub. Images Impeccable posts into your pull requests are displayed by GitHub, which fetches them without a login. We serve those images from unguessable links for that purpose. The data-handling description at the address in Section 18.9 says which images this covers and how the rest of your review media is protected.
7.4 Deletion on uninstall. When you uninstall the App from an account, the installation is marked deleted, the Service stops reading and serving its data, and we run a deletion sweep over its stored artifacts (screenshots, recordings, audio, persona portraits, preview archives, and model inputs and outputs). Review records in our primary database are retained afterwards, as the Privacy Policy states, so that abuse can be investigated and the account restored if you reinstall; we do not delete them on a schedule, and you may have them deleted at any time by emailing privacy@renaissance-geek.ai, and the Data Processing Addendum sets the deletion obligations for personal data. Copies in backups expire on the schedule stated in the Privacy Policy.
7.5 After termination. We have no obligation to retain or return Customer Content or Output after termination.
8. Fees
8.1 The Closed Beta is free. We charge nothing for the Service during the Closed Beta. No payment method is required, and nothing you do in the Service during the Closed Beta creates a charge.
8.2 Ending the Closed Beta and fees after it. We may end the Closed Beta at any time, without a notice period. When we do, the Service may stop for your account until an owner accepts the version of these Terms for the next phase, which may state fees; if you do not accept, your access ends and Section 7 governs your data. Prices and how usage is measured are stated in that version, and nothing reviewed during the Closed Beta is ever charged. We may, at our discretion, give accounts that took part in the Closed Beta a credit against any fees.
8.3 Once fees apply. From the effective date of a version that states fees: fees exclude taxes, and you are responsible for any sales, use, VAT, GST, or similar taxes other than taxes on our income; fees are non-refundable except where we have billed in error or the law requires otherwise, and disputes must be raised within 30 days of the invoice; and we may suspend the Service for any installation with an overdue balance.
9. Acceptable use
You will not, and will not allow anyone to:
- use the Service to violate law or the rights of others, or to review content you have no right to share with us;
- attempt to bypass usage limits, billing, the installation gate, preview gating, or any security control;
- probe, scan, or test the Service for vulnerabilities without our written permission, or interfere with its operation (if you find a vulnerability, report it to the security address in Section 18.9 and do not access data that is not yours);
- deliberately craft repository content, pull requests, or Previews to manipulate the Service's models or to cause it to take actions against third parties;
- direct the Service at Previews or URLs you do not control or are not authorized to have visited;
- reverse engineer, scrape, or copy the Service, or use it to build a competing product;
- resell or sublicense the Service. Using it on repositories you work on for a client is fine, provided the client's owner installs the App or has authorized you to connect the repository.
We may suspend or terminate access for violations, and may remove or refuse to process any content.
10. Confidentiality and feedback
10.1 Your confidential information. Customer Content, Output, and the design profiles, personas, and other knowledge we derive about your repositories are your confidential information. We will use them only to provide, secure, and support the Service for you, and for the product analytics described in Section 3.2; give access only to our personnel and the subprocessors in Section 6 who need it for that purpose and are bound by confidentiality; and not disclose them to anyone else except as required by law, in which case we will notify you first where the law allows. Section 7.3 describes the one exception you control: images that you cause to be posted to GitHub are served from unguessable links.
10.2 Our confidential information. Non-public information about the Service that we share with you during the Closed Beta, including unreleased features, pricing plans, roadmaps, and performance details, is our confidential information. You will not disclose it to third parties without our consent. This does not restrict you from discussing your own Output on your own pull requests, from publishing your own evaluation of the Service, or from disclosures required by law.
10.3 Feedback. If you give us suggestions, bug reports, or other feedback, you grant us a perpetual, irrevocable, worldwide, royalty-free license to use it for any purpose, without obligation to you.
11. Intellectual property
11.1 Ours. We and our licensors own the Service, including its software, models, prompts, rules, review methods, and improvements to them. Except for the limited rights in these Terms, no rights are granted. The design profiles and personas we derive for your repositories describe your design system and your users; they are Customer Content for the purposes of ownership and confidentiality, and we claim no rights in your underlying design system.
11.2 Open-source engine. Parts of the Service are built on the open-source Impeccable project, which is licensed separately under its own terms. These Terms govern the hosted Service, not that code.
11.3 Trademarks. "Impeccable", "Impeccable PRs", and associated marks are ours. You may not use them without permission, except to accurately state that you use the Service.
12. Security
12.1 Our measures. We apply administrative, technical, and physical safeguards appropriate for a pre-release service, summarized in the data-handling description at the address in Section 18.9. That description is informational and is not a certification.
12.2 Your measures. You are responsible for the security of your GitHub account, your organization's membership and permissions, your CI configuration, and your Previews. Notify us promptly at the security address in Section 18.9 if you believe the Service has been compromised.
12.3 Incidents. If we become aware of unauthorized access to Customer Content, we will notify affected Customers without undue delay in the workspace and at the email address on the account. The Data Processing Addendum sets the timing for personal data breaches.
13. Disclaimers
THE SERVICE AND ALL OUTPUT ARE PROVIDED "AS IS" AND "AS AVAILABLE". TO THE FULLEST EXTENT PERMITTED BY LAW, WE DISCLAIM ALL WARRANTIES, EXPRESS, IMPLIED, OR STATUTORY, INCLUDING WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AND UNINTERRUPTED OR ERROR-FREE OPERATION. WE DO NOT WARRANT THAT OUTPUT WILL BE CORRECT, COMPLETE, OR SUITABLE FOR ANY PURPOSE, THAT THE SERVICE WILL DETECT ANY PARTICULAR DEFECT, OR THAT CUSTOMER CONTENT WILL NOT BE LOST. YOU USE A CLOSED BETA SERVICE AT YOUR OWN RISK.
14. Limitation of liability
14.1 Exclusion. TO THE FULLEST EXTENT PERMITTED BY LAW, AND SUBJECT TO SECTION 14.3, NEITHER PARTY WILL BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, OR PUNITIVE DAMAGES, OR FOR LOST PROFITS, REVENUE, DATA, OR GOODWILL, OR FOR THE COST OF SUBSTITUTE SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, EVEN IF ADVISED OF THE POSSIBILITY.
14.2 Cap on our liability. TO THE FULLEST EXTENT PERMITTED BY LAW, OUR TOTAL LIABILITY ARISING OUT OF OR RELATING TO THESE TERMS, THE DATA PROCESSING ADDENDUM, OR THE SERVICE, FOR ALL CLAIMS TOGETHER AND UNDER ANY THEORY, WILL NOT EXCEED THE GREATER OF (A) THE FEES, IF ANY, YOU PAID US IN THE THREE MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM AND (B) USD 100. DURING THE CLOSED BETA, WHERE NO FEES ARE PAID, THE CAP IS USD 100.
14.3 Your liability. Section 14.1 and the cap in Section 14.2 do not limit your payment obligations, your indemnification obligations under Section 15.1, or your liability for breach of Section 9 or Section 10.2.
14.4 Specific exclusions. WITHOUT LIMITING THE ABOVE, WE ARE NOT LIABLE FOR: DECISIONS MADE OR CODE CHANGED IN RELIANCE ON OUTPUT; ACTIONS TAKEN BY PERSONA VISITS ON PREVIEWS YOU CONNECTED; DISCLOSURE OF IMAGES THROUGH THE LINKS DESCRIBED IN SECTION 7.3; ACTS OR OMISSIONS OF GITHUB, CLOUDFLARE, OR AI PROVIDERS; LOSS OF DATA IN A CLOSED BETA SERVICE; OR CONTENT OR CONDUCT OF THIRD PARTIES, INCLUDING INSTRUCTIONS PLANTED IN REPOSITORY CONTENT OR PREVIEWS.
14.5 Basis of the bargain. These limitations are fundamental to the Closed Beta being offered free of charge, and to any later phase being offered at its price, and it would not be offered without them. Nothing in these Terms excludes liability that cannot be excluded by law.
15. Indemnification
15.1 By you. You will defend, indemnify, and hold harmless Renaissance Geek and its officers, directors, employees, and contractors from any third-party claim, and resulting damages, costs, and reasonable attorneys' fees, to the extent arising from: (a) an allegation that Customer Content infringes or misappropriates a third party's intellectual property or violates law; (b) your use of the Service in breach of these Terms or of law; or (c) a Preview you connected in breach of Section 5.2. This does not apply to the extent a claim is caused by our breach of these Terms, or by our gross negligence or wilful misconduct.
15.2 Infringement claims against the Service. If the Service itself (excluding Customer Content, Output, and the open-source engine) is alleged to infringe a third party's intellectual property rights, we may modify it, replace the affected part, or end your access to it. During the Closed Beta that is your sole remedy for such a claim, and we give no indemnity for it; a defense-and-pay indemnity may be offered in a paid phase. We will tell you if such a claim leads us to change or end the Service.
15.3 Procedure. We will notify you promptly of a claim under Section 15.1, let you control the defense (provided you do not settle in a way that admits fault on our behalf or imposes obligations on us without our consent), and cooperate at your expense.
16. Term, suspension, and termination
16.1 Term. These Terms apply from your first use and continue until terminated.
16.2 By you. Uninstall the App from every account and, if you wish, request deletion by email.
16.3 By us. We may suspend or terminate your access at any time, with or without cause, including at the end of the Closed Beta. Where practical we will give notice, but we are not required to.
16.4 Effect. On termination, your rights under these Terms end, any fees owed under a version that states them become due, and Section 7 governs data. Sections 3.4, 4, 7.4, 7.5, 8, 10, 11, 13, 14, 15, 16.4, 17, and 18 survive.
17. Changes to these Terms
We may update these Terms. Each version carries a version number and an effective date. We publish each version at the address in Section 18.9 with a note of what changed, and say so in the workspace and at the email address on the account before its effective date. Until the effective date, the version you accepted continues to govern and the Service keeps running. Adding or replacing a subprocessor is not a change to these Terms; Section 6.1 and the Data Processing Addendum govern it. Ending the Closed Beta under Sections 1.2 and 8.2 is not a change to these Terms and needs no notice period; the version that follows it is a new version like any other, except that the Service may pause until it is accepted. From the effective date, the new version governs, and using the Service after that date means you accept it. If you do not agree, stop using the Service and uninstall the App before then. For some changes, such as fees (Section 8), we instead ask an owner to accept the new version, and the Service pauses for the account until one does; the note at the top of that version says so. Every version stays readable at its own address.
18. General
18.1 Governing law and venue. These Terms are governed by the laws of the State of Delaware, without regard to conflict-of-law rules. The state and federal courts located in New Castle County, Delaware have exclusive jurisdiction, and each party consents to that venue. The United Nations Convention on Contracts for the International Sale of Goods does not apply.
18.2 Export and sanctions. You will comply with applicable export control and sanctions laws and will not use the Service if you are located in an embargoed jurisdiction or on a restricted-party list.
18.3 Government use. The Service is commercial computer software. Government users acquire only the rights granted to all Customers.
18.4 Assignment. You may not assign these Terms without our consent. We may assign them in connection with a merger, acquisition, or sale of assets.
18.5 Force majeure. Neither party is liable for delay or failure caused by events beyond its reasonable control, except payment obligations.
18.6 Entire agreement. These Terms, including the Data Processing Addendum, are the entire agreement about the Service and supersede prior discussions. Order forms, purchase orders, or your own terms do not apply. If there is a conflict about personal data, the Data Processing Addendum controls.
18.7 Severability and waiver. If a provision is unenforceable, the rest remains in effect and the provision is enforced to the maximum extent permitted. A waiver must be in writing.
18.8 Relationship. The parties are independent contractors. No third-party beneficiaries are intended.
18.9 Notices. Notices to us go to legal@renaissance-geek.ai. Security reports go to security@renaissance-geek.ai. Notices to you are posted in the workspace and, where the account has one, sent to its email address. The current Terms, Data Processing Addendum, Privacy Policy, and data-handling description are at https://impeccable.reviews/terms, https://impeccable.reviews/dpa, https://impeccable.reviews/privacy, and https://impeccable.reviews/permissions-and-data.
Renaissance Geek, Inc. · legal@renaissance-geek.ai