These Terms of Service (the "Terms") govern access to and use of Bugweg's website, GitHub app, dashboard, and related services (together, the "Service"), offered by PAFTAK Software Inc., a corporation incorporated under the laws of the Province of Alberta, operating under the trade name "Bugweg," with its principal place of business in Alberta, Canada ("Bugweg," "PAFTAK," "we"). By creating an account, installing Bugweg's GitHub app, or otherwise using the Service, you ("you" or "Customer") agree to these Terms on your own behalf and, where applicable, on behalf of the organization you represent.
1. Acceptance of these Terms
If you do not agree to these Terms, do not install, access, or use the Service. If you enter into these Terms on behalf of a company or other organization, you represent that you have the authority to bind it, in which case "you" refers to that organization.
2. Description of the Service
Bugweg is an AI-assisted code review and defect-prevention platform. The Service:
- analyzes pull request diffs on repositories you connect through a multi-stage pipeline (edge pattern-matching, structural analysis, comparison against bug history, and, where warranted, a large-language-model review), and posts review comments on your pull requests;
- maintains, per repository, a history of previously flagged and fixed defect patterns ("Bug Genealogy"), a per-file risk score, and, if an organization admin switches it on, a per-developer pattern profile ("Developer Bug DNA");
- lets you turn a fixed defect into a rule that flags or blocks similar future changes ("Recurrence Firewall"); and
- when you connect a supported error tracker (currently Sentry and Rollbar), detects when a production incident is marked resolved and generates a candidate regression test, validated against the commits before and after the fix, delivered as a pull request for your team's review ("Production Lock").
The Service evolves over time; we may add, modify, or remove features, and will give notice as described in section 18 of any change that removes or reduces a feature you pay for.
3. Eligibility and accounts
You must be at least 18 years old, or have reached the age of legal majority in your jurisdiction, and have the legal capacity to enter into these Terms. You are responsible for the confidentiality of your account credentials and for all activity under your account. Notify us promptly at security@bugweg.com if you suspect unauthorized use of your account.
Not offered in Quebec. The Service is not offered to customers located in the Province of Quebec, Canada. You are "located in Quebec" if you are an individual who resides in Quebec, or an organization whose billing address is in Quebec or whose establishment in Quebec enters into, or pays for, these Terms. By installing the Service, creating an account, starting a free trial, or subscribing to a paid plan, you represent that you are not located in Quebec and, if you act for an organization, that it is not located in Quebec. We check the billing address you give when you verify a card or subscribe. We do not start a free trial for a Quebec billing address. If a Quebec billing address is entered at payment, we cancel the subscription immediately and refund that payment in full. If we later learn that a customer is located in Quebec, we may refuse, suspend, or end its access; if we end a paid subscription for that reason, we will refund the amount paid for the period not yet used. We rely on the location information you give us. If you use the Service from Quebec by giving us inaccurate location or billing information, or by masking your location (for example with a VPN), you do so at your own risk and in breach of these Terms, and, to the extent permitted by law, we are not liable for any loss or claim that results.
4. Plans, billing, and free trials
The Service is offered under the plans described on our pricing page, currently a free trial and paid Developer and Team plans billed per seat, in advance, monthly or annually as you choose at checkout or later from the billing page, plus applicable taxes. A "seat" means a person (or a GitHub bot account, as described below) who is the author of a pull request that the Service reviews on your repositories during a calendar month (UTC), counted when the pull request is opened or updated, and counted once per month however many pull requests they author. GitHub bot accounts (accounts GitHub marks as bots, such as names ending in "[bot]", including GitHub App accounts) are counted as seats on the Team plan, one seat each, like other accounts, on public as well as private repositories (a bot account is never treated as an outside contributor). If a bot account that you did not add or install was counted as a seat, write to hello@bugweg.com within 30 days of the renewal and we will refund that seat. Other accounts, including machine users, are counted. A GitHub bot account can never hold the Developer seat. On a public repository, the author of a pull request whom GitHub does not list as an owner, member or collaborator of the repository (an outside contributor) is not counted as a seat and does not take the Developer seat; their pull requests are reviewed and use your review allowance. On the Team plan, the author of a pull request that is not reviewed because your monthly allowance or a review ceiling has been reached is not counted for that pull request. Only an organization admin can subscribe. The Developer plan covers one seat, held by the subscriber: the GitHub account connected to the bugweg account of the admin who subscribed (connecting one is required to subscribe to Developer), or of an organization admin who later moves the seat to themselves in the dashboard. If the seat is ever unset, for example after a change from the Team plan to the Developer plan, the first person (other than an outside contributor or a GitHub bot account) whose pull request the Service is asked to review in a calendar month holds it for that month, until an organization admin takes it. Pull requests from anyone else, including GitHub bot accounts, are not reviewed until you move to the Team plan, except pull requests from outside contributors. The Team plan has a minimum of two seats; each renewal is charged for the higher of the number of seats in the current and in the previous calendar month, as last counted before the renewal (we update the count daily). Your monthly pull-request review allowance, and how reviews are counted against it (currently at most one review per pull request per day, UTC), are set out on the pricing page; on the Team plan it is calculated on the higher of the seats counted in the current month and the seats you are billed for. A pull request is reviewed at most 10 times a day (UTC). The Developer and Team plans also have review ceilings (see how reviews are counted), which count every review that starts, even if it then fails or does not complete, including further reviews of a pull request that use none of your allowance: a daily ceiling, per day (UTC), of 30 reviews on the Developer plan and, on the Team plan, 15 reviews per seat with a minimum of 40; and a monthly ceiling, per calendar month (UTC), of one and a half times the plan's monthly allowance, that is 225 reviews on the Developer plan and, on the Team plan, 150 reviews per seat with a minimum of 450. If reviews fail because of a fault on our side and this causes you to reach a ceiling, write to hello@bugweg.com and we will look into it. Seats are counted for the ceilings as for the allowance. Once a ceiling is reached, pull requests are not reviewed: a review refused for this reason is not run and uses none of your allowance, and the pull request's check says why (for the monthly ceiling, we also comment on a pull request when it is opened). A refused review is not run again on its own: once the daily ceiling resets at 00:00 UTC, or the monthly ceiling on the first day of the next calendar month (UTC), the next push to a pull request, or a newly opened one, is reviewed. The monthly ceiling follows the calendar month, not your billing period. The ceilings that apply are those of the plan you are on when a review starts, and the reviews already counted that day or month still count after a change of plan (for example, after a change from the Team plan to the Developer plan, the Developer ceilings apply to the rest of the month). Prices, the review allowance and the review ceilings may change only as described in section 18. The ceilings do not apply to the free trial and do not change the price of any plan.
- Free trial. The Service includes a one-time free trial of three PR reviews for each developer, for up to as many developers as there are members of your bugweg team, for each payment card verified with us. In this bullet, a "developer" is the GitHub account, identified by its numeric GitHub user id (so renaming the account does not change it), that authored the pull request being reviewed, and your "bugweg team" is your organization in your bugweg account; its members are the people who belong to that organization. Card verification (a $0 authorization, not a charge) is required to start the trial; your card is not charged during the trial. The number of developers is checked when a developer's first trial review on a card would start: once a card covers as many developers as your bugweg team then has members (at least one), pull requests from further developers are not reviewed under the trial with that card. A developer who has started a trial with a card continues it on every GitHub account (personal or GitHub organization account) and repository verified with that card, and keeps any reviews they have left if your bugweg team later becomes smaller. Trial reviews used with a card before the per-developer trial began on October 14, 2026 count against the three reviews of the first developer who uses the trial with that card after that date. Pull requests from outside contributors on public repositories (as described above) do not count as developers; with each card, they share one further set of three trial reviews. Each GitHub bot account gets its own three trial reviews with each card, for up to three bot accounts per card, and bot accounts do not count toward the number of developers a card covers; further bot accounts share the outside contributors' set. Every review counts, including the review of each new push to a pull request, and a trial review counts when the review starts, even if it then fails or does not complete. You must not verify additional payment cards, create or use additional GitHub accounts, or add people to your bugweg team who do not work with you, in order to obtain trial reviews for a person who has already used theirs. You are responsible for informing the developers whose pull requests are reviewed under the trial that we keep their numeric GitHub user id for this purpose, as described in section 3 of our Privacy Policy. If the trial is blocked in error, or a trial review fails because of a fault on our side, write to hello@bugweg.com and we will look into it. To keep receiving reviews once your trial reviews are used, you must subscribe to a paid plan, at which point your payment method will be charged on a recurring basis until cancelled.
- Payment processing. Payments are processed by Stripe. By subscribing, you authorize us (through Stripe) to charge your payment method on a recurring basis until cancelled.
- Plan changes and cancellation. An organization admin may change plans or cancel at any time from the billing page in the dashboard; anyone at your organization can also write to hello@bugweg.com and we will cancel on request. A change to a higher plan, or from monthly to annual billing, applies at once and the difference is charged at once. For a higher plan, the charge is prorated for the rest of the current period. For annual billing, you pay a full year, less a credit for the unused part of the current month. The billing page shows the amount, with taxes, before you confirm. A change to a lower plan, or from annual to monthly billing, applies at the end of the billing period you have paid for, with no refund for the rest of it. A team can have only one subscription at a time; if a second one is paid while the first is active, we cancel the second one and refund it in full. If you cancel, the cancellation takes effect at the end of the billing period you have paid for (the month, or the year on an annual plan): the Service stays available until then, you are not charged again, and your paid plan then ends. Cancellations requested by email take effect in the same way. This does not apply where these Terms provide for an immediate cancellation with a refund (section 3, section 6, section 18, or a duplicate subscription). Except as stated above, in section 3, section 6 and section 18 or where required by law, amounts already paid are non-refundable.
- Annual plans. An annual subscription to the Developer or Team plan begins on the date you enter into it: your checkout date, or the date you switch from monthly to annual billing. From that date it is a commitment for a term of 12 months, and the year is charged at the start of the term, as described above and, for the Team plan's seats, on the pricing page. If you cancel during the term, the cancellation takes effect at the end of the term, as described above. Unless cancelled, the subscription renews automatically for a new 12-month term, charged at the start of that term. The price and the usage limits (the monthly review allowance and the review ceilings) in effect at the start of a term stay the same until the end of that term. Each renewal is charged at the price per seat, and has the usage limits, in effect on the renewal date. A higher price or lower usage limits apply at a renewal only if we gave you notice of them at least 30 full days and not more than 60 days before the renewal date, as described in section 18. Amounts paid for an annual term are not refunded if you cancel early, except as stated in these Terms or where required by law.
- Price changes. A change to a price never affects a billing period that has already started: the price in effect at the start of a monthly billing period, or of an annual 12-month term, stays the same until that period or term ends. A higher price applies to your subscription only from the start of a later billing period (on an annual plan, from a renewal), and only if we have given you notice of it, at least 30 full days and not more than 60 days before that period starts, as described in section 18. On a monthly plan, this means the new price usually applies from the second billing period after our notice, not the next one. If you do nothing, your subscription renews at the new price and keeps renewing until you cancel. If you cancel before the period the new price applies to starts, you are not charged the new price. On the Team plan, the price is the price per seat: a change in the number of seats you are billed for is not a change of price, and neither is a change in applicable taxes. The notice rule above does not apply to a change of plan or of billing period that you choose: it is charged at the price in effect for new subscriptions on the day you make it, as shown on the billing page before you confirm. A lower price may apply sooner.
- Plan limits. Each plan includes a monthly PR-review allowance, the review ceilings described above, and specific features described on the pricing page. Once the allowance or a ceiling is reached, further pull requests are not reviewed (they are not queued) until it resets; on the Developer plan you can move to the Team plan for a larger allowance.
5. Acceptable use policy
You must not, and must not permit any third party to:
- use the Service to store, transmit, or process credentials, source code, or data that were disclosed, stolen, or unlawfully obtained;
- resell, sublicense, or redistribute code summaries, review results, or Bug Genealogy data generated by the Service to a third party as a standalone product or service;
- reverse engineer, decompile, or attempt to extract the underlying models, prompts, or algorithms used by the Service, except to the extent such a restriction is unenforceable under applicable law;
- use the Service to build a competing product;
- attempt to circumvent rate limits, plan limits, or authentication controls; or
- use the Service in violation of applicable law, including export control, sanctions, and data protection law.
We may suspend or terminate access for violation of this section, with notice where reasonably practicable.
6. App permissions and third-party integrations
The Service requires installing a GitHub app with the minimum permissions necessary for it to function: read access to pull request and repository content, and the ability to post commit statuses, checks, and (for Production Lock only) open pull requests. The current permission set and its rationale are described on our Security page. You may connect optional third-party integrations (including Slack, Jira, Linear, Sentry and Rollbar); your use of those integrations is also subject to that third party's own terms, and we are not responsible for their acts or omissions.
Service providers that process your code and data. We use service providers (subprocessors) to provide the Service. The providers that process your code and data are Cloudflare (review pipeline and the API behind the dashboard, including the Cloudflare Workers AI model that triages pull request diffs), Neon (database hosting), Fly.io (code parsing and test sandboxes), Anthropic (language model inference for review, test generation and Bug Search assessment) and Voyage AI (text embeddings); Vercel, Clerk, Stripe, Sentry, Resend and Zoho Mail receive account, billing, support or website-visit data. The complete list, with the purpose, data and location for each provider, is in section 7 of our Privacy Policy, which is incorporated into these Terms by reference. We will update that list before a new or replacement provider begins processing your data. If the new or replacement provider will receive your code, we will also notify you by email at the address associated with your account (for an organization, its administrators) at least 30 full days, and not more than 60 days, in advance (or as soon as reasonably practicable if an urgent security or continuity need requires a faster change); if you object, you may cancel your subscription before the change takes effect and receive a prorated refund of any prepaid fees for the remaining term. Updates to that list are governed by this section rather than by section 18.
Voyage AI training opt-out. Voyage AI's standard terms allow it to use customer content to train and improve its models unless the customer opts out. We opted out on October 2, 2026. Before that date, the Service was in private testing: the only content we sent to Voyage AI came from repositories in our own GitHub accounts and from test data, and no customer content was sent to Voyage AI before the opt-out took effect.
7. AI-generated content; no guarantee of accuracy
You are solely responsible for reviewing, testing, and validating any suggestion, comment, risk score, code, or test generated before relying on it or merging an associated change. Bugweg is not responsible for decisions made in reliance on content generated by the Service, including a failure to flag a real defect ("false negative") or an incorrect flag ("false positive").
8. Regression tests and Production Lock
When enabled, Production Lock generates a candidate regression test from a resolved production incident and validates it by confirming the test fails on the commit before the fix and passes on the commit after it, before opening it as a pull request. This validation reduces, but does not eliminate, the risk that a generated test is subtly incorrect or incomplete. Generated tests and associated code changes are never merged automatically. Your team is responsible for reviewing and approving every such pull request before merging, exactly as with any other contribution to your repository.
9. Intellectual property
Your content. You and your organization retain all right, title, and interest in your source code, repositories, and data. Nothing in these Terms transfers ownership of your code to Bugweg.
Our Service. We and our licensors retain all right, title, and interest in the Service itself, including its software, models, prompts, risk-scoring methodology, and any aggregated or de-identified data derived from Service usage (such as bug-pattern fingerprints and embedding vectors; note that AI-generated issue descriptions stored as part of that data may quote short excerpts of your code — see our Privacy Policy, section 4 for exactly what is and isn't retained). We grant you a limited, non-exclusive, non-transferable license to access and use the Service during your subscription, solely for internal business purposes.
Feedback. If you provide us suggestions or feedback about the Service, you grant us a perpetual, irrevocable, royalty-free license to use it without restriction or obligation to you.
10. Fair use and rate limits
To protect the Service and other customers from abuse or runaway costs, we apply per-team rate limits on natural-language queries, API calls, and analysis requests. We may adjust these rate limits from time to time and will describe current limits on our pricing or documentation pages. Your plan's monthly review allowance and the review ceilings (section 4) are usage limits that we set as a business decision; we may change them as described in section 18: with notice, and on an annual subscription not during its current 12-month term.
11. Confidentiality of your code
The Service is designed so that pull request diffs, and the full content of files read for analysis, are processed without being written to our database. Bug Search stores numerical embeddings of code chunks (not the code text), and test runs use a temporary copy of the needed files, or of the repository for Test Coverage Gap, in a sandbox that is discarded after the run. The AI-generated review text describing a flagged issue is, however, retained, and may quote a short excerpt of your code where relevant to the explanation. Your code is shared with the service providers listed in section 6 only as needed to provide the Service, including the Voyage AI disclosure in that section. The full detail of what is and isn't retained is described in our Privacy Policy and our Security page, which are incorporated into these Terms by reference.
12. Disclaimer of warranties
Except as expressly stated in these Terms, the Service is provided "as is" and "as available," without warranty of any kind, express, implied, or statutory, including the implied warranties of merchantability, fitness for a particular purpose, title, and non-infringement. We do not warrant that the Service will be uninterrupted, error-free, or that all defects will be detected or fixed.
13. Limitation of liability
To the maximum extent permitted by applicable law: (a) neither party is liable for indirect, incidental, special, consequential, or punitive damages, or loss of profits, revenue, data, or goodwill, arising from these Terms or the Service, even if advised of the possibility of such damages; and (b) our total liability arising from these Terms or the Service will not exceed the amount you paid us for the Service in the twelve (12) months preceding the event giving rise to the claim. Nothing in this section limits liability that cannot be limited under applicable law, including liability for gross negligence, willful misconduct, or death or personal injury caused by our negligence, where applicable law prohibits such a limitation.
14. Indemnification
You will defend, indemnify, and hold Bugweg harmless from any third-party claim arising from your breach of these Terms, your misuse of the Service, or your violation of applicable law, except to the extent it results from our own breach of these Terms.
15. Export control
You represent that you are not located in, and do not use the Service from, a country subject to comprehensive trade sanctions, and are not a person or entity subject to applicable export control or sanctions restrictions. You will not use the Service to analyze or process source code or data whose export is restricted under applicable law without the required authorization.
16. Term, suspension, and termination
These Terms remain in effect for as long as you use the Service. We may suspend or terminate your access for material breach of these Terms, non-payment, ineligibility under section 3, or a legal or security requirement, with notice where reasonably practicable. You may terminate at any time by cancelling your subscription and uninstalling the GitHub app; cancellation takes effect as described in section 4. Sections that by their nature should survive termination (including sections 9, 12, 13, 14, and 17) survive.
17. Governing law and dispute resolution
These Terms are governed by the laws of the Province of Alberta and the federal laws of Canada applicable therein, without regard to conflict-of-law principles. Subject to any mandatory consumer-protection law of your jurisdiction that cannot be waived, you and Bugweg submit to the exclusive jurisdiction of the courts of Alberta for any dispute arising from these Terms or the Service.
Where the Service is offered. We offer the Service from Alberta, Canada. See section 3, "Not offered in Quebec".
18. Changes to these Terms, prices and usage limits
How we give notice. When this section says we give notice of a change, we email your organization's admins (and your billing contact, if different) and show the notice in the dashboard at least 30 full days, and not more than 60 days, before the change takes effect for your subscription, not counting the day we send the notice or the day the change takes effect. The notice says what changes (the new text of any changed provision of these Terms, or the old and the new price or usage limit), why, the date it takes effect for your subscription, what happens if you do nothing, and how to cancel before that date, as described below.
Changes to these Terms. We may change these provisions of these Terms: the description of the Service (section 2); plans, prices, seat counting, free trials, review allowances and review ceilings (section 4); acceptable use and fair use (sections 5 and 10); app permissions and service providers (section 6); and any other provision where a change is needed because of a change in the law or a regulator's requirement, or because a service provider changes or withdraws its service. A change to the cancellation or refund terms can only add to your rights or reduce your obligations, never the reverse. A change applies only from the date it takes effect; it never applies to a claim or dispute that arose before that date. We give notice of each new version as described above, except that a version that only corrects or clarifies wording without changing anyone's rights or obligations, or that only adds to your rights, may take effect on the day we email it to your organization's admins. When a new version takes effect, each user is asked to accept it in the dashboard; until a user accepts it, that user can use only the billing page, the steps to cancel, and the tools to delete data. A new version of these Terms never pauses or stops reviews of your organization's pull requests: reviews continue whether or not anyone has accepted it. If your organization keeps using the Service after a new version takes effect, for example by keeping the GitHub app installed so that we keep reviewing pull requests, or by renewing your subscription, the new version applies to your organization from the date it takes effect, even if no organization admin has accepted it in the dashboard. If you do not agree to a new version, cancel your subscription and uninstall the GitHub app. The billing page stays available for that purpose, and you can get a refund as described in the next paragraph.
Refund if you do not accept a new version. If you cancel because you do not accept a new version of these Terms, you get a refund. To claim it, tell us at hello@bugweg.com, within 30 days after the new version takes effect, that you are cancelling because you do not accept it. The cancellation then takes effect on the day you tell us (or, if you tell us before the new version takes effect, on the date it takes effect), the Service is not available after that, and the new version does not apply to you. We refund the amount you paid for the billing period, or the annual term, in progress on the day the cancellation takes effect, prorated by the day: that amount multiplied by the number of days from that day to the end of the period or term, divided by the number of days in the period or term. Applicable taxes are refunded in the same proportion. We send the refund within 15 days after you tell us. There is no refund under this paragraph if an organization admin accepted the new version before you told us; for a subscription that started after we sent the notice of that version, if the new version and the date it takes effect were shown to you before you subscribed; or for an annual term that renewed more than 30 full days after we sent that notice. We give at most one such refund per subscription for each version of these Terms.
Changes to prices and usage limits. We set our prices and usage limits (each plan's monthly review allowance and the review ceilings in section 4) as business decisions, and we may change them, for example because of changes in our costs or in the market. A change never applies to a billing period that has already started: the price and the usage limits in effect at the start of a monthly billing period, or of an annual 12-month term, stay the same until that period or term ends. A higher price or a lower usage limit applies to your subscription only from the start of a later billing period (on an annual subscription, from a renewal), and only if we have given you notice of it as described above; the notice gives the date on which your subscription first pays the new price or has the new limit. If you do nothing, your subscription renews on that date at the new price, or with the new limits, and keeps renewing until you cancel. A lower price or a higher limit may apply sooner, including during a billing period, without a notice period. On the Team plan, the price is the price per seat: a change in the number of seats you are billed for (section 4) is not a change of price, and neither is a change in applicable taxes. A change to the Team plan's minimum number of seats, or to how seats are counted, that can increase the amount you pay is treated as a higher price. If a change also changes the text of these Terms (for example, the review ceilings stated in section 4), the updated Terms are a new version, given with the same notice; the changed prices or limits still apply to a subscription only from the billing period or renewal described in this paragraph.
If you do not want to continue. You can cancel your subscription from the billing page, or by writing to hello@bugweg.com, at any time before a change takes effect. The cancellation takes effect at the end of the billing period you have paid for (section 4), unless you claim a refund under the paragraph on new versions of these Terms, in which case it takes effect as described there. Because a higher price or a lower usage limit applies only from a later billing period or renewal, you are not charged the higher price, and your usage limits are not reduced, before your subscription ends. If your subscription is charged, for the first time, a higher price per seat, or a higher amount because of a change to the minimum number of seats or to how seats are counted, that we gave you notice of under this section, and within 14 days after that charge you tell us at hello@bugweg.com that you are cancelling (or you cancel from the billing page and tell us), your subscription ends on the day you tell us and we refund that charge, prorated by the day for the days left in the billing period or term, with applicable taxes in the same proportion, within 15 days. This refund is given once per subscription for each price change, and not for a charge that is higher only because more seats were counted under the rules already in effect, because of a change in taxes, or because of a plan or billing change you chose. If we ever charge your subscription a higher price, or apply a lower usage limit, without giving you the notice this section requires, the higher price or lower limit does not apply to that billing period or term: we refund the difference within 15 days of learning of it, and you may also cancel and receive the refund described above.
Consumers. If you are a consumer under a consumer protection law that applies to you, we make changes to your agreement in the way that law requires, and where it gives you more notice or other rights than this section, those apply.
19. Miscellaneous
Your rights under consumer protection laws. Nothing in these Terms limits any right you have under consumer protection laws that apply to you and that cannot be waived or limited by contract.
Entire agreement. These Terms, together with the Privacy Policy and any order form or plan description referenced in them, constitute the entire agreement between you and Bugweg regarding the Service.
Severability. If a provision is found unenforceable, the remaining provisions remain in effect, and the unenforceable provision will be deemed modified to the minimum extent necessary to make it enforceable.
Assignment. You may not assign these Terms without our prior written consent; we may assign these Terms in connection with a merger, acquisition, or sale of substantially all of our assets.
Force majeure. Neither party is liable for a failure to perform caused by events outside its reasonable control.
No waiver. Failure to enforce a provision is not a waiver of the right to do so later.
20. Contact
Questions about these Terms can be sent to hello@bugweg.com. Security-related reports can be sent to security@bugweg.com.