Cookie Notice
SealApply uses browser storage heavily — that is how a local-first app works — but almost all of it is your own data, sitting on your own machine. The exceptions are the cookies Microsoft Clarity uses for session recording and heatmaps, and the cookies Google AdSense uses to serve the ads that pay for SealApply, both described below.
1. Cookies and the other things like them
A cookie is a small file a site stores in your browser. Several related technologies do similar jobs, and this notice covers all of them:
- Cookies — session cookies disappear when you close the browser; persistent ones stay until they expire or you delete them.
- Local storage and IndexedDB — larger stores in your browser. This is where SealApply keeps your resumes, jobs and settings. It is by far the biggest category of storage we use, and none of it is sent to us.
- Session replay — code that records clicks, mouse movement, scrolling and navigation so the interface can be watched back later. We use Microsoft Clarity for this; see section 2.
- Pixels and web beacons — we do not use these, and we send no marketing email.
2. What SealApply uses
Strictly necessary — always on
These make the app function. They cannot be switched off from here, because without them there is no app; you can still clear them through your browser.
| What | Set by | Purpose | Lasts |
|---|---|---|---|
| IndexedDB application database | SealApply (first party) | Your resumes, profile, saved jobs, generated documents and application statuses. Never transmitted to us. | Until you delete it |
sealapply:consent | SealApply (first party) | Remembers which version of the Terms and Privacy Policy you accepted, so you are not asked on every visit. | Until you clear site data |
| Theme and interface preferences | SealApply (first party) | Light or dark mode, sidebar state and similar choices, so the app looks the way you left it. | Until you clear site data |
| Puter.js storage and session | Puter | Provides the browser storage layer the app is built on, and keeps you signed in if you chose to sign in with Puter. | Session, or until sign-out |
Analytics
These help us see which parts of the interface people struggle with. PostHog runs in memory-only mode: it sets no cookie, writes nothing to your browser’s storage, and keeps no identifier for you between page loads. Microsoft Clarity does set cookies, so that it can group a visit into one recording and recognise a returning browser. Google Analytics counts visits and where they come from; in the EEA, UK, Switzerland, Iceland, Liechtenstein and Norway it runs without cookies.
| What | Set by | Purpose | Lasts |
|---|---|---|---|
| PostHog | PostHog | Feature usage, page views and error reporting, so we can see which features are used and what is crashing. Includes browser, screen size and approximate location inferred from your IP address. No session replay. | Nothing in your browser; up to 12 months in PostHog’s own records |
_clck | Microsoft Clarity | Keeps a random Clarity user id and preferences, so visits from the same browser are recognised as one visitor. | 1 year |
_clsk | Microsoft Clarity | Joins the page views of one visit into a single session recording. | 1 day |
CLID, MUID | Microsoft | Identify a browser across Clarity sessions and Microsoft services that use Clarity. | 1 year |
| Session recordings and heatmaps | Microsoft Clarity | Clicks, scrolling, mouse movement and navigation, replayed so we can see where the interface confuses people. Typed form input is masked. | Recordings 30 days; heatmap data up to 13 months, in Microsoft’s records |
_ga, _ga_2C7YDBMEDV | Google Analytics | Counts visits, pages viewed and how people found the site (search, links, campaigns), so we know which pages are working. Not set in the EEA, UK, Switzerland, Iceland, Liechtenstein or Norway, where Google Analytics runs without cookies. Not used for advertising. | 2 years; event data 14 months in Google’s records |
We do not send your resume content, profile fields or API keys to PostHog. Clarity is different in one respect you should know about: because it replays the interface, text that is visible on screen while you work — which can include parts of your resume — may appear in a recording. What you type into form fields is masked.
Video — only if you play one
Tutorial videos are embedded from youtube-nocookie.com, YouTube’s privacy-enhanced mode. Nothing is set unless you press play, and no advertising cookies are set at all. Playing a video is governed by Google’s privacy policy.
Advertising — Google AdSense and sponsors
SealApply is free and is paid for by advertising. Inside the app, Google AdSense loads ads from googlesyndication.com and related Google domains. Google and its partners set cookies (such as __gads, __gpi and IDE) to serve and measure ads and, where the law allows, to personalise them based on your visits to this and other websites. In the EEA, UK and Switzerland, Google’s consent message asks you first. You can turn off personalised ads in Google’s Ads Settings or at aboutads.info, and read how Google uses this data in Google’s advertising policy.
Sponsor ads, which we sell directly, are images served from our own site. They set no cookies and send nothing about you to the sponsor.
3. How to control all of this
- Opt-out signals — if your browser sends a Global Privacy Control or Do Not Track signal, we treat it as a refusal and never load analytics — PostHog, Clarity or Google Analytics — at all.
- Objecting — you can also object to analytics in writing, at the address in section 5, and we will confirm it.
- Your browser — every major browser lets you block or delete cookies and site data. Be aware that clearing site data for SealApply deletes your resumes and saved jobs, because that is where they live. Export a backup from Settings → Backup first.
- Everything at once — clearing site data removes every item in the tables above.
4. Changes
If we add an analytics provider, or use an existing one for a new purpose, we update this notice.
5. Contact
Questions about this notice go to hello@sealapply.com. For the wider picture, see the Privacy Policy.