Cookie policy
1. What cookies and similar technologies are
Cookies are small text files stored on your device. Similar technologies include local storage keys, session tokens, pixels, and software development kits (SDKs) that recognize browsers or devices over time. Together we refer to them as “cookies” unless a distinction matters.
2. Why we use them
We use cookies to:
- Maintain secure sessions and authenticate users;
- Remember preferences (language, cookie consent choices);
- Measure site performance and diagnose errors;
- Understand aggregated traffic patterns to improve content;
- Mitigate abuse (rate limiting, bot detection).
3. Categories
3.1 Strictly necessary
These cookies are essential for core functionality—for example, maintaining your logged-in session in Fundolar Central, enforcing CSRF protections, routing requests correctly, or honoring security settings. Because they are necessary to provide the service you requested, many jurisdictions do not require consent, though you can still block cookies through browser settings at the cost of functionality.
3.2 Functional
Functional cookies remember choices such as UI preferences or dismissal of informational banners. They improve usability but are not strictly required for bare operation.
3.3 Analytics
If enabled, analytics cookies help us understand how visitors navigate pages and whether documentation paths succeed. Where required, we will solicit consent before setting non-essential analytics cookies and load analytics scripts only after acceptance.
3.4 Marketing
Fundolar does not currently use marketing or retargeting cookies on our corporate websites. If we introduce advertising cookies in the future, we will update this policy and obtain consent where required before setting them.
4. Typical cookies (examples)
Exact names evolve with deployments. Representative examples include:
- Session identifiers — tie your browser to an authenticated Fundolar Central session; typically session-scoped or short-lived;
- Consent records — remember whether you accepted optional cookies;
- Load-balancing or routing tokens — improve reliability across infrastructure;
- Analytics identifiers — pseudonymous IDs used only if analytics are enabled.
5. Third-party cookies
Fundolar Central and our websites may load scripts from infrastructure, security, and payment partners that set their own cookies or storage keys necessary to operate the Services. Embedded third-party content (such as videos or maps) may set additional cookies outside Fundolar’s direct control; we limit such embeds on checkout and authentication surfaces.
6. Retention
Session cookies expire when you close your browser. Persistent cookies are retained only as long as needed for their purpose:
- Authentication and security tokens — for the duration of your session or up to 30 days where “remember me” is enabled;
- Functional preferences — up to 12 months;
- Consent records — up to 24 months where we must demonstrate compliance with privacy regulations;
- Analytics identifiers — up to 13 months where analytics cookies are enabled and consented to.
7. Managing preferences
You can:
- Use in-product cookie banners or preference centers where provided;
- Adjust browser settings to block or delete cookies;
- Use reputable tracker-blocking extensions (may impair functionality).
Because strictly necessary cookies underpin authentication, blocking all cookies may prevent sign-in to Fundolar Central.
8. Do Not Track
There is no uniform global standard for “Do Not Track” browser signals. Fundolar treats granular consent choices presented through our interfaces as authoritative where regulations require opt-in for non-essential processing.
9. Updates
When we introduce new cookies materially affecting privacy, we will refresh this policy and, where appropriate, re-seek consent.
10. More information
For personal information processing beyond cookies, see our Privacy policy. Questions about this Cookie Policy: info@fundolar.com.