Last updated: 19 Aug 2026

Cookie Policy — CargoScreen

Controller: social.tech SIA · Reģ.nr. 40203514705 · Augusta Dombrovska iela 75 k-2-8, Rīga, LV-1015, Latvia Service: CargoScreen (cargoscreen.eu) Version: 1.0 · Effective date: 19 Aug 2026 Binding language: Latvian. This English text is the official translation; the Latvian version prevails.


1. What are cookies

Cookies are small text files stored on your device when you visit a website, and similar technologies (local storage, pixels, SDKs) that store or access information on your device. They let a service function, remember your choices, and (with your consent) measure usage or support marketing.

2. Legal framework and our approach

2.1. Setting or reading non-essential cookies requires your prior, informed, freely given, specific, and unambiguous consent, in accordance with the ePrivacy Directive (2002/58/EC, as transposed in Latvia) and the consent standard of the GDPR. Strictly necessary cookies do not require consent.

2.2. We ask for consent through a cookie banner before any non-essential cookie is set. You can accept all, reject all, or choose by category, and you can change your choice at any time (clause 6).

2.3. Upcoming change (for information). The EU withdrew the proposed ePrivacy Regulation on 11 February 2026, and the "Digital Omnibus" package proposes to move cookie rules into the GDPR (proposed Articles 88a/88b), including single-click reject with equal prominence, a limit on re-prompting after refusal, and recognition of machine-readable browser consent signals. This is a proposal and not yet law; the current framework in clause 2.1 applies. We will update this Policy if and when the reform takes effect.

3. Categories of cookies we use

  • Strictly necessary (no consent required): needed to run the Service — authentication/session, security, load balancing, and storing your cookie-consent choice itself.
  • Functional (consent required unless strictly necessary): remember preferences such as language.
  • Analytics/performance (consent required): help us understand usage to improve the Service. We prefer first-party, privacy-friendly, aggregated measurement.
  • Marketing (consent required): {only if used} support campaigns and attribution.

4. Cookies we set — details

Fill from an actual scan. Example structure below; remove rows that don't apply and add the real ones.

NameProviderCategoryPurposeDuration
{session/auth cookie}first-party (Supabase/GoTrue)Strictly necessarykeep you logged in; securitysession / {N} days
{consent cookie}first-partyStrictly necessarystore your cookie choices{6–12} months
{csrf/security}first-partyStrictly necessaryprotect against request forgerysession
Stripe cookiesStripeStrictly necessary (payment) / fraud preventionprocess payments securely, fraud detection during checkoutper Stripe
{language pref}first-partyFunctionalremember interface language{N} months
{analytics, if any}{provider}Analyticsaggregated usage measurement{N} months
{marketing, if any}{provider}Marketing{purpose}{N} months

4.1. Strictly necessary cookies are set on load. All other categories are set only after you consent.

5. How our consent banner works

Our consent mechanism is designed to meet current standards and the direction of the Digital Omnibus:

  • Prior consent: non-essential cookies fire only after you opt in.
  • Equal prominence: "Reject all" is as easy and visible as "Accept all"; rejecting takes no more clicks than accepting.
  • No dark patterns: no pre-ticked boxes, no misleading colours or wording, no nagging designed to wear you down.
  • Granular: you can consent per category.
  • Withdrawable: you can change or withdraw consent at any time via the "Cookie settings" link (clause 6), as easily as you gave it.
  • Re-prompting limit: after you refuse, we will not re-ask for the same consent for at least {6} months, unless our cookies change materially or you clear your cookies.
  • Browser signals: where technically supported, we honour machine-readable consent/opt-out signals (e.g. Global Privacy Control).

5.1. Record of consent (consent_log). We record your consent choices (categories, timestamp, and the banner version shown) to be able to demonstrate consent as required by the GDPR. This record is itself stored via a strictly necessary mechanism.

6. Managing and withdrawing consent

  • Use the "Cookie settings" link in the footer of cargoscreen.eu at any time to review and change your choices.
  • You can also control cookies through your browser settings (block or delete cookies). Blocking strictly necessary cookies may break parts of the Service.
  • Withdrawing consent does not affect cookies already read while consent was valid, but stops further non-essential processing.

7. Third-party cookies and transfers

Some cookies are set by third parties (e.g. Stripe for payments). Their processing is governed by their own policies. Where any consented cookie involves a transfer of personal data outside the EEA, the safeguards described in the Privacy Policy (clause 7 there) apply.

8. Relationship to other policies

This Cookie Policy forms part of, and should be read with, our Privacy Policy ({URL_PRIVACY_POLICY}). Definitions and your data-subject rights are set out there.

9. Changes

We may update this Policy to reflect changes in the cookies we use or in the law (notably the Digital Omnibus reform). The current version and date are shown at the top.

10. Contact

social.tech SIA · privacy@cargoscreen.eu · Augusta Dombrovska iela 75 k-2-8, Rīga, LV-1015, Latvia


Changelog

VersionDateChange
1.019 Aug 2026Initial version.