Cookie Policy
Snap Matrix · Cookie Policy · v1.0 · effective 29 July 2026
| Field | Value |
| Operator | Trexadoc OÜ |
| Company number | 17367549 |
| Registered office | Harju maakond, Tallinn, Kesklinna linnaosa, Pärnu mnt 20, 10141, Estonia |
| Trading name / brand | Snap Matrix |
| Website | https://snap-matrix.com |
| Contact email | info@snap-matrix.com |
| Support / complaints | info@snap-matrix.com |
| Governing law | Laws of the Republic of Estonia |
| Document version | v1.0 |
| Effective date | 29 July 2026 |
| Important: Strictly necessary cookies and similar technologies support security, login, checkout and consent choices. Analytics, preference and marketing technologies are used only after the consent required by applicable law and can be changed through the cookie settings. |
1. Introduction and scope
1.1 This Cookie Policy describes how Trexadoc OÜ uses cookies, local storage, pixels, software development kit functions and comparable technologies on snap-matrix.com. It applies to the public website, Account pages and checkout transitions controlled by Snap Matrix.
1.2 Some payment, authentication or embedded providers set technologies under their own responsibility. Where their technology is presented through our website, we seek to classify it accurately and provide the consent controls required by law.
1.3 The Privacy Policy explains the broader processing of personal data, including lawful bases, recipients, transfers, retention and rights. This policy focuses on information stored on, or read from, a user’s device.
2. What cookies and similar technologies are
2.1 A cookie is a small text record stored by a browser and returned to a website on later requests. A session cookie normally expires when the browser session ends; a persistent cookie remains until its stated expiry or earlier deletion.
2.2 Local storage can retain settings or identifiers without using a conventional cookie. Pixels and event tags can report that a page or message was viewed. Server-side identifiers can connect browser events to an Account or Order without exposing full payment credentials.
2.3 First-party technologies are set for Snap Matrix. Third-party technologies are provided by another organisation, for example a Payment Provider, analytics vendor or security service. Classification depends on purpose rather than the technical label alone.
3. Why we use cookies
3.1 Essential technologies establish secure sessions, authenticate users, protect forms, balance traffic, remember consent choices, preserve checkout state and detect malicious requests. Disabling them may prevent login, purchase, generation or support functions.
3.2 Preference technologies remember interface choices such as language, display or recent settings. Analytics technologies help us understand aggregate usage, errors and performance. Marketing technologies measure campaigns or support relevant advertising where enabled.
3.3 We do not use a non-essential purpose merely because a technology is convenient. Each technology is assessed by its actual function, duration, provider and whether information is combined across services.
4. Cookie categories
4.1 Snap Matrix groups technologies into strictly necessary, functional or preference, analytics or performance, and marketing categories. A technology that serves several purposes is classified according to the purpose that creates the greatest privacy impact.
4.2 Strictly necessary technologies do not require consent where they are genuinely required to provide a function requested by the user or transmit a communication. The remaining categories are disabled until valid consent is available in jurisdictions requiring prior consent.
4.3 The effect of rejecting a category is described below. Rejection does not reduce the price of a Token Pack and does not remove essential security controls.
| Category | Purpose | Consent required | Effect if disabled |
| Strictly necessary | Security, authentication, checkout continuity, load management and consent records | No, where legally exempt | Login, payment, generation or preference storage may fail |
| Functional / preferences | Remember optional interface and user-experience choices | Yes where not strictly requested | Choices may reset and some convenience features may not persist |
| Analytics / performance | Measure visits, failures, speed and aggregate feature use | Yes in the EEA | Core service remains available; product insight is less complete |
| Marketing | Measure campaigns, attribution and permitted advertising audiences | Yes | Core service remains available; campaign measurement is reduced |
5. Lawful basis and consent
5.1 For non-essential device access in the European Economic Area, the legal basis is consent under applicable electronic-communications rules. Any related personal-data processing also relies on consent unless another basis lawfully applies to a separate operation.
5.2 The consent interface allows acceptance of all optional categories or a more granular choice. Consent must be freely given, specific, informed and indicated by a clear action; continuing to browse is not treated as consent.
5.3 You may withdraw consent as easily as it was given. Withdrawal applies prospectively. A minimal consent record may be retained to demonstrate the choice and avoid repeatedly presenting the banner.
5.4 Essential security and session technologies remain active after optional consent is rejected because they are necessary to provide the website, Account and checkout functions requested.
6. Cookie inventory and technology functions
6.1 The inventory uses functional names because a provider may rotate the exact technical identifier while preserving the same purpose. Material changes to provider, purpose, duration or data sharing require an inventory update and, where relevant, renewed consent.
6.2 Durations are maximum ordinary periods. A browser setting, Account logout, provider security event or earlier deletion may shorten them. A third-party provider may maintain its own records after the browser identifier expires under its separate notice.
| Cookie / technology | Type | Purpose | Duration | Provider |
| Secure session identifier | Strictly necessary | Maintain an authenticated or anonymous session and prevent session substitution | Session | Snap Matrix |
| Cross-site request protection token | Strictly necessary | Verify that form and Account actions originate from the active session | Session | Snap Matrix |
| Authentication refresh record | Strictly necessary | Keep an authorised user signed in on the selected device | Up to 30 days | Snap Matrix / authentication provider |
| Consent preference record | Strictly necessary | Store accepted and rejected cookie categories and policy version | 6 months | Snap Matrix / consent manager |
| Checkout continuity identifier | Strictly necessary | Connect the Order to the secure payment session and prevent duplicate submission | Session to 24 hours | Snap Matrix / Payment Provider |
| Fraud and device risk identifier | Strictly necessary | Detect automated abuse, stolen instruments and anomalous payment attempts | Up to 13 months | Payment or fraud-prevention provider |
| Interface preference storage | Functional / preferences | Remember optional language, display or generation-interface choices | 6 months | Snap Matrix |
| Aggregate analytics identifier | Analytics / performance | Measure visits, feature use, errors and performance after consent | Up to 13 months | Analytics provider |
| Campaign attribution tag | Marketing | Measure whether a permitted campaign led to a visit or purchase | Up to 90 days | Advertising or analytics provider |
| Marketing consent signal | Marketing | Transmit the user’s allowed advertising choice to configured tags | 6 months | Snap Matrix / consent manager |
7. Third-party cookies and embedded services
7.1 A Payment Provider may set essential security or authentication technologies when the checkout opens. Those technologies can be necessary to prevent fraud, perform strong customer authentication and return the payment result.
7.2 An analytics or advertising provider receives events only where the relevant optional category is enabled. We configure data minimisation, limited retention and restricted use where the provider offers those controls.
7.3 An embedded feature may communicate with its provider when loaded. Where loading would place a non-essential identifier or transmit data for optional purposes, the feature is blocked until the appropriate consent is recorded.
7.4 Third-party providers may change technical identifiers. The inventory is updated based on deployment checks, provider documentation and consent-manager scans rather than relying on the identifier name alone.
8. Managing preferences
8.1 Use the “Cookie Settings” control on the website to review or change optional categories. The new choice applies to future use on that browser and device.
8.2 Browser controls can block or delete cookies, clear local storage and restrict tracking. Blocking all technologies may prevent secure login, checkout or continuity of the generation interface because the browser cannot maintain a valid session.
8.3 Choices are device- and browser-specific unless an Account setting synchronises them. Clearing storage, using private browsing or changing browsers may require a new selection.
8.4 To stop marketing email, use the unsubscribe control in the message. Cookie withdrawal and email-marketing withdrawal are separate because they concern different channels.
9. Retention and inventory governance
9.1 Each technology has an operational owner, purpose, category, provider and maximum duration. A new non-essential technology is not released to production until it is classified, documented and connected to the correct consent state.
9.2 The inventory is checked after material website releases, changes to payment or analytics providers, consent complaints, and at least quarterly. Technologies that are obsolete, misclassified or longer-lived than necessary are removed or reconfigured.
9.3 Consent records are retained for five years after withdrawal or replacement to demonstrate the notice and choice presented. This record is separate from the browser cookie, which ordinarily expires after six months.
9.4 Security logs derived from essential technologies may be retained for up to 13 months, while transaction evidence may follow the longer accounting and dispute periods described in the Privacy Policy.
10. Do-Not-Track and browser signals
10.1 Some browsers send a Do-Not-Track signal, but no uniform legal or technical standard defines the response. Snap Matrix therefore relies on the consent interface and legally recognised opt-out signals rather than treating every Do-Not-Track header identically.
10.2 Where a legally binding browser signal applies, we use reasonable measures to honour it for the relevant processing. A signal does not disable technologies required for security, authentication or a requested checkout.
10.3 Users can still select preferences directly. A direct setting may be used to clarify the user’s choice where the browser signal is ambiguous or unsupported.
11. Children and age
11.1 The Service is limited to people aged 18 or older. We do not use optional advertising technologies to profile children through Snap Matrix.
11.2 If we learn that an underage user provided optional consent, we will treat the consent as invalid, disable the relevant processing and take appropriate Account action.
11.3 A parent or guardian who believes a child used the website should contact support with enough information to investigate without sending unnecessary identity documents.
12. International data flows
12.1 A provider may process cookie-derived data outside the European Economic Area. Where personal data is transferred, we use an adequacy decision, standard contractual clauses or another valid transfer safeguard.
12.2 The risk assessment considers the provider, destination, data fields, purpose, retention and available controls. Optional providers are not activated merely because a transfer mechanism exists; the separate requirement for consent still applies.
12.3 Further information about transfer safeguards and privacy rights appears in the Privacy Policy.
13. Changes to this policy
13.1 We update this policy when technologies, providers, categories, durations, legal requirements or consent controls materially change. The version line identifies the current policy.
13.2 A material expansion of optional processing requires a refreshed notice and, where necessary, renewed consent. A purely technical identifier change with the same provider, purpose and duration may be reflected in the inventory without resetting consent.
13.3 The policy version linked to a consent choice governs the record of that choice. Earlier consent records remain linked to the version shown when the choice was made.
14. Contact
14.1 Questions about technologies or consent may be sent to info@snap-matrix.com. Include the browser, device, approximate time and the technology or behaviour observed where the request concerns a technical issue.
14.2 Privacy rights concerning cookie-derived personal data are handled under the Privacy Policy. You may also complain to the Estonian Data Protection Inspectorate or another competent supervisory authority.
15. Operational Maintenance Checklist
15.1 Release control: identify every new script, tag, software development kit or embedded service before deployment; document its provider, purpose, data fields, category and maximum duration.
15.2 Consent control: verify that optional tags remain blocked before consent, that rejecting all works, that withdrawal stops future activation, and that essential functions continue without optional categories.
15.3 Inventory control: compare browser storage, network calls, provider documentation and consent-manager scans; investigate unknown identifiers and remove obsolete entries.
15.4 Duration control: test whether expiry settings match this policy and whether server-side data follows the Privacy Policy rather than silently continuing after browser expiry.
15.5 Provider control: reassess contracts, international transfers, independent-controller roles and sub-processors after a provider change or material update.
15.6 Evidence control: preserve the banner text, category design, policy version and consent event needed to demonstrate the choice presented, without retaining more device data than necessary.
Snap Matrix · Cookie Policy · v1.0 · effective 29 July 2026. This version applies from the effective date and supersedes earlier versions for future use.