RUNBAYDiscover Runbay RUNBAY / LEGAL DOCUMENTS
Cookies and similar technologies on the Runbay website, and how they differ from mobile app storage.
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.
The reviewed Vue app contains no cookie-writing code, local/session storage functions, advertising pixels or analytics SDKs. Photos and fonts load from site files. The homepage GPS drawing and performance values are illustrative; visitor location is not accessed and mobile health records are not connected. Language selection is represented in the URL and does not require a preference cookie.
| Technology / purpose | Current status | Duration |
|---|---|---|
| First-party application cookie | Not created by the site code. | Not applicable. |
| Preference cookie, localStorage or sessionStorage | Not used by the site code. | Not applicable. |
| Analytics or performance tracking cookie | No analytics in the site code. | Not applicable. |
| 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. |
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. The fact that site code creates no cookies does not mean the browser contains no provider cookies.
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.
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.
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.
Since current site code has no optional trackers, it does not display a banner collecting apparent consent for inactive categories. Future analytics or advertising technology must not activate without rejection and withdrawal options; names, purposes, providers, party status and durations must be updated. Scrolling or continuing to browse alone is not explicit consent.
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.
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.