Cookie Notice
This Cookie Notice explains how WALO uses cookies, pixels, local storage, device identifiers, OAuth state, security checks, and similar browser technologies on walohq.com, api.walohq.com, dashboards, PWA screens, and related WALO tools.
WALO will show cookie controls only when a control is actually available for that page or feature. Browser settings, provider settings, operating-system ad controls, and legal privacy request links remain available even when no WALO cookie panel is shown.
1. What cookies and similar technologies do
Cookies are small files placed in your browser. Similar technologies include local storage, session storage, pixels, tags, SDK identifiers, OAuth state values, PWA cache entries, server logs, and device signals. WALO may use these technologies to keep you signed in, protect accounts, remember preferences, measure site performance, understand campaign results, connect approved apps, prevent abuse, and improve the product.
These technologies may involve IP address, approximate location from IP address, browser type, device type, operating system, referral page, pages viewed, buttons clicked, feature events, timestamps, session IDs, consent choices, security events, OAuth flow state, and error logs.
2. Cookie and storage types WALO may use
Used for account login, session state, PWA install behavior, magic links or OAuth return checks, account settings, workspace state, and basic app navigation. These are required for protected WALO features to work.
Used for Cloudflare protection, Turnstile verification, rate limiting, abuse detection, bot checks, CSRF protection, suspicious login review, and replay/debug protection. Some security cookies cannot be disabled without breaking protected forms or logins.
Used to remember cookie choices, display preferences, language, accessibility settings, notification settings, recently used tools, PWA state, and dashboard UI state.
Used to measure visits, page speed, broken flows, errors, feature usage, referral paths, SEO scan usage, article queue submissions, and which pages need improvement. WALO is designed to avoid storing private connected-app content in analytics tools.
Where enabled, WALO may use pixels or tags to understand whether ads, search listings, social links, creator pages, or public campaigns lead to visits, signups, form starts, or purchases. These tools may be treated as targeted advertising, sharing, or sale under some state privacy laws depending on configuration.
When you connect Google, Microsoft, Yahoo, GitHub, Cloudflare, Vercel, Stripe, Spotify, WhatsApp/Meta, or another provider, cookies and OAuth state may help complete the connection. Provider cookies are controlled by that provider. WALO uses the permission result only for the feature you turn on.
If WALO embeds YouTube videos, maps, social widgets, share buttons, or app previews, those services may set cookies or collect events when the embed loads or when you interact with it.
3. Provider-specific notices and policy links
WALO may use or connect to the providers below depending on the feature, page, region, account type, and user choices. A provider listed here does not mean every visitor gets that provider's cookies on every page.
Cloudflare Hosting, DNS, security, caching, bot protection, Turnstile verification, Workers, logs, and abuse prevention. Cloudflare may process IP address, device data, request headers, security events, and challenge results.
Cloudflare privacyGoogle Analytics, Search Console, Ads, YouTube embeds, OAuth, Google account connections, Gmail/Calendar/Drive features, maps or geocoding, and AI or cloud services where enabled.
Google privacyMeta, Facebook, Instagram, and WhatsApp WhatsApp messaging features, Meta business tools, conversion measurement, pixels, Instagram/Facebook links, and social campaign tracking where enabled.
Meta privacyMicrosoft and Bing Microsoft account connections, Outlook/Calendar/OneDrive workflows, Bing indexing or webmaster tools, Microsoft advertising, and enterprise identity workflows where enabled.
Microsoft privacyLinkedIn Business campaign tracking, recruiting or company-page measurement, LinkedIn ads, and profile or company links where enabled.
LinkedIn privacyTikTok Campaign measurement, pixel events, creator traffic, and ad performance where enabled.
TikTok privacyYahoo Yahoo account or mail-related connections, email workflow support, and Yahoo/Verizon advertising or media measurement where enabled.
Yahoo privacyGitHub GitHub OAuth, repo access, deployment workflows, issue or commit automation, and user-approved code/project connections.
GitHub privacyVercel Deployment, hosting, preview links, build logs, observability, and project connection workflows where a user chooses Vercel.
Vercel privacyStripe Payment links, billing, invoices, checkout, payment method handling, fraud prevention, and tax/payment compliance where paid features are enabled.
Stripe privacySpotify Song Seeker account connection, playlist creation, saved track flows, and music metadata linking where you connect Spotify and grant permissions.
Spotify privacyOpenAI and other AI providers AI processing, model routing, transcription, reasoning, classification, summarization, or agent workflows where enabled. WALO is designed to send only the data needed for the requested task.
OpenAI privacy4. Connected app cookies and permissions
Connected apps are controlled by their own login screens, OAuth prompts, cookie systems, and privacy policies. WALO does not own those cookies and does not use a provider cookie to sign into that provider without your authorization. You can disconnect WALO inside WALO where available, and you may also revoke access directly in the provider's account settings.
For example, connecting GitHub may allow WALO to help with a repo task you approve. Connecting Spotify may allow WALO Song Seeker to create or update a playlist if you grant that scope. Connecting Google or Microsoft may allow email, calendar, file, or identity features if those scopes are granted. The exact permissions are shown by the provider or WALO flow before you approve the connection when the connection is active.
5. Your choices
- Browser controls: Most browsers let you block or delete cookies, clear local storage, limit third-party cookies, and control site permissions.
- WALO controls: When WALO shows a cookie or privacy control on a page, you can use it there. If no control is shown, that page may only use essential storage or controls may not yet be available.
- Provider controls: Google, Meta, Microsoft, LinkedIn, TikTok, Yahoo, Spotify, GitHub, Stripe, Vercel, and Cloudflare may offer their own privacy, ad, cookie, and connected-app settings.
- Device controls: Mobile operating systems may let you limit ad tracking, reset advertising IDs, control notifications, and manage app permissions.
- Privacy rights: Depending on your location, you may have rights to access, correct, delete, or opt out of certain processing. See the Privacy Policy and Privacy Choices.
Blocking cookies may affect login, magic links, security checks, PWA install behavior, accessibility preferences, connected apps, analytics accuracy, payment flows, and saved dashboard state.
6. Do Not Track, Global Privacy Control, and updates
Because there is no single accepted standard for Do Not Track signals across all websites, WALO does not currently change behavior automatically when a DNT signal is received. Where a binding law or technical standard requires honoring Global Privacy Control or another opt-out signal, WALO will treat the signal according to that law and the feature's configuration.
WALO may update this Cookie Notice as features, providers, laws, and browser rules change. If a new provider materially changes cookie or tracking behavior, WALO will update this page and, where required, request consent or provide an opt-out.
This notice is a product and privacy disclosure for WALO. It should be reviewed by qualified legal counsel before being treated as final legal advice.
Back to Legal Center