Strictly necessary
Required for authentication, security, sessions, forms, and storing your privacy choices.
Cookie Policy
This Cookie Policy explains how InnOneWeb OÜ, doing business as FieldCosts (“FieldCosts,” “we,” “us,” or “our”), uses cookies, local storage, software development kits, pixels, and similar technologies on the FieldCosts websites and applications.
1. What these technologies are
Cookies are small text files stored on a browser or device.
Similar technologies include:
- local storage;
- session storage;
- mobile SDK identifiers;
- pixels;
- tags;
- device identifiers;
- server-side event identifiers.
Some technologies are necessary for the Service to function. Others are used only with consent where required.
2. Categories
2.1. Strictly necessary
These technologies are required for:
- login and authentication;
- session continuity;
- account and workspace security;
- fraud and abuse prevention;
- load balancing;
- saving privacy choices;
- essential forms and navigation.
They cannot generally be disabled through the consent banner because the requested Service cannot operate without them.
2.2. Functional
These technologies remember optional preferences such as:
- interface choices;
- language;
- display preferences;
- non-essential personalization.
2.3. Analytics
These technologies help us understand:
- pages and features used;
- navigation patterns;
- performance;
- errors;
- aggregate usage trends.
Analytics must not load before consent where consent is legally required.
FieldCosts limits optional analytics to the public marketing pages listed in the website navigation. Analytics is not loaded in authenticated customer workspaces, platform administration, login, registration, support, or legal-policy pages.
2.4. Marketing
These technologies may be used to:
- measure advertising campaigns;
- create or use advertising audiences;
- recognize a browser across sites;
- support targeted or cross-context behavioral advertising.
FieldCosts does not currently use advertising or cross-context behavioral marketing technologies. This category remains disabled.
3. Current technology inventory
| Name | Provider | Category | Purpose | Data | Duration | First/third party |
|---|---|---|---|---|---|---|
| PHPSESSID | FieldCosts | Necessary | Authenticated session | Random session ID | Session | First party |
| fieldcosts_consent | FieldCosts | Necessary | Stores privacy choices | Consent categories, version, timestamp, GPC state | 12 months | First party local storage |
| fc_analytics_sid | FieldCosts | Analytics | Counts a consented public marketing visit | Random per-tab session ID | Browser tab session | First party session storage |
| fc_analytics_token | FieldCosts | Analytics | Prevents another sender from adding events to the same analytics session | Random per-tab session secret | Browser tab session | First party session storage |
| _ga | Google Analytics | Analytics | Distinguishes consented marketing-site visitors | Pseudonymous ID | Up to 2 years | Third party |
| _ga_G-PYNPLHWXJY | Google Analytics | Analytics | Maintains consented analytics session state | Pseudonymous ID and session state | Up to 2 years | Third party |
The FieldCosts first-party tracker records only the marketing page path, a referring hostname, validated campaign labels, page views, and explicitly labelled CTA or conversion events. It does not collect element text, form values, full link destinations, cursor coordinates, screen replay, authenticated workspace content, full IP addresses, or full user-agent strings.
4. Consent
Where required, FieldCosts will:
- block non-essential technologies before consent;
- provide equally accessible options to accept or reject non-essential technologies;
- allow granular category choices;
- avoid pre-selected non-essential categories;
- record the consent version, timestamp, and selected categories;
- make withdrawal as easy as giving consent; and
- request consent again when purposes or vendors materially change.
Consent is not required for storage or access that is strictly necessary to provide a service explicitly requested by the user.
5. Managing choices
Users can reopen the consent panel by selecting “Cookie settings” in the website footer.
Browser settings may also be used to block or delete cookies. Blocking strictly necessary cookies may prevent account login or Service functionality.
6. Global Privacy Control and similar signals
Where legally required, FieldCosts will recognize supported opt-out preference signals such as Global Privacy Control for sale, sharing, or targeted advertising.
A Global Privacy Control signal is not automatically treated as consent to analytics.
7. Mobile applications
The current FieldCosts mobile applications store authentication state needed to keep a user signed in and use operating-system permissions for camera, files, and feature operation. They do not currently include optional advertising or product-analytics SDKs. App Store and Google Play disclosures are reviewed when the mobile SDK inventory changes.
8. Changes
We may update this Policy when technologies, providers, purposes, or laws change.
9. Contact
Privacy email: support@fieldcosts.com Registered address: Sakala 7-2, 10141 Tallinn, Estonia