Cookie Policy

Pawalink is operated by Fortis Buildnext. This policy explains how the Pawalink platform uses cookies and similar technologies such as session identifiers, browser storage, IndexedDB, service-worker caches, push-subscription records, and analytics tags. Some of these technologies are stored directly by your browser or device rather than as classic cookies.

The platform currently uses httpOnly authentication cookies for server-managed access and refresh flows. Client-side code may also use browser-managed storage such as IndexedDB and local caches to support offline behavior, cache public or merchant views, and hold queued photo uploads or other locally stored media until they sync.

Strictly necessary technologies help users sign in, stay authenticated, secure sessions, prevent abuse, and route requests correctly. Functional technologies help the app remember workflow state, deliver PWA features, cache storefront and order data, and keep work available when connectivity is poor.

Where enabled, analytics technologies help Pawalink understand product usage, reliability, and conversion paths. Communications technologies may also be used to support push notifications or delivery of service messages.

• Strictly necessary: authentication, session continuity, abuse prevention, request integrity.
• Functional and offline: remembered workflow state, IndexedDB caches, queued uploads, and background sync for supported local uploads.
• Analytics: telemetry and event measurement where enabled.
• Communications: push-subscription handling and notification delivery where enabled.

You can manage cookies and many similar technologies through browser settings, device settings, or by clearing site data. Blocking some technologies may break sign-in, offline access, payment flows, receipt views, or storefront publishing.

If you use a shared or public device, clear browser data after use. Local browser storage may continue to hold cached content until it expires or is manually cleared.