This policy concerns the Runbay website. A cookie is a small record placed in a browser by an online service and read in later requests. Local storage, session storage and similar technologies work differently, but their names alone do not remove the need to assess personal data processing.
Mobile app sessions and offline activity records are not cookies belonging to this website. They are covered separately in the Privacy Policy.
SECTION 02
Website application layer
Google Analytics 4 measures website visits only after acceptance. Before acceptance and after rejection, the Google tag is not loaded. Advertising permissions remain denied. Photos and fonts are served locally; language selection is stored in the URL. No mobile health records are sent to analytics.
Inventory of website code written by Runbay
Technology / purpose
Current status
Duration
Google Analytics: _ga, _ga_*
Google; first-party website audience measurement, only after acceptance.
180 days (configured maximum).
localStorage: runbay.analytics-consent.v1
Remembers acceptance or rejection on this browser.
180 days; checked on subsequent visits.
Advertising, retargeting and social tracking
No such trackers in the site code.
Not applicable.
External font or photo request
Fonts and the hero image are served from local site files.
Normal browser caching is separate.
SECTION 03
Hosting and access layer
The website’s primary address is https://runbay.co. The hosting provider may use cookies and technical records independently of the app code for access validation, session security or abuse prevention. Provider cookies are separate from the analytics cookies listed above.
Cookie names, provider domains, first/third-party status, purposes and actual retention periods for this layer have not yet been confirmed in a production inventory. No invented cookie list or duration is provided. The policy must be completed with an inventory covering the provider layer.
SECTION 04
Server logs and caching
Serving pages may involve infrastructure processing of IP addresses, request times, requested URLs, browser/device request information and response/error logs. This does not necessarily involve cookies. Purposes, legal bases, recipients and retention should be read with the Data Protection Notice.
Browser caching of pages, fonts or images for faster loading does not mean the app creates advertising profiles. Caching depends on browser behavior and server headers; this policy does not promise an unknown fixed cache duration.
SECTION 05
Legal basis and preferences
Whether a strictly necessary cookie requires explicit consent depends on its actual purpose and the Law’s processing conditions. Merely calling a cookie necessary is insufficient. Optional technology based on consent requires appropriate information and an active choice before activation.
Use Cookie settings at the bottom of any page to accept, reject or withdraw analytics permission. Withdrawal clears accessible GA cookies and reloads the page to stop the Google runtime. Your choice is remembered for 180 days; clearing site storage resets it. Browsing or scrolling does not count as acceptance.
You can inspect and delete cookies or restrict third-party cookies in browser privacy or site-data settings. Menu names vary by operating system and browser version. Deleting a provider cookie needed for access may require signing in again to a private review area.
Clearing web cookies does not delete mobile running history or your Runbay account. Manage mobile permissions in phone settings and account deletion in the app’s relevant screen.
SECTION 07
Updates and requests
This policy must be reassessed when the domain, hosting, access controls or measurement tools change. An update does not assume consent that was never given. Personal data requests are subject to the rights and procedures in the Data Protection Notice.
The controller’s verified identity and request channel must appear in this document’s identity section. Missing identity and provider inventory details must be completed by the operator.