Cookie Policy
Last updated: 13 September 2026
This Cookie Policy explains how Aviggo uses cookies and similar browser technologies when you use aviggo.com, the web app or the Progressive Web App (PWA). It should be read together with our Privacy Policy.
1. What is a cookie?
A cookie is a small data file that may be stored by your browser or device when you use a website. Cookies can help keep a session active, remember authentication, support security and enable requested functionality.
2. What are similar technologies?
Aviggo may also use session storage, service workers, Cache Storage, push-subscription identifiers and other necessary browser storage. These technologies are not identical to cookies but may support similar operational purposes.
3. Scope
This policy applies to cookies and similar technologies used within aviggo.com and the Aviggo website/PWA experience. Third-party sites and services may have their own cookie policies.
4. Essential cookies
Some cookies are necessary for core functions such as sign-in, authenticated sessions, security, account access and request verification.
5. WordPress authentication and session cookies
Aviggo runs on WordPress. When you sign in, WordPress may use authentication/session cookies to associate your browser with your logged-in session. Blocking these cookies can prevent sign-in or authenticated features from working correctly.
6. Remembered login
Aviggo’s current login flow may use a persistent WordPress authentication session so you do not need to sign in again on every page. Signing out ends or invalidates the relevant session.
7. Security and request verification
WordPress nonces, session state or other necessary technical identifiers may be used for security, CSRF protection, authenticated requests and abuse prevention.
8. Near Me location cookie
When you use Near Me or current-location search, Aviggo may temporarily store coordinates obtained with your permission in a signed, HttpOnly cookie. In the current implementation this cookie is named aviggo_nearby_v1 and expires after approximately 30 minutes.
9. Why the Near Me cookie is used
The temporary cookie allows Aviggo to calculate nearby-provider distance without placing precise coordinates in the search URL or browser history. It is not used to build an advertising profile.
10. Near Me cookie safeguards
The current Near Me cookie is signed and HttpOnly, uses Secure when HTTPS is available, and uses SameSite=Lax. Tampered values are not accepted as valid location data.
11. Location permission is separate
Browser location permission allows the device to provide a location; the Near Me cookie temporarily supports the resulting search session. You can control location permission separately in your browser or device settings.
12. Session Storage
Aviggo may keep short-lived technical state in browser sessionStorage. The current implementation uses session-only state for one-time session refresh/recovery behavior. Session storage normally disappears when the relevant browser session ends.
13. Local Storage
The current Aviggo Core/Theme experience does not depend on persistent localStorage unless needed by a feature or provider. If Aviggo begins using persistent localStorage for additional user-facing purposes, this policy will be updated as appropriate.
14. PWA and Service Workers
Aviggo uses a service worker and web-app manifest for installable PWA functionality. The service worker may use browser Cache Storage for necessary static resources or technical responses to improve reliability, performance and an app-like experience.
15. PWA cache is not an advertising profile
PWA caching is primarily a technical delivery mechanism. It is not, by itself, used to create a personal advertising profile. Clearing site data may also remove service-worker caches.
16. Push notifications
If you grant notification permission, Aviggo may use a push provider such as OneSignal to deliver transactional notifications. Browser/device push-subscription identifiers and provider-required browser storage may be used for this purpose.
17. Notification permission is your choice
Push notifications are optional. You can turn permission off in browser or device settings. Doing so may stop booking, message, review or account push alerts while leaving other website features available.
18. Google Sign-In
When you use Google Sign-In, Google may use cookies or similar technologies on its own domains to operate the authentication flow. Google’s practices are governed by its own policies and Aviggo does not control the lifetime or behavior of those third-party cookies.
19. Facebook Login
If Facebook Login is enabled and used, Meta/Facebook may use its own cookies or similar technologies for authentication. Those technologies are governed by the provider’s own policies.
20. First-party and third-party technologies
Cookies set through aviggo.com may be first-party cookies. Technologies used by providers such as Google, Facebook or OneSignal through their domains or SDKs may be third-party technologies.
21. Search Insights
Aviggo’s current internal Search Insights feature may store limited server-side data such as searched keywords/filters and result counts to understand demand and coverage. The current Core implementation does not store visitor IP addresses or user-agent strings in these search logs and does not require an advertising cookie.
22. Analytics
Aviggo may use privacy-conscious measurement to improve performance and products. The current Core/Theme code does not make third-party advertising cookies or Google Analytics a required core feature. If non-essential analytics are introduced, Aviggo will provide notice or consent controls where required by applicable law.
23. Advertising cookies
The current core experience does not depend on interest-based advertising cookies. If targeted advertising or marketing cookies are introduced later, this policy and any legally required consent choices will be updated.
24. Language and interface preferences
Bangla/English language and interface state may be handled through account, URL, session or necessary site settings. If future preference features use cookies or persistent storage, they will fall within this policy.
25. Cookies and personal data
If a cookie or technical identifier can identify you directly or when combined with other information, it may be personal data under applicable privacy/data-protection law and will be handled under our Privacy Policy.
26. What we do not intend to do with cookies
- Store passwords or OTPs in plain text cookies;
- Use the precise Near Me cookie for advertising;
- Sell personal information merely because cookies are used;
- Store sensitive information in browser storage when it is not needed.
27. How long cookies last
Duration depends on purpose. Some cookies may last only for a browser session, authentication cookies may persist for a defined period, and the current Near Me precise-location cookie lasts about 30 minutes. Third-party retention is governed by the relevant provider.
28. Browser controls
Most browsers let you view, block or delete cookies and clear site data. Menu names and steps vary by browser and version.
29. What happens if you block cookies
Blocking all cookies may prevent sign-in, authenticated account functions, security verification or parts of Near Me from working correctly. Aviggo aims to keep core service available when non-essential technologies are disabled.
30. Clearing site data
After clearing cookies or site data you may need to sign in again, provide Near Me location again, recreate notification/PWA browser state and re-download cached resources.
31. Private or Incognito browsing
Private-browsing modes can treat browser storage differently and may delete local data when a session ends. Login, PWA or notification behavior can therefore differ from normal browsing.
32. Consent and necessary technologies
Where applicable law requires consent for non-essential cookies or similar tracking, Aviggo will provide an appropriate consent or preference mechanism. Strictly necessary authentication, security or user-requested functionality may require technical storage to provide the service.
33. Privacy rights
If personal data is processed through cookies or similar technologies, rights under Bangladesh’s Personal Data Protection Act 2026 and other applicable law may include access, correction, deletion, withdrawal of consent or complaint rights. See the Privacy Policy for more information.
34. Third-party policies
Cookies/storage used by Google, Meta/Facebook, OneSignal, browser vendors or other third-party providers are not under Aviggo’s direct control and may be governed by their own privacy and cookie terms.
35. Children and minors
Applicable age, consent and guardian requirements are addressed in our Terms of Service and Privacy Policy.
36. Security
Aviggo uses reasonable safeguards intended to reduce misuse of cookies and browser-based state. No internet/browser system is completely secure; on shared devices, signing out and using device/browser locks are important.
37. Changes to this policy
This Cookie Policy may be updated when browser technology, Aviggo features, third-party services or applicable law change. The last-updated date will be revised for material updates and additional notice may be provided when appropriate.
38. Relationship with other policies
This policy focuses on cookies and similar technologies. For broader personal-data practices see the Privacy Policy; for account and platform rules see the Terms of Service.
39. Contact
For questions about cookies, browser storage, privacy or data controls, contact Aviggo using the current details on the Contact Us page.