YESIM Cookie Policy
Effective date: 25 September 2026
Data Controller:
Genesis Group AG
Bahnhofstrasse 4, Baar, 6340, Switzerland
Registration number: CHE-135.623.633
Email: support@yesim.app
EU Representative (Article 27 GDPR):
Priverion Deutschland GmbH
Schellingstr. 109a
80798 Munich, Germany
1. WHEN DOES THIS COOKIE POLICY APPLY?
Summary: This Cookie Policy explains what cookies and other tracking technologies we use, why we use them, how you can manage your preferences, and how these technologies relate to the processing of your personal data.
- 1.1. In this Cookie Policy, references to “YESIM”, “we”, “us”, or “our” refer to Genesis Group AG, Registration number: CHE-135.623.633, Bahnhofstrasse 4, Baar, 6340, Switzerland.
- 1.2. We are committed to respecting your privacy and being transparent about how we or third parties acting on our behalf may use cookies and other tracking technologies on our website https://yesim.app/ (“Website”) or mobile application “Yesim: eSIM & Mobile Data”, published on App Store and Google Play (“Application”). This Cookie Policy explains what cookies and other tracking technologies are, which types we use, for what purposes, and how you can manage or withdraw your consent.
- 1.3. This Cookie Policy should be read together with our Privacy Policy (https://yesim.app/privacy-policy/), which provides more detailed information about how we process personal data and your rights under applicable data protection laws.
2. WHAT ARE COOKIES?
Summary: Cookies are small text files stored on your device when you visit a website. They may contain information about your device and your use of the Website, including unique identifiers that may qualify as personal data.
- 2.1. Cookies are small files that store information about your device, how you use the Website, and sometimes anonymized personal data. They allow the Website or Application to:
- ensure proper functionality
- enhance user experience
- recognize your device
- remember your preferences
- personalize content
- collect information about how the service is used
- analyze website traffic and user behavior
- 2.2. In addition to cookies, we may use similar technologies, such as software development kits (SDKs), pixels, tags, local storage, or device identifiers, which perform functions similar to cookies, including enabling certain features, measuring performance, analyzing usage, and supporting marketing activities. Depending on their purpose and configuration, these technologies may collect information such as your device and browser details, IP address, interaction data, or usage patterns, and may involve first-party technologies set by us or third-party technologies set by our partners or technology providers.
- 2.3. International data transfers. Some of our partners are located in, or process data in, countries outside Switzerland, the European Economic Area and the United Kingdom, including the United States. Where these countries are not recognised as providing an adequate level of data protection, we rely on appropriate safeguards, such as the EU-U.S. Data Privacy Framework, the UK Extension to it and the Swiss-U.S. Data Privacy Framework (where the recipient is certified), or the Standard Contractual Clauses approved by the European Commission, together with the amendments required under Swiss and UK law. You may request a copy of the relevant safeguards by contacting us at support@yesim.app.
3. WHAT TYPES OF COOKIES AND SIMILAR TECHNOLOGIES WE USE?
Summary: We use different types of cookies and other tracking technologies on our Website and Application. Depending on their purpose, some cookies are strictly necessary and are always enabled, while others are used only with your consent.
3.1. Strictly Necessary Cookies (“Basic only”)
These cookies are essential for the Website and Application to function properly and cannot be turned off. Without these cookies, core features and services you request may not work as intended.
They are used, for example, to:
- enable basic website and application functionality
- ensure security and network management
- remember essential user inputs or session information
- enable access to secure areas
We use Strictly Necessary Cookies because they are essential to provide the Website and Application you request. Their use is exempt from consent under Article 5(3) of Directive 2002/58/EC and the corresponding national laws, and the related processing of personal data is based on our legitimate interest in providing a secure and functioning service (Article 6(1)(f) GDPR). We use all other cookies and similar technologies only on the basis of your consent (Article 6(1)(a) GDPR and Article 5(3) of Directive 2002/58/EC). Where Swiss law applies, we inform you about the use of these technologies and give you the option to refuse them in accordance with the Federal Act on Data Protection and Article 45c of the Telecommunications Act.
3.2. Performance and Analytics Cookies
These cookies help us understand how our Website and Application are used, for example, which pages or features are most and least popular, how users navigate through the services, and whether technical issues occur.
The information collected is used to:
- analyze usage and performance
- improve functionality and user experience
- optimize content and service design
These cookies are used only with your consent. Some of these cookies contain unique identifiers that allow us or our partners to recognise your browser or device across visits.
3.3. Advertising and Targeting Cookies
These cookies are used to personalize marketing communications and offers and to measure the effectiveness of our advertising campaigns. Some of these cookies are set by us, while others are set by trusted third-party partners.
They may store information about your preferences and interactions with our Website or Application in order to:
- display relevant advertisements
- limit how often you see an advertisement
- help us understand the effectiveness of marketing campaigns
These cookies are used only with your consent. Some of these cookies contain unique identifiers that allow us or our partners to recognise your browser or device across visits.
4. WHAT ARE FIRST-PARTY COOKIES AND HOW DO WE USE THEM?
Summary: First-party cookies are set directly by YESIM. They are primarily used to ensure the proper functioning, security, and basic performance of our Website and Application, as well as to remember essential settings and user inputs. You can find more information about these cookies in the table below:
| Name | Type | Purpose | Retention Period |
|---|---|---|---|
| aws-waf-token | Strictly Necessary | A security cookie that helps protect our Website from malicious traffic and automated attacks. | About 5 days |
| currency | Strictly Necessary | Remembers your selected currency so prices display correctly for you. | About 90 days |
| from | Strictly Necessary | Stores information about your location or how you found our Website. | About 24 hours |
| initial_referrer | Strictly Necessary | Stores the first referrer (the website or link) that brought you to our Website. | About 30 days |
| user_uuid | Strictly Necessary | A first-party identifier we use internally to recognize you as a visitor during your session and on future visits. | About 12 months |
| cookieAlert | Strictly Necessary | Remembers whether you accepted or rejected cookies, so we don't ask again unnecessarily. | About 90 days |
| FlutterSharedPreferences.xml | Strictly Necessary | Stores basic App settings and technical state (such as session counters and push-permission prompts) needed for the App to function normally. | Until App data is cleared or overwritten by the App |
| flutter.session_count | Strictly Necessary | Stores basic App settings and technical state (such as session counters and push-permission prompts) needed for the App to function normally. | Until App data is cleared or reset by the App |
| flutter.ask_push_token | Strictly Necessary | Stores basic App settings and technical state (such as session counters and push-permission prompts) needed for the App to function normally. | Until App data is cleared or updated by the App |
| flutter.af_conversion_data | Advertising & Targeting | Temporarily stores AppsFlyer campaign-attribution data within App settings. | Until App data is cleared or overwritten by the App |
The table above provides an overview of the cookies currently used and may be updated from time to time.
5. WHAT ARE THIRD-PARTY COOKIES AND HOW DO WE USE THEM?
Summary: Third-party cookies and similar technologies are set by third-party partners or technology providers. They may be used to analyze how our Website and Application are used, measure the effectiveness of marketing campaigns, or deliver relevant content and advertisements. You can find more information about these cookies in the table below:
| Vendor | Name, Identifier | Type | Purpose | Retention Period |
|---|---|---|---|---|
| Website | ||||
| Google Accounts | ACCOUNT_CHOOSER | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 12 months |
| Google Accounts | LSID | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 13 months |
| Google Accounts | LSOLH | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 12 months |
| Google Accounts | SMSV | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 12 months |
| Google Accounts | __Host-GAPS | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 13 months |
| Google Accounts | __Host-1PLSID | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 13 months |
| Google Accounts | __Host-3PLSID | Strictly Necessary | Used to keep you signed in to your Google Account and support related sign-in security/session features when you choose to log in via Google on our Website. | About 13 months |
| Stripe | __stripe_mid | Strictly Necessary | Used for fraud prevention and to support secure payment processing on our Website. | About 12 months |
| TikTok | _tt_enable_cookie | Strictly Necessary | Remembers your cookie-consent choice for the TikTok Pixel. | About 13 months |
| Amazon Ads | ad-id | Advertising & Targeting | Used to measure the performance of Amazon advertising campaigns and personalize the ads you see, including on other sites. | About 9 months |
| Amazon Ads | ad-privacy | Advertising & Targeting | Used to measure the performance of Amazon advertising campaigns and personalize the ads you see, including on other sites. | About 13 months |
| AppLovin | axcrt | Advertising & Targeting | Used to attribute app installs/purchases to AppLovin ad campaigns and measure their effectiveness. | About 12 months |
| Axon | _axidd | Advertising & Targeting | Used to attribute conversions to Axon ad campaigns and measure their effectiveness. | About 12 months |
| Axon | _axwrt | Advertising & Targeting | Used to attribute conversions to Axon ad campaigns and measure their effectiveness. | About 12 months |
| Axon | _axwrt_ts | Advertising & Targeting | Used to attribute conversions to Axon ad campaigns and measure their effectiveness. | About 12 months |
| Axon | ax_visitor | Advertising & Targeting | Used to attribute conversions to Axon ad campaigns and measure their effectiveness. | About 12 months |
| Facebook / Meta | _fbp | Advertising & Targeting | Used by Meta to link your visit to ad campaigns, enabling ad attribution and retargeting across Meta platforms. | About 90 days |
| Google Ads | IDE | Advertising & Targeting | Used by Google to measure ad campaign performance and link ad clicks to actions you take on our Website. | About 13 months |
| Google Ads | _gcl_au | Advertising & Targeting | Used by Google to measure ad campaign performance and link ad clicks to actions you take on our Website. | About 90 days |
| Microsoft Bing Ads | MUID | Advertising & Targeting | Used by Microsoft Advertising to measure ad campaign performance and recognize your browser across visits for ad attribution. | About 13 months |
| Microsoft Bing Ads | _RwBf | Advertising & Targeting | Used by Microsoft Advertising to measure ad campaign performance and recognize your browser across visits for ad attribution. | Set dynamically (per browser-assigned value); typically a session or short-lived identifier |
| Microsoft Bing Ads | SRCHD | Advertising & Targeting | Used by Microsoft Advertising to measure ad campaign performance and recognize your browser across visits for ad attribution. | Set dynamically (per browser-assigned value); typically a session or short-lived identifier |
| Microsoft Bing Ads | _uetsid | Advertising & Targeting | Used by Microsoft Advertising to measure ad campaign performance and recognize your browser across visits for ad attribution. | About 2-3 days |
| Microsoft Bing Ads | _uetvid | Advertising & Targeting | Used by Microsoft Advertising to measure ad campaign performance and recognize your browser across visits for ad attribution. | About 13 months |
| Reddit Ads | _rdt_em | Advertising & Targeting | Used by Reddit to attribute ad campaign performance and measure conversions from Reddit ads. | About 90 days |
| Reddit Ads | _rdt_pn | Advertising & Targeting | Used by Reddit to attribute ad campaign performance and measure conversions from Reddit ads. | About 90 days |
| Reddit Ads | _rdt_uuid | Advertising & Targeting | Used by Reddit to attribute ad campaign performance and measure conversions from Reddit ads. | About 90 days |
| Snapchat | X-AB | Advertising & Targeting | Used by Snapchat to attribute ad campaign performance and measure conversions from Snapchat ads. | About 2-3 days |
| Snapchat | sc_at | Advertising & Targeting | Used by Snapchat to attribute ad campaign performance and measure conversions from Snapchat ads. | About 13 months |
| Snapchat | _scid | Advertising & Targeting | Used by Snapchat to attribute ad campaign performance and measure conversions from Snapchat ads. | About 12 months |
| Snapchat | _scid_r | Advertising & Targeting | Used by Snapchat to attribute ad campaign performance and measure conversions from Snapchat ads. | About 13 months |
| Snapchat | _sctr | Advertising & Targeting | Used by Snapchat to attribute ad campaign performance and measure conversions from Snapchat ads. | About 13 months |
| Tapad | TapAd_3WAY_SYNCS | Advertising & Targeting | Used to recognize the same user across different devices, for cross-device advertising measurement. | About 90 days |
| Tapad | TapAd_DID | Advertising & Targeting | Used to recognize the same user across different devices, for cross-device advertising measurement. | About 90 days |
| Tapad | TapAd_TS | Advertising & Targeting | Used to recognize the same user across different devices, for cross-device advertising measurement. | About 90 days |
| TikTok | _ttp | Advertising & Targeting | Used by the TikTok Pixel to measure advertising performance, understand user interactions with our Website and TikTok advertisements, and support ad targeting. | About 13 months |
| TikTok | ttcsid | Advertising & Targeting | Used by the TikTok Pixel to measure advertising performance, understand user interactions with our Website and TikTok advertisements, and support ad targeting. | About 13 months |
| TikTok | ttcsid_D8BK3I3C77UDG683GMUG | Advertising & Targeting | Used by the TikTok Pixel to measure advertising performance, understand user interactions with our Website and TikTok advertisements, and support ad targeting. | About 13 months |
| Google Accounts | OTZ | Performance & Analytics | A Google cookie that supports analytics and personalization of Google's own services when you interact with Google sign-in on our site. | About 7 days |
| Google Analytics / Google | _ga | Performance & Analytics | Helps us distinguish between different visitors and recognize returning visitors, so we can measure how our Website is used and produce traffic reports. | About 13 months |
| Google Analytics / Google | _ga_11YEGYYGB6 | Performance & Analytics | Helps us distinguish between different visitors and recognize returning visitors for this specific Google Analytics property. | About 13 months |
| Google Analytics / Google | _ga_26XN7B267M | Performance & Analytics | Helps us distinguish between different visitors and recognize returning visitors for this specific Google Analytics property. | About 13 months |
| Google Analytics / Google | _ga_Q5HDJDNFC3 | Performance & Analytics | Helps us distinguish between different visitors and recognize returning visitors for this specific Google Analytics property. | About 13 months |
| Google Analytics / Google | _ga_JL3RR3JH55 | Performance & Analytics | Helps us distinguish between different visitors and recognize returning visitors for this specific Google Analytics property. | About 9 months |
| Google Analytics / Google | FPID | Performance & Analytics | A first-party identifier that lets Google Analytics recognize your browser across visits to our domain, used to measure Website traffic and usage. | About 13 months |
| Google Analytics / Google | FPLC | Performance & Analytics | A short-lived first-party cookie that links an ad click to your visit, used to measure how effective our ad campaigns are. | About 2-3 days |
| Google Analytics / Google | FPGSID | Performance & Analytics | Identifies your current browsing session for Google Analytics session reporting. | Set dynamically (per browser-assigned value); typically a session or short-lived identifier |
| PostHog | ph_phc_dMSoHiQNtNS7nnuNCkM3bLxLkphlIBHoQeSgacgpA5Z_posthog | Performance & Analytics | Remembers your device and session so PostHog can analyze how you use our Website to help us improve our product; this includes session replay, which is enabled for this cookie. | About 12 months |
| PostHog | ph_device_205839 | Performance & Analytics | Remembers your device so we can understand how you use our Website and improve our product. | About 13 months |
| PostHog | sessionid | Performance & Analytics | Keeps you signed in to your current session while using analytics-connected features. | About 30 days |
| PostHog | remember-cookie_5fa02aac-1428-4229-8516-e101ceb9da0f | Performance & Analytics | Remembers your device so we can understand how you use our Website and improve our product. | About 30 days |
| PostHog | posthog_csrftoken | Performance & Analytics | A security cookie that protects PostHog-related requests from cross-site attacks. | About 30 days |
| Application | ||||
| Device operating system | Advertising ID (IDFA on iOS / Google Advertising ID on Android) | Advertising & Targeting | Used to attribute App installs and purchases to advertising campaigns. On iOS, accessed only if you allow tracking through App Tracking Transparency. | Controlled by your device; you can reset or delete it at any time in your device settings |
| AppsFlyer | appsflyer-data.xml / AF_INSTALLATION | Performance & Analytics | Used to attribute your app install to the marketing source that led you to install the App, and to measure campaign performance. | Until app data is cleared, the App is uninstalled, or the SDK is reset |
| AppsFlyer | attributionId | Performance & Analytics | Used to attribute your app install to the marketing source that led you to install the App, and to measure campaign performance. | Until app data is cleared or attribution data is refreshed |
| AppsFlyer | AFRequestCache/* | Performance & Analytics | Used to attribute your app install to the marketing source that led you to install the App, and to measure campaign performance. | Temporary — until sent, expired, or app data is cleared |
| Facebook / Meta | anonymousAppDeviceGUID | Advertising & Targeting | Used by Meta to measure app install/purchase attribution and the effectiveness of Meta ad campaigns for the App. | Until app data is cleared/deleted or the SDK is reset |
| Facebook / Meta | AppEventsLogger.persistedevents | Advertising & Targeting | Used by Meta to measure app install/purchase attribution and the effectiveness of Meta ad campaigns for the App. | Temporary — until sent or cleared |
| Facebook / Meta | com.facebook.sdk.attributionTracking.xml | Advertising & Targeting | Used by Meta to measure app install/purchase attribution and the effectiveness of Meta ad campaigns for the App. | Until app data is cleared or the SDK is updated |
| Facebook / Meta | IAP_CACHE_GPBLV2V7.xml | Advertising & Targeting | Used by Meta to measure app install/purchase attribution and the effectiveness of Meta ad campaigns for the App. | Until app data is cleared or the SDK cache is refreshed |
| PostHog | anonymousId | Performance & Analytics | Recognizes your device so we can understand how you use the App. | Until app data is cleared or the SDK is reset/re-identified |
| PostHog | deviceId | Performance & Analytics | Recognizes your device so we can understand how you use the App. | Until app data is cleared or the SDK is reset |
| PostHog | sessionReplay | Performance & Analytics | Stores your session-replay configuration, used where enabled to review App usage for product improvement. | Until SDK update or app data is cleared |
| PostHog | featureFlags / featureFlagsPayload | Strictly Necessary | Remembers which App features/experiments are enabled for you for core App functionality to work correctly. | Until SDK update or app data is cleared |
| Firebase / GA4 | app_instance_id | Performance & Analytics | Used for Firebase/Google Analytics to understand how the App is used and measure engagement. | Until app data is cleared or the analytics identity is reset |
| Firebase / GA4 | session_id | Performance & Analytics | Used for Firebase/Google Analytics to understand how the App is used and measure engagement. | Session-based; kept until overwritten or cleared |
| Firebase / GA4 | first_open_time | Performance & Analytics | Used for Firebase/Google Analytics to understand how the App is used and measure engagement. | Until App data is cleared |
| Firebase / GA4 | consent_settings | Strictly Necessary | Stores your privacy/consent choice locally so the App and Google services respect your preference. | Until consent choice changes, SDK overwrites it, or App data is cleared |
| Firebase / GA4 | dma_consent_settings | Strictly Necessary | Stores your consent choice for Google's EU digital-markets requirements locally on your device. | Until consent choice changes, SDK overwrites it, or App data is cleared |
| Firebase / GA4 | google_app_measurement_local.db | Performance & Analytics | A local technical queue that temporarily stores analytics events before they are sent. | Temporary — until sent or deleted |
| Firebase Remote Config | frc_*_firebase_activate.json | Strictly Necessary | A technical cache used to load App configuration and feature settings; not used to track you personally. | Until Remote Config updates or App data is cleared |
| Firebase Remote Config | frc_*_firebase_settings.xml | Strictly Necessary | A technical cache used to load App configuration and feature settings; not used to track you personally. | Until Remote Config updates or App data is cleared |
| Firebase Installations | Fid | Strictly Necessary | Used to technically identify this App installation, supporting crash reporting, push notifications, and app configuration delivery. | Until App data is cleared or the Firebase installation is reset |
| Firebase Installations | AuthToken | Strictly Necessary | A short-lived security token used to authenticate this App installation with Firebase. | About 7 days (604,800 seconds) |
| Firebase Installations | RefreshToken | Strictly Necessary | Used to renew the App's Firebase authentication without requiring you to do anything. | Until App data is cleared or the Firebase identifier is rotated/removed |
| Firebase Crashlytics | firebase.installation.id | Performance & Analytics | Used to identify crash and error reports for this App installation, helping us diagnose and fix bugs. | Until App data is cleared or Firebase is reset |
| Firebase Crashlytics | crashlytics.installation.id | Performance & Analytics | Used to identify crash and error reports for this App installation, helping us diagnose and fix bugs. | Until App data is cleared or Crashlytics is reset |
| Firebase Crashlytics | .crashlytics.v3/open-sessions/* | Performance & Analytics | Used to identify crash and error reports for this App installation, helping us diagnose and fix bugs. | Until sent, expired, or deleted |
| Google DataTransport | com.google.android.datatransport.events | Strictly Necessary | A local technical queue used by Google/Firebase SDKs to deliver events reliably; not used to track you individually. | Temporary — until sent or deleted |
| Intercom | push_token | Strictly Necessary | Used to operate in-App customer support chat and deliver related push notifications. | Until token refresh, app data is cleared, or the App is uninstalled |
| Intercom | intercom_*_datastore.preferences_pb | Strictly Necessary | Used to operate in-App customer support chat and deliver related push notifications. | Until App data is cleared or updated by Intercom |
The table above provides an overview of the cookies currently used and may be updated from time to time.
Our Application does not use browser cookies. Instead, it uses SDKs and local storage on your device that perform similar functions (for example, SharedPreferences and local databases on Android, and UserDefaults and Keychain on iOS). In this Cookie Policy, references to "cookies" include these technologies. The names listed in the tables below are those used in the Android version of the Application. The iOS version uses the same SDKs for the same purposes, but the names of the stored files and keys may differ.
How our partners use your data. Some of our advertising and analytics partners, including Meta, Google, Microsoft, TikTok, Snap, Reddit, Amazon and Tapad, may use the information collected through their cookies and SDKs for their own purposes. In such cases, they act as independent controllers, or as joint controllers with us for the collection and transmission of the data. Where we act as joint controllers, our responsibility is limited to the collection and transmission of the data to the relevant partner. For more information on how these partners process your data and how you can opt out, please see their privacy policies.
6. HOW CAN YOU MANAGE YOUR COOKIE PREFERENCES?
Summary: You can choose whether to allow non-essential cookies and can change or withdraw your consent at any time.
- 6.1. We only deploy Strictly Necessary Cookies (“Basic only”) when you first access our Website or Application. All other cookies are considered non-essential and are used only where you have provided your prior consent.
- 6.2. We request your consent to use non-essential cookies through our cookie banner as follows:
- by selecting “Accept all”, you consent to the use of all cookies, including non-essential cookies;
- by selecting “Basic only”, you choose to allow only strictly necessary cookies, and no non-essential cookies will be used;
- by selecting “Customize”, you can choose which categories of non-essential cookies you wish to allow before they are deployed on your device.
- 6.3. Once you have set your cookie preferences, you may change or withdraw your consent at any time through our cookie banner or settings page https://yesim.app/terms-of-service/?srsltid=AU7gw4W2Kw7E_f3CUuGs4Y1f5wyMtUA1eP8jHU3HZj1wFc50ukwp3z1A . Withdrawing your consent will not affect the lawfulness of any processing carried out before your consent was withdrawn.
- 6.4. You can also manage cookies directly through your browser settings. Most browsers allow you to block cookies, delete existing cookies, or alert you when a website attempts to place or update a cookie on your device. Please note that if you access our Website or Application from more than one device or browser, you may need to adjust your settings separately for each of them. Additional guidance on managing cookies is available through the help or support section of your browser.
- 6.5. Managing your preferences in the Application. When you first open the Application, we ask you to choose your preferences for non-essential SDKs through an in-app consent screen. No non-essential SDK is activated, and no data is sent to our analytics or advertising partners, before you make your choice. You can change your choice at any time in the Application under Profile > Settings > Privacy. On iOS, we ask for your permission through Apple's App Tracking Transparency framework before accessing your device's advertising identifier (IDFA). You can change this permission at any time in Settings > Privacy & Security > Tracking. On Android, you can reset or delete your advertising ID in your device settings (usually under Settings > Google > Ads; menu names may vary by device).
7. YOUR RIGHTS
7.1. For information about your rights in relation to your personal data, please see our Privacy Policy. You also have the right to lodge a complaint with the Swiss Federal Data Protection and Information Commissioner (FDPIC) or with the data protection supervisory authority in the EU or EEA country where you live or work, or where you believe an infringement has occurred.
8. DO WE MAKE CHANGES TO THIS COOKIE POLICY?
Summary: Yes, we will update this Cookie Policy as necessary to reflect relevant changes.
- 8.1. We may update this Cookie Policy from time to time to reflect changes in legal requirements, technological developments, or our business practices. When we make material changes, we may notify you in a manner appropriate to the significance of those changes — for example, by displaying a prominent notice within our Website or Application or by sending you a direct notification.
- 8.2. We encourage you to review this Cookie Policy periodically to stay informed about how we use cookies. The “Effective date” at the top of this page indicates when this Cookie Policy was last revised.
9. HOW CAN YOU CONTACT US?
- 9.1. If you have any questions, comments, or requests regarding this Cookie Policy or the way we use cookies, you may contact us at:
- Email: support@yesim.app;
- Postal address: Bahnhofstrasse 4, Baar, 6340, Switzerland.
We will respond to your inquiry in accordance with applicable laws.
- 9.2. If you are located in the European Union or the European Economic Area, you may also contact our representative appointed under Article 27 of the GDPR: Priverion Deutschland GmbH Schellingstr. 109a, 80798 Munich, Germany. Our representative may be contacted in addition to us or instead of us on all matters relating to the processing of your personal data.