Cookies and browser storage used by Fameoria
This policy explains the first-party cookies and localStorage values currently used by Fameoria, why they are needed, how long they can remain and what happens when you remove or block them.
Last reviewed August 2026
- No advertising cookies
- No analytics cookies currently loaded
- Language and currency preferences last up to one year
- The signed-in session cookie is HTTP-only
01What cookies and local storage are
A cookie is a small value stored by the browser and sent with matching requests. localStorage is browser storage read by site scripts and is not automatically sent with every request. Fameoria uses both where the server and browser need to keep a consistent preference.
First-party means the value belongs to the Fameoria site you are visiting. A provider can set separate third-party or provider-domain storage after you follow a hosted payment or external-platform link.
02Current storage summary
The current Fameoria implementation uses:
- `fam_consent` for the consent-banner choice, up to 180 days
- `bf_locale` for English, Turkish or Arabic, up to one year
- `bf_currency` for the selected display currency, up to one year and mirrored in localStorage
- `bf_session` for a signed-in customer session, up to 30 days unless revoked earlier
Exact expiry can be earlier when you clear browser data, sign out, revoke a session or use a browser that deletes storage automatically.
03Your cookie choice
Stored as fam_consent. This first-party value records whether you selected all currently available categories or essential-only in the notice. It can remain for up to 180 days and the same choice may be mirrored in localStorage so the banner behaves consistently.
Choosing all also loads Google Analytics, which Fameoria uses to see which pages and products visitors open. Choosing essential leaves it switched off, and no advertising service is loaded in either case. The consent control exists so any future optional category must be documented and connected to a meaningful choice before loading where consent is required.
04Language preference
Stored as bf_locale. This first-party preference remembers English, Turkish or Arabic for up to one year. It helps the server choose the correct localized route and keeps navigation, metadata and content in the selected language. It uses SameSite=Lax.
Deleting it can return language selection to browser, country or default-locale logic. The locale value is functional and is not used to infer ethnicity or build an advertising profile.
05Currency preference
Stored as bf_currency. This first-party preference is stored in a cookie and localStorage for up to one year. It lets the server and browser show the same selected currency on the first render. Turkish storefront pricing can use TRY while another market can use its configured display currency.
The preference does not lock an exchange rate, create a payment or override the cart total. The confirmed checkout and hosted payment quote remain the transaction records.
06Sign-in session
Stored as bf_session. When you sign in, this HTTP-only cookie keeps the customer session active for up to 30 days unless it expires or is revoked earlier. Client-side scripts cannot read the token. In production it is marked Secure and uses SameSite=Lax.
Removing the cookie signs you out on that browser but does not delete the customer account or order records. A session can also be revoked after password reset, suspected unauthorised access or a security response.
07Essential and optional categories
Session, security and preference storage supports features a visitor or customer asks to use. Blocking it can prevent sign-in, language persistence, currency persistence or consent-state retention.
Fameoria loads Google Analytics for audience measurement, and only after you choose all. No advertising or cross-site behavioural tracking cookies are used. If optional analytics or marketing is introduced, it must be listed with provider, purpose and duration and must respect the required consent choice before activation.
08Hosted payments and external sites
When you leave Fameoria for the hosted payment provider, that provider can set cookies under its own policy. Instagram, TikTok, linked blogs or another external destination can do the same. Fameoria cannot read or control storage set only on another operator's domain.
Review the provider notice on that page. Returning to Fameoria can include a transaction reference or status needed to match the payment to the order, which is an order record rather than an advertising cookie.
09Managing or deleting storage
Browser settings can show, block and delete site data. Private-browsing modes and privacy extensions can delete values automatically or prevent them from being written. You can also change language and currency through the site controls and sign out to end the active session.
- deleting `bf_session` signs you out
- deleting `bf_locale` resets the remembered language
- deleting `bf_currency` resets the remembered display currency
- deleting `fam_consent` makes the notice appear again
Blocking all storage can make account and preference features unreliable.
10Changes and contact
This policy must be updated when a cookie name, purpose, provider, category or duration changes. The review date identifies the current version. A material optional-tracking change should also be reflected in the banner before the technology loads where consent is required.
Contact support with the cookie name, page, browser and concern if you see a value that is not explained here. Do not send the value of a live session token.
Questions about a stored value?
Tell us the cookie name and browser where you saw it.