SaaSHammer
1. Cookies and related technologies
A cookie is a small browser-stored value. Similar technologies include local storage, pixels, tags, and online identifiers. SaaSHammer uses them to keep sessions working, protect forms, remember choices, measure performance when enabled, and connect with external services requested by a user.
2. Necessary session technology
| Name or type | Why it is used | Typical duration |
|---|---|---|
saashammer_user | Maintains a signed-in user session and stores form-protection data. | Browser session |
saashammer_admin | Maintains a separately protected administrator session. | Browser session |
| Security and checkout session identifiers | Protect requests, preserve a requested workflow, and help prevent duplicate or fraudulent actions. | Session or provider-defined |
Blocking necessary cookies can prevent sign-in, submissions, dashboard actions, or checkout from working.
3. Optional measurement technologies
SaaSHammer loads Google Tag Manager as the container for configured tags. The container itself manages tag delivery; tools loaded through it may store or read identifiers.
| Service | Possible identifiers | Purpose |
|---|---|---|
| Google Analytics, when enabled | _ga and property-specific identifiers | Audience, sessions, page use, events, device information, and approximate geography. |
| Microsoft Clarity, when enabled | _clck, _clsk, and provider identifiers | Heatmaps, interaction patterns, usability, and session diagnostics. |
The exact technologies present can depend on tag configuration, consent, browser settings, and provider changes.
4. Sign-in, checkout, and external destinations
Google Sign-In and the external payment provider may set cookies or similar identifiers for authentication, security, fraud prevention, and checkout continuity. Product and advertising cards can open third-party websites; those destinations apply their own cookie policies after you leave SaaSHammer.
Advertising purchased on SaaSHammer does not itself create a recurring subscription. Provider security technology may still be used during the one-time checkout.
5. Consent and browser controls
Where law requires it, non-essential storage or measurement should run only after the required choice. Available controls vary by browser and location. You can also:
- block or delete cookies in browser settings;
- use browser or provider opt-out features;
- decline optional technologies when a consent control is shown;
- use supported privacy signals where applicable.
Deleting session cookies signs you out and may reset an unfinished workflow.
6. Duration and provider changes
Session cookies normally end when the browser session expires. Analytics and provider-controlled identifiers can last longer according to their configuration and policies. Names and durations can change when browsers, providers, or our configuration changes, so this page describes both known first-party sessions and the categories of external technology that may be active.
7. Updates and contact
We will revise this page when our session names, analytics configuration, payment provider, retention settings, or legal requirements materially change.
Questions about cookies or tracking can be sent to [email protected].