Event documents 22.10.2026

Cookies

Document contents

COOKIE POLICY TEDxUzhhorod 2026

Version date: 22 October 2026

1. General provisions

1.1. This Cookie Policy (the “Policy”) governs the use of cookies and other similar technologies on the official TEDxUzhhorod website (the “Website”) and informs users about the purposes of their use, their categories, possible ways in which information is processed, and the mechanisms available for managing privacy settings.

1.2. TEDxUzhhorod is an independently organized event operated under license from TED in accordance with the principle “Ideas Worth Spreading.”

1.3. The Website operator is:

Individual entrepreneur Sviatashova Maiia Serhiivna

Taxpayer identification number (RNOKPP): 3191210820

Registered location / correspondence address: 4V Zelena Street, Onokivtsi village, Uzhhorod District, Zakarpattia Region

Contact email address: tedxuzhhorod@gmail.com

Official Website address: tedxuzhhorod.com

1.4. The operator determines the purposes and methods of using cookie technologies on the Website within its authority and in accordance with Ukrainian law.

1.5. If information obtained through cookies or similar technologies enables a natural person to be identified directly or indirectly, it is also processed in accordance with personal data protection legislation.

1.6. The operator aims to ensure that cookies are used transparently, on justified grounds and only to the minimum extent necessary, without unjustified collection of information about users.

1.7. This Policy applies to technologies used directly on the Website, including those of the technical providers engaged.

1.8. When visiting external websites, including payment platforms, social networks and video services, the separate policies of their respective operators may apply.

1.9. This Policy forms part of the Website's legal documentation and applies together with the Privacy Policy and the Website Terms of Use of TEDxUzhhorod.

2. What cookies and similar technologies are

2.1. Cookies are small text files that a website or a service integrated with it may store on a user's device when a webpage is visited.

2.2. Cookies may contain technical identifiers, settings information, session parameters or other information needed for the Website and its individual functions to operate.

2.3. Depending on their purpose, cookies may be used for:

● ensuring that webpages display correctly;
● maintaining the Website's technical operation;
● ensuring information security;
● preventing automated attacks;
● storing the user's privacy choices;
● remembering certain settings;
● analysing website traffic;
● enabling embedded content to work;
● other lawful and specified purposes.

2.4. In addition to cookies, the Website may use similar technologies, including:

● Local Storage;
● Session Storage;
● technical browser identifiers;
● application programming interfaces and SDKs;
● analytics scripts;
● tracking pixels;
● other means of storing information on, or obtaining information from, a device.

2.5. The application of this Policy to a particular technology depends on whether it is actually used, the nature of the data, its function and the applicable legal requirements.

2.6. Not all cookies contain personal data. However, a technical identifier, an IP address or a combination of data about a user's behaviour may, in certain circumstances, make it possible to identify that user.

2.7. The use of cookies does not in itself mean access to all the contents of a user's device or their personal files.

3. Categories of cookies

Depending on their function, the following categories of technologies may be used on the Website.

3.1. Strictly necessary cookies

3.1.1. This category includes technologies that are objectively necessary for the Website to work correctly, to ensure its security or to provide a function specifically requested by the user.

3.1.2. Such technologies may include:

● technical session identifiers;
● mechanisms for protection against cyber threats;
● tools for preventing misuse;
● load-balancing technologies;
● storage of cookie preferences;
● other technical tools without which the requested function cannot operate correctly.

3.1.3. Strictly necessary cookies are used only to the extent justified by the relevant technical or functional need.

3.1.4. Where applicable law does not require consent for a particular strictly necessary technology, that technology may be used without obtaining separate consent.

3.1.5. Cookies cannot be placed in this category merely as a formality. Analytics, marketing or other optional tools are not considered strictly necessary simply because they are useful to the Website operator.

3.2. Functional cookies

3.2.1. Functional cookies are intended to provide additional features and personalize the user experience.

3.2.2. They may be used for:

● storing the selected language;
● remembering display settings;
● supporting certain interactive features;
● customizing how content is displayed;
● other additional functions that are not essential for basic browsing of the Website.

3.2.3. If functional cookies are not strictly necessary to provide a service specifically requested by the user, they are used after consent has been obtained where such consent is required by applicable law.

3.2.4. Refusing optional functional cookies must not unjustifiably restrict access to basic information about the Event.

3.3. Analytics cookies

3.3.1. Analytics cookies may be used to obtain statistical information about visits to the Website and to assess how effectively it works.

3.3.2. Such information may include:

● the number of visits;
● pages viewed;
● general sources of traffic;
● session duration;
● technical browser characteristics;
● device type;
● page loading errors;
● other indicators of website use.

3.3.3. Analytics tools may help the operator improve navigation, access to information and the Website's technical stability.

3.3.4. Analytics cookies may be used only if they have actually been connected and there is an appropriate legal basis.

3.3.5. If applicable law requires prior consent for a particular analytics technology, its use begins only after that consent has been given.

3.3.6. The operator aims to apply the principles of data minimization, limited retention and, where technically possible, anonymization or a reduction in the level of detail of analytics information.

3.3.7. This Policy does not confirm the use of any particular analytics service until its actual integration has been verified.

3.4. Third-party service and embedded content cookies

3.4.1. The Website may contain embedded third-party materials, including:

● video recordings of TEDx Talks;
● videos from video-hosting platforms;
● interactive maps;
● other external information modules.

3.4.2. To display such content, the user's browser may connect to the relevant provider's servers.

3.4.3. Depending on the technical implementation, the third-party provider may receive certain technical data, including the IP address, browser information, the time of the request or other identifiers.

3.4.4. If loading third-party content involves optional cookies or other technologies requiring prior consent, that content is activated only after consent has been obtained.

3.4.5. The operator may use a prior-notice mechanism that displays an information panel instead of embedded material until the necessary permission has been obtained.

3.4.6. The user may decline to load third-party content and continue using the Website's other functions.

3.5. Marketing and advertising cookies

3.5.1. The TEDxUzhhorod Website is intended to provide information about an independently organized event and is not a platform for third-party commercial advertising.

3.5.2. Under the rules of TEDx the use of the website for third-party advertising is restricted.

3.5.3. The use of marketing cookies, advertising pixels, behavioural profiling or personalized advertising technologies is not provided for by default.

3.5.4. Before considering the integration of such technologies, the operator must check:

● their compliance with the rules of TEDx;
● the existence of a lawful purpose for their use;
● the legal grounds for processing data;
● the need for prior consent;
● the conditions for transferring information to third parties;
● the implications for users' privacy.

3.5.5. Such tools must not be activated until the relevant assessment has been completed and the necessary safeguards have been implemented.

4. Classification of cookies by duration and origin

4.1. By duration, cookies may be classified as session cookies or persistent cookies.

4.2. Session cookies are used during the current browser session and are usually deleted when that session ends.

4.3. Persistent cookies may remain on a device for a specified period or until the user deletes them.

4.4. The retention period of a particular cookie depends on its purpose, technical settings and applicable legal requirements.

4.5. By origin, cookies are classified as:

● first-party cookies, set by the Website's domain;
● third-party cookies, set by or accessible to other providers through integrated services.

4.6. A cookie's origin does not automatically determine its legal status or whether consent is required. Its function, technical implementation and the applicable legal rules are decisive.

5. Inventory of cookies and technologies used

5.1. The operator maintains an up-to-date inventory of cookies and other similar technologies used on the Website.

5.2. This inventory is compiled on the basis of an actual inspection of the Website's technical configuration.

5.3. The following is specified for each technology in use:

● the name of the cookie or other identifier;
● the provider or domain;
● its function;
● its category;
● its retention period;
● the legal basis for its use;
● information about possible transfers of data to third parties or outside Ukraine;
● a link to the relevant provider's policy, where applicable.

5.4. The specific inventory of technologies is to be published after the technical inspection has been completed.

5.5. The operator does not claim to use Google Analytics, Meta Pixel, YouTube, Google Maps or any other particular tools unless their use is confirmed by the Website's actual configuration.

5.6. When a new service is connected or the purpose of an existing cookie changes, the relevant information is reviewed and updated.

5.7. If a new technology requires prior consent, it may be activated only after the necessary mechanism for obtaining that consent has been implemented.

6. Legal grounds for using cookies

6.1. Cookies and the personal data associated with them are used and processed in accordance with Ukrainian law and, where applicable, the relevant international and European requirements.

6.2. The principal Ukrainian legislation on personal data protection is the Law of Ukraine “On Personal Data Protection.”

6.3. If data obtained through cookies are personal data, they must be processed on one of the legal grounds provided for by law.

6.4. Depending on the purpose of the technology and the actual circumstances, those grounds may include:

● the data subject's consent;
● the necessity of performing a contract or taking actions provided for by law;
● compliance with a legal obligation;
● other legal grounds provided for by applicable law.

6.5. For strictly necessary technologies, the issue of obtaining consent is determined in light of their purpose and the applicable legal requirements.

6.6. For optional technologies, the operator uses consent-management mechanisms to the extent required by applicable law.

6.7. If the GDPR and relevant ePrivacy requirements apply to the operator's activities, cookies requiring prior consent are not set or read until valid consent has been obtained.

6.8. Consent to the use of cookies and the legal basis for subsequent processing of personal data are assessed separately where required by the relevant legislation.

6.9. The technical ability to set cookies is not an independent legal basis for using them.

7. Obtaining user consent

7.1. Where the use of particular cookies requires prior consent, the operator provides a clear privacy-settings mechanism through which users can give it.

7.2. On a user's first visit to the Website, an information banner may explain the use of cookies and the available choices.

7.3. The banner must provide access to the following actions:

● “Accept all”;
● “Reject optional”;
● “Customize”.

7.4. When choosing individual settings, the user can manage separate categories of optional cookies.

7.5. Strictly necessary cookies may be marked as mandatory where that classification is justified.

7.6. The consent mechanism must follow the principles of consent being:

● freely given;
● specific;
● informed;
● unambiguous;
● understandable;
● withdrawable.

7.7. Silence, inactivity, continued browsing of the Website or pre-ticked boxes are not considered valid consent where the law requires an affirmative indication of the user's wishes.

7.8. Buttons for accepting and rejecting optional cookies must be clear and visible and must not put unjustified pressure on the user.

7.9. Refusing optional cookies must not unjustifiably prevent the user from viewing basic information about TEDxUzhhorod.

7.10. The current advertising tracking mode is described in “Connected technologies”. You can turn it off through “Cookie settings” in the footer.

7.11. If a user rejects optional cookies, the operator stores that choice in the manner necessary to implement it technically.

8. Withdrawing consent and changing settings

8.1. The user can change their preferences for optional cookies at any time.

8.2. For this purpose, the Website provides a permanently accessible link:

“Cookie settings”

8.3. The link is placed in the Website footer or another permanently accessible interface element.

8.4. Through that interface, the user can:

● review permissions previously given;
● change their category choices;
● withdraw consent;
● give consent again;
● read information about the technologies used.

8.5. Withdrawing consent must be no more difficult than giving it where this is required by applicable law.

8.6. After consent is withdrawn, the operator stops further use of the relevant optional technologies to the extent that this is within its technical control.

8.7. Where technically possible, cookies set directly by the operator on the basis of the withdrawn consent are deleted or cease to be used.

8.8. Third-party cookies may require the user to take additional steps in their browser or the relevant service's settings.

8.9. Withdrawal of consent does not affect the lawfulness of processing carried out on the basis of that consent before withdrawal, unless otherwise provided by law.

8.10. The operator may periodically ask the user to choose their settings again, in particular if technologies change significantly or the validity period of a previous choice expires.

9. Use of TEDx videos and other embedded services

9.1. The Website may contain links to official TEDx Talks recordings and other materials published in accordance with the rules of TEDx.

9.2. Third-party technology platforms may be used to display videos.

9.3. Embedded materials may cause the user's browser to contact the relevant provider's servers.

9.4. If loading a video requires the activation of optional cookies or other technologies requiring prior consent, the operator provides an appropriate mechanism for obtaining permission.

9.5. Before the necessary consent is obtained, an information placeholder may be displayed instead of the video, with an option to activate external content.

9.6. Similar approaches may be applied to interactive maps, social plugins and other external components.

9.7. The user may choose to open the relevant material directly on the external provider's website where this option is available.

9.8. After the user visits a third-party resource or activates external content, the relevant provider may process information independently under its own privacy policy.

9.9. External platforms are used with regard to the applicable rules of TEDx and the rights of the relevant rights holders.

10. Payment service cookies

10.1. The WayForPay payment service may be used to sell electronic tickets to TEDxUzhhorod.

10.2. If a user follows a link from the Website to a separate WayForPay payment page, that page may use the payment service's own technologies and policies.

10.3. Cookies needed to process payments securely, prevent fraud, confirm transactions or operate the payment interface may be processed by the payment provider in accordance with its legal obligations and terms of service.

10.4. The Website operator does not control all technical processes of an independent payment service.

10.5. If a payment module is integrated directly into the Website, the operator assesses the relevant technologies and informs users within the scope of its authority.

10.6. Before making a payment, the user is advised to read the relevant payment service's terms.

10.7. The Website operator must not use a payment service's technical processes as a justification for the unjustified collection of additional personal data.

11. Transfers to third parties and outside Ukraine

11.1. Depending on the technology services actually connected, information obtained through cookies may be processed by the technical service providers engaged.

11.2. These providers may include:

● hosting providers;
● information security services;
● analytics platforms;
● video services;
● mapping services;
● other providers involved in operating the Website.

11.3. Personal data are transferred only where there is an appropriate legal basis and in compliance with Ukrainian law.

11.4. If the actual operation of a third-party service involves transferring personal data outside Ukraine, the operator checks the lawfulness of the transfer and the relevant conditions for processing the information.

11.5. Where the GDPR applies, international transfers of personal data also comply with its requirements.

11.6. The operator does not state that all personal data are stored exclusively in Ukraine unless this is confirmed by the Website's technical configuration and the terms of the providers engaged.

11.7. Details of specific providers, the categories of data transferred and the relevant policies are disclosed in the current cookie register and Privacy Policy.

12. Information retention periods

12.1. Cookies and the data associated with them are retained for the period necessary to achieve the relevant lawful purpose.

12.2. Retention periods may vary depending on the category of technology, its purpose and the provider's requirements.

12.3. Strictly necessary cookies are retained no longer than justified by their function, except where a different period is necessary and lawful.

12.4. Analytics and other optional technologies must use limited and justified retention periods.

12.5. The operator does not set arbitrary personal data retention periods solely on the basis of the technical ability to accumulate such data.

12.6. The specific lifetime of cookies is stated in the relevant register following technical verification.

12.7. Information about a user's cookie choices may be retained for the period necessary for the consent-management mechanism to work properly and for compliance with legal obligations.

12.8. If cookies are deleted by the user or their browser, the Website may ask the user to set their preferences again.

13. Managing cookies through your browser

13.1. The user can also manage cookies through their browser settings.

13.2. Most modern browsers allow users to:

● view stored cookies;
● delete individual cookies;
● clear website data;
● block third-party cookies;
● restrict information storage;
● set additional privacy preferences.

13.3. The procedure for configuring cookies depends on the browser and its version.

13.4. Disabling all cookies in the browser may affect the availability of certain technical functions of the Website.

13.5. Deleting cookies through browser settings does not always automatically delete personal data previously transferred lawfully and stored on the operator's or a third-party provider's servers.

13.6. Browser settings are an additional means of control and do not replace the operator's obligation to provide an appropriate mechanism for obtaining and withdrawing consent where required by law.

14. Information security

14.1. The operator applies appropriate organizational and technical measures to protect information obtained through the Website and the technologies used.

14.2. Depending on the technical configuration, these measures may include:

● the use of secure information-transfer protocols;
● restricted access to administrative systems;
● access-rights management;
● control of integrated third-party scripts;
● software updates;
● minimization of the data processed;
● configuration of retention periods;
● checks for technical vulnerabilities;
● response to information security incidents.

14.3. The operator aims to prevent unauthorized access to personal data, unlawful use of such data and accidental loss.

14.4. No technology can guarantee absolute protection against every possible cyber threat; however, the operator must comply with applicable legal requirements and take appropriate protective measures.

14.5. If an incident involving personal data is detected, the operator acts in accordance with applicable law and internal incident-response procedures.

15. Users' rights regarding personal data

15.1. If information obtained through cookies is personal data, the user has the rights provided for by Ukrainian law.

15.2. In particular, in the circumstances provided for by law, the user has the right to:

● obtain information about the processing of their personal data;
● know the purposes and legal grounds of that processing;
● obtain information about recipients of personal data as provided for by law;
● object to processing;
● request correction of inaccurate data;
● request destruction of data where there are lawful grounds;
● withdraw consent where processing is based on that consent;
● seek protection of their rights from the competent authorities or a court.

15.3. If the GDPR applies to particular processing, the user may exercise additional rights under its provisions.

15.4. The procedure for exercising users' rights and further information about personal data processing are set out in the Privacy Policy of TEDxUzhhorod.

16. Changes to this Policy

16.1. The operator may revise this Policy following changes in legislation, the Website's technical configuration, the list of integrated services or the way information is processed.

16.2. When new technologies that materially affect users' privacy are connected, the operator carries out the relevant legal and technical assessment.

16.3. The current version of the Policy is published on the Website with its update date.

16.4. If changes involve new optional cookies requiring consent, that consent is obtained before they are activated.

16.5. Changes to the Policy cannot in themselves replace valid user consent or another necessary legal basis.

16.6. The operator ensures that the published version of the Policy corresponds to the Website's actual technical processes.

17. Contact information

17.1. For questions about cookies, privacy settings and personal data processing, users may contact the Website operator.

TEDxUzhhorod 2026

Official Event page:

https://www.ted.com/tedx/events/69351

Official website: tedxuzhhorod.com

Contact email address: tedxuzhhorod@gmail.com

17.2. Enquiries are considered according to the nature of the matter raised and the applicable requirements of Ukrainian law.

17.3. If it is necessary to verify the applicant's identity, the operator may request only the additional information objectively necessary to consider the enquiry properly.

18. Final provisions

18.1. This Policy applies together with:

● the Privacy and Personal Data Protection Policy;
● the Website Terms of Use;
● the Rules for Ticket Purchases, Changes and Refunds;
● other applicable documents of TEDxUzhhorod.

18.2. If any provisions of this Policy conflict with mandatory rules of Ukrainian law, the relevant rules of law apply.

18.3. The Policy is interpreted in accordance with the principles of lawfulness, transparency, good faith, data minimization and the protection of users' privacy.

18.4. This Policy takes effect on the date of its official publication on the Website.

18.5. Before all Website functions are put into operation, the operator verifies the actual inventory of cookies and ensures that their settings comply with the published Policy.

TEDxUzhhorod is an independently organized event operated under license from TED.

This independent TEDx event is operated under license from TED.

Connected technologies · 26 October 2026

This website uses Meta Pixel (Meta Platforms) to measure advertising and build audiences for TEDxUzhhorod ads on Facebook and Instagram. Pixel starts when you visit, without a prior confirmation banner. You can turn advertising tracking off through “Cookie settings” in the footer; a previously saved refusal is also respected.

Events include PageView (page visit), AddToCart (opening the form), InitiateCheckout (a saved request and handoff to WayForPay) and Purchase (confirmed payment). PageView, AddToCart, InitiateCheckout and Purchase are also sent through the server-side Conversions API. Events include ticket quantity, value in UAH, page address and, where available, browser information, IP address and advertising identifiers. To match InitiateCheckout and Purchase to advertising interactions, the server sends Meta SHA-256 hashes of email and phone. Telegram is not sent to Meta; contact fields are not added to page URLs or browser event parameters. An explicit tracking opt-out is honoured.

Cookie settings: tedx_marketing_consent_v1 in this website’s localStorage records only explicitly chosen settings and the time of your choice. Visiting the website does not create a consent record. Settings remain valid for 180 days and can be changed in the footer or removed through your browser.
Meta advertising identifiers: _fbp identifies a browser; _fbc stores an available Meta click ID. The website prepares these first-party identifiers before sending events, keeps existing values across its pages and sets a cookie lifetime of up to 90 days. A new click can replace an older click ID; a direct visit without a click does not create one. Browser restrictions may shorten cookie retention. The current Meta policy governs use of these identifiers.

This website also uses Google Analytics 4 (Google) to analyse visits: page views (page_view), opening the form (add_to_cart), payment handoff (begin_checkout) and confirmed purchases (purchase), ticket quantity and value in UAH. GA4 starts on a visit; a previously saved tracking opt-out also applies to GA4. Our code does not send contact field values; automatic interactions depend on the GA4 web stream settings. The _ga and _ga_41GC17HGDK cookies help distinguish visits and sessions. See the Google Privacy Policy. Google may process information outside Ukraine.

On the landing page, GA4 also receives section and speaker-card visibility (at least half of the smaller of the element or viewport for two seconds), visible time in a focused tab, ticket-button location, FAQ openings and scroll milestones. These are visibility estimates, not proof of reading. Hidden-tab time and contact-field contents are not included. Form errors are sent only as fixed categories, without entered values.

Meta may process information outside Ukraine. See the Meta Privacy Policy and Meta Cookies Policy.

Refusing does not restrict access to the website. Turning tracking off stops further Meta and Google Analytics events and removes _fbp, _fbc, _ga and _ga_41GC17HGDK cookies accessible to this website; it does not erase information already sent to these services.

The website stores your request (phone, email, optional Telegram username and selected quantity) separately from WayForPay payment confirmations. Ticket delivery uses the email entered in WayForPay. Card details are processed by WayForPay and are not stored on this website. The tedx_locale preference lasts two hours; tedx_marketing stores the tracking preference for 180 days. A secure HttpOnly receipt cookie lasts two hours and lets the result page display the verified payment status.

For requests from tagged links, the website records recognised UTM labels and advertising IDs and sends them with the request to the team’s Telegram notifications. The last tagged visit is retained in localStorage under tedx_campaign_attribution_v1 for up to 30 days; an untagged visit does not replace it. Tracking opt-out clears this browser record. Arbitrary URL parameters, URL fragments, payment tokens and Meta click/browser cookies are not included in the Telegram campaign link. A payment is not automatically assigned the source of a request.

Microsoft Clarity · cookieless analytics

Clarity loads automatically on the event landing pages without a separate permission banner. Analytics and advertising storage signals are set to denied; Clarity cookies are not enabled. This limited mode collects page views and basic interactions, but sessions can be fragmented and recordings and visitor journeys may be incomplete. Ticket forms and their dialog are masked before loading. Checkout and payment status pages are excluded. General tracking opt-out, browser Global Privacy Control and a previously saved recording refusal are respected. Microsoft processes interaction data under its privacy statement.

Back to the event