1. What Are Cookies?
Cookies are small text files placed on your device (computer, tablet, or mobile phone) when you visit a website or use a web application. They allow the site to remember your actions and preferences over a period of time so that you don't have to re-enter them every time you come back.
In addition to traditional cookies, we may use similar tracking technologies, including:
- Local storage and session storage: Browser-based storage mechanisms used to persist authentication state and user preferences during and between sessions
- Web beacons / pixel tags: Tiny image files used in emails and web pages to track opens, clicks, and page visits
- Device fingerprinting: Techniques that use device characteristics (browser type, OS, screen resolution, etc.) for security and fraud detection — we use this minimally and only for security purposes
References to "cookies" in this Policy include all of the above technologies unless otherwise stated.
2. How FieldDNA Uses Cookies
We use cookies across three distinct contexts:
- Our marketing website — to understand how visitors find and interact with our website, optimise our content, and support marketing campaigns
- The FieldDNA web application — to authenticate users, maintain sessions, remember preferences, and ensure secure access to the platform
- Transactional emails — to track whether emails are delivered and opened (subject to your email client's settings)
3. Types of Cookies We Use
4. Third-Party Cookies and Trackers
Some cookies are set by third-party services that appear on our pages. We do not control these third-party cookies and they are governed by each provider's own privacy policy. The table above identifies the third-party providers we use. Key providers include:
- Google Analytics: policies.google.com/privacy
- Meta (Facebook): facebook.com/privacy/policy
- LinkedIn: linkedin.com/legal/privacy-policy
- Intercom / [Chat Provider]: [Link to provider privacy policy]
5. Cookie Consent Banner
When you first visit the FieldDNA website or log in from a new device, you will see a cookie consent banner. Below is a preview of the banner design and copy. Your development or web team should implement this using a compliant Consent Management Platform (CMP) such as Cookiebot, OneTrust, or CookieYes.
Implementation Notes for Your Development Team
- The banner must fire before any non-essential cookies are set (strictly necessary cookies may load immediately)
- Consent must be affirmative — pre-ticked boxes are not valid under GDPR
- Users must be able to withdraw consent as easily as they gave it
- Consent records must be stored (timestamp, categories accepted, version of policy) for compliance audit purposes
- Geo-detect EU/UK visitors and display the full granular consent UI; for other regions, a simplified notice may be used
- Integrate the CMP with your Google Tag Manager (GTM) or analytics setup to block non-consented tags
6. Managing Your Cookie Preferences
6.1 Via the Consent Banner
When you first visit the site, the consent banner allows you to accept all cookies, reject optional cookies, or customise your preferences by category. You can update your choices at any time through Settings → Privacy & Cookies within the FieldDNA application.
6.2 Via Your Browser
Most browsers allow you to refuse or delete cookies. The settings vary by browser:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Firefox: Settings → Privacy & Security → Cookies and Site Data
- Safari: Preferences → Privacy → Manage Website Data
- Edge: Settings → Cookies and site permissions → Cookies and site data
Please note that blocking or deleting strictly necessary cookies will prevent you from logging in to FieldDNA or using core platform features.
6.3 Opt-Out of Analytics Providers
- Google Analytics: Install the Google Analytics Opt-out Browser Add-on
- Facebook: Use Facebook's Ad Preferences settings
- LinkedIn: Adjust settings via your LinkedIn account under Data for LinkedIn Ads
7. Cookies and the Mobile App
The FieldDNA mobile application (iOS and Android) does not use cookies in the traditional browser sense. However, it uses equivalent technologies:
- Secure local storage: Used to store authentication tokens and offline data (e.g., beat plans cached for use in low-connectivity areas)
- Device identifiers: Used for push notification delivery, session management, and fraud detection
- GPS / location services: Used for route optimisation, attendance verification, and beat plan compliance — enabled only with your explicit permission via the device OS permission prompt. You may revoke this permission at any time via your device settings.
- Analytics SDK: Usage data (screens viewed, features tapped) is collected to improve the app — subject to your consent settings on the app's initial setup screen
8. Do Not Track Signals
Some browsers support a "Do Not Track" (DNT) setting that signals your preference not to be tracked across websites. As there is currently no universally accepted standard for responding to DNT signals, FieldDNA does not currently alter its data collection practices based on DNT signals. You can manage your preferences directly via our consent banner or browser settings as described above.
9. Changes to This Policy
We may update this Cookie Policy from time to time to reflect changes in our cookie usage, technology, or applicable law. We will display a notice on the FieldDNA website and reset the consent banner so you can review and re-confirm your preferences when material changes are made. The "Last Updated" date at the top of this page will always reflect the date of the most recent version.
10. Contact Us
Questions about cookies?
Invasystems Pvt Ltd
[Address], Pune, Maharashtra — [PIN CODE], India
Email: privacy@invasystems.com
You can also update your cookie preferences at any time via Settings → Privacy & Cookies within the FieldDNA app.