StuFlex legal
Cookie Notice
Necessary storage, first-party statistics and optional website analytics on StuFlex.
Version 1.0 · effective 9 November 2026
1. How we use these technologies
We use necessary storage for sign-in, security and requested features. We also use limited first-party statistics to understand website performance and business outcomes. Google Analytics and Microsoft Clarity are optional and start only after you accept analytics.
2. Necessary technologies
| Provider / item | Purpose | Typical duration |
|---|---|---|
| Firebase Authentication browser storage (Google) | Keep the user's requested sign-in state, refresh authentication securely and protect the account | Normally until sign-out, account deletion, browser-site-data removal or provider expiry |
StuFlex __session cookie | Maintain authorised Company-portal access | Seven days, or earlier sign-out/deletion |
calendar_oauth_google or calendar_oauth_microsoft | Bind a user-requested calendar authorisation response to the browser that started it and prevent request forgery | Ten minutes or completion of the connection |
Firebase App Check/reCAPTCHA browser storage, including _GRECAPTCHA and other provider security state (Google), when App Check is configured | Assess request risk, obtain an application-integrity token and prevent automated abuse of account and API functions | App Check tokens use the provider-configured lifetime (currently 30 minutes to seven days; one day by default) and are refreshed when needed; provider security state uses provider-controlled periods and may be removed earlier through browser-site-data controls |
| Firebase SDK integrity/heartbeat storage (Google) | Maintain security-token and SDK state needed for reliable authenticated service requests | Rotated or removed by the SDK, browser-site-data removal or account/service expiry |
These items are used for a requested account, connection or security function and are not switched on through an optional-marketing consent banner. App Check/reCAPTCHA is invoked when a protected service request needs application-integrity verification. Browser blocking may prevent login, calendar connection or portal functions.
3. Limited diagnostics
When configured, StuFlex uses Sentry for limited error monitoring. The browser configuration does not send default personal identifiers and has advertising tracking, session replay and client-side performance tracing switched off. It does not intentionally set a StuFlex advertising or tracking cookie; transient event or session identifiers may be used to diagnose an error. Server-side performance monitoring does not place information on the user's device. Diagnostic records are handled under the Privacy Notice and the applicable provider retention settings.
4. Optional analytics
With your analytics consent, Google Analytics 4 measures page visits, broad acquisition sources, engagement, clicks and form progress. Microsoft Clarity provides heatmaps and interaction recordings on selected public pages. Recordings may include signup and login screens, with strict masking of text and form inputs. Private accounts, workspaces, admin pages, documents and URLs containing query parameters or fragments are excluded from recordings. These services can process online identifiers, browser/device information and IP-related metadata; not setting cookies does not make a service anonymous.
| Provider / item | Purpose | Duration |
|---|---|---|
Google Analytics 4: _ga and _ga_* | Consented usage measurement and continuity. Advertising storage, advertising personalization, Google Signals and user-provided identifiers are disabled. | Configured cookie lifetime: up to 180 days; user/event data retention: two months. Standard aggregate reports can remain longer. |
Microsoft Clarity: _clck, _clsk and related provider storage | Consented interaction recordings, heatmaps and session continuity. Advertising consent remains denied. | Provider cookie periods vary, including a one-year identifier cookie and a one-day session cookie; StuFlex withdraws consent and removes accessible analytics cookies when your local choice expires or you reject analytics. |
Optional scripts stay blocked until acceptance. We use Google Basic Consent Mode: no pre-consent Google analytics pings. Clarity is also blocked before consent, including its cookieless recording mode. We do not send names, email addresses, passwords, document contents, authentication tokens, arbitrary URL parameters or form-field values as analytics properties.
5. Limited first-party statistics
Separately from optional providers, StuFlex counts approved page and workspace-screen views, entry pages, broad source categories, selected actions, form progress and rounded performance measurements. Page and screen-view totals include hour and broad device category; public-page totals also include approximate country. A local country database derives the country from the connection IP; the IP and full browser description are discarded before metric storage. These are pageview totals, not unique visitor counts or individual browsing histories. No persistent visitor ID or browser fingerprint is created. The measurement pipeline does not store IP addresses, full referrers, query strings, entered text or private page paths. Short-lived security limits protect the endpoint without creating an analytics identifier. Minimal count batches are kept in restricted EU logging storage for seven days and combined into daily aggregates; they are not session recordings. Backend-confirmed registrations, successful logins, daily active accounts (including restored sign-ins), applications, reviews and placement outcomes are counted from operational records. We also measure company login activity, first opens of introduced candidates and tracked email sends before email opt-out or account deletion. These account-linked operational records are separate from anonymous website measurement; no email-open tracking is used. Aggregate counts that cannot identify anyone can be retained longer.
This limited measurement is used to evaluate the service with no or only minor privacy impact under the Dutch limited-analytics exception. Where personal data is involved in transport or protection of the service, we rely on the relevant legitimate interests described in the Privacy Notice. Browser blocking can still make traffic counts incomplete.
6. Your choice
Choose “Accept analytics” or “Reject optional” in the banner. Both choices leave normal website access available. Inactivity, scrolling and closing a page do not grant consent. There is one optional analytics category, including the interaction recordings described above. You can change or withdraw your choice at any time using “Analytics preferences” in the footer or account settings. Withdrawal stops further optional collection; it does not make earlier lawful collection unlawful.
We remember only your choice, its policy version and the decision time in stuflex_analytics_consent for up to 180 days. This preference is not an analytics or advertising identifier. Blocking storage can prevent the choice from being remembered. A new choice may be requested when it expires or the purposes materially change.
7. Contact and further information
See the Privacy Notice for purposes, providers, international transfers, retention and your rights. You can also inspect/delete site data in your browser; removing necessary state may sign you out. Contact privacy@stuflex.nl with questions.