MEDIA PARTNER OS / PRIVACY

Privacy Notice

This notice explains the information Media Partner OS currently processes during the Myanmar Media Partner trial and how it supports application review, security and operations.

Operational launch version · 21 September 2026

Media Partner OS is operated by the business responsible for this service (the “Operator”). The Operator's formal legal entity, business address, jurisdiction and permanent privacy contact have not yet been confirmed for publication and will be added before a broader public launch.

  • Telegram identity information used for sign-in, such as verified provider subject, Telegram numeric ID, name, username and profile photo when supplied by Telegram.
  • Applicant profile, contact details, preferred language and Individual or Organization Partner Type.
  • Media Asset and Media Claim details, including URLs or handles, categories, audience country and self-reported metrics.
  • Ownership Evidence, supporting URLs, Applicant notes, application versions, review outcomes and correction requests.
  • Session, login, security, audit and fraud-prevention records.
  • A random first-party acquisition session identifier, landing path, referring site host, standard UTM acquisition fields when present, and Partner application funnel events. The identifier is held in an HTTP-only same-site cookie and does not contain UTM values.

Information is used to authenticate Applicants, resume an account, receive and review applications, verify Media ownership, request corrections or more evidence, approve or reject participation, provide support, preserve review history, secure the service and investigate suspected abuse or fraud, understand which sources bring prospective Media Partners to the service, and improve the Partner application process. The service does not use a third-party advertising pixel or browser fingerprint for this measurement.

  • Telegram provides the login identity and authorisation flow.
  • Vercel hosts and delivers the web application.
  • Supabase provides the production PostgreSQL database and private evidence Storage.

Ownership Evidence is stored in a private bucket. The application checks the current session before serving evidence to the submitting Applicant or an authorised Admin reviewer. Evidence is processed by the Operator and the service providers needed to host, secure and review it; it is not published as public website content.

If an Applicant becomes an approved Partner, affiliate account, commission, identity verification, withdrawal or payout activity may be handled in a separate external system. That system is authoritative for its own account and payment information and may provide separate privacy information.

The service uses access controls, revocable sessions, private Storage and audit records to protect the review workflow. Records are kept as reasonably needed for application operations, security, dispute review and historical integrity. An exact retention schedule remains an operator decision and has not been represented as a fixed legal period.

To ask what information is associated with your application or to request a correction, contact the Operator through the Telegram conversation used for your invitation or Applicant support. The Operator may verify identity before acting. Some immutable review, audit and security records cannot be rewritten, but an appropriate correction or status note may be recorded.