Stackie legal document
Stackie Cookie and Tracking Notice
- Document version
- 2026.07.28.1
- Document effective date
- 2026-07-28
Acceptance Evidence
- Acceptance mode
- Separate acceptance where used
- Manifest version
2026.06.20- Rendered document hash
d44d14819b4650f6eda6c40ede2807f2523d187d16ca9c4852878e0d81a03b5a- Public legal bundle hash
74145aaa10743e41788a22457265026c17e068b4009d61c102378f0c20945ade- Assent statement hash
75f16fee9a6ff220b085569c28c5065e9442660f0718c71073c579c9384f53a5- Acceptance metadata hash
f5e2aec7feb5fe5ad8dbf41d21b2172f0f5378429510bd974e4cee435f0ba4f5- Required acceptance surfaces
- None
- Available publication surfaces
- Stackie website, Stackie Cloud, Stackie app, embedded dashboard
- Separate acceptance surfaces
- Stackie website, Stackie Cloud, Stackie app, embedded dashboard
I acknowledge that Stackie made Stackie Cookie and Tracking Notice version 2026.07.28.1, effective 2026-07-28 available as the current cookie and tracking notice for the applicable Stackie surface, and any nonessential cookie or tracking consent is governed by the consent choice presented for that surface. I represent that I am acting for trade, business, professional, freelance, employment, or organizational development purposes and not for personal, household, or consumer use unless Stackie Ltd expressly permits that use in a signed agreement, checkout flow, or product-specific consumer schedule.
This Cookie and Tracking Notice explains how Stackie Ltd uses cookies, local storage, device identifiers, analytics identifiers, crash identifiers, chat identifiers, session replay identifiers, pixels, SDKs, and similar technologies on Stackie websites, applications, embedded dashboards, documentation, and cloud services.
Categories of Technologies
Stackie may use strictly necessary technologies for authentication, security, session continuity, fraud prevention, legal acceptance evidence, load balancing, service delivery, and user-selected settings. These technologies are required for the relevant service and cannot always be disabled without affecting functionality.
Stackie may use functional technologies to remember preferences, product settings, local dashboard state, region choices, and support interactions.
Stackie uses limited operational product use, device notification, security, and reliability data only as described in the current table below. Separate non-essential analytics, diagnostics, crash reporting, support desk, chat, session replay, newsletter, marketing, or campaign measurement technologies are not active unless the table marks the specific tool active.
Stackie will not deploy a non-essential tool merely because a category is described in this notice. Before activation, Stackie must update the tracking inventory, provider evidence, retention, minimization, masking, legal basis, consent or opt-out controls, and public disclosure posture required for that tool and jurisdiction.
Consent and Choices
Where law requires consent for non-essential cookies or similar technologies, Stackie will request consent before using them. Where law permits opt-out or legitimate-interest processing, Stackie will provide the required notice and choice. Users may change browser settings, device settings, or in-product choices where available.
Tools marked as not currently active are not used under this notice unless and until Stackie lawfully enables and discloses them through the tracking inventory, generated table, and applicable consent or opt-out controls.
Stackie applies required browser privacy-preference signal handling only for surfaces where that handling is implemented and legally required. Marketing emails include an unsubscribe mechanism where required.
Session Replay, Chat, and Crash Reporting
Session replay, customer chat, support desk tooling, and crash reporting can involve sensitive context if configured carelessly. Stackie may use these tools only when represented in the current inventory and configured with appropriate masking, minimization, retention, access controls, and consent or opt-out controls for the applicable jurisdiction and surface.
Third Parties
Approved third-party providers are listed in the Tracking Tool Register and Subprocessor List where applicable. A provider is not approved merely because a category is described in this notice.
Changes
Stackie may update this notice when technologies, consent-management tools, providers, purposes, retention, or legal requirements change. The table below is the current public summary of Stackie's tracked cookie, analytics, communications, and similar-technology practices.
Cookie and Tracking Table
Governed Tracking Data Categories
| Category | Current Status | Purpose | Lawful Basis | Retention |
|---|---|---|---|---|
| product usage data | currently active | service operation and product improvement | legitimate interests | kept for a limited analytics period, then aggregated or deleted |
| device notification data | currently active | device linking, notifications, and security | contract necessity | kept while the device is registered and then for a limited security audit period |
| behavioural analytics data | planned or available only after activation | product improvement, support, and debugging | consent | kept for a short review period, then deleted |
| marketing communication data | planned or available only after activation | marketing emails and newsletters | consent | kept while subscribed, then limited suppression records are kept to honor opt-outs |
Tracking Tool Register
| Category | Status | Technology/Party | Storage or Identifier Names | Technology Description | Purpose | Consent | Retention | Storage Duration |
|---|---|---|---|---|---|---|---|---|
| analytics | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | No cookie, SDK, local storage, or similar tracking identifier is currently deployed for this tool. | Product analytics and product improvement. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
| marketing email | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | No cookie, SDK, local storage, or similar tracking identifier is currently deployed for this tool. | Marketing emails and lifecycle campaigns. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
| support desk | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | No cookie, SDK, local storage, or similar tracking identifier is currently deployed for this tool. | Support requests, troubleshooting, and incident follow-up. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
| crash reporting | In use | Third-party | No cookie, SDK, local storage, or similar identifier currently deployed | Sentry receives minimized technical-error events on approved Stackie surfaces. No Sentry cookie, SDK identity, local-storage identifier, session-storage identifier, replay token, feedback, attachment, profiling, original source-code upload, or AI-analysis feature is used. Separately disclosed operational diagnostics may use private sanitized JavaScript source maps without original source content. | Detect, diagnose and remediate technical faults and information-security failures on Stackie surfaces using minimised technical-error events. | notice and opt-out | Active searchable technical-error events expire within a maximum of 30 days; provider backup and deletion follow a separately documented lifecycle. | Active searchable technical-error events are available for up to 30 days; provider backup and deletion follow a separate lifecycle. |
| operational diagnostics | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | Sentry may receive minimized operational telemetry and private diagnostic build artifacts needed to detect, diagnose, measure and remediate faults. This category includes bounded technical-error, custom trace, coarse metric, aggregate release-health, runtime check-in, live uptime and exact JavaScript release/source-map data. The private processing register enumerates every retained and derived field. Stackie excludes user/customer identity, customer content, raw requests or responses, free text, logs, replay, screenshots, attachments, profiling, User Feedback, original source content, native debug symbols, public source maps and Seer or AI analysis. | Detect, diagnose, measure and remediate technical faults and information-security failures using minimized operational telemetry and private diagnostic build artifacts. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
| session replay | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | No cookie, SDK, local storage, or similar tracking identifier is currently deployed for this tool. | Hosted app and dashboard troubleshooting and UX diagnostics. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
| customer chat | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | No cookie, SDK, local storage, or similar tracking identifier is currently deployed for this tool. | Customer support chat and troubleshooting. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
| newsletters | Not currently active; will not be used unless lawfully enabled and disclosed | Not active | No cookie, SDK, local storage, or similar identifier currently deployed | No cookie, SDK, local storage, or similar tracking identifier is currently deployed for this tool. | Product newsletters and launch announcements. | Not used unless activated after notice and consent where required | Not applicable while inactive | Not applicable while inactive |
Jurisdiction Consent Posture
| Jurisdiction | Launch Availability | Cookie Consent | Marketing Email | GPC Required | Unsubscribe Required |
|---|---|---|---|---|---|
| United Kingdom | currently available for the Stackie surface covered by this notice | opt-in consent | soft opt-in where lawful | where implemented and legally required | yes |
| European Union and EEA | not offered through Stackie's initial self-serve launch in this jurisdiction; future availability requires separate review | opt-in consent | opt-in consent | where implemented and legally required | yes |
| United States baseline with state privacy overlays | currently available for the Stackie surface covered by this notice | notice and opt-out | opt-out | where implemented and legally required | yes |