Cookies and similar technologies
What happens on your device
Cookies, device storage and third-party requests explained separately for the website and mobile app.
Effective: 11 October 2026 · Version 1.0.0
Summary
The public Jepify website currently has no first-party analytics configured and its project settings do not enable Google Analytics. Our legal pages are designed not to load remote fonts or analytics. That does not mean that other website pages or external services necessarily make no requests, store no information or set no cookies.
This policy describes the currently documented setup and what is still being checked. The full Privacy notice gives the controller’s identity, purposes, legal bases and your rights.
The website
| Technology | Why it is present | Current treatment |
|---|---|---|
| Firebase Hosting | Delivers website pages and necessarily handles technical connection information such as IP addresses | Operational processing; verify provider cookies and retention before stating any precise cookie list |
| Google Fonts | Some non-legal pages request typeface resources from Google’s servers | A network request may share technical connection information; not an assertion that Google sets a cookie |
| Google Forms | May provide an embedded or linked early-access form once configured | Google’s own page or embedded form may use cookies/storage; read its separate disclosure before entering information |
| Site analytics | Site configuration currently has no Google Analytics ID | No first-party analytics-enabled tracking in current source configuration |
| Language selection | Lets visitors choose a language | Verify whether preference is held in URL, browser storage or other technology before listing a storage duration |
No optional website analytics or advertising storage should be activated before the relevant consent mechanism and disclosures are implemented when required. A consent banner is not needed merely because a site has a Cookie Policy; the actual technologies and applicable exemptions determine the requirement.
Similar technologies in the mobile app
Mobile apps do not have to use traditional browser cookies to store information. Jepify’s current design uses local storage for account/session access, offline commands and security functions. These essential app functions differ from optional product-usage analytics. Technical diagnostics may involve software-generated identifiers and require their own necessity and lawful-basis analysis.
Optional child usage information is handled by a separate permission decision, subject to who is legally entitled to decide. You can find the processing purposes and the consent/withdrawal procedure in the Privacy notice. Agreeing to the adult Terms does not grant permission for optional child usage analytics.
Managing choices
- Device or browser settings may permit you to clear local storage or restrict cookies; doing so can sign you out or affect necessary features.
- On a third-party form or linked provider site, use that provider’s available controls.
- For optional child usage analytics, use the controls or rights-request route described in the Privacy notice.
- If the website introduces non-essential cookies or similar storage, it must provide an appropriate choice before use where required, and explain how to withdraw the choice.
Open verification
The exact cookies, local storage keys, lifetimes and provider behaviour depend on the deployed website and mobile builds. These still require verification: Firebase Hosting response behaviour, Google Fonts requests on marketing pages, embedded Google Forms, any language-selector storage, and app SDK device-storage behaviour.
We will not invent a cookie inventory or state that Google definitely sets a cookie just because it serves fonts or hosting. Verified technical results can be added as a detailed table without changing users’ existing rights.
Privacy questions: privacy@dynamikus.com. Back to the Legal Centre.