Terms of Service & Privacy Policy Links Not Working — Redirect to Main Page

Open Beginner friendly

#2,026 opened on Aug 12, 2026 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 2/5
Estimated time: 1-3 hours
Newbie friendliness: 65/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: javascript
Domain: mobile

Research direction

Start in the Account section of the Enatega Multivendor app and inspect the Terms of Service and Privacy Policy link handlers or URL configuration. Run the app and tap both links to confirm the current redirects; done means each link opens its corresponding document page rather than the main website homepage.

Written by the indexing model from the issue text.

Description

Describe the bug
In the Enatega Multivendor app, the links to the Terms of Service and Privacy Policy do not open their respective pages. Instead, both links redirect the user to the Enatega main website homepage, making it impossible to view the actual terms or privacy policy.

To Reproduce
Steps to reproduce the behavior:

Open the Enatega Multivendor app.
Navigate to the Terms of Service and Privacy Policy links in the Account section.
Tap on Terms of Service or Privacy Policy.
Notice that both links open the Enatega main site homepage instead of the correct document.
Expected behavior
The Terms of Service link should open the terms page, and the Privacy Policy link should open the privacy policy page directly.

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.

Labels: Enatega Multivendor Customer App, Bug

Dominant language: JavaScript
Stars: 0
Forks: 0
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.