Skip to main content
Rekaro
Om ossProduktResurserDemoPris
Rekaro

Procurement that is faster, clearer, and more traceable

En modern plattform för att matcha inköpare och leverantörer: RFQ, real-time kommunikation, notiser och AI med kontrollerade verktyg.

GovernanceReal-timeB2B matching
Product
  • Demo
  • Explore
  • AI assistant
  • Create RFQ
  • Settings
Company
  • About us
  • Why Rekaro
  • Security & governance
  • Security
Resources
  • FAQ
  • Our principles
  • Contact
Legal
  • Privacy
  • Cookiepolicy
  • Terms

Theme

Control platform theme and color mode globally from the footer.

Färgläge

Byt mellan en ljus arbetsyta och ett mörkare fokuserat läge.

© 2026 Rekaro
FAQDemoContactPrivacySecurityTerms

Cookie policy

Known storage keys and consent choices

This policy covers cookies, localStorage, and sessionStorage. Optional analytics and error reporting remain off until the user makes a choice.

Legal overviewAsk before a pilot
VERSION 0.1 - TECHNICAL DRAFT. The inventory must be verified in a clean browser before final approval.Version 0.1, 2026-07-30. Owner: [TODO human legal and privacy owner].

Necessary: consent choice

localStorage: rekaro_cookie_consent_v1. Contains version, status, selected categories, and choice time. Purpose: remember and enforce the choice. Retention: [TODO verification and decision].

Necessary: language and session

Language may be stored in a cookie and localStorage. Login may use a session hint and local authentication keys. Exact name, domain, lifetime, SameSite, Secure, HttpOnly, and necessity assessment: [TODO runtime inventory].

Optional: analytics

After analytics consent, localStorage may contain an anonymous id, attribution, and analytics session. Page view, route, referrer, and limited business context may be sent to Rekaro's backend. Retention and clearing after withdrawal: [TODO].

Optional: error reporting

After separate consent, technical errors, route, requestId, breadcrumbs, browser, and limited user context may be sent to Rekaro's backend. Free text, URLs, and console data may contain unexpected values and must not be described as fully masked.

Change or withdraw

Cookie settings remain available after the choice. The user can reject all optional processing or select analytics and error reporting separately. Clearing existing optional identifiers must be verified and documented: [TODO].

Runtime verification before final policy

  • Inventory cookies, localStorage, sessionStorage, and network requests before a choice
  • Repeat for reject, custom, accept, and withdrawal
  • Document name, provider, domain, data, purpose, and lifetime
  • Verify that optional traffic is blocked without consent
  • Test clearing and update the version
PTS cookie guidanceSwedish Electronic Communications Act