Privacy
The shortest privacy policy we could honestly write.
Privacy is not a settings page. Applye Desktop is local-first. This marketing site is static. A future account-backed web product is not available yet, and it will have its own privacy model.
The desktop app
- Your data stays on your machine. Profile, job list, scores, documents, notes, and history live in a local SQLite database. There is no account, no cloud sync, and no server of ours that could hold a copy.
- No telemetry. Applye Desktop sends no analytics, crash reports, or usage pings. We literally cannot see how you use the desktop app.
- AI calls are opt-in and minimal. Nothing reaches an AI provider until you click an AI action. When you do, only the minimum needed for that one request (for example, the job description and the relevant profile fields) goes to the provider you configured, under your API key and their privacy terms. Results are cached locally so identical requests are never sent twice.
- Discover fetches public feeds only. The scan engine requests public job APIs and RSS feeds over HTTPS. It sends no personal data with those requests.
- Your keys stay local. Provider keys are stored on your device and used only to call the provider you chose.
- Deleting desktop data is deleting a file. Remove the local database and that desktop copy is gone. This is the desktop model. It is not a statement that a future web product stores nothing.
Applye Web, not available yet
- A Career Intelligence web platform is in development. It is not something you can sign up for today.
- When it exists, it will be a separate, account-backed surface. Private web data will be stored on a server under that product's own privacy model. This page does not pretend that model is already written.
- Community sharing, if it ships, will be explicit and reviewable. A web account will not upload Applye Desktop data by itself.
This website
- Static pages. No forms, no accounts, no comment widgets, no social embeds. The only third-party scripts on the site are the two analytics ones described below.
- No cookies at all - not for analytics either. Your theme preference and your analytics choice are kept in your browser's local storage, and nowhere else.
- Cloudflare Web Analytics runs on every visit, including before you answer the consent bar. It is why we can say the site had visitors at all. It sets no cookie, writes nothing to your browser, builds no identifier, and cannot follow you to another site: it counts a page view, its referrer, and coarse device and country information, and that is the whole of it. Because it stores nothing on your device and identifies nobody, it needs no permission to ask for.
- Google Analytics 4 runs only if you allow it. Anonymised IPs, advertising signals switched off. It records page views and six named clicks - nothing else, and nothing you type. Decline and nothing is loaded or sent. The full list, and the switch itself.
Two tools sound like more surveillance than one; it is the opposite trade. The cookieless one counts everybody but knows nothing about anybody, so the consenting one never has to be the source of the basic question "did anyone visit". Neither can see anything you type.
Applye Desktop has no telemetry. This website counts page views, so the docs that get read are the docs that get written. A future web product is not covered by the desktop telemetry promise.
Verify, don't trust
Every claim above is checkable, because the code opens to the public shortly: