ElanoryaJewelry AI · Legal links
The legal links hand you to your browser, and to one of two languages
Tapping Terms or Privacy does not open a reader inside the app. The app builds a web address on elanorya.com and hands it to your browser. Which text the address asks for is decided by one rule with two outcomes: a Turkish interface gets the Turkish text, every other interface language gets the English one.
The tap hands over an address
Terms and Privacy are not screens in Jewelry AI. When you tap either link, the app assembles a web address on elanorya.com from the document you asked for and the language rule described below, and passes that address to your browser (apps/jewelry-mobile/src/features/legal/legal-urls.ts).
The reason recorded for this arrangement is release timing: text that lives on the web can be corrected without waiting for a store release of the app. That is a statement about where the text is fetched from, and nothing more - this page does not describe what is at the other end, and it cannot confirm what those pages contain.
One document in this area still opens inside the app: Help, reached from Profile (apps/jewelry-mobile/src/app/legal/help.tsx:4). It is a help document. It is not what the terms or privacy links point to.
Two languages, decided before the address exists
The legal text exists in Turkish and English. The app applies a mapping: an interface set to Turkish is given the Turkish text, and every other interface language is given the English one (apps/jewelry-mobile/src/features/legal/legal-locale.ts).
This is a rule applied up front, not a fallback that fires when something is missing. The server side matches it: it recognises a document fingerprint for those two languages only, so an acceptance cannot be recorded against a third language. The language noted with an acceptance is therefore one of the two.
If your interface is set to something else entirely, the English text is the expected outcome of the mapping. Nothing on the screen is reporting a failure to find your language, because no lookup of that kind takes place.
Reading what happened after you tapped
Four outcomes are distinguishable, and they call for different responses.
| Situation | Choose | Why |
|---|---|---|
| A browser opened a page at elanorya.com. | Read it there; do not look for a way back into an in-app reader. | The app handed over an address rather than rendering a document, so there is no in-app copy to return to. |
| Nothing opened, and a notice appeared containing an address. | Use that address - the same one - from another browser or another device. | The shared opener shows the address precisely so the text stays reachable when the handover fails. |
| Nothing opened and no notice appeared. | Try the same link from the welcome, registration, profile, store, acceptance or create-wizard surface. | The notice is part of the shared opener, and only those surfaces use it. |
| The text arrived in English while your interface is set elsewhere. | Treat that as the mapped result and read the English text. | Every interface language other than Turkish is mapped to English before the address is built. |
Where this catches a seller out
Expecting an offline reader inside the app.
Those documents no longer open in the app at all. The link produces an address, and the browser is what displays anything.
Reading the jump to the browser as an untrustworthy redirect.
The address is assembled by the app itself on elanorya.com. Leaving the app is the mechanism, not a symptom.
Waiting for the documents to appear in a third language.
The mapping has two outcomes and the server accepts fingerprints for the same two. There is no third path for the app to take.
Reporting a broken link after a tap on a surface with no notice.
Check the surface first: the address-carrying notice comes from the shared opener, so its absence says something about the surface rather than about the address.
If the link did not take you anywhere
Four checks, in the order that separates the possible causes.
- Look for a notice on screen: if one appeared, the address it contains is the address the link would have opened.
- Open that address in a browser on another device, which removes the handover from the picture entirely.
- Note which screen you tapped from, since the notice is only shown on surfaces that use the shared opener.
- If your interface is not Turkish, expect the English text - that is the mapping doing its job, not a language lookup that failed.
Outside what this page covers
The evidence here is limited to how a legal link is built and opened.
- The contents of the documents, their meaning, their scope and what they cover.
- Whether separate regional or country-specific versions exist; this page examines the two-language mapping only and does not open that question.
- How the interface language itself is changed in the app.
- What the app records when you accept, and what that record is pinned to.
- The mandatory acceptance screen and which requests are refused while an acceptance is outstanding.
- Which version of the text is live in production at any moment.
The files these statements were read from
Language mapping: apps/jewelry-mobile/src/features/legal/legal-locale.ts, which resolves a Turkish interface to the Turkish text and every other interface language to the English one.
Address assembly: apps/jewelry-mobile/src/features/legal/legal-urls.ts, which builds the address from the site origin, the language prefix and the document name.
Failed handover: apps/jewelry-mobile/src/features/legal/use-open-legal.ts, which shows a message containing the address.
The in-app help document: apps/jewelry-mobile/src/app/legal/help.tsx:4, reached from Profile.
Questions
Why do the documents not open inside the app?
Because the links are built as web addresses on elanorya.com and handed to the browser. The recorded reason is release timing: text held on the web can be corrected without waiting for a store release of the app.
Can I read them in the language my app is set to?
Only if that language is Turkish. The mapping sends a Turkish interface to the Turkish text and every other interface language to the English one, and it is applied before the address is built.
Nothing happened when I tapped the link. What now?
Look for a notice: when the browser cannot be opened, the app shows a message containing the address so you can open it elsewhere. That notice comes from the shared opener, which is in place on the welcome, registration, profile, store, acceptance and create-wizard surfaces.
Is the Help screen in the app the same as the terms?
No. Help is a help document, reached from Profile, and it is the one document of this area that still opens inside the app. The terms and privacy links leave the app for an address instead.