1. Agreement
These Terms are between you (and, if you install on behalf of an organisation, that organisation) and SeedQ (“SeedQ”, “we”). By installing or using SeedQ Launch you agree to them. If you don’t agree, don’t install the app. Our handling of personal data is described in our Privacy Policy.
2. The service
SeedQ is a GitHub App and hosted dashboard that scans the repositories you connect and reports findings about launch-readiness, agentic-readiness, integrations and GDPR-readiness, with suggested fixes. The Launch and Agentic scans are free. The features, limits and price of each paid plan are those shown on our pricing page and in the order summary when you subscribe. Not every plan is on sale at any given time. We may change, add or remove features over time.
AI logic review (beta). For workspaces we invite, SeedQ offers an optional AI logic review. It runs only after we have switched it on for your workspace and one of your administrators has agreed to it on your behalf, and an administrator can withdraw that agreement at any time. When you start an AI logic review, SeedQ gives our AI provider, Anthropic, read access to your repository for the length of that review. Anthropic checks it out into a sandbox it runs on our behalf, and deletes it when the review ends; it is never copied to SeedQ’s own servers. The model reads your source code there, whatever the size of your app. We instruct it never to open environment files, keys, database dumps, data files or logs, and we record every file it opens or searches; if it opens one of those files anyway, we mark the review and drop anything it says about that file. Secrets in the files the model opens are not masked before it reads them; we remove any we can detect from what the review reports. For a second, blind check, our servers read the few files each finding points at through the GitHub API and send the lines around it to Anthropic once more. Anthropic processes this on our behalf and does not use it to train its models. You can switch the review off at any time. On SeedQ Guardian, with AI review on for an app, SeedQ also re-checks the parts that changed after each push to its main branch. Our Privacy Policy describes this in more detail. By agreeing, your administrator confirms they may authorise that for the repository. The results are shown only inside your workspace, marked as an AI estimate. When AI review is on, its findings appear with your scan results and count among the things to fix before launch; an admin can mark any of them as not a problem. They never change any Guardian check, and SeedQ does not write anything to your repository as part of it. A review of a pull request you ask SeedQ to look at is the exception: it also gives Anthropic that pull request’s title, description and changes, may run your app’s own lint and test commands in the sandbox, and posts a comment on that pull request as described in section 3. Where an administrator has chosen SeedQ to run the Research stage of an intent’s workflow, the model may also search the public web and read public pages through Anthropic: the searches, which the model writes about the intent’s subject, are run by Anthropic, and the pages are fetched by Anthropic, never from SeedQ’s own servers.
The core review. On any plan, including the free plan, an administrator or owner of your workspace can turn on a core review for an app. SeedQ’s own fixed rules then read each pull request on that app and post what they found on it, as described in section 3. For a core review SeedQ sends nothing to Anthropic or any other model provider, and it uses no AI tokens.
3. Access to your code: what we read and what we can write
SeedQ reads your repositories through the GitHub API to produce scans. SeedQ’s own servers never clone your repository. If an administrator has turned on the AI logic review, Anthropic checks the repository out into a sandbox for the length of one review, and if an administrator has chosen to have SeedQ build an app’s tasks, for the length of one build, and if an administrator has chosen SeedQ to run a stage of a task’s workflow, for the length of that stage. SeedQ writes your application code only there, or in a revert of a task’s change, where an administrator switched Roll back on. There, its own agent writes the change, and SeedQ pushes it to a new branch and opens a pull request, which SeedQ never merges on its own. The only changes SeedQ can make on GitHub are check runs, issue comments (including an answer a member of your workspace asks SeedQ to post on their behalf), labels on a task a member of your workspace answers in Review, issues you ask it to file, a review comment on a pull request you ask SeedQ to look at or of an app you turned reviews on for, resolving the conversations on its own review comments with a one-line reply saying why, a GitHub Actions workflow file you ask it to propose, a pull request taking a task’s change back out, where an administrator switched Roll back on, a new branch and pull request holding a change SeedQ built, where an administrator chose that, the removal of its own comments when you ask for that, and merging a pull request you approve, and all of them happen only with the permissions you grant at installation. If an administrator has switched Roll back on for an app, SeedQ opens one pull request reverting a task’s merged change when the check after it goes live fails; it goes in only when a person approves it in SeedQ. The check runs include a check run for SeedQ’s checks on a pull request SeedQ started, saying which checks went through; it never blocks a merge. Where the AI review is on, SeedQ also reviews a pull request that someone on your side has labelled seedq-review on GitHub: it publishes a check run and posts one GitHub review with comments on at most five of the lines that pull request changed, and does so again for each new commit while the label stays on. Where someone adds that label and the AI review cannot run, for example because your plan does not cover it, SeedQ still publishes that check run, on any plan, as a neutral notice saying why, and posts no review, unless that pull request gets the core review instead, as described below. Where the AI review is on, and an administrator of your workspace has chosen automatic reviews or SeedQ has switched them on for your workspace at your request, SeedQ reviews pull requests nobody labelled in the same way, as each is opened, reopened or marked ready for review, up to the number of pull requests set for your workspace, or with no limit where SeedQ has set that at your request, and again for each new commit to one it has reviewed while automatic reviews stay on. That review is only ever a comment, marked as an AI estimate: it never approves a pull request or requests changes, its check never fails, and it never blocks a merge. SeedQ brings its own review up to date in place, with a line in it saying so, when the checks on that pull request finish or when it has looked into a point the review was not sure of; that changes the review’s answer and the lines under it, never what it found or its line comments. SeedQ keeps one review live on a pull request: a newer commit whose review has the same answer, with nothing found either time, updates the review already there rather than posting another, and a newer review cuts the one it replaces down to one line naming the newer commit and hides it on GitHub as outdated, leaving its line comments as they are. SeedQ does not dismiss or delete a review once posted, reviews a pull request nobody labelled only where automatic reviews are on or the core review is on for that app, and has no setting that labels one. SeedQ resolves the conversations on its own review comments, with a one-line reply saying why, only when a newer review of the same pull request finds the problem gone or a member of your workspace marks it not a problem in SeedQ; it never resolves a conversation someone else started and never reopens one a person resolved. On any plan, including the free plan, an administrator or owner of your workspace may turn on the core review for an app; it is off until someone does. SeedQ then publishes a check run named “SeedQ / Core review” on every pull request of that app, with no label and no limit, and again for each new commit, and posts one GitHub review on that pull request saying what its rules found, with comments on at most five of the lines that pull request changed where they found something. SeedQ’s own fixed rules read the pull request, and SeedQ sends nothing to Anthropic or any other model provider for it. A core review gives facts and a count, never an answer on whether to merge, and it is only ever a comment: it never approves a pull request or requests changes, its check never fails, and it never blocks a merge. SeedQ keeps one core review on a pull request, brings it up to date in place and hides one it replaces on GitHub as outdated, as it does for the AI review. Where an AI review of a pull request was asked for and cannot run, because there are no AI tokens, AI is paused or your plan does not cover it, on an app set to the AI review or on one nobody has chosen for, that pull request gets the core review instead, saying why. Where SeedQ staff have switched on both reviews side by side for your workspace, at its request, an app set to the AI review gets this check run and review too, beside the AI review’s, so the pull request carries one live review of each. When an administrator or owner of your workspace marks a core review finding not a problem in SeedQ, SeedQ records that decision for the app’s rule checks and resolves the conversation on its own comment for that finding, with a one-line reply saying who marked it; that is the only time SeedQ resolves a core review’s conversation. SeedQ may also start the self-test of the Claude Code workflow file or of the SeedQ Loop workflow file described below when an administrator of your workspace presses Check it now, and does nothing else with that run. SeedQ may also save one repository secret, CLAUDE_CODE_OAUTH_TOKEN, when an administrator of your workspace pastes a Claude token on that setup card. The token is encrypted in the administrator’s browser so only GitHub can read it, and SeedQ writes no other secret.
A workflow file is bounded three ways: it may only be placed inside .github/workflows/, it is only ever committed to a new branch and offered as a pull request you choose to merge, and it is only created when an administrator of your workspace asks for it. SeedQ never commits a file to your default branch. Outside a build or a revert an administrator chose (above), SeedQ writes no other file. The capability is off entirely unless your workspace has approved the corresponding permission.
One such file is the SeedQ Loop workflow. Once you merge it, it runs your own coding agent in your own GitHub account, under your own agreement and plan with that agent’s provider and with tokens you provide. The pull requests it opens are your agent’s work; SeedQ never merges them, and you are responsible for what you merge.
On the SeedQ Guardian plan, SeedQ additionally publishes check runs on your pull requests and pushes, and a quality comment on your issues. A pull-request check may include inline notes on the lines that pull request changed; these form part of the check run and are removed with it. Each of the three can be set to Off, Warn or Block per workspace or per repository. Only the pull-request check can affect a merge, and only if you choose Block and make it a required check in your branch protection; issues and pushes are always advisory. If you leave Guardian, any repository that has already received a pull-request check from SeedQ continues to receive an automatic passing check, so that a check you made required cannot block your pull requests indefinitely.
Where your repository’s changes go straight to a branch rather than through pull requests, the same pull-request check is instead published on the update you pushed. It is always advisory and can never block anything, because the change has already landed by the time SeedQ looks — this is true even if you have set that gate to Block, which applies only in the merge box. SeedQ decides which of the two applies from how your repository is actually used, tells you what it concluded, and you can change it at any time in your Guardian settings. Unlike the pull-request check, this one simply stops if you leave Guardian: it is never a required check, so nothing waits on it.
On any paid plan, an administrator of your workspace may file an individual finding into one of your repositories as a GitHub issue — a work order containing the finding and its suggested fix. This happens only when a person on your side chooses it — for the finding they chose, or for the findings in one scan report or one app, at most 100 per press, one issue each — and SeedQ adds no labels and changes nothing else in the repository. An administrator may switch filing off for the workspace under Scan settings. On any paid plan, an administrator may instead switch on creating issues after each scheduled check for the workspace, under Health check → Settings, in which case SeedQ files up to five new or returning findings from each scheduled scan without a further instruction and, on SeedQ Guardian with a coding agent connected, hands each to that agent. That setting is off unless somebody in your workspace turns it on, only an administrator can change it, and SeedQ records who changed it and when. You are responsible for the issues created in your repositories while it is on. The issue is yours once filed; SeedQ does not edit or close it.
The same rules apply to incidents — bug reports your workspace collects through SeedQ. On any paid plan, an administrator may file an incident into one of your repositories as a GitHub issue containing SeedQ’s summary of the report and the reporter’s account, with links, formatting and anything instruction-shaped stripped out before it is stored. SeedQ does not edit or close the issue once filed.
On SeedQ Launch Pro and SeedQ Launch Studio, an administrator chooses for each app, under Reports → Integrations, what happens to each kind of report — bug reports, ideas and feedback: it stays in SeedQ, it is filed as a GitHub issue when an administrator chooses, or it is filed as an issue as soon as it arrives. An idea or feedback filed this way contains SeedQ’s rewritten version of what was sent. The administrator may also pick labels for each kind from the labels that already exist in the repository; SeedQ applies only labels that still exist when it files, and never creates one. Every kind stays in SeedQ until an administrator changes it, except bug reports, which are filed when an administrator chooses. You are responsible for the issues created in your repositories under these settings.
On SeedQ Guardian, filing happens only when an administrator on your side chooses it, for the incident they chose, unless an administrator switches on automatic filing for the workspace, under Guardian → Settings, in which case SeedQ files each incident it can read as an issue without a further instruction. That setting is off unless somebody in your workspace turns it on, only an administrator can change it, and SeedQ records who changed it and when. You are responsible for the issues created in your repositories while it is on.
On SeedQ Guardian only, an administrator may also hand a filed incident to the coding agent your workspace uses. SeedQ posts one comment on that issue setting out the constraints for the work and assigns the issue to that agent. By default this happens only when a person on your side chooses it, for the incident they chose. An administrator may instead switch on automatic hand-over for the workspace, under Guardian → Settings, choosing the lowest severity that qualifies; SeedQ then hands over incidents at that level and above without a further instruction, and retries an attempt that runs out of time a limited number of times before stopping. That setting is off unless somebody in your workspace turns it on, only an administrator can change it, and SeedQ records who changed it and when. An administrator may instead save a workflow for an app in which a stage is run by their own coding agent; SeedQ then hands that stage over for each task on that workflow without a further instruction, until an administrator changes the workflow. Work handed over automatically is work you have instructed us to hand over. What the agent then does in your repository is performed by that provider under your own agreement and plan with them, using permissions you granted them — SeedQ does not write that code, and is not responsible for it, including any charges that provider makes for work started this way. If SeedQ reviews a pull request your agent opens, that review is posted as a comment, either an AI estimate or what SeedQ’s own rules found; it is not an approval of the code and does not make SeedQ responsible for it. SeedQ will merge it only where an administrator of your workspace expressly instructs it to, as set out immediately below.
Where your coding agent has asked a question on an issue in your repository, a member of your workspace may answer it in the app. SeedQ then posts that answer as one comment on the issue, naming the member who sent it. This happens only when that member presses Send, once per press, and never automatically. The answer is the member’s own words: SeedQ does not write, change or check it, and you are responsible for what is posted this way, as you are for anything your team writes on the issue directly.
A member may also answer the questions on several issues at once in Review, from an AI assistant connected to SeedQ (such as Claude). When that member saves, SeedQ posts one comment per issue, as above, and then changes that issue’s labels the way your Review settings say: by default it takes off the label that marked the issue as waiting on a person and adds the label that marks it ready for your coding agent. Labels change only on an issue that carried one of the waiting labels in those settings, only after its answer is posted, and only when that member saves. An administrator can change the labels, or switch label changes off, for each app under Tasks → Settings → Review.
An administrator may also adopt an issue that already exists in your repository, so the paragraph above can be applied to it. Adopting changes nothing on GitHub — SeedQ does not edit, label, comment on or close the issue in order to adopt it — but it means the coding agent can be pointed at an issue your team wrote, rather than one SeedQ composed. The instructions SeedQ gives the agent are the same either way, and so is everything in the paragraph above about whose provider, plan and code the resulting work is. SeedQ adopts an issue only where an administrator presses the button on that issue. A task starts on its own only from a trigger an administrator has switched on for that app, each off unless switched on: a pull request is opened, an issue gets the label they named, or SeedQ files an issue from a setting. SeedQ will decline to adopt an issue that was not opened by somebody inside your organisation or team.
An administrator may also ask SeedQ to hand a work order to your coding agent, either when filing it or afterwards, in the same way as an incident. SeedQ does this only when that administrator presses the button on that finding, or through the scheduled-scan setting described above. The instructions ask the agent to check the finding is real before changing anything and to say so on the issue if it is not. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies to it in the same way.
Your coding agent may also be handed a pull request you asked SeedQ to review, rather than an issue SeedQ filed, where that pull request’s own checks have failed or its review found something to fix. SeedQ does this only when a person on your side asks for it, for that pull request, in the app or, for failing checks, with a comment on the pull request, or, on SeedQ Guardian, where Fix on its own is on for that app: a setting that is off by default and that SeedQ switches on only at your workspace’s request, under which SeedQ hands over a pull request your coding agent opened on its own when its review finds a problem at the level chosen or a check the review ran fails, never one from a fork, one a person on your side has pushed commits to, or one the review has an open question to you on. No other setting does it automatically. A pull request is handed over at most twice in all. SeedQ then posts one comment on that pull request setting out the work and naming its branch, and assigns nothing. Your agent writes the fix and pushes it to that branch from your own GitHub account, with tokens you provide; SeedQ never pushes to your branch. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies to it in the same way.
On SeedQ Guardian, immediately after an administrator creates a report-widget key, they may also ask SeedQ to file one issue asking for the widget to be installed in that key's repository, containing the install instructions and the widget key, and to hand it to your coding agent. SeedQ does this only on that press, once per key, and no setting does it automatically. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies to it in the same way: the change to your site is made by your agent and merged by you. On the other paid plans SeedQ files no install issue and shows the install instructions instead.
An administrator may also accept a feature suggestion made by a member of your team, by writing up what should be built, and ask SeedQ to file that write-up as one issue and hand it to your coding agent. SeedQ files nothing for a suggestion that has not been accepted, and your agent is given the administrator's write-up rather than the suggestion as it was submitted. If an administrator has turned on sending on accept, accepting is itself the request to file and hand over. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies in the same way, and reviewing what your agent builds before you merge it is yours to do.
While release notes are on for an app, an administrator may also ask SeedQ to file one issue to set up release notes, asking your coding agent to add a pull request template with a release notes section and a rule telling coding agents to fill it in, and to hand it to your coding agent. SeedQ does this only on that press, once for each app, and no setting does it automatically. The instructions are the same for every customer, so reviewing what your agent builds before you merge it is yours to do. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies to it in the same way.
When SeedQ has seen no automatic tests run for an app, an administrator may also ask SeedQ to file one issue to add automated tests, asking your coding agent to add tests and a workflow that runs them, and to hand it to your coding agent. SeedQ does this only on that press, once for each app, and no setting does it automatically. The instructions are the same for every customer, so reviewing what your agent builds before you merge it is yours to do. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies to it in the same way.
Where the AI logic review is turned on, an administrator may also ask SeedQ to file one issue for a problem the AI logic review estimated, carrying what the review found about it, and to hand it to your coding agent. SeedQ does this only on that press, once for each finding, and no setting does it automatically. The issue says that its content is an AI estimate, which can be wrong, and asks the agent to check that the problem is real first; deciding whether it is, and reviewing what your agent builds before you merge it, is yours to do. Everything in the paragraphs above about whose provider, plan and code the resulting work is applies to it in the same way.
Still on SeedQ Guardian, where a coding agent has opened a pull request, an administrator of your workspace may press Approve & ship or Let these in in the app, and SeedQ will merge the pull requests that press names into your default branch. That, and the setting described next, are the only circumstances in which SeedQ changes what your application runs. It happens only on that press, or where an administrator has switched on Let changes in on their own for that app, in which case SeedQ lets an agent’s change in on its own when the review finds nothing to stop it and the checks are green — each press authorises only the pull requests it names, each at the commit shown, and cannot be re-used or acted on by any automated process. Where a branch has changed since the page was loaded, SeedQ declines that pull request and tells you. A workflow’s Merge by rules is the existing Let changes in on their own setting, narrowed by that workflow’s rules and never widened. The resulting merge commit records that the merge was approved in SeedQ and by whom, and SeedQ keeps its own record of each one. The code merged is the agent’s, produced under your agreement with that provider; merging it at your instruction is not a representation by SeedQ that it is correct, that it is fit for any purpose, or that the reported problem is resolved. Deciding to press the button, and what you do afterwards, remain yours.
Some agents can only be handed work by a person rather than by an application, so an administrator may choose to give SeedQ a key for one. If you do, we use it only to hand over incidents someone on your side has chosen to send. Work handed over with your key is done as that account — it is billed to whoever owns it and appears under their name — and it remains subject to your own agreement with the provider. Disconnecting the agent deletes the key immediately.
Release notes you publish. If you turn on release notes for an app, SeedQ publishes only the releases you choose to publish, at a public address you choose, and takes a release down when you hide it or switch the page or the feed off. You are responsible for what your release notes say; SeedQ publishes them on your behalf as your processor and does not review them.
Release notes SeedQ writes with your key. If you give SeedQ a model API key to write your release notes, your model provider bills you for that key’s use, and you are responsible for what the provider returns until you publish it.
Removal on request. If you ask us to, SeedQ will delete the issue comments it posted across your repositories. This happens only when you ask, it removes only comments SeedQ itself wrote, and SeedQ tells you how many were removed. It does not close or delete issues you asked it to file, and it does not close proposed changes. Check runs and their inline notes cannot be removed by anyone, including SeedQ — GitHub provides no means to delete a published check — so those remain attached to the commit they assessed.
4. Accounts & eligibility
You need a GitHub account to use SeedQ, and you must have authority to install it on any organisation you connect. You’re responsible for activity under your account and for keeping your access secure. You must be at least 18.
An owner or admin of a workspace can let SeedQ staff view it, read only, for 14 days. We use that access only to help with what you asked us about. Staff can’t change anything while viewing, the access ends by itself after 14 days or as soon as an owner or admin ends it, and every visit is listed on the workspace’s Members page. We never view a workspace this way unless it has been switched on.
5. Acceptable use
You agree not to:
- use SeedQ to break the law or infringe others’ rights;
- scan repositories you don’t own or have permission to analyse;
- attempt to disrupt, overload, reverse-engineer or gain unauthorised access to the service; or
- resell or misrepresent the service.
6. Your integrations
The Integrations scans run against read-only credentials you provide — API tokens or OAuth grants for providers such as Supabase, Vercel, Neon, Stripe and Cloudflare. Your use of those providers remains subject to their own terms, and any usage under your credentials is billed to your own account. If a credential is missing or invalid, SeedQ degrades gracefully (the scan reports what isn’t connected) rather than failing your workflow.
If you connect SeedQ to your builder, the builder can read what you see in SeedQ about the apps in that workspace: their names, when each was last checked and what the check found (problem titles, plain explanations, fix prompts and counts, and the file and line each problem is in), your launch checklist and your own steps before launch (which it can also add to and tick off, as you), what is waiting for your decision, what Guardian recorded about your pull requests, issues, builds and bug reports, SeedQ’s AI reviews of your pull requests (the verdict, each point the review raised and the fix it suggests, never a file path or line number), and the bug reports and ideas your users sent (their titles, how many people sent each, when and on which page, and for a bug the number of the GitHub issue we filed for it), and your themes and the open tasks not sorted into one (their titles and the start of their text, read from GitHub and not kept), for which it can suggest a theme, as you, that waits in SeedQ until you accept it. It never receives your files, commit messages or anyone’s email address. On a free plan it sees only the titles of locked areas, as you do. To disconnect it, revoke its token under Settings › Connect › Your builder; it stops working at once.
If you connect SeedQ in the Claude app or in Lovable, that connection is treated as a builder token: it acts as you, in the one workspace you chose, until you disconnect it.
7. Subscriptions, trial & billing
Each paid plan — SeedQ Launch Pro, SeedQ Launch Studio and SeedQ Guardian — is a recurring subscription billed through Stripe at the price shown at checkout, and may include a free trial. Unless you cancel before the trial or renewal date, the subscription renews automatically for the next period. You can cancel any time from your billing settings; cancellation takes effect at the end of the current period. If you’re unhappy within 14 days of your first charge, email us and we’ll refund it. Beyond that, subscription payments are non-refundable except where the law requires otherwise. Prepaid AI tokens have their own refund rule, below. We may change pricing on reasonable notice.
Prepaid tokens
On a paid plan you can buy AI tokens, which pay for the work SeedQ does with an AI model, such as AI review. 100 tokens cost $1, and a purchase is at least $10. Your rule-check scans never use tokens.
- Tokens are not money. They are prepaid credit for SeedQ’s AI work in the workspace that bought them. They have no cash value, and they can’t be transferred, sold or exchanged for anything else.
- What a run costs. When “Quote before each run” is on, we show you the most a run can cost before it starts, and it doesn’t start until you press Run. An AI review of a pull request does not wait for you to press Run: the label or automatic reviews start it. A run never takes more tokens than your limit per run, or than your balance when you haven’t set a limit. If the work costs us more than that, we pay the difference.
- Auto top-up. If you turn on auto top-up, you are giving us a standing instruction to charge the card saved with Stripe the amount you chose each time your balance falls below the level you set. It stays in force until you turn it off, which you can do at any time in your settings.
- Expiry. Tokens don’t expire while the workspace has an active paid plan. They can only be spent while it does, and they are deleted with the workspace if it is erased.
- Refunds. Ask us within 30 days of buying tokens and we’ll refund the ones you haven’t used to the card you paid with. Tokens SeedQ added to your balance without charge aren’t refundable. This doesn’t limit any right you have by law.
8. Intellectual property
We own the SeedQ application, its design and content. You keep all rights in your code and repositories — using SeedQ grants us no ownership of them, only the limited read access needed to provide the service. Scan output we generate for you is yours to use within your organisation and to share with your own clients.
9. Disclaimers
SeedQ’s findings are advisory. They are automated checks, not a guarantee. A passing scan does not certify that your software is secure, compliant or production-ready, and SeedQ is not a substitute for professional security, legal or data-protection advice — including on GDPR. You remain responsible for your own compliance.
AI logic review results are estimates. They are produced by an AI model, can be wrong in either direction, and are labelled as estimates wherever they appear. A review that finds nothing does not mean your app has no logic problems. Check a finding yourself before acting on it.
The service is provided “as is” and “as available”. To the fullest extent permitted by law we disclaim all implied warranties, including merchantability, fitness for a particular purpose, and that findings are complete, accurate or error-free.
10. Limitation of liability
To the fullest extent permitted by law, SeedQ will not be liable for indirect, incidental or consequential losses, or for lost profits, data or goodwill. Our total liability arising from the service is limited to the greater of the amount you paid us in the 12 months before the claim, or £100. Nothing in these Terms excludes liability that cannot be excluded by law (such as for death or personal injury caused by negligence, or fraud).
11. Termination
You can stop using SeedQ and uninstall the GitHub App at any time. We may suspend or terminate access if you breach these Terms or to protect the service, and while SeedQ is in beta we may end anyone’s beta access at any time. When we end access we may also remove the SeedQ GitHub App from your GitHub account. On termination your right to use the service ends; the data provisions in our Privacy Policygovern what happens to your data, and you can request erasure.
12. Changes to these terms
We may update these Terms as the product evolves. We’ll update the date above and, for material changes, give prominent notice. Continued use after a change means you accept the updated Terms.
13. Governing law
These Terms are governed by the laws of Germany, and its courts have exclusive jurisdiction, subject to any mandatory consumer protections in your country of residence.
14. Contact
Questions about these Terms: support@seedq.dev.