Privacy Policy

Analytics status

Analytics is not configured for this deployment, so the website does not load a public analytics script or report visitor countries yet.

1. Who this policy applies to

This policy applies to visitors, account holders, team members, admins, and users who connect the Windows application to the same UGP account.

If you use UGP through an organization, the organization may control the account, team, billing, and project records associated with your use.

For procurement, invoices, or formal notices, use the contact below so the UGP owner can provide the appropriate contracting details instead of publishing unverified legal identifiers on the public site.

2. Information you provide

Account information can include email address, display name, password authentication state, Google OAuth identifiers when Google sign-in is used, profile settings, team memberships, billing email, support messages, and security preferences.

Billing information can include plan, subscription status, Stripe customer and subscription identifiers, invoice references, payment portal events, credits, usage totals, and cancellation state. Full card details are handled by Stripe, not stored by the UGP website.

Team and organization information can include team names, roles, invitations, ownership, members, project links, account permissions, and audit-relevant account actions.

3. Project, agent, and usage information

Project records can include project name, local path label, language, status, team association, timestamps, and activity counts. The website shows these records when the API returns them.

Agent records can include goals, statuses, provider and model metadata, steps, checkpoints, tool events, timestamps, messages, and project links. These records help you review what happened during an AI-assisted coding task.

Usage records can include provider, model, input tokens, output tokens, cost, forecast, monthly spend, remaining credits, and export events so the account portal can show consumption and plan limits.

4. Desktop application and local code

UGP is designed around a Windows application for local coding work. Opening, reading, editing, testing, terminal actions, and Git-related work happen in the desktop workflow.

Whether prompts, file excerpts, command output, or responses are sent to an external AI provider depends on the server configuration, selected provider, account settings, and action you request.

You should review generated code, commands, and suggested changes before relying on them. AI output may be incomplete, incorrect, or unsuitable for your project without human review.

5. Information collected automatically

The website and API may process session cookies, request metadata, IP-derived security signals, device records, browser details, route access, rate-limit events, and error logs to keep accounts and protected pages working.

Linked device records can include device name, platform, OS version, scopes, status, IP address, linked time, last activity, and revocation state.

Optional website analytics is loaded only when a real provider is configured, documented in the Cookie Policy, and the visitor explicitly accepts optional analytics. Analytics must not be represented as active when provider configuration or consent is missing.

6. How UGP uses information

UGP uses information to authenticate users, keep sessions secure, operate the account portal, connect the Windows application, show projects and agent history, manage API keys, teams, devices, and integrations, and process billing through configured providers.

UGP also uses information to calculate usage, show plan limits, prevent abuse, debug service errors, respond to support requests, maintain security, and comply with legal or billing obligations.

UGP does not sell personal information. UGP does not use public website text to imply that code or prompts are used for model training unless that is expressly documented by the configured provider and accepted by the account owner.

7. How information is shared

Information may be shared with service providers that are necessary to operate UGP, such as hosting, database, authentication, email delivery, billing, logging, security, and AI provider services configured by the operator.

Stripe may receive billing information when you open Checkout or the Customer Portal. Google may receive OAuth information when Google sign-in is configured and used.

For team accounts, admins and owners may see team members, project records, usage, billing state, invitations, API key metadata, and device records needed to operate the team.

UGP may disclose information if required by law, to protect rights and security, to investigate abuse, or as part of a business transfer where user information remains subject to appropriate protections.

8. Retention and deletion

UGP keeps account, billing, security, and usage records for as long as needed to operate the service, meet billing and legal obligations, resolve disputes, maintain audit history, and prevent abuse.

Account pages can expose deletion, export, revocation, and logout actions where supported by the API. Some records, such as invoices, security logs, or abuse-prevention records, may need to be retained longer.

If you want access, correction, export, deletion, or account closure, contact support with the email address associated with the account.

9. Security

UGP uses protected routes, session cookies, API authentication, scoped keys, revocation flows, and account security pages to reduce unauthorized access.

No internet service can guarantee perfect security. You are responsible for protecting your account credentials, reviewing linked devices, rotating exposed API keys, and limiting team permissions to the access people need.

If you believe your account, key, device, or team has been compromised, contact support immediately and revoke affected sessions or credentials from the portal where possible.

10. Your choices and rights

Depending on your location, you may have rights to access, correct, delete, export, restrict, or object to certain processing of personal information.

You can manage account settings, API keys, devices, teams, and billing routes from the portal. You can also contact support for privacy requests that are not available in the UI.

You may select necessary-only cookies or change a prior optional-analytics choice on the Cookie Policy page. Necessary cookies are required for sign-in, security, and account sessions.

11. Children, international use, and changes

UGP is intended for professional and developer use and is not directed to children.

If you access UGP from another country, your information may be processed where the service, hosting, billing, email, or AI providers operate.

UGP may update this policy as the product, providers, legal requirements, or account features change. Material updates should be reflected on this page with a new date.