General provisions
This Cookie Policy explains how NAVIA may use cookies, local storage, pixels, tags, mobile identifiers, SDKs, push tokens and similar technologies on the website, mobile application, payment pages and related services. This Policy applies together with the Privacy Policy and other NAVIA documents.
What technologies are covered
Cookies are small files or identifiers stored on the user's device. Similar technologies may include local storage, session storage, pixels, tags, software development kits, device identifiers, advertising identifiers, analytics identifiers and push-notification tokens.
Viewing a public page does not constitute consent to optional tracking.
Why NAVIA uses these technologies
NAVIA may use these technologies to operate the service, keep users logged in, protect accounts, remember preferences, process payments, measure performance, analyse usage, improve features, deliver notifications, support advertising and prevent fraud.
Each independent optional purpose must have an explained lawful basis.
Strictly necessary technologies
Strictly necessary technologies are required for login, authentication, security, payment flow, fraud prevention, user preferences that are essential for operation and technical functioning of the website or application. These technologies may be used without separate optional consent where permitted by law.
Optional advertising must not be labelled necessary to view an open page.
Functional technologies
Functional technologies help remember language, region, settings, user choices, interface preferences and other features that make NAVIA easier to use.
Necessity and the lawful basis depend on the function, the user’s request and applicable law.
Analytics technologies
Analytics technologies help NAVIA understand how users use the service, which features work, where errors occur and how the product may be improved. Depending on applicable law and settings, analytics may require consent or may rely on another lawful basis where permitted.
Where prior consent is required for optional identifiers it is requested before their use. Another basis is permitted only for processing that actually meets its requirements.
Advertising and marketing technologies
NAVIA may use advertising or marketing technologies to measure campaigns, show relevant offers, prevent repeated advertising, analyse conversion and improve marketing. Where required by law, NAVIA will request consent before using non-essential advertising technologies.
This is a separate permission: account creation, publication and a licence for a specific promotional material do not replace consent for optional advertising tracking.
Payment and anti-fraud technologies
Payment providers, app stores, Stripe or other payment partners may use cookies or similar technologies for payment processing, fraud prevention, authentication, chargeback handling and compliance. Such technologies may be governed by the relevant provider's own terms and privacy documents.
Mobile identifiers and SDKs
The NAVIA mobile application may use SDKs, device identifiers, app instance identifiers, crash reports, diagnostics and similar technologies to operate, secure and improve the application.
Users must be informed about actual third-party tools, purposes and necessary choices before the corresponding processing.
Push notifications
If the user enables push notifications, NAVIA may process push tokens and related device information to send service messages, security notices, product updates, reminders or optional marketing where permitted. The user may disable push notifications through device settings or app settings, if available.
Marketing messages require a separate permission where law requires it. Device push permission is not consent to use personal materials in advertising.
Consent and choice
Where required, NAVIA will request consent for non-essential cookies and similar technologies. The user may accept, reject or manage categories where the interface provides such options. Withdrawal of consent does not affect the lawfulness of processing based on consent before withdrawal.
Optional categories use separate understandable accept, refuse and manage choices, without preselected boxes or advertising required for registration or guest viewing. Withdrawal must be as easy as giving consent. Changing cookie choices does not automatically withdraw a licence for a specific promotional material; those permissions are managed separately.
Managing cookies and similar technologies
The user may manage cookies through the browser settings, cookie banner, privacy settings, device permissions or app settings where available. Blocking certain technologies may affect login, payments, security, preferences or other functions.
Refusing optional advertising technologies is not a basis for hiding open pages or deleting an account.
Third-party technologies
Third parties such as payment providers, analytics services, advertising partners, app stores or infrastructure providers may use their own technologies when the user interacts with NAVIA. NAVIA does not fully control third-party technologies outside NAVIA's reasonable control.
NAVIA is responsible for its integrations, while independent third-party actions outside its operations are not entirely under its control.
Do Not Sell/Share and similar rights
Users from California and other jurisdictions may have rights regarding sale, sharing, targeted advertising or use of sensitive personal information. NAVIA should provide required notices and choices where such laws apply and where NAVIA's practices fall within their scope.
Internet-publication consent does not permit the sale of personal data.
Changes to this Policy
NAVIA may update this Policy to reflect new technologies, providers, legal requirements or product changes.
A new purpose requiring consent is not automatically enabled by continued browsing.
Contacts
Questions about cookies and similar technologies may be sent to office@navia.land or info@navia.land.