MewGo

MewGo legal

Privacy Policy

This policy explains how 413 Vision LLC handles personal data when people visit MewGo, apply for access, use a MewGo workspace, or connect an external provider.

Effective
August 11, 2026
Last updated
August 11, 2026
Version
2026.08.11

1. Who we are and when this policy applies

413 Vision LLC, a Colorado limited liability company, operates MewGo. In this policy, “MewGo,” “we,” “us,” and “our” refer to 413 Vision LLC and the MewGo service. “Customer” means the organization that has requested or purchased a MewGo workspace. “Authorized User” means a person whom a Customer permits to use its workspace. “Customer Content” means the briefs, brand materials, claims, media, contacts, instructions, drafts, approvals, and other material a Customer or its Authorized Users submit to or create in MewGo.

This policy applies to mewgo.ai, MewGo applications and workspaces, access and Founding Partner applications, support communications, and integrations that MewGo operates. It does not govern a third-party website or service under that third party's own policy, including a provider page you open from MewGo.

2. Our privacy roles

For MewGo account information, website activity, access applications, billing records, service security, and our direct business communications, 413 Vision LLC generally determines why and how the data is processed.

A Customer generally determines why and how personal data contained in its Customer Content is processed. For that data, 413 Vision LLC processes the data on the Customer's instructions to provide MewGo, subject to our independent duties to secure, operate, and comply with law. If you use MewGo through your employer or another organization, that organization may administer your account, control workspace content, and respond to requests concerning that content.

3. Personal data we collect

Depending on how you interact with MewGo, we may process:

Identity and account data
Name, work email, authentication identifiers, profile details, organization and brand memberships, roles, invitations, account status, and legal-document acceptance records.
Prospect and commercial data
Company or brand name, website, business use case, campaign workflow, team size, goals, bottlenecks, launch timing, decision role, pricing acknowledgement, offer status, and communications about access or purchase.
Customer Content
Brand context, briefs, source material, claims and proof, prompts, drafts, images, designs, email documents, schedules, approvals, comments, exports, publication records, and version history.
Integration data
Provider account and resource identifiers, safe account labels, permissions, mapping and connection state, encrypted or protected credentials, synchronization state, provider request references, publication results, and provider-derived analytics.
Payment and transaction data
Customer and invoice identifiers, order terms, payment status, amounts, dates, and limited billing details. Payment providers handle complete card or bank credentials under their own terms.
Service, device, and security data
Browser and device type, approximate location, page and route activity, referrer, authentication and security events, feature usage, timestamps, bounded request identifiers, safe error categories, and audit history. Operational records are designed to exclude raw credentials, authorization headers, cookies, request bodies, and arbitrary URLs.
Communications
Support requests, privacy requests, account notices, email delivery events, feedback, and other messages you send to us.

MewGo is not designed to collect sensitive personal data such as government identification numbers, precise geolocation, medical records, or payment credentials in Customer Content. Customers should not submit sensitive data unless we have expressly agreed to process it for a supported purpose.

4. How we collect personal data

  • Directly from you when you apply, create an account, use MewGo, connect a provider, contact us, or make a purchase.
  • From the Customer and its administrators when they invite you, assign access, configure a brand, or provide Customer Content.
  • From connected services when an authorized person grants MewGo access to a selected account or resource.
  • Automatically from MewGo, our hosting environment, authentication service, and security and analytics tools.
  • From public brand materials that a Customer identifies or authorizes MewGo to analyze.

5. How and why we use personal data

We use personal data to:

  • Review access applications, create accounts, provision workspaces, and manage Customer relationships.
  • Provide campaign planning, content and image generation, editing, review, scheduling, analytics, export, and approved distribution features.
  • Keep organizations and brands separated, enforce roles and permissions, preserve version lineage, and record approvals.
  • Connect provider accounts, perform requested synchronizations, and deliver approved content to an authorized destination.
  • Process orders, invoices, payments, usage limits, renewals, and account administration.
  • Send transactional messages, support replies, service notices, and marketing messages where permitted.
  • Detect misuse, protect accounts, debug failures, maintain reliability, and investigate security incidents.
  • Comply with law, enforce agreements, establish or defend claims, and protect MewGo, Customers, and others.
  • Understand feature performance and improve MewGo using controlled testing, feedback, and data that is aggregated or de-identified where appropriate.

Where a law requires a legal basis, our bases may include performing a contract, taking requested pre-contract steps, pursuing legitimate interests in operating and securing MewGo, complying with legal obligations, and consent. When we rely on consent, you may withdraw it for future processing. MewGo does not use solely automated processing to make decisions about individuals that produce legal or similarly significant effects.

6. AI features and customer learning

When an Authorized User invokes an AI feature, MewGo sends the inputs needed for that request to an approved AI provider and receives the generated result. Inputs may include the selected brief, brand context, proof, source media, editing instruction, or current artifact. MewGo records provider and model attribution, usage, version lineage, and safe operational evidence so the request can be governed and audited.

MewGo does not use Customer Content, private feedback, or one Customer's decisions to train a model shared across Customers. Our configured OpenAI API requests are not used to train OpenAI models unless 413 Vision LLC separately opts in, and we do not opt in with Customer Content. A provider may retain limited data for abuse monitoring or legal compliance under its applicable data terms.

AI results can be incomplete, inaccurate, or similar to results provided to others. MewGo uses versioning, proof controls, and human review to reduce risk, but Customers remain responsible for reviewing content before external use.

7. Facebook Page connections and publishing

A Customer owner or administrator may connect Facebook Pages the Customer is authorized to manage. Sign-in and permission approval occur through Meta. MewGo does not receive the person's Facebook password. Depending on the enabled capability, MewGo may request permission to list managed Pages, read Page engagement or insights, or create and manage Page posts. Insight-only access does not grant posting authority automatically.

For a connected Facebook Page, MewGo may process:

  • Page names, provider identifiers and digests, Page task and permission state, connection state, and brand-to-Page mappings.
  • Page access credentials in a protected server-side credential store. Credentials are not returned to the browser, included in exports, or exposed to the AI model.
  • The exact approved copy, links, image bytes, alt text, destination, and schedule selected by an authorized person.
  • Delivery attempts, timestamps, safe failure categories, Meta request references, provider post identifiers or digests, confirmed permalinks, and organic Page insight records when analytics is enabled.

MewGo uses this data to discover eligible Pages, maintain the selected mapping, publish approved scheduled material once, prevent duplicate sends, reconcile uncertain results, present delivery history, and connect confirmed posts with requested Page insights. MewGo does not use Page credentials to buy ads, manage messages or comments, or publish content that has not passed MewGo's approval and scheduling controls.

Disconnecting and deleting Meta data

An authorized Customer administrator may disconnect a Meta connection in MewGo. A person may also remove MewGo through Meta's business integration settings. Disconnection or provider revocation stops future provider access and publishing. It does not by itself erase the Customer's original campaigns or approval history in MewGo.

MewGo verifies Meta deauthorization and data-deletion callbacks before acting on them. A verified deletion request receives a confirmation code and status URL. MewGo does not report the request complete until covered credentials, provider identifiers, Page state, provider analytics, publication jobs and attempts, provider bindings, rollout grants, and reconstructable provider-derived data have been removed or de-identified under the approved deletion policy. The Customer's independently created campaign content remains subject to the Customer's MewGo account lifecycle.

Use of Facebook and other Meta products is also subject to the applicable Meta termsand policies.

8. Cookies, browser storage, and analytics

MewGo uses cookies that are necessary for authentication, security, session continuity, and remembering an authorized workspace. Some editing and generation features use local or session storage to recover an in-progress operation or editor state. Clearing browser storage may sign you out or remove that local recovery state.

We use Vercel Web Analytics to understand page views, routes, referrers, approximate region, browser, operating system, and device type. Vercel Web Analytics does not use cookies and uses a daily rotating request-derived hash rather than a persistent cross-site identifier. We do not configure analytics events to include Customer Content, email addresses, provider credentials, or private access tokens. MewGo does not use advertising pixels for cross-site tracking.

9. How we disclose personal data

We may disclose data in these circumstances:

  • At the Customer's direction. To Authorized Users, selected recipients, or connected providers when the Customer requests a feature or distribution.
  • Service providers. To vendors that help us provide hosting, authentication, databases, storage, AI processing, email, analytics, billing, support, and security.
  • Known platform providers. These include Supabase for authentication, database, and private storage; Vercel for hosting and web analytics; OpenAI for AI generation; Resend for email delivery; Stripe or Mercury for an approved payment path; Meta for Facebook and Instagram integrations; and Google when a Customer enables Google Analytics 4.
  • Legal and safety. When reasonably necessary to comply with law or legal process, enforce agreements, investigate misuse, protect rights or safety, or establish and defend legal claims.
  • Business transaction. In connection with financing, diligence, reorganization, acquisition, sale, or transfer, subject to appropriate confidentiality and continued protection.

Providers receive only the data reasonably needed for their service and process it under their contracts and applicable law. Customers may request current subprocessor information from us.

10. Sale, sharing, and targeted advertising

MewGo does not sell personal data for money or other valuable consideration. We do not share personal data for cross-context behavioral advertising, and we do not process personal data for targeted advertising. We also do not knowingly sell or share the personal data of anyone under 18.

Because MewGo does not conduct these activities, a browser-based universal opt-out signal does not change advertising or sale behavior on MewGo today. If our practices change, we will update this policy, provide any required opt-out control, and honor recognized universal opt-out mechanisms where applicable.

11. Retention and deletion

We retain data for as long as reasonably necessary to provide MewGo, follow Customer instructions, maintain security and auditability, comply with legal and financial obligations, and resolve disputes. The approved MewGo retention schedule includes:

  • Customer Content, brand assets, analytics evidence, reviews, and approvals for the life of the active account.
  • AI request, usage, guardrail, delegated-authority, and tenant audit evidence for up to 24 months on a rolling basis.
  • Temporary OAuth, rate-limit, checkpoint, safe-error, and similar operational state for no more than 90 days, unless needed for an active incident.
  • Access requests submitted before an organization exists for up to 12 months.
  • Email consent evidence for five years from the last send and digest-only opt-out records for as long as the opt-out must be honored.
  • Content-free billing and usage records for up to seven years where needed for financial recordkeeping.

Under MewGo's approved account lifecycle, a suspended workspace retains its data but loses workspace and analytics access. After 12 months of suspension, MewGo may begin deletion after notice to the owner. An accepted owner deletion request has a 14-day cancellation period, and a requested export completes before purge begins. Covered live Customer data is scheduled for removal within 30 days after the grace period, and backup copies rotate out within 90 days. Some self-service lifecycle controls are still being introduced, so an owner should contact us to begin or confirm a request.

We may retain limited data when required by law, a litigation hold, security investigation, or an ongoing dispute. When possible, we separate, restrict, aggregate, or de-identify that data. Provider-held data follows the applicable provider contract and deletion process, which may use a different schedule.

12. Security

MewGo uses administrative, technical, and organizational safeguards designed for the nature of the service. These include organization and brand authorization, database row-level security, private storage, server-only provider credentials, protected credential storage, least-privilege roles, stronger authentication for internal control functions, bounded operational logging, versioned approvals, and audited provider delivery records.

No method of transmission or storage is completely secure. Customers and Authorized Users must protect account credentials, use appropriate access roles, and tell us promptly about suspected unauthorized use.

13. International processing

413 Vision LLC is based in the United States. We and our providers may process data in the United States and other countries where we or they operate. Those countries may have different privacy laws. Where required, we use contractual or other recognized safeguards for international transfers. A Customer with specific data-location or transfer requirements should raise them before submitting regulated data to MewGo.

14. Your privacy rights

Depending on where you live and the context in which we process your data, you may have the right to request access, correction, deletion, restriction, objection, or a portable copy; withdraw consent; opt out of sale, sharing, or targeted advertising; and appeal a denied request. MewGo does not currently sell, share, or use personal data for targeted advertising.

Send a request to hello@mewgo.aiwith “Privacy request” in the subject line. Describe the request and the MewGo organization connected to it. You may also write to the address in the footer. We may need to verify your identity and authority before acting. We will respond within the period required by applicable law and will not discriminate against you for exercising a privacy right.

An authorized agent may submit a request where law permits, but we may require proof of authority and direct identity confirmation. If we deny a request, you may appeal by replying to our decision with “Privacy appeal” and an explanation. We will provide the result of the appeal and any regulator contact information required by law.

If the request concerns Customer Content in an organization's workspace, contact that organization first. We may refer the request to the Customer or assist the Customer as its service provider. A Customer administrator may need to preserve data for legitimate business or legal reasons.

15. Children

MewGo is a business service intended for people who are at least 18 years old and is not directed to children. We do not knowingly collect personal data from children under 13. If you believe a child has provided personal data to MewGo, contact us so we can investigate and take appropriate action.

16. Changes to this policy

We may update this policy as MewGo, our providers, or applicable law changes. We will post the updated version with a new effective date. If a change materially affects how we use personal data, we will provide additional notice where appropriate or required. A Customer's continued use after the effective date is subject to the updated policy, but we will seek consent when law requires it.

17. Contact us

The data controller contact is 413 Vision LLC, 2950 Brighton Blvd #753, Denver, CO 80216, United States. Email privacy questions or requests to hello@mewgo.ai.

For contract terms governing use of the service, see the MewGo Terms of Service.