ElanoryaJewelry AI · Terms and Privacy
Your country does not select the documents you are shown
The regional annexes — one for Turkey, one for the European Economic Area — were removed outright, and what remains is a set of three slots that carry no country of their own. One input still changes the text you open, and it is not where you sell from.
The answer, and the single input behind it
There is no European Union edition and no Turkish edition of the app's documents waiting to be routed to. The two regional annexes were removed outright, and the document set that remains is three slots with no country attached to any of them (apps/jewelry-mobile/src/features/legal/legal-types.ts, read in the 2026-08 working copy).
One input does change which text opens: the language your interface is set to, with a Turkish interface opening the Turkish text and every other interface language opening the English one. That rule is owned and explained in full by the page on where the Terms and the Privacy Policy open; it is stated here once and left there.
Country plays no part in any of it. A resolver that could select by country is present in the source, but the app never calls it — its only caller is its own test, and the module that would store a country somebody declared is not reached from any screen either (apps/jewelry-mobile/src/features/legal/jurisdiction.ts). It is not a switch anyone can reach, and its presence in the source says nothing about what the app will do later.
The region recorded alongside an acceptance follows from that: it is a single fixed value, the same for every user, so an acceptance record does not encode where a seller works from.
What you came looking for, and what the app does instead
Four ways this question arrives, and the answer each one gets. The reason column is the part worth carrying away.
| Situation | Choose | Why |
|---|---|---|
| You sell into the European Union and want to open the annex for the European Economic Area. | There is no annex to open. | It was removed along with the Turkish one, and the three remaining document slots carry no regional entry (apps/jewelry-mobile/src/features/legal/legal-types.ts). |
| You are in Turkey and expect a Turkish annex alongside the main documents. | Same answer, with one difference that is about language, not place. | Both annexes were removed together. What a seller in Turkey is shown still follows from the interface language, not from where the shop is. |
| You want confirmation that your country was considered when you accepted. | Assume it was not. | No screen resolves a country, and acceptance is recorded against one fixed global region for everyone (apps/jewelry-mobile/src/features/legal/jurisdiction.ts). |
| You want to know which rules govern your shop, or whether the app meets them. | This page cannot answer it, and does not try. | The source behind it covers when acceptance is requested and what is presented. It carries nothing about the content, reach or effect of any document. |
Signals sellers expect to matter, and what each one changes today
Read the right column as the complete answer for that row. Where it says nothing changes, there is no partial effect underneath it.
| Signal | What it changes about what you are shown |
|---|---|
| The language your interface is set to | It selects between the Turkish text and the English text of the documents that exist. |
| The country you sell from, or your store region | Nothing. No screen consults it when deciding what to present. |
| A country you might expect to declare somewhere | Nothing. No screen asks for one for this purpose, and the module that would hold it is never reached. |
| The region recorded with your acceptance | It is one fixed global value and is identical for every user. |
The three statements this page rests on
All three come from the mobile app source as read in the 2026-08 working copy.
- The regional annexes were removed, not hidden.
- They are absent from the document slots the app defines, and three slots remain (apps/jewelry-mobile/src/features/legal/legal-types.ts).
- The country resolver has no caller inside the app.
- Its only caller is its own test file, and the module for a declared country is not reached from any screen (apps/jewelry-mobile/src/features/legal/jurisdiction.ts). Nobody is presented a different document or a different acceptance on account of where they are.
- Acceptance carries one region for everyone.
- The region considered when an acceptance is recorded is fixed and global (apps/jewelry-mobile/src/features/legal/jurisdiction.ts).
Outside the reach of this page
This page describes app behaviour only. Every line below is a question its sources cannot answer, and none of them is answered indirectly anywhere above.
- Which rules or laws apply to you, what any of them require, and whether the app meets them.
- What any document means, how far it reaches, or what it grants you. Only which text opens is described here.
- Whether the texts were reviewed by a lawyer, and what their publication status is.
- Which document version is live in production, and which build is in the stores.
- Whether the same texts are published anywhere outside the app, and what those copies contain.
- How acceptance relates to payment, subscription, credit or refund flows.
- How the interface language itself is chosen, and how complete the interface translations are; both belong to their own pages.
- How acceptance records are viewed or reported on internally.
Questions
Is there a separate European Union version of the app's documents?
No. The annex for the European Economic Area was removed, together with the Turkish one, and the three document slots that remain carry no regional entry (apps/jewelry-mobile/src/features/legal/legal-types.ts, read in the 2026-08 working copy). There is nothing in the app that routes a seller in the European Union to a different text.
Does the app decide anything from my country or my store region?
Not for this. A resolver that could select by country exists in the source but the app never calls it — its only caller is its own test — and the region recorded with an acceptance is a single fixed global value for every user (apps/jewelry-mobile/src/features/legal/jurisdiction.ts). What you are shown follows from your interface language.
I remember two annexes being listed. What happened to them?
They were removed. Before that, the selector meant to pick between them never ran in production because the country signal it relied on was never populated, so both annexes were presented to everyone (apps/jewelry-mobile/src/features/legal/legal-types.ts:9-14). The removal ended that; a screen with no annexes on it is the current state, not a fault.
So which set of rules applies to me, and does the app satisfy them?
That is outside everything this page rests on. The source behind it describes when acceptance is requested, what is presented and what the acceptance record holds — it says nothing about the content of any document, which regulations may be relevant to a seller, or whether any of them are met. Treat this page as a description of app behaviour and nothing further.