Privacy Policy

Effective date: October 1, 2026

Responsible operator: UGC.run

Privacy contact: contact@ugc.run

This Policy explains personal-information practices for UGC.run’s website, management dashboard, creator mobile app, reporting tools, APIs, CLI, MCP connections, and related support. It also covers information about people whose public social content a Customer asks us to track, even if those people have not created a UGC.run account.

For account administration, our own billing, security, service operations, and the improvement activities described below, UGC.run determines the purposes and means of processing. When we process campaign records on a Customer’s instructions, we generally act as its service provider or processor, subject to the relevant agreement and applicable law. The Customer controls its campaign purposes and is responsible for its own notices and lawful instructions. These roles depend on the actual processing, not just the labels used here.

A Customer can add a Creator and public handles before that Creator joins the app. Customers and authorized managers may view, correct, export, or delete campaign information and may approve someone’s access to an existing creator record. Contact your campaign manager about campaign-specific decisions. You can also contact us, and we will route requests where appropriate rather than treating all campaign information as beyond our responsibility.

Account and identity information

We process names, email addresses, user and authentication-provider identifiers, login/session information, roles, invitations, project memberships, approval decisions, and related timestamps. Information comes from you, authorized administrators, and sign-in providers such as Apple and Google through our authentication service. An Apple private-relay address may be used when selected. We do not receive your Apple or Google password through social sign-in. Password-based sign-in, where offered, is handled by our authentication provider.

Campaign and creator information

We process campaign names, creator names, linked platforms and handles, posting requirements, account status, rate settings and histories, assignments, permissions, performance qualifications, and administrative notes. A Customer may provide these records directly. The app can associate an approved member with previously stored creator information rather than asking for all information again.

Social profiles, content, and metrics

From handles, public URLs, social-data providers, and connected services, we obtain public profile information and account identifiers; post descriptions and captions; post IDs and links; thumbnail and video URLs; publication and observation times; and available view, like, comment-count, and share metrics. Account checks can retrieve additional public-profile response fields needed to assess the profile and match its handle. The current tracking features primarily store engagement counts, not a general archive of commenters’ private messages.

We store content references, metrics, snapshots, qualification flags, and derived summaries used in the Service. Media may be retrieved or transferred when displayed, downloaded, or cross-posted. A public post can contain names, faces, voices, or other personal information, including information about people who are not UGC.run users. Public availability does not eliminate applicable privacy rights.

Payment instructions and campaign records

Creators and managers may provide a payment method and a recipient reference, such as an email address, username, phone number, or bank-transfer reference. We store those details and campaign payment calculations, adjustments, notes, paid/unpaid status, and related dates. Do not enter full bank-login credentials, card numbers, or unrelated financial details into these fields. These campaign records are distinct from the payment information used to buy a UGC.run subscription.

UGC.run subscription information

Stripe processes subscription checkout and billing. We receive and store identifiers and subscription information needed to manage billing, such as customer, checkout, subscription, price, and event identifiers; plan and billing-period details; status; and account-related billing metadata. Card information entered into Stripe’s checkout is processed by Stripe; the reviewed UGC.run application does not store full payment-card numbers in its own subscription tables. Stripe’s own privacy terms also apply to its processing.

Checklists, uploaded media, and communications

Customers can upload checklist images and videos and provide text, tips, links, and instructions. We process file information, stored-media references, checklist versions, completion information, and video-watch verification tokens and related records. The watch mechanism supports completion checks; it does not record the viewer through their camera.

We process notifications, reminder settings, message content, delivery/read information where supported, support correspondence, and campaign support contact details. Notifications can include information visible on a device’s lock screen, depending on device settings.

Integrations and cross-posting

When an authorized user configures a connection, we process the relevant API keys or access tokens, account/application identifiers, selected creators and destinations, and settings. RevenueCat and Superwall chart integrations retrieve reporting data such as new-user, trial, revenue, proceeds, and cohort totals. The reviewed chart implementation requests reporting aggregates rather than a general customer-identity export. Meta integration requests account-level ad-spend information. Actual provider responses and their request metadata are processed to supply these features.

For PostBridge cross-posting, we process source media, captions, target-account information, publishing instructions, job identifiers, and success/error states, and transfer content to PostBridge and selected destinations.

Developer access and AI-connected clients

We process developer-key and OAuth connection metadata, scopes, authorized projects, operation names, relevant record IDs, request identifiers, timestamps, and outcomes. Requests can include campaign data and instructions. Responses may contain records the caller is authorized to retrieve. Idempotency records can retain response content, and background jobs can store inputs, results, and error details.

An external AI client receives the tool results it requests under its authorization. We receive what that client sends to UGC.run, which may include user text or content in tool arguments; we do not automatically receive every message in its conversation. Its provider may retain or use information under its own terms. Review that provider before connecting it.

Device, usage, and local information

Our servers and providers process technical request information such as IP addresses, device/browser characteristics, timestamps, accessed URLs, error information, and security events as needed to deliver and protect the Service. Web Analytics processes page-visit and device-related statistics as described below.

The mobile app stores authentication/session information and local preferences, selected campaign and creator identifiers, cached media, and some legacy device/recovery information. Supported legacy access paths use an Apple identifier-for-vendor or a generated device identifier. Push registration processes a device push token associated with the relevant account or campaign. These are not the advertising identifier used for cross-app advertising tracking.

We do not require continuous location, contacts, microphone, camera, health-record, or biometric-identification collection for the reviewed core app features. Network requests and public content can nevertheless reveal approximate location or information about a person. If a future feature requests additional device access, its purpose and permission request will be explained at that time.

We process information for the following purposes:

• Deliver the Service: authenticate users, manage memberships, retain campaign accounts and records, display content and analytics, calculate campaign records, and perform requested integrations. Where applicable, this relies on contractual necessity, Customer instructions, or legitimate interests in delivering authorized business services.
• Billing and administration: manage subscriptions, investigate payment issues, maintain accounting records, and respond to support. Relevant bases include contract, legitimate interests, and legal obligations.
• Security and reliability: prevent unauthorized access, misuse, duplicates, and fraud; log operations; troubleshoot provider errors; investigate incidents; and enforce lawful terms. We rely on legitimate interests or legal obligations where applicable.
• Product improvement: analyze feature usage, performance, error patterns, and service outcomes; test fixes; improve workflows; and create appropriate aggregate or deidentified statistics. Legitimate interests may apply where the processing is necessary, proportionate, and consistent with reasonable expectations. We use consent where required.
• Communications: provide invitations, approval notices, operational updates, reminders, and messages users or campaign managers request. Any optional marketing communications must provide a legally appropriate choice and opt-out.
• Compliance and disputes: meet legal duties, respond to valid legal process, preserve relevant evidence, and establish or defend legal claims.

Where consent is the basis, you may withdraw it without affecting processing already lawfully performed. Contractual necessity is not used to justify unrelated optional activities. For data processed on a Customer’s behalf, that Customer is responsible for establishing its basis and any required notices or consents; we assist as required by our agreement and law.

We use operational and usage information to improve UGC.run. Authorized personnel and providers may examine relevant records when needed to support users, diagnose problems, test corrections, or investigate abuse, under appropriate access restrictions.

We may develop statistics or benchmarks that do not identify an individual or expose a Customer’s confidential campaign. Merely removing a name or replacing it with an identifier does not necessarily make information anonymous. Where we maintain deidentified data, we will take reasonable measures against reidentification and require appropriate restrictions on recipients. Any combined information that remains identifiable is handled as personal information.

We do not sell personal information, share it for cross-context behavioral advertising, or use identifiable Customer Data to train general-purpose AI models. We do not automatically transmit all campaign data to an AI model just because MCP or API access exists. A user-selected AI client may receive authorized data through its connection, as explained above.

We will explain a new materially different data use before starting it and obtain any required consent or contractual authorization. Updating this Policy does not retroactively override earlier commitments or provide unlimited permission to use previously collected data.

We disclose information in the following situations, subject to the purpose, permissions, and applicable obligations:

This table identifies relevant services rather than promising every provider is used for every user. Service providers act under applicable agreements; some also act independently for activities described in their own policies. A future provider change will be handled under our notice, contractual, and legal obligations. We do not list an unused SDK dependency as an active recipient merely because it appears in the package manifest.

Third-party media, fonts, embeds, and links can cause your browser or app to contact their host, disclosing connection information such as an IP address. Published content can become available to a broad audience under the destination platform’s settings. Removing it from UGC.run does not necessarily remove third-party copies.

The website uses authentication cookies and browser storage for functions such as keeping a session, selecting a campaign, and remembering interface preferences. Administrative preview functionality also uses a short-lived cookie. The mobile app uses operating-system storage and caches for sessions and preferences. Blocking essential storage can prevent sign-in or other features.

The website includes Vercel Web Analytics. Vercel describes this product as not using tracking cookies or identifiers to follow people across websites; that does not mean the Service processes no technical or personal information. Relevant visit statistics can include pages, referrers, browser/device attributes, and approximate country derived during processing. Infrastructure logs are separate from analytics statistics. We will configure analytics to avoid unnecessary personal data in URLs or events and apply additional controls where legally required.

Manage browser cookies through your browser and notification permissions through iOS Settings. Campaign reminder preferences and connected-service settings provide further controls where available. You may revoke external OAuth access and developer keys through the relevant controls. These actions do not automatically delete existing campaign history.

We keep information only for as long as reasonably needed for the purposes described here, considering the service relationship, Customer instructions, sensitivity, legal and accounting duties, security, disputes, and technical recovery requirements. Different records have different lifecycles; not all information disappears when you sign out, uninstall the app, remove a handle, or lose campaign access.

Campaign archiving and membership revocation preserve records for the campaign. An authorized deletion can remove database records; storage objects, backups, processor records, and external published copies may require separate handling. Where retention is required or permitted after a deletion request, we will limit the retained information and its use to the applicable purpose.

Developer records have category-specific retention periods, including expiry of OAuth and idempotency records and cleanup of old rate-limit records, completed jobs, and audit entries. These periods do not apply to all campaign or account information. Records may remain longer where needed for security, legal obligations, disputes, or technical recovery.

Contact contact@ugc.run to request access, correction, deletion, or a copy of your personal information, to ask about a public profile being tracked, or to raise a privacy concern. Include enough information to locate the relevant account or campaign, but do not send passwords, API secrets, full card details, or unnecessary identity documents. We may proportionately verify identity and authority before fulfilling a request.

For public-social-data requests, include the relevant profile or post URL. We will consider requests under applicable law, including where the requester has no UGC.run account. Removing a source post does not necessarily remove previously retained metrics or third-party copies; tell us what record you want reviewed.

Depending on applicable law, you may have rights to access, correct, delete, obtain portability, restrict or object to processing, withdraw consent, opt out of specified processing, appeal a decision, and complain to a supervisory authority. Some requests are subject to lawful exceptions and verification. We will explain a denial or partial response and the available appeal route where required. Exercise of a protected right will not result in unlawful discrimination.

For campaign-controlled information, we may need to coordinate with the Customer, but will still meet duties that apply directly to us. Customers may have independent retention duties. A request to UGC.run does not automatically delete data from an external AI client, social network, payment provider, or a Customer’s separate systems.

EEA, United Kingdom, and Switzerland

Where applicable, information about our processing bases is in section 3. Rights can include access, rectification, erasure, restriction, portability, and objection, subject to conditions. You may complain to the competent data-protection authority and need not contact us first. We will explain any legally significant automated processing and available safeguards if applicable.

Performance flags, rankings, qualification rules, and automatic inactivity archiving may influence campaign administration. They use configured rules and data that can be inaccurate. Customers must assess whether their use creates legally significant automated decisions and provide required review and contest mechanisms. We do not claim such processing is exempt merely because a business selected the settings.

United States state privacy laws, including California

To the extent applicable, the categories collected include identifiers; commercial and payment-related records; internet or device activity; visual/audio information contained in media; professional/campaign information; and derived performance information. Credentials and certain payment details may require heightened protection under applicable law. Sources, purposes, and recipient categories are described in sections 2–5.

As described in section 4, we do not sell personal information or share it for cross-context behavioral advertising. We do not use sensitive personal information to infer sensitive characteristics for advertising. Public content may nevertheless contain sensitive information and remains subject to applicable protections.

Applicable rights may include knowing or accessing information, correction, deletion, portability, opting out of covered activities, authorized-agent requests, and appeal. Submit requests or appeals to contact@ugc.run; we will respond within applicable time limits and provide additional appeal or regulator information as required. Rights and requirements depend on the law applicable to you and the relevant processing.

Other jurisdictions

Mandatory rights under other applicable privacy and consumer laws are not waived. We will assess local notice, consent, representative, transfer, and request requirements before offering features in a jurisdiction that requires additional measures.

Information may be processed in countries where we and our providers operate, which may have different legal protections. We will use a lawful transfer mechanism when one is required, such as applicable contractual safeguards with necessary supplementary measures. You can request information about the relevant safeguards at contact@ugc.run.

We use safeguards appropriate to the nature of the Service, including authenticated access, project-scoped authorization, restricted management permissions, protected integration credentials, expiring signed media access, and operational controls. No system or transmission can be guaranteed completely secure. Security features are not a promise of certification, complete isolation from all human access, or immunity from incidents.

Protect your credentials and review integrations and team membership. If you suspect unauthorized use, contact contact@ugc.run. We will investigate and provide breach notifications when legally required. Do not include secrets or excessive personal data in a report.

The Service is intended for adults 18 and older and is not directed to children. We do not knowingly permit children to register. If you believe a child has supplied information, contact contact@ugc.run so we can investigate and take appropriate action. Customers must not use the Service to track children or submit children’s information without a separately approved lawful arrangement.

We will update the effective date and provide appropriate notice of material changes. Where required, we will obtain consent before beginning a new use or materially expanding an existing one. This notice does not waive statutory rights or make all processing conditional on an undifferentiated agreement to a privacy policy.

For privacy requests, legal notices, billing questions, or security concerns, contact contact@ugc.run.

UGC.run uses YouTube API Services when you connect a channel. Google authorization grants access to channel identity and comments. We store your channel ID and title, encrypted OAuth credentials, your keyword rule, and matching comment IDs, video IDs, comment text, and reply results. We use this information to post the public reply you configure, prevent duplicate replies, and show connection status and reply history to authorized members of your project. We do not use YouTube data for advertising or AI training. The Google Privacy Policy also applies to Google services.

Reply history and stored comment data are deleted after 30 days. OAuth credentials are retained while the channel is connected. Disconnecting YouTube stops automation, removes the channel credentials, deletes reply history, and requests revocation of Google access. You can also revoke access through Google account permissions. If you revoke access there, UGC.run cannot continue replying; disconnect in the portal to delete the saved connection and history. For deletion requests or questions about these practices, contact contact@ugc.run.