You control what you share. Account credentials, messages, verification evidence and parental-consent records are not public profile information. You can manage interactions, request help with your data, and contact us even if you cannot sign in.
This summary helps you navigate the policy; the full sections below explain the details.01Who we are and what this policy covers
Upmanch operates the Upmanch website and mobile applications. In this policy, ‘we’, ‘us’ and ‘our’ refer to Upmanch. This policy covers personal information processed to provide accounts, profiles, posts, reels, stories, interactions, messaging, communities, verification, parental consent and support, where those features are available.
It applies when you use the service, contact us, submit a report, or act as a parent or lawful guardian. It does not govern an independent website, external messaging app, or other service you choose to visit through a link. Those services apply their own privacy practices.
02Account and profile information
Registration information includes your email address, username, display name, password and acceptance of the Terms. Age and parental-consent checks use a date of birth and the information needed to establish an eligible guardian’s approval. We store password hashes rather than readable passwords.
Your profile may contain an avatar, cover image, biography, location, website, YouTube channel and optional category. Profile presentation settings determine which supported fields are displayed. Do not place an address, identity-document number, private contact information, or another person’s information in a public profile unless you intend and are entitled to share it.
03Content and interactions
We process media and text you upload, captions, polls and votes, comments and replies, story activity, likes, follows, saves, shares and view activity. These records let the service display content, maintain interaction counts, deliver relevant notifications and respect audience restrictions.
Your saved-post collection is private to your account. Publishing a public post makes its content, author identity and supported engagement information available to viewers. Follower-only content has a restricted in-service audience, but a viewer may still retain a screenshot or other copy. An audience setting cannot prevent every off-platform disclosure.
04Payment and promotion records
If you purchase a verification subscription or Sponsored spotlight placement, Upmanch processes the selected plan, price and currency, recurring-consent version and time, provider order or mandate references, payment status, confirmed service period, cancellation requests, bids and relevant moderation decisions. These records support delivery, accounting, fraud prevention, payment questions and refunds. Financial history is not displayed on your public profile.
Google Play and Apple process new verification subscriptions in the mobile apps. Upmanch sends an opaque account or purchase-intent identifier and verifies store transaction records to link access to your account, restore purchases and process subscription changes. Website promotion checkout and existing web subscriptions may use Razorpay or Cashfree where configured; the name, email and payment-contact number needed for that checkout are sent to that provider. Full card numbers, bank credentials, payment OTPs and authorization secrets are entered with the payment provider, not stored as Upmanch profile fields. Providers handle their own required identity and payment processing under their policies. Keep payment references when asking support, but never send financial credentials.
05Messages and private sharing
When you use messaging or direct sharing, we process participants, message text, attachments, shared-post references, timestamps, delivery or read state and related safety information. We use this information to deliver the conversation, maintain its history, and apply participant and account controls.
Private means that ordinary users outside the authorised conversation cannot access it through the service. It is not a promise of end-to-end encryption. Technical operations, lawful requests and authorised safety investigations may require controlled access. Recipients can copy or disclose what you send, so consider what you share.
06Device, session and technical information
We process session and trusted-device identifiers, device labels, sign-in and refresh events, IP information, request identifiers, browser or app information and error or reliability records. This supports authentication, abuse prevention, troubleshooting, security investigations and safe account switching.
Sensitive authentication tokens are kept out of ordinary application logs. Server records can still contain request paths, times, response outcomes and the minimum security metadata needed to detect misuse. We do not need your password or verification code in a support message.
08Camera, photos, microphone and downloads
The mobile application may request access to media you choose to upload, camera functions you use, audio recording when supported, and the photo library when you save a downloaded reel. Operating-system permissions apply independently of your account settings.
You can refuse or revoke these permissions in device settings. The affected feature may then be unavailable. Choosing a file does not give other users access to your device’s entire photo library. Downloads are saved through the supported browser or device mechanism and can remain on that device after a post is removed online.
09How and why we use information
We use account information to register and authenticate you, communicate about verification or recovery, and maintain your account. Content and interaction data support publishing, feeds, search, communities, messaging and notifications. Safety information helps investigate abuse, protect users, enforce our Terms and meet legal duties.
We also process necessary technical information to maintain performance, diagnose failures and prevent unauthorised access. We rely on the grounds permitted by applicable law, including your requested service, valid consent where required, and legal or security obligations. Agreeing to this policy is not blanket consent for an unrelated future use; a materially different use requires an appropriate notice and lawful basis.
10Public visibility and your choices
Your username, display name, public profile fields and permitted public verification status can appear alongside your content and interactions. Where supported, you can limit a post’s audience, control who may comment, block accounts, and allow or disable reel downloads. An administrator can disable the platform’s download feature regardless of your preference.
A download may include the Upmanch watermark and your username for attribution. Blocking and audience controls apply within supported Upmanch features; they cannot recall copies already obtained by recipients or independently stored elsewhere. Review your content before making it public.
11Private verification evidence
Applying for verification can involve legal identity details, supporting explanations, public links and private identity or organisation documents. We use the submitted evidence to review authenticity and eligibility, handle follow-up questions, and preserve a record of the decision.
Private evidence is separated from the public profile. Public verification displays only the permitted badge and category, not an identity document. Authorised reviewers use restricted, time-limited document access, and administrative document access is audited. Approval is not an endorsement of every statement an account makes.
12Young people and parental consent
Registration is restricted to people aged 13 or older. Users aged 13–17 require verified consent from a parent or lawful guardian before an account can be created or enabled. A guardian must be an identifiable adult with authority to act for the young person. A young person should not use their own email address in place of a guardian’s.
Consent processing may include a guardian’s contact details, age and identity evidence, relationship declaration, consent choices and decision history. This information is used for consent verification and safeguarding, not as public profile content. A guardian can request withdrawal and exercise appropriate privacy requests. We do not use the parental-consent process to authorise targeted advertising to children. Contact us if an account may belong to someone below the minimum age or may be using false age information.
13Service providers and disclosures
Infrastructure, object storage, transactional email, security and support providers may process information needed to operate Upmanch. Transactional account emails are handled through our configured email delivery service, currently ZeptoMail. Providers receive only information needed for the function they perform, subject to the applicable arrangements and safeguards.
We may disclose necessary information to comply with a valid legal obligation, respond to an authorised request, protect people or systems, investigate fraud, or defend a legal claim. If the service undergoes a restructuring or transfer, affected information must remain subject to appropriate notice and lawful protections. We do not describe public posting or your voluntary use of an external sharing app as a confidential disclosure.
14Processing locations and external services
Hosting and delivery providers may operate in different jurisdictions. The location of processing depends on the services used to run Upmanch and applicable restrictions. Where a transfer requires specific protections or consent, those requirements must be satisfied; this policy is not a claim that every record is stored only in India.
External links, embedded destinations and device sharing tools can disclose information to the destination you select. Review the destination’s policy. Upmanch cannot apply its account controls to another platform or guarantee that an independent provider will remove a copy you shared there.
15Retention, deletion and backups
We keep information for the purpose for which it is collected, including maintaining an active account, delivering content and conversations, investigating abuse, resolving disputes and complying with applicable retention obligations. Different categories have different needs: session credentials expire, reports require decision history, and verification or consent evidence has restricted retention considerations.
Deleting a post removes it from supported viewing surfaces; it does not necessarily immediately erase every database record, audit entry, backup, recipient copy or record under a legal hold. Use Delete account and data at upmanch.com/delete-account or Settings → Account in the app. Confirm ownership with your account email and password. Account access and public content are removed when accepted; uploaded files are queued for secure removal. Requests normally finish within 30 days, with an email confirmation when complete. Payment and tax records, fraud/security audit history, child-safety consent records and information under a legal hold may remain restricted where required. Retention follows the applicable obligation; contact support@upmanch.com for details. Restricted backups expire under the backup retention schedule, and deletion must be reapplied after a restore.
16Access, correction and other privacy requests
You can edit supported profile fields and manage available account and content controls in the application. For access, correction, an eligible copy of your information, deletion, consent withdrawal or a privacy grievance, contact support@upmanch.com or use Contact Support with the Privacy category.
State your username, the request and enough context to identify the affected information. We may need proportionate verification before providing private records or changing an account. A lawful guardian may need to establish their authority. We will explain relevant limitations or lawful retention needs. Rights, review routes and response requirements depend on the law applicable to the request; nothing here limits a right that cannot be waived.
17Security and incident handling
Upmanch uses password hashing, short-lived and rotating session credentials, restricted private storage, access controls, bounded uploads and audited privileged actions. Production operation requires secure transport and appropriate infrastructure safeguards. These controls reduce risk but cannot make any online service immune to misuse, compromise or operational failure.
Use a unique password, review devices and sessions, protect your email account and avoid sharing sign-in codes. If you suspect unauthorised access, reset your password and contact us promptly. Where notification of an incident is required, we will follow the applicable legal requirements rather than rely on a promise of absolute security.
18Policy updates and contacting us
The date at the top identifies this version. When processing practices change, we will update the policy and provide appropriate notice. A policy update does not by itself validate an unlawful use of information or remove rights you have under applicable law.
Upmanch’s public contact for privacy questions and grievances is support@upmanch.com. You may use email if you cannot access your account. Do not attach an identity document unless you are directed to an appropriate secure verification process. Include a previous support reference when following up so the request can be connected to its history.