Cookie Policy
Walkie Pro
Last updated: 11 October 2026 Version: 2.6
1. What this covers
This policy explains how Walkie Corporation (“Walkie,” “we,” “us”) uses cookies and similar technologies across three surfaces, which behave differently:
| Surface | What it uses |
|---|---|
| walkiepro.com — our marketing website | Necessary cookies always. Analytics and Advertising cookies only after you accept each category — §5 |
| The Walkie Pro app | No cookies. Some SDKs with device identifiers — §6 |
Public job bulletin pages (app.walkiepro.com/b/…) |
Nothing at all — §7 |
It forms part of our Privacy Policy.
2. What cookies are
Cookies are small text files placed on your device when you visit a website, letting a site remember things between pages and visits.
First-party cookies are set by the site you are visiting. Third-party cookies are set by someone else — an analytics or advertising provider.
We also use similar technologies: local storage, pixels and web beacons, and in the app, mobile SDKs and device identifiers, which do a comparable job without cookies.
3. The categories we use
| Category | Purpose | Consent needed |
|---|---|---|
| Strictly necessary | Security, page loading, remembering your cookie choices | No — the site cannot work without them |
| Analytics | Which pages people visit, where they run into trouble | Yes — nothing is set until you accept |
| Advertising | Showing Walkie Pro ads on Facebook and Instagram to people who have visited walkiepro.com, measuring whether those ads lead to signups, and measuring which Google ads lead people to install the app or open it in a browser | Yes — nothing is set, Meta’s pixel is not loaded, and Google’s tag stores nothing for advertising, unless you accept the Advertising category |
Advertising cookies count as “sharing” personal information for cross-context behavioral advertising under California law. The Advertising category is the control, and you can opt out at any time — see §8.
4. What this does not cover — an important line
We do not use advertising or analytics cookies inside the app, and we never use your communications for advertising.
Your messages, calls, recordings, transcripts, summaries, photos, documents, lists, and contacts are not used to build advertising audiences, are not shared with advertising platforms, and are not used to target ads. We show no advertising in the app.
The cookies described here relate to visitors to our marketing website. When you create an account or start a paid plan, our servers — not a cookie, and not the app — tell Meta that it happened, with a hashed email address and never your phone number. We tell Google nothing from our servers. Privacy Policy §7 explains that and sets out the whole line in a table.
5. Cookies on walkiepro.com
| Name | Purpose | Set by | Type | Expires | Category |
|---|---|---|---|---|---|
cookieyes-consent |
Records your cookie choices — a consent ID and your answer for each category — so you are not asked on every page | walkiepro.com (CookieYes) | First-party cookie | 12 months | Strictly necessary — cannot be rejected |
_ga |
Distinguishes visitors so we can count unique users | Google Analytics | First-party cookie on .walkiepro.com |
2 years | Analytics — set only after you accept |
_ga_DQ0ZCEH2TS |
Maintains session state for our Google Analytics property | Google Analytics | First-party cookie on .walkiepro.com |
2 years | Analytics — set only after you accept |
walkie_attr |
Remembers which campaign or referral link first brought you here — the utm_source, utm_medium, utm_campaign, utm_content, utm_term and ref values from that first URL, and, only if you also accept the Advertising category, the Google ad-click identifier from it (gclid, gbraid or wbraid) — so a later visit does not get credited to the wrong source. It holds only those values and never anything you type; a click identifier names the ad click, not you |
walkiepro.com (Walkie) | First-party cookie | 90 days | Analytics for the campaign and referral values, Advertising for the click identifier — each set only after you accept |
_fbp |
Identifies your browser to Meta, so Meta can recognise a later visit and tell us whether an ad led to it | Meta pixel | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
_fbc |
Holds the ad-click identifier when you arrive by clicking a Meta ad, so the visit is credited to that ad | Meta pixel, or walkiepro.com on its behalf | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
fr |
Meta’s own advertising cookie, used to deliver and measure ads and to recognise you if you use Facebook or Instagram | Meta (.facebook.com) |
Third-party cookie | 90 days | Advertising — set only after you accept, and only if your browser allows third-party cookies |
_gcl_au |
Google’s conversion-linking cookie: it lets a later App Store, Google Play or web-app tap be credited to the Google ad that brought you here | Google tag (the conversion linker) | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
_gcl_aw |
Holds the Google ad-click identifier (gclid) when you arrive by clicking a Google ad, so the visit is credited to that ad |
Google tag (the conversion linker) | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
_gcl_gb |
The same, for the gbraid and wbraid identifiers Google uses in place of gclid when a click crosses between a browser and an app |
Google tag (the conversion linker) | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
_gcl_gs |
A further ad-click value the same tag stores beside _gcl_aw; Google documents it as part of the same conversion-linking set |
Google tag (the conversion linker) | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
Conversion |
Google’s own cookie, set when your browser reports a conversion to Google Ads; Google lists its purposes as advertising and security | Google (www.googleadservices.com) |
Third-party cookie | 90 days | Advertising — set only after you accept, and only if your browser allows third-party cookies |
_gcl_ag, _gcl_dc, _gac_gb_… |
The remaining cookies in the same conversion-linking set, which Google documents with the same lifespan and the same first-party placement. The third one’s name ends in the identifier of the Google Analytics property, and it appears where that property is linked to a Google Ads account | Google tag (the conversion linker) | First-party cookie on .walkiepro.com |
90 days | Advertising — set only after you accept |
That is the entire list of cookies we set or allow. Until you accept a category, the only cookie on this website is the one recording your cookie choices. Google Analytics is loaded with consent denied by default, so it does not set the two _ga cookies until you say yes, and walkie_attr is not written either — the campaign values wait in your browser’s session storage, which is not a cookie and is discarded when you close the tab. Meta’s pixel is not loaded at all until you accept the Advertising category, so none of the three Meta cookies can be set before that. If you arrive from a Meta ad, the click identifier waits in session storage the same way, and is written to _fbc only if you accept.
Google’s advertising cookies work the same way, through a different switch. Google’s tag is already on the page for our website analytics, so what waits for your consent is not the loading of a script but the storing. Until you accept the Advertising category we set Google’s own consent signals to deny advertising storage: Google writes none of the _gcl_ cookies above, and reads none already on your device. If you arrive from a Google ad, the click identifier waits in session storage, exactly as a Meta one does, and reaches a cookie only if you accept. Google’s tag does still send a ping from each page while the switch is off — with no cookie, and with your IP address truncated — which Privacy Policy §7 describes in full.
One thing beside that table. Google also documents that its conversion linker keeps the same ad-click information in your browser’s local storage, under the key _gcl_ls. Local storage is not a cookie, it is written under the same consent, and clearing this site’s data in your browser removes it.
We do not remarket on Google. No audience is built from your visit, and the third-party cookies Google uses for remarketing — IDE on doubleclick.net, which Google documents as lasting 13 months in the UK and EEA and 24 months elsewhere — are not set. If we ever turn remarketing on, we will add them to the table above, and ask for your consent, before the first one is set.
6. The mobile app
The app does not use browser cookies. It uses SDKs that perform similar functions with device identifiers.
| SDK | Purpose | What it accesses |
|---|---|---|
| Firebase Cloud Messaging (Google) | Delivering push notifications | Device push token, device and app identifiers |
| Google Play Billing Library (Google) — Android only | When you choose to subscribe, checking that Google’s external content links programme is available to you, showing Google’s information screen, and obtaining the transaction token Google requires | The Google Play app and account on your device. Runs only when you tap to subscribe, not at launch |
| Supabase | Authentication and data sync | Session tokens stored on your device |
Firebase starts when the app launches — before any screen where you could make a choice about it. It is integral: without Firebase you receive no call or message notifications. We disclose this rather than describe it as optional, because in the app it is not.
Payment does not happen in the app or on walkiepro.com. When you subscribe, or open your card and invoice settings, the app sends you to pages run by our payment processor, Stripe, on Stripe’s own domain. Any cookies set there are Stripe’s, not ours, and are governed by Stripe’s own policies.
Push notification registration happens only after you sign in and grant notification permission. Your device push token is not sent to us before that.
No advertising or analytics SDK runs in the app. The signup and payment events described in Privacy Policy §7 are sent from our servers, not from the app, and on iPhone only if you allow tracking when iOS asks.
Your controls: turn off notifications in device settings or in the app’s notification preferences; delete the app to stop all SDK activity.
7. Public job bulletin pages
If a job has a public page — reachable by link or QR code at app.walkiepro.com/b/… — that page is deliberately the plainest thing we run.
It sets no cookies. It uses no local storage. It runs no analytics. It contacts no third party of any kind — no fonts, no CDN, no tracking pixels, no advertising. It makes exactly one network request, to our own servers, to fetch the notices it displays.
We do not log visitors’ IP addresses. We keep an aggregate count of how many times a page has been viewed, and when it was last viewed. Nothing identifies who viewed it.
The page also carries instructions asking search engines not to index or archive it, and it sends no referrer information when you follow a link from it.
There is no cookie banner on that page because there is nothing to consent to.
8. Your choices
Cookie banner. On your first visit to walkiepro.com you can accept or reject each non-essential category, including Analytics and Advertising. Strictly necessary cookies cannot be rejected. Both non-essential categories start switched off, and nothing in them is set until you say yes.
Change your mind at any time through the Cookie preferences link in the website footer, which reopens the banner on any page.
The Advertising category is the control for the website. While it is off — and it is off unless you turn it on — Meta’s pixel is not loaded, Google’s tag writes and reads no advertising cookie, no advertising cookie is set, no audience is built from your visit, and no website visit data is shared with an advertising platform beyond the Google consent-state ping described in §5.
Turning off ad tracking. The Cookie preferences link in the website footer appears on every page, and using it to refuse the Advertising category stops advertising cookies and stops any sharing of website visit data for advertising. The footer’s Your privacy choices link goes to the section of our Privacy Policy that lists every control, including how to stop the signup and payment events about your account — Privacy Policy §13.
Global Privacy Control. We honor GPC. If your browser or an extension sends a GPC signal, we treat it as a refusal of advertising for that browser, with nothing further needed from you.
Do Not Track. There is still no agreed standard for DNT, so we do not respond to it. We do respond to GPC.
Browser controls. Most browsers let you block or delete cookies. Blocking all cookies may break parts of the website. Chrome · Safari · Firefox · Edge
Google-specific. Opt out of Google Analytics anywhere with the opt-out add-on, and manage ad personalization at myadcenter.google.com.
Meta-specific. Manage the ads Meta shows you at facebook.com/adpreferences, and read how Meta uses what it receives in the Meta Privacy Policy.
9. Third-party links
The website and app may link elsewhere. Once you leave, their cookie practices apply, not ours.
10. Changes
We may update this policy when the technologies we use change, or for legal or operational reasons. The “Last updated” date shows when.
If we add a cookie category or a new advertising provider, we will update this policy and ask for your consent before setting those cookies.
11. Contact
Walkie Corporation (dba Walkie Pro) 23945 Calabasas Rd, Suite 101, Calabasas, CA 91302, United States support@walkiepro.com · +1 (323) 504-7400