Cookie Policy
This policy explains how Swiftener uses cookies and similar technologies on swiftener.com.
What are cookies?
Cookies are small text files stored on your device by your browser. They help websites remember preferences and understand how visitors use the site.
How we use cookies
Swiftener uses a minimal set of cookies:
- Essential cookies: Required for basic site functionality and security. These cannot be disabled without affecting the service.
- Preference cookies: May remember settings you choose within a tool suite (stored locally in your browser where possible), such as light/dark theme.
- Analytics cookies: When you Accept, Google Analytics may set cookies (e.g.
_ga,_gid) and Microsoft Clarity may set its own cookies to measure usage anonymously — pages viewed, traffic sources, approximate location, and session heatmaps/replays. - Advertising cookies: When you Accept, Google AdSense may set cookies to show ads (including personalized ads where allowed). If you Reject, ads may still appear in a limited, non-personalized form.
Third-party cookies
We use Google Analytics (gtag.js), Microsoft Clarity, and Google AdSense. Google and Microsoft may set cookies according to their Google and Microsoft privacy policies. We may also load fonts from Google Fonts. Tool subdomains may use additional third-party resources; refer to each suite's documentation for details.
Managing cookies
You can control cookies through your browser settings. Blocking all cookies may limit site functionality.
For analytics and ads, Swiftener shows a consent banner on your first visit. Until you Accept, Google Analytics and AdSense run in Consent Mode with storage denied and Microsoft Clarity is not loaded. Your choice is stored in localStorage as swiftener-analytics-consent (granted or denied). To change it later, clear that key in your browser’s site data for swiftener.com (and tool subdomains) and reload — the banner will appear again.
Consent Mode and what “Reject” means
Swiftener implements Google Consent Mode v2. Until you Accept, analytics_storage, ad_storage, ad_user_data, and ad_personalization default to denied. That means measurement and ads run in a limited cookieless mode where possible. Clarity session replay is not loaded until consent is granted.
Choosing Reject keeps those storage signals denied. You can still browse the catalog and use tools. Some ads may appear in a non-personalized form if AdSense is loaded; they should not rely on advertising cookies for personalization when storage remains denied.
Local storage versus cookies
Many suite preferences (theme, last-used tool, editor layout) live in localStorage or IndexedDB rather than cookies. Those keys stay on your device and are not sent with every HTTP request the way cookies are. Clearing site data for a subdomain removes them. Browser-first tools that process files locally may also keep temporary blobs in memory or IndexedDB for the session; closing the tab usually ends that state.
Cross-subdomain note
Swiftener suites live on subdomains (for example audio.swiftener.com). Consent and preference keys may need to be set per origin. If you Accept on the hub and later open a suite that shows the banner again, Accept or Reject there as well. Cookie and localStorage isolation by origin is a browser security feature, not a tracking trick.
How long cookies last
Essential session cookies may expire when you close the browser. Preference and analytics cookies set by third parties typically last from days to months according to Google or Microsoft defaults. We do not independently extend third-party lifetimes. Clearing cookies and site data for swiftener.com and its subdomains removes what your browser still holds.
Related policies
See the Privacy Policy for categories of data we process, and Contact if you need a human answer about consent or ads.txt.
Contact
Questions about this policy: michaeldunga1@gmail.com