1. Overview
How PODFY thinks about cookies
PODFY is built for logistics teams and drivers, not ad-tech. Our design choices follow three rules:
- Minimal by default: we avoid storing data in the browser unless it is necessary for security or user experience.
- No tracking for sale: we do not use cookies for advertising, retargeting, or selling profiles.
- Transparent control: if we ever introduce non-essential cookies, they will be clearly disclosed and optional.
This policy focuses on browser-side storage (cookies, localStorage, sessionStorage and similar).
For server-side logging, sub-processors, and data subject rights, see the
Privacy Policy and Security pages.
2. Cookies & related technologies
What we mean by “cookies” here
Modern browsers provide several ways to store small pieces of data on the client. In this policy,
“cookies” is shorthand for all of the following:
- HTTP cookies: small name–value pairs sent with HTTP requests, which can be session-based or persistent.
- localStorage / sessionStorage: browser key–value storage accessible via JavaScript. PODFY aims to minimise use of this.
- IndexedDB and similar APIs: advanced browser storage. We do not currently use these for PODFY.
When we do set technical cookies (for example for sessions in podfy.app), they are configured with modern
security attributes where the platform supports them:
- Secure: only sent over HTTPS.
- HttpOnly: where possible, not readable from JavaScript.
- SameSite: set to
Lax or Strict to reduce cross-site request risks.
We distinguish between:
- First-party cookies: set by the podfy.net or podfy.app domain itself.
- Third-party cookies: set by external domains (for example ad networks).
PODFY does not use third-party cookies.
3. Current usage at PODFY
What is stored in your browser today
3.1 podfy.net – website & marketing pages
The public website at podfy.net is intentionally simple. As of this version of the policy:
- We do not set analytics, advertising, or tracking cookies.
- We do not embed third-party trackers such as Google Analytics, Meta Pixel, or similar tools.
- Server and edge logs are kept on the backend for security and reliability, but these do not rely on browser cookies.
3.2 podfy.app – operational POD platform
The application at podfy.app may need limited first-party cookies or equivalent storage to function securely.
Where used, these are:
- Strictly necessary: used for authentication, keeping you logged in, or protecting forms from abuse.
- Scoped: limited to the app domain and not reused for marketing or any third-party products.
- Short-lived: session-based or with reasonable expiries aligned with security goals.
Delivery portals & driver links
Drivers and partners access POD documents via tokenised links (URLs containing a one-time or time-limited token).
These tokens are validated on the server and are not stored in browser cookies. They act as references to a
single POD or shipment and are logged for auditing, but they do not track behaviour across pages or sessions.
3.3 No marketing or behavioural profiling
We do not use cookies to build behavioural profiles, sell usage data, or run third-party ad campaigns based on how
you or your drivers use PODFY.
4. Legal bases & consent
How this fits with GDPR & ePrivacy rules
In the EU/EEA, cookies are governed primarily by the ePrivacy Directive (as implemented locally) and, where personal
data is involved, by the GDPR. In practical terms:
-
Strictly necessary cookies (for example secure login, load-balancing, service security) may be set
without consent but must still be documented.
-
Non-essential cookies (analytics, marketing, tracking) require prior, freely given and revocable
consent before being stored or read.
Today, since we do not set analytics or marketing cookies, no separate cookie banner is required for podfy.net.
If we introduce non-essential cookies in the future:
- We will present a clear consent interface (banner or panel) before such cookies are used.
- You will be able to refuse non-essential cookies and still use core PODFY functionality.
- Each category (for example analytics vs. preferences) will be explained in plain language, including purpose and lifespan.
The underlying legal bases for cookie-related processing (for example legitimate interest vs. consent) are described
in more detail in the Privacy Policy.
5. Managing cookies & browser storage
How you stay in control
Even with a low-cookie product, you remain fully in charge of your browser. All modern browsers provide a control
centre for cookies and site data:
- Chrome / Edge: Settings → “Privacy and security” → “Cookies and other site data”.
- Firefox: Settings → “Privacy & Security” → “Cookies and Site Data”.
- Safari: Settings / Preferences → “Privacy”.
You can typically:
- Block third-party cookies globally (safe for PODFY).
- Delete existing cookies and cached data per-site or across all sites.
- Configure stricter rules for private/incognito windows.
For rights around personal data (access, correction, deletion, objection), please refer to the
Privacy Policy, which explains how to exercise these rights with PODFY.
6. Changes to this policy & contact
Keeping this document up to date
We will update this Cookie Policy whenever there is a material change in how we use browser storage
(for example, if we introduce first-party analytics or new preference cookies).
- The “Last updated” date at the top will always show the current version.
- For major changes, we may also show a notice on podfy.net or highlight the change in the app.
Questions or concerns?
If you have questions about cookies, tracking, or browser storage at PODFY, or if you believe this
policy is inaccurate or incomplete, please contact us:
Email: [email protected]