Granites, marbles, sandstones

+48-608-489-076

kontakt@gagagranit.pl

Niepodległości 37

Strzegom, 58-150

Mon - Sat 7.00 - 18.00

Sunday CLOSED

Cookies belonging to the GAGA Hurtownia Kamienia Budowlanego

Below is a list of cookies belonging to the GAGA Wholesale Building Stone Company. These are files that help in the quick and effective operation of the website.

Facebook (Persistent cookies
authentication)

lu

2 years

User ID and various login details (e.g. number of logins per account, status of the "Remember me" field, etc.) Used to save information about whether the user wants to stay logged in

xs

90 days

Session ID, creation time, authentication value, secure session state, grouping group ID. Used in conjunction with the c_user cookie to authenticate the user's identity on Facebook

c_user

90 days

User ID. Used in conjunction with the cookie xs to authenticate the user's identity on Facebook

m_user

90 days

E-mail address, user ID, authentication value, version, user permissions, creation time, Facebook version designation. Used to authenticate the user's identity on the Facebook mobile site

pl

90 days

T/N. Used to register the fact that the device or browser is logged in via the Facebook platform

dbln

2 years

Login authentication values. Used to allow logging in by device

aks

30 days

Account Kit access token. Specifies the login status of the person visiting the site accountkit.com

aksb

30 minutes

The value of the request time. Authenticates logins using the Account Kit

sfau

1 day

An encrypted user ID, contact person, time stamp and other login details. Optimizes the recovery procedure after unsuccessful login attempts

Facebook (An encrypted user ID, contact person, time stamp and other login details. Optimizes the recovery procedure after unsuccessful login attempts)

ick

2 years

Encryption key. Saves the encryption key used to encrypt cookies

csm

90 days

2 or 0. Indicates when the HTTPS protocol is needed to access the FB servers

s

90 days

Digital signature and time stamp. Used to indicate when the last user entered the password

datr

2 years

Browser ID and time stamp. Identifies browsers for site security and integrity, including recovering accounts and identifying potentially affected accounts

sb

2 years

Browser ID and time stamp. Identifies the browser for logging and authentication purposes

Facebook (Advertising and measuring effectiveness)

fr

90 days

Advertising and measurement of effectiveness User and browser identifier; time stamp; various other data. The basic cookie used in Facebook ads, used to display, measure effectiveness and improve the relevance of ads

oo

5 years

1 or 0. Used to save the opt-out options

ddid

28 days

The object and application identifier. Used to open a specific location in the advertiser's application after installation

Facebook (Features and services on the site)

Location

7 days

Locale. Identifies the country and selected language of the last logged-in browser user or the international domain used to access Facebook

sb

2 years

Browser ID and time stamp. Used to improve the suggestions for adding to friends

Facebook (Effectiveness)

js_ver

7 days

Number of days. Saves the age of Facebook javascript files

rc

7 days

A numeric value between 1 and 20. Used to optimize the website's performance for advertisers

Facebook (Analysis and research)

campaign_click_url

30 days

Analysis and research. Saves the URL of the Facebook page the user has reached after clicking on the Facebook promotion

Facebook (session cookies)

Checkpoint

removed after closing the browser

Session cookie that is responsible for authentication

lp

removed after closing the browser

Session cookie that is responsible for authentication

hckd

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

sfiu

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

ar

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

av

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

noscript

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

m_ts

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

next

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

next_path

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

presence

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

rdir

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

i_user

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

i_key

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

i_id

removed after closing the browser

Session cookie that is responsible for the security, integrity of the website and the product

m_pixel_ratio

removed after closing the browser

Session cookie responsible for effectiveness

p

removed after closing the browser

Session cookie responsible for effectiveness

dpr

removed after closing the browser

Session cookie responsible for effectiveness

sW

removed after closing the browser

Session cookie responsible for effectiveness

wd

removed after closing the browser

Session cookie responsible for effectiveness

a11y

removed after closing the browser

Session cookie responsible for effectiveness

act

removed after closing the browser

Session cookie that is responsible for analysis and research

reg_ext_ref

removed after closing the browser

Session cookie that is responsible for analysis and research

reg_fb_gate

removed after closing the browser

Session cookie that is responsible for analysis and research

reg_fb_ref

removed after closing the browser

Session cookie that is responsible for analysis and research

reg_uniqid

removed after closing the browser

Session cookie that is responsible for analysis and research

x-referer

removed after closing the browser

Session cookie that is responsible for analysis and research

x-src

removed after closing the browser

Session cookie that is responsible for analysis and research

Google Analitics

_ga

2 years

The cookie is responsible for distinguishing users. The file is saved by the Google Analytics server

_gid

24h

Used to distinguish between users saved by the Google Analytics website tracking service (1st party).

_gat

1 minut

File used for Google Analytics - "throttle request rate". If Google Analytics is implemented by Google Tag Manager, then the cookie will be named _dc_gtm_<property-id>

AMP_TOKEN

30 seconds to 1 year

It contains a token that can be used to download the Client ID from the AMP Client ID service. The AMP code can be used with various plugins, which can additionally generate cookies and collect information about the user. Files will be marked as AMP cookie.

_gac_<property-id>

90 days

Provides additional information about user interaction with Ad Words ads. For example, if Google Analytics is connected to Google AdWords, the file associated with the conversion Google Adwords will read the cookie until it is removed. Learn more.

__utma

2 years since the foundation / update

Used to distinguish users and sessions. A cookie file is created when you run the javascript library and there are no existing __utma cookies. The cookie file is updated each time data is sent to Google Analytics.

__utmt

10 minutes

File used for Google Analytics - "throttle request rate"

__utmb

30 minutes from the start / update

30 minutes from the start / update. Used to define new sessions / visits. A cookie file is created when you run the javascript library and there are no existing __utmb cookies. The cookie file is updated each time data is sent to Google Analytics.

__utmc

End of browser session

Not used in ga.js. Set up for interaction with urchin.js. Historically, this cookie worked in conjunction with the __utmb cookie to determine if the user was in a new session / visit.

__utmz

6 months from the beginning / update

Stores a traffic source or campaign explaining how a user has reached your site. A cookie file is created when the javascript library is run and is updated every time data is sent to Google Analytics.

__utmv

2 years since the foundation / update


Used to store custom variable data at the user level. This cookie is created when the programmer uses the _setCustomVar method with a custom variable at the user level. This cookie was also used for the withdrawn _setVar method. The cookie file is updated each time data is sent to Google Analytics. Learn more.

__utmx

18 months

For websites that use Google Analytics experiments. Specifies the user's inclusion in the experiment.

__utmxx

18 months

For websites that use Google Analytics experiments.

_gaexp

Depending on the duration of the experiment, but usually 90 days

For sites that use Optymize 360. Specify the user's inclusion in the experiment and the expiration of experiments in which the user has been included.

Remember that you can withdraw your consent to saving cookies at any time (by contacting the administrator - kontakt@gagagranit.pl) through the sites belonging to the GAGA Wholesale Building Stone Company.

Withdrawing consent you will prevent us from saving new cookies. If you want to delete all or selected cookies saved by our websites, please use the instructions contained in our website privacy policy

Files embedded in the article

Taking care of the reliability, timeliness and attractiveness of websites, we embed embedded files in the content of articles. We use the codes that generate the creators of these files, such as: Facebook, Twitter, YouTube, Instagram, Google, Flowplayer, TVN, Flickr, Infogram, DataWrapper and Google tools, such as: Data Studio, Fusion Tables, Google Maps, Google Earth , Fusion Tables.