FabricAR

Cookie Policy

Last updated: 8 November 2026

This is a translation. In case of discrepancy, the Turkish version prevails.

This policy explains which cookies and similar records FabricAR writes to your device on its website, web app and Android app, why we use them, and how you can control them.

In short: We do not use analytics or marketing cookies. We write to your device only what is needed for the service to work and to remember your preferences. For that reason we do not show a cookie consent banner.

1. What are cookies and similar technologies?

This policy covers all three. FabricAR does not use cookies (document.cookie); the tables below list only localStorage and sessionStorage entries.

2. Scope

3. Technologies we use

3.1 Website (www.fabricar.app)

The marketing pages (home page, fabric maker, furniture maker and upholsterer pages, privacy and this page) write nothing to your device. Fonts are loaded from our own server; no request goes to a third-party provider for fonts. The entries below appear only on the application pages of www.fabricar.app (operator and dealer panels, customer showcase) and only when you use the related feature.

NameTypeProviderPurposeDurationCategory
sb-<project-ref>-auth-tokenlocalStorageFirst partySession token in the operator and dealer panels (recognises the signed-in user)While the session stays open; deleted on sign-outEssential
fa-langlocalStorageFirst partyLanguage preference (TR/EN); written only when you press the language buttonUntil you delete itPreference
fabricar_signals_seen_atlocalStorageFirst partyWhen new buyer notifications were last seen in the operator panelUntil you delete itPreference
fabricar.captureDeclarationlocalStorageFirst partyRemembers the fabric capture declaration form in the operator panel so it need not be refilledUntil you delete itPreference
fabricar_catalog_cache, fabricar_user_fabricslocalStorageFirst partyLocal copy of the fabric catalog on the device in the operator panelUntil you delete itEssential (panel operation)
fabricar_ar_tryon_quotalocalStorageFirst partyRemaining number of try-ons with your own photo in the customer showcaseUntil you delete itEssential

Which fabrics you view, zoom into or try on in the customer showcase is recorded in our own database to improve our products and to recommend fabrics that suit you. Nothing is written to your device for this; the records are kept under a random session number that is valid only while the page is open. If you submit the sample request form during the same visit, the fabrics you viewed in that visit (at most the last 50 interactions) are added to your request and used to evaluate it.

3.2 App (app.fabricar.app and Android)

The app does not use cookies. The entries below are created while you use the app.

NameTypeProviderPurposeDurationCategory
sb-<project-ref>-auth-tokenlocalStorageFirst partySupabase session tokenWhile the session stays open; deleted on sign-outEssential
fabricar_app_store_v2localStorageFirst partyWhether the intro screen was seen, and in-app historyUntil you delete itEssential / Preference
fabricar_dillocalStorageFirst partyLanguage preference (TR/EN)Until you delete itPreference
fabricar_asistan_sayac:<user>:<day>localStorageFirst partyShows the assistant's daily question counter on screenDailyEssential
fabricar_session_statesessionStorageFirst partySession stateUp to 1 hour; deleted when the tab closesEssential

In the tables, <project-ref>, <user> and <day> mean that the project ID, the user ID and the date, respectively, appear in the entry's name.

4. Categories

We use essential and functional/preference entries. We do not use analytics or marketing cookies. If we ever do, we will ask for your explicit consent before starting.

5. Legal basis

Essential entries are used under Article 5(2) of Law No. 6698 (KVKK), sub-paragraph (c) (necessary for the conclusion or performance of a contract) and sub-paragraph (f) (the controller's legitimate interests). Under the Personal Data Protection Board's Guide on Cookie Practices (2022), consent is not required for essential cookies; this page provides the information.

6. Third-party services

The web app and panel pages load some code libraries from external content delivery networks (cdn.tailwindcss.com, esm.sh; cdn.jsdelivr.net on the account verification and password reset pages). Your IP address is technically transmitted to these providers while this happens; files loaded from these sources do not write cookies to your browser.

7. How can you control them?

You can delete or block site data from your browser:

Menu names may differ slightly between browser versions. sessionStorage entries are deleted anyway when you close the tab.

If you block the essential entries, sign-in and your session will not work.

In the app: signing out deletes the session token. To clear all app data on Android, go to Settings → Apps → FabricAR → Storage → Clear data.

8. Your rights

For your rights under Article 11 of the KVKK and for the data controller's details, see the Privacy Policy. You can send your requests to info@fabricar.app.

9. Changes

This policy may be updated. When it is, the date below changes as well.

Last updated: 8 November 2026