Welo

Privacy Policy

Last updated: October 17, 2026

This Privacy Policy explains how Welobadge, LLC ("Welo", "we", "us" or "our") processes personal data when you visit welobadge.com, create or use a Welo account, apply for or hold a Welo Badge, submit or read a review, use a Welo Page or widget, contact support, or use another Welo service. It does not replace a separate notice that may apply to a specific service or business relationship.

1. Who we are

Welobadge, LLC is incorporated in Delaware, United States, and has its registered office at 131 Continental Dr, Suite 305, Newark, DE 19713, New Castle County, USA. For privacy questions, contact daniel@welobadge.com or support@welobadge.com. Any separate controller or processor allocation for a business using Welo for reviews, widgets or a Welo Page will be described in the applicable service terms.

We receive data from you, authorized colleagues, people submitting reviews, public business sources and service providers involved in the requested service. Supplying account, application and payment information is necessary for the corresponding service; without it, we may be unable to provide that service. Marketing consent is optional.

2. Data we collect and service context

  • Account and application data: name, email address, phone number, date of birth and gender where requested, login and verification information, company identity and website details, role, country, headquarters, company type, employee count, foundation year, motivation and other information submitted for an application.
  • Verification and content data: documents and evidence submitted for business verification, company information, review text, ratings, reviewer details, attachments, images and video, moderation and verification records, and communications about them.
  • Payment and subscription data: payment status, Stripe customer and subscription identifiers, checkout and invoice references, dates, amounts, currency, refunds or disputes and limited payment-method details returned by Stripe. Welo does not receive or store full card numbers through its application.
  • Support and communications: messages, support requests, email preferences, delivery and suppression information, and records needed to respond to you.
  • Technical, security and usage data: IP address and request metadata where collected, browser and device information, access times, pages and interactions, authentication and security events, error information, and product usage.
  • Attribution and analytics data: consent preferences, campaign parameters, referring page, first-party visitor and session identifiers, device category, country where available, and advertising event identifiers. Analytics identifiers are created only after analytics consent. Welo may write limited first-touch session context; external advertising tags and transmission require marketing consent; first-party campaign context, including URL identifiers, may be processed separately as described below. Where marketing consent is not present, application submission removes optional visitor and campaign history, while necessary registration context may remain.
  • AI and automation inputs: information submitted to Welo AI chat, research, enrichment or automation features, together with generated outputs and operational logs, where those features are used.

Contact and identity data can include names, business email, phone, address, country, role, company affiliation and information used to recover or protect an account. Application data can include website, business type, location, ownership or representative information, employee or foundation details, answers, motivation, evidence links and document metadata. We use these details to distinguish an authorised person from an unauthorised request and to understand the company being reviewed.

Verification and review data can include document images, files, links, ratings, written statements, reviewer contact or display details, attachments, photos, videos, moderation decisions, reports and correspondence. Some material may contain special or sensitive information supplied by a person; do not submit more than the workflow requests. Public display is a separate decision from internal review. A company may request a correction or removal through the available process, but copies made by independent visitors or search engines are outside Welo's control.

Payment data can include customer and subscription identifiers, checkout and invoice references, payment state, dates, amounts, currency, dispute or refund state and limited payment-method details returned by Stripe. Welo does not store full payment-card numbers through the client application. Support data can include the message, attachments, account context, delivery state, preference and the steps taken to resolve the issue. Security data can include IP address and request metadata when collected, device and browser information, authentication events, rate-limit events, error context and signals used to prevent abuse.

Attribution data can include first-party session context, landing and referring URLs, campaign parameters, device category, country where available and consent state. External advertising or analytics services receive events only when their configuration and the applicable consent allow it. AI and automation inputs, outputs and logs depend on the feature used; the same retention and security criteria apply to them as to other operational records.

For an account, identity, login, membership and security events help us authenticate you and provide the portal. For an application, company details, answers, documents, evidence and reviewer records let us assess the request, request corrections, record a decision and handle a later challenge. For a Welo Page, the company chooses what business information, images, links and approved trust information to publish; private evidence remains private service data.

For reviews, submission, verification, moderation and publication data support the review process. For widgets, company and page identifiers retrieve and render the selected badge, reviews, media, tag or full-review experience. For payments, checkout, invoice and subscription status returned by Stripe support activation, maintenance, restriction or restoration. For support, conversation and account context allow a response and an operational record. These examples do not give a visitor access to another person's private data.

When an AI or automation feature is used, it receives inputs needed for that request and limited context needed for security, troubleshooting or an operational record. Staff may review, correct or disregard generated output. Do not submit secrets, full payment-card details or unrelated sensitive information to an optional assistant.

3. Sources and information about other people

We receive information through registration, applications, verification, payment, review, contact and support forms. Your company may provide information about an authorised representative, employee or business contact. A reviewer may send a rating, written review, photo or video. We may also receive company facts from public websites, registries, directories and other sources used to verify an application or keep a public profile accurate. Technical events can come from the browser, application and embedded widgets when they operate.

Public availability does not make private contact information suitable for publication. If you submit information about another person, you must have a lawful reason and the authority to do so. Submit only documents and media relevant to the requested service. Verification evidence, identity documents, private contact details and moderation notes are private service data unless a separate notice says otherwise.

  • Provide accounts and services: create and secure accounts, process applications, conduct verification, publish or maintain an eligible Welo Page, operate reviews and widgets, deliver support and provide requested features. The basis is performance of a contract or steps requested before a contract, and where applicable legitimate interests.
  • Payments and subscriptions: create checkout or billing sessions, record payment and subscription state, reconcile transactions, prevent duplicate or fraudulent payment activity, and manage cancellation or disputes. The basis is contract, legal obligation and legitimate interests in payment security.
  • Service communications: send verification, account, transaction, security, application and support messages. The basis is contract, legal obligation or legitimate interests. Promotional communications are sent only where the required consent or other lawful basis exists and can be stopped by the unsubscribe controls.
  • Security and abuse prevention: authenticate users, rate-limit requests, detect fraud, moderate content, investigate incidents and enforce the Terms. The basis is legitimate interests, contract and legal obligation.
  • Analytics and product improvement: with analytics consent, measure visits and interactions, understand product use and improve services. The basis is consent where required. These measurements are not described as anonymous: the runtime can use first-party visitor and session identifiers, URLs, referrers, campaign fields, device category and country where available.
  • Advertising and attribution: with marketing consent, measure campaigns, preserve first-touch attribution and send eligible events to advertising systems. The basis is consent where required.
  • AI-assisted features: process the inputs and outputs needed to provide the requested AI or automation feature, protect the service and keep operational records. The basis is performance of the requested service or our legitimate interests in assisting staff with verification, research and support, subject to applicable safeguards. You can contact us to request a human review of a verification outcome.
  • Legal and corporate purposes: comply with law, keep records required for tax or accounting purposes, respond to lawful requests, exercise or defend legal rights, and complete a merger, acquisition or transfer of business subject to applicable law.

5. Public pages, reviews and private verification evidence

A published Welo Page, approved review, rating, reviewer name or company information may be publicly visible and may be copied or indexed by third parties. Verification evidence, identity documents, private contact details, moderation records and account-area information are handled as private service data and are not published merely because an application or review exists. Do not submit information that you do not have the right to share.

An application record may include company identity, website, jurisdiction, business description, ownership or identity information, answers, evidence links, submitted documents, requests for correction, decisions and the history needed to protect process integrity. Verification material may contain personal data about owners, directors, employees, representatives, customers or other people shown in a document. Welo may redact, restrict, replace or delete material that is unnecessary, unsafe to publish or supplied without a sufficient right to share.

When a review is submitted, we may process the text, rating, reviewer name or display name, contact details used for verification, attachments, media metadata, moderation events and related communications. A review may be held, formatted, rejected, reported or published under the applicable review rules. A published review, rating, selected reviewer name and business response can be visible to visitors and copied, cached or indexed outside Welo. A published Welo Page may contain company identity, description, location, website, logos, images, video, trust information, review summaries and links. The company is responsible for the rights and accuracy of material it submits.

6. Cookies, analytics and campaign attribution

Necessary browser storage supports authentication, security, preferences, registration continuity and consent state. Separate analytics or marketing technologies may be enabled according to the cookie controls and applicable law. Welo may record first-party session context such as landing page, referrer, campaign values or visitor/session state for registration, attribution, abuse prevention and measurement. This internal context is not described as anonymous. External vendor tags, pixels and event transmissions are enabled only when the applicable consent and configuration permit them.

Configured measurement services may include Google Analytics, Umami or Ahrefs. Campaign integrations may include Meta or TikTok. Turning off optional technologies may limit measurement or convenience functions but should not prevent core account functions. The Cookie Policy describes the browser technologies presented and how to change choices. Privacy describes processing; it is not blanket consent to optional analytics or marketing.

7. Recipients, providers and business transfers

Supabase supports authentication, database and storage; Stripe supports checkout, subscriptions, invoices and payment status; Resend supports service email delivery; Mux supports review video processing; OpenAI supports selected AI-assisted features; Sentry supports error monitoring; and Crisp supports support conversations where enabled. Google Analytics and Umami support configured analytics, Ahrefs supports configured website or search analysis, and Meta and TikTok support configured campaign measurement or advertising events; Paved supports configured advertising measurement where enabled and consented. A provider receives data needed for its function and may be a processor, independent controller or sub-processor depending on the service and applicable terms. We do not claim every provider is used for every visitor or that every feature is enabled in every region.

We may share data with professional advisers, auditors, insurers, payment or fraud partners, successor entities in a corporate transaction, or authorities and courts when required or permitted by law. We do not sell personal data as a data-broker product and do not give infrastructure providers permission to use private account data for unrelated marketing merely because they host a service. Public information can be copied by visitors and search engines after publication.

8. International transfers

Welo and its providers may process data in countries outside your country of residence, including outside the EEA. Where applicable law requires safeguards for an international transfer, a valid transfer mechanism is required, such as an applicable adequacy decision or contractual safeguards. Contact us for information about the locations and safeguards relevant to your data.

9. Retention and deletion

We keep personal data only for as long as needed for the stated purpose, legal obligations, security and dispute handling. Retention is assessed by data category, the service used, account and application status, legal and accounting duties, security needs and the need to establish, exercise or defend legal claims. Some browser storage has shorter technical lifetimes described in the Cookie Policy. We review deletion requests against these criteria; where deletion is not required, data may be anonymized or retained as necessary.

  • Applications and verification: consider whether an application is incomplete, under review, approved, declined or disputed; whether evidence is still needed to support the decision; and whether an outstanding correction, security matter or legal claim requires a protected record. Private documents are not retained simply to turn them into public content.
  • Active and closed accounts: keep the data needed to operate an active account. After closure, review which data can be deleted or anonymized and which limited records must remain for accounting, security, rights requests, disputes or another lawful purpose. Closing an account does not necessarily erase an independently lawful public review.
  • Payments, support and communications: applicable accounting or tax duties and outstanding payment disputes affect transaction records. Support history is assessed against resolving and documenting the request. Promotional processing stops after withdrawal or objection where required; a minimal record may remain to prevent further unwanted messages.
  • Media, analytics and operational records: assess whether a review or page remains published, whether media is still relevant, the purpose of the measurement, consent state, incident needs and the technical storage lifecycle. Browser-cookie expiry does not establish the retention of related server records. Ask us about the criteria relevant to a particular category.

10. Your rights

Where the GDPR or another applicable law gives you these rights, you can exercise them for your own personal data. The conditions differ by right and processing purpose; identifying the request helps us apply the relevant rule without disclosing another person's information.

  • Access: ask whether we process your personal data and obtain a copy together with information about purposes, data categories, recipients, retention and any applicable transfer safeguards. A copy may require redaction of another person's data or protected information; this does not remove your right to an explanation of the processing.
  • Correction: ask us to correct inaccurate information or complete an incomplete record. Explain the fact disputed and the correction requested. We may need to distinguish your current contact details from an accurate historical record or a reviewer's opinion. Where appropriate, we correct the display or record the updated information alongside the history.
  • Deletion: request removal where data is no longer needed, consent has been withdrawn and no other basis applies, processing is unlawful or another legal ground for erasure applies. The right is not absolute: records may remain for legal duties, establishing or defending claims and other lawful exceptions. We explain any limit and consider deletion, anonymization or restricted retention as appropriate.
  • Restriction: ask for processing to be limited in the cases provided by law, including while accuracy or an objection is assessed, or when you need a record for a claim instead of deletion. Restricted data may still be stored, with further processing limited to permitted grounds. We will explain any applicable effect on your requested service.
  • Portability: where processing is automated and based on consent or a contract, ask for personal data you supplied in a structured, commonly used and machine-readable format. Where applicable and technically feasible, you may ask for transfer to another controller. This right does not require disclosure of another person's data or unrestricted access to Welo's internal analyses.
  • Objection: object on grounds relating to your situation to processing based on legitimate interests. We assess whether overriding lawful grounds or a legal-claims exception apply. You may object to direct marketing at any time; where that right applies, the data will no longer be used for that marketing. A minimal suppression record can remain to respect the choice.
  • Withdrawal of consent: withdraw a consent at any time through the relevant control or by contacting us. Withdrawal does not affect earlier lawful processing. Cookie controls, email preferences and participation in an optional feature are separate choices; withdrawing one does not automatically cancel every other consent or close the account.
  • Human intervention and complaint: if a solely automated decision with legal or similarly significant effects falls within applicable legal protection, you may request the safeguards provided by that law, including human intervention, expressing your view or contesting the outcome where applicable. You may also complain to the competent supervisory authority, including the Italian Garante where relevant, without being required to contact Welo first.

11. How to make a request and protect other people

Send a rights request to daniel@welobadge.com or support@welobadge.com, identifying the data and the right you wish to exercise. We respond without undue delay and, where the GDPR applies, within one month of receiving the request. A lawful extension may be used for complex or numerous requests; we will notify you within the first month and explain the reason. If we do not act on a request, we explain the reasons and the available complaint or judicial remedies within the applicable period. We may seek additional identity information only where proportionate and permitted by law. Requests are normally free; any lawful fee or refusal for a manifestly unfounded or excessive request will be explained.

We may ask you to identify whether a request concerns your own data, a company record, a review you submitted, a review about your business, or evidence containing another person. This helps us avoid disclosing one person's information to another. We may contact the relevant account holder or reviewer where appropriate, while respecting confidentiality and applicable law. If you believe a public page or review contains inaccurate personal data, identify the specific statement and explain the correction requested. A general disagreement with an opinion is different from an inaccurate personal-data request and may follow the review or moderation process instead.

We keep a record of rights requests and our response so we can demonstrate compliance, prevent repeated misuse and apply the same preference consistently. That record is itself protected and retained under the criteria above.

12. Security and personal-data incidents

We use technical and organizational measures appropriate to the risk, including access controls, authentication, transport security, rate limiting, backups and provider controls. No internet service is completely secure. If a personal-data incident requires notification under applicable law, we will follow the required process.

13. Children and age requirements

Consumer eligibility is subject to the applicable age, consent and legal-capacity rules. A person under 18 must use the service with the supervision and consent of a parent or legal guardian where required by applicable law; any stricter local age requirement applies. Business representatives must be at least 18 and authorized to bind the business.

14. Changes and contacts

We may update this Policy. We will publish the updated version and, where required, provide additional notice. The update date appears at the top of this page. For questions or requests, contact daniel@welobadge.com or support@welobadge.com, or write to Welobadge, LLC, 131 Continental Dr, Suite 305, Newark, DE 19713, USA.

Welobadge, LLC — 131 Continental Dr, Suite 305, Newark, DE 19713, USA. Email: daniel@welobadge.com; support@welobadge.com.