1. About this policy
This policy covers the Jeda Android app, its Jeda Motion companion, and jeda.today. The Jeda developer uses the GitHub identity mikqi. For privacy questions or requests about your data, contact support@jeda.today.
Jeda is an entertainment launcher and browser. You do not need to create a Jeda account. Accounts you use to sign in to websites such as YouTube or streaming services belong to those providers.
2. Data processed and its purposes
- Shortcuts and preferences: names and addresses of websites you save or share with Jeda, shortcut visibility, backgrounds, and browser settings are stored on your device to prepare the phone and car interface.
- Website data: Android WebView stores cookies, sign-in sessions, cache, and website storage so pages and sign-ins can work. When you open a website, its operators and content providers may receive your IP address, browser/device information, requested pages, and information you enter.
- Device and car status: network status, app/Android/WebView/Android Auto versions, and restriction signals from the car host are used for compatibility, browser recovery, and restrictions on use in the car. Restriction signals do not involve collecting GPS location.
- Local diagnostics: event codes, timestamps, session status, and version information help investigate problems. Event logs are limited to the latest 50 entries. Diagnostic exports exclude saved URLs, cookies, and passwords. Diagnostics are shared only when you choose to share them.
- Support messages: if you send an email, the developer receives your email address, message, and attachments to answer questions or resolve problems.
The app version underlying this policy does not integrate advertising, analytics, or automatic crash-reporting SDKs that report to the developer. Local app data is not uploaded to a Jeda account server. This does not prevent data processing by websites you open.
3. Jeda Motion and third parties
If the verified Jeda Motion companion is installed, Motion can read and store a copy of Jeda shortcuts and preferences on the same device. This communication checks the companion app's package identity and signing certificate.
The login-sharing feature sends a copy of cookies for the chosen website to Motion only after you request it. Cookies may contain session tokens that provide access to a website account. Transfer happens between apps on your device, not through a developer server. Subsequent sign-ins and sign-outs in the two apps are separate; deleting Jeda data does not delete the copy in Motion.
Websites you open and their login, content, or media providers follow their own privacy policies. Jeda does not operate those services and does not sell your personal data. Support data is handled through the email provider to respond to messages; disclosure may occur where required by applicable law.
4. Permissions and security
The apps use Internet and network-state permissions to load websites and detect connectivity. The reviewed version does not request location, camera, microphone, contacts, or access to device photos/files. The browser denies website requests for camera and microphone access.
Website addresses must use HTTPS without credentials embedded in the URL. The browser rejects TLS certificate errors and blocks third-party cookies. Websites with protected-content support enabled may obtain access to WebView's protected-media identifier for DRM playback; media providers handle that data under their own policies.
Preferences are stored in private app storage; Android backup is disabled in the reviewed app configuration. The developer does not record cookie tokens in diagnostics. No storage or communication method can be guaranteed completely secure; keep your device secure and check websites before signing in.
5. Retention and deletion
Shortcuts and preferences remain until you change or delete them or clear app storage. Cookies and website data persist according to cookie expiry and WebView/website behavior until you clear them. Local diagnostic logs are replaced beyond the 50-entry limit and can be cleared through browsing-data deletion.
In Jeda, open Settings → Privacy → Clear browsing data → Clear all data to clear cookies, cache, and website storage. Shortcuts and preferences remain saved. To remove all local data, use Android settings to clear storage for Jeda and, if installed, Jeda Motion separately.
Support messages are retained for as long as needed to answer your request and follow up. You can request deletion of messages you sent by contacting support@jeda.today. Data required to be retained by law may be kept for the duration of that obligation; if this applies to your request, the reason will be explained.
See the data deletion guide for full steps. Clearing local data does not delete accounts, subscriptions, or data stored by third-party websites.
6. Website and demo
The jeda.today demo does not load streaming websites or ask you to sign in. Demo settings are held temporarily in page memory and reset when you reload. Your chosen language is stored locally in your browser so future visits can use it. When you have not chosen a language, the site uses your browser's language preferences. The site does not install analytics or advertising cookies.
The hosting provider may process IP addresses, browser information, access times, and requested URLs in operational logs to serve and secure the website. Log retention follows the hosting provider's configuration and policies. Email support messages are separate from demo data.
7. Children and policy changes
Jeda is intended for adults and is not specifically designed for children. Do not send children's personal information through support. If you believe a child's data has been sent to the developer, contact support@jeda.today so it can be reviewed and deleted.
This policy will be updated if features or data practices change. The update date appears on this page. Changes requiring additional notice or consent will be explained through an appropriate channel.