Back to legal center

ELVOAQ Cookie Policy

Effective Date: July 1, 2026

Last Updated: July 1, 2026

Operator: Lukas Rajnic, trading as ELVOAQ

Legal Form: Sole trader, a natural person conducting business under the law of the Slovak Republic

Country of Establishment: Slovak Republic

VAT Number: Not registered for VAT (no VAT identification number exists)

Privacy Contact: privacy@elvoaq.com

Legal Contact: legal@elvoaq.com

Support Contact: support@elvoaq.com

Website: www.elvoaq.com

1. Introduction

This Cookie Policy explains how ELVOAQ uses cookies, local storage, session storage, pixels, tags, software identifiers, authentication tokens, consent records, server logs, security technologies, and similar technologies in connection with the ELVOAQ website, platform, digital vault, asset management tools, document management tools, controlled sharing features, account systems, subscriptions, payment flows, support tools, trial access, demo environments, AI-assisted features, and related products and services.

ELVOAQ is a brand operated by Lukas Rajnic, a natural person conducting business as a sole trader established in the Slovak Republic. The operator is not registered for value added tax and has no VAT identification number.

ELVOAQ is a privacy-first platform designed for managing valuable assets, proof documents, sensitive information, private records, ownership information, secure workflows, and controlled digital access.

Because ELVOAQ may be used to organize confidential asset records, proof documents, warranties, certificates, receipts, contracts, private notes, family records, business information, and other sensitive data, we aim to use cookies and similar technologies in a controlled, transparent, and security-conscious manner.

This Cookie Policy should be read together with the ELVOAQ Privacy Policy, Terms of Use, Refund Policy, subscription terms, and any other legal documents made available by ELVOAQ.

2. Purpose of This Cookie Policy

This Cookie Policy explains:

1. what cookies and similar technologies are;

2. why ELVOAQ uses them;

3. which categories of cookies may be used;

4. which cookies are strictly necessary;

5. which cookies may be optional;

6. how consent is requested and stored;

7. how users can manage cookie preferences;

8. how payment, support, and security cookies may work;

9. how cookies may support account login and controlled sharing;

10. how ELVOAQ handles analytics and retargeting;

11. how cookie-related data may be processed;

12. how long cookies may remain on a device;

13. how users may withdraw consent;

14. how this Cookie Policy may be updated.

This Cookie Policy applies to all visitors, users, subscribers, customers, trial users, demo users, administrators, invited users, business users, organizational users, and any other person who accesses or uses ELVOAQ through a browser, application, device, or compatible interface.

3. What Are Cookies?

Cookies are small text files placed on your device when you visit a website or use an online service.

Cookies may allow a website or platform to:

1. recognize your browser;

2. keep you logged in;

3. secure your account;

4. remember preferences;

5. store consent choices;

6. support payment flows;

7. prevent fraud;

8. measure technical performance;

9. detect errors;

10. support platform functionality.

Cookies may be set directly by ELVOAQ or by third-party providers used by ELVOAQ.

Cookies can be:

1. session cookies, which are deleted when you close your browser;

2. persistent cookies, which remain on your device for a defined period or until deleted;

3. first-party cookies, which are set by ELVOAQ;

4. third-party cookies, which are set by external providers;

5. strictly necessary cookies, which are required for the website or platform to work;

6. functional cookies, which remember preferences or improve usability;

7. security cookies, which protect accounts and systems;

8. payment cookies, which support checkout and fraud prevention;

9. optional cookies, which may require consent depending on their purpose and applicable law.

4. Similar Technologies

In this Cookie Policy, the word “cookies” also includes similar technologies unless the context requires otherwise.

Similar technologies may include:

1. local storage;

2. session storage;

3. pixels;

4. tracking tags;

5. device identifiers;

6. browser identifiers;

7. authentication tokens;

8. software development kits;

9. consent records;

10. embedded scripts;

11. security tokens;

12. server logs;

13. error monitoring technologies;

14. payment security technologies;

15. anti-fraud technologies;

16. support widget identifiers;

17. controlled sharing access tokens.

These technologies may store or process information on your device or in our systems to support ELVOAQ functionality, security, payments, support, and legal compliance.

5. Why ELVOAQ Uses Cookies

ELVOAQ may use cookies and similar technologies for the following purposes:

1. operating the website;

2. operating the logged-in platform;

3. authenticating users;

4. keeping users logged in;

5. protecting account sessions;

6. preventing unauthorized access;

7. preventing fraud and abuse;

8. storing cookie preferences;

9. remembering interface preferences;

10. supporting secure payment flows;

11. supporting customer support tools;

12. supporting controlled sharing;

13. protecting shared access links;

14. maintaining workspace access;

15. improving platform reliability;

16. detecting technical errors;

17. securing uploads and downloads;

18. supporting demo and trial access;

19. supporting AI-assisted workflow sessions;

20. complying with legal obligations;

21. enforcing the Terms of Use;

22. protecting ELVOAQ, users, and third parties.

ELVOAQ does not use cookies to sell private vault content.

ELVOAQ does not use cookies to turn private asset records, uploaded documents, ownership notes, certificates, warranties, receipts, contracts, or sensitive Customer Data into advertising inventory.

ELVOAQ does not currently use analytics tracking according to the current platform configuration.

ELVOAQ does not currently use retargeting advertising according to the current platform configuration.

6. Legal Framework

ELVOAQ is operated from the Slovak Republic. Slovak and European Union data protection and electronic communications rules may apply to the use of cookies and similar technologies.

Depending on the location of a visitor or user, EU/EEA, UK, or other cookie and privacy rules may also apply.

In general:

1. strictly necessary cookies may be used because they are required to provide the website or platform functionality requested by the user;

2. optional cookies may require user consent depending on their purpose and the applicable law;

3. users should receive clear and transparent information about cookie use;

4. users should be able to manage preferences where optional cookies are used;

5. consent should be freely given, specific, informed, and revocable where required;

6. private or sensitive customer content should not be used for hidden tracking or advertising.

Where required by applicable law, ELVOAQ will request consent before placing optional cookies or similar technologies.

If ELVOAQ later introduces analytics, marketing, advertising, retargeting, or high-risk profiling cookies, this Cookie Policy and the cookie banner should be updated before or at the time those technologies are deployed.

7. Cookie Consent Banner

ELVOAQ uses a cookie banner with options including Accept All and Customize.

The cookie banner should allow users to:

1. accept all optional cookies;

2. customize cookie preferences;

3. understand the categories of cookies used;

4. manage optional cookie choices;

5. access the Cookie Policy;

6. access the Privacy Policy;

7. change preferences later where technically available.

For a stronger compliance and trust standard, ELVOAQ should also consider offering a clear Reject Non-Essential option directly on the first banner layer, especially for EU/EEA users.

Optional cookies should not be activated before valid consent where consent is legally required.

Strictly necessary cookies may be used without consent because they are required to operate the requested service.

8. Cookie Categories Used by ELVOAQ

ELVOAQ may use the following cookie categories:

1. strictly necessary cookies;

2. security cookies;

3. authentication cookies;

4. session cookies;

5. consent preference cookies;

6. functional cookies;

7. payment-related cookies;

8. support-related cookies;

9. controlled sharing cookies;

10. demo and trial access cookies;

11. AI workflow support cookies;

12. technical logging and error support technologies.

ELVOAQ currently does not use analytics tracking cookies according to the provided configuration.

ELVOAQ currently does not use retargeting advertising cookies according to the provided configuration.

ELVOAQ currently does not use marketing cookies for retargeting or behavioral advertising according to the provided configuration.

9. Strictly Necessary Cookies

Strictly necessary cookies are required for the ELVOAQ website or platform to function properly.

These cookies may support:

1. basic website operation;

2. login functionality;

3. authentication;

4. secure sessions;

5. account access;

6. workspace access;

7. form submission;

8. fraud prevention;

9. cookie consent storage;

10. security protection;

11. payment flow security;

12. load balancing;

13. access control;

14. protection against unauthorized requests;

15. controlled sharing access;

16. system stability.

Without strictly necessary cookies, ELVOAQ may not function correctly.

Strictly necessary cookies generally do not require consent, but they are described in this Cookie Policy for transparency.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Authentication cookie | Keeps the user securely logged in | Session or limited persistent period | No |

| Session cookie | Maintains active session state | Session | No |

| Security token | Helps prevent unauthorized requests | Session or limited persistent period | No |

| Consent preference cookie | Remembers cookie choices | 6 to 12 months | No |

| Load balancing cookie | Supports stable platform delivery | Session | No |

| Checkout security cookie | Supports secure payment flow | Session or limited persistent period | No |

| Workspace access cookie | Supports access to selected workspace | Session or limited persistent period | No |

Actual cookie names and durations may vary depending on the technical configuration of ELVOAQ.

10. Authentication and Account Cookies

ELVOAQ may use authentication and account cookies to:

1. identify logged-in users;

2. maintain secure sessions;

3. prevent repeated login prompts;

4. protect account access;

5. support workspace membership;

6. maintain administrator sessions;

7. support invited user access;

8. detect unusual login behavior;

9. manage account security;

10. prevent unauthorized session use.

These cookies are generally strictly necessary for the logged-in platform.

If these cookies are blocked or deleted, users may be logged out or may be unable to access ELVOAQ.

11. Security Cookies

Security cookies and similar technologies help protect ELVOAQ, users, accounts, workspaces, and shared records.

They may be used to:

1. detect suspicious login attempts;

2. prevent account takeover;

3. identify repeated failed logins;

4. reduce spam;

5. prevent abuse;

6. detect automated traffic;

7. support rate limiting;

8. identify malicious activity;

9. protect against cross-site request forgery;

10. protect against session hijacking;

11. maintain audit logs;

12. support fraud prevention;

13. protect payment flows;

14. protect controlled sharing links;

15. enforce the Terms of Use.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Anti-CSRF token | Prevents unauthorized form submissions | Session | No |

| Session protection cookie | Helps secure login sessions | Session or limited persistent period | No |

| Abuse prevention cookie | Helps detect suspicious traffic | Session to 12 months | Usually no |

| Bot protection cookie | Helps distinguish legitimate users from automated traffic | Session to 12 months | Usually no |

| Rate-limit identifier | Helps protect against abuse and excessive requests | Session to 12 months | Usually no |

Some security cookies may be strictly necessary. Others may depend on the provider, configuration, and applicable law.

12. Consent Preference Cookies

ELVOAQ may use cookies or local storage to remember your cookie choices.

These technologies may store:

1. whether you accepted optional cookies;

2. whether you customized preferences;

3. which categories you allowed;

4. the date and time of your choice;

5. the version of the cookie banner or policy shown;

6. your region or consent mode;

7. an anonymous consent identifier.

Consent records help ELVOAQ respect your preferences and demonstrate compliance with applicable law.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Cookie consent record | Stores cookie preferences | 6 to 12 months | No |

| Consent version marker | Records which banner/policy version applied | 6 to 12 months | No |

| Preference storage | Remembers customized choices | 6 to 12 months | No |

13. Functional Cookies

Functional cookies help ELVOAQ remember user choices and improve usability.

These cookies may support:

1. language preferences;

2. region preferences;

3. interface preferences;

4. dashboard preferences;

5. remembered workspace selection;

6. saved layout choices;

7. accessibility settings;

8. form state;

9. dismissed notices;

10. user interface continuity.

Functional cookies may improve user experience but may not always be strictly necessary.

Depending on the applicable law and technical purpose, some functional cookies may require consent.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Language preference | Remembers selected language | 6 to 12 months | Depends |

| Interface preference | Remembers dashboard or layout setting | 6 to 12 months | Depends |

| Workspace preference | Remembers recent workspace | Session or limited persistent period | Usually no if required |

| Dismissed notice cookie | Remembers dismissed platform notices | 6 to 12 months | Depends |

14. Payment-Related Cookies

ELVOAQ may use multiple payment providers to process yearly subscriptions, invoices, refunds, checkout flows, tax calculations, and billing-related transactions.

Payment-related cookies and similar technologies may support:

1. secure checkout;

2. fraud prevention;

3. payment authentication;

4. subscription purchase;

5. checkout session continuity;

6. invoice generation;

7. payment method verification;

8. refund processing;

9. tax calculation;

10. compliance with payment security requirements.

Some payment cookies may be strictly necessary to complete a transaction requested by the user.

Payment providers may process personal data and cookie-related data according to their own privacy and cookie policies.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Checkout session cookie | Maintains checkout session | Session | Usually no |

| Payment fraud prevention cookie | Detects suspicious payment behavior | Session to 12 months | Usually no |

| Payment authentication cookie | Supports secure payment confirmation | Session | Usually no |

| Billing flow cookie | Supports subscription purchase flow | Session or limited persistent period | Usually no |

Actual cookies depend on the payment providers used.

15. Support-Related Cookies

ELVOAQ may use customer support tools, contact forms, helpdesk systems, email support, or chat support.

Support-related cookies may support:

1. support chat functionality;

2. support ticket continuity;

3. remembering support session state;

4. attaching account context to a support request;

5. avoiding repeated prompts;

6. troubleshooting technical issues;

7. identifying errors reported by users;

8. maintaining secure support interactions.

Depending on the support tool, support cookies may be functional or strictly necessary for a requested support feature.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Support session cookie | Maintains active support chat or ticket context | Session | Depends |

| Helpdesk preference cookie | Remembers support widget state | Session to 12 months | Depends |

| Contact form security cookie | Protects against spam and abuse | Session | Usually no |

16. Controlled Sharing Cookies

ELVOAQ may allow users to share selected records, documents, asset profiles, or views with third parties.

Cookies and similar technologies may be used to:

1. authenticate recipients;

2. validate access links;

3. maintain temporary access state;

4. protect shared views;

5. prevent unauthorized access;

6. monitor access for security;

7. support revocation of sharing links;

8. prevent abuse of shared links;

9. maintain session continuity during shared access.

These cookies are generally used to provide secure access to shared information and may be strictly necessary for the controlled sharing feature.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Shared access token | Validates access to shared view | Session or limited persistent period | Usually no |

| Recipient session cookie | Maintains secure shared access session | Session | Usually no |

| Sharing security cookie | Helps prevent unauthorized access attempts | Session to 12 months | Usually no |

17. Demo and Trial Access Cookies

ELVOAQ may offer demo access, trial access, preview environments, or evaluation features.

Cookies may be used to:

1. remember demo session state;

2. maintain trial access;

3. prevent trial abuse;

4. enforce trial limits;

5. remember demo preferences;

6. protect demo environments;

7. detect suspicious trial activity;

8. support account conversion from trial to paid plan.

Examples may include:

| Cookie Type | Purpose | Typical Duration | Consent Required |

|---|---|---:|---|

| Trial session cookie | Maintains trial session | Session or limited persistent period | Usually no |

| Demo environment cookie | Maintains demo state | Session | Usually no |

| Trial abuse prevention cookie | Helps prevent repeated unauthorized trial use | Session to 12 months | Usually no |

18. AI Workflow Support Cookies

ELVOAQ may provide AI-assisted features to support categorization, organization, document workflows, asset record suggestions, or platform assistance.

Cookies and similar technologies may support AI-assisted workflows by:

1. maintaining session state during an AI-assisted task;

2. remembering temporary interface state;

3. applying rate limits;

4. preventing abuse;

5. protecting account access;

6. supporting feature availability;

7. tracking technical errors in the workflow;

8. preserving user settings for AI-assisted tools.

When you use an AI-assisted feature, the content you submit to it - including uploaded documents and images - is transmitted to our AI provider xAI (Grok) for processing.

Cookies are not used to sell or advertise based on private AI workflow content.

19. Local Storage and Session Storage

ELVOAQ may use local storage or session storage in your browser.

These technologies may store:

1. session state;

2. interface preferences;

3. temporary upload state;

4. dashboard settings;

5. workspace selection;

6. consent preferences;

7. security tokens where appropriate;

8. temporary form data;

9. feature flags;

10. user interface state;

11. demo or trial state;

12. controlled sharing state.

Local storage may remain until deleted by the user, browser, or platform logic.

Session storage usually ends when the browser session ends.

Because local storage and session storage may store information on your device, you should protect your device, browser profile, and operating system account.

20. Server Logs

When you access ELVOAQ, our systems and service providers may collect server logs.

Server logs may include:

1. IP address;

2. request date and time;

3. browser type;

4. browser version;

5. operating system;

6. device type;

7. user agent;

8. requested page or endpoint;

9. referring page;

10. response status;

11. error codes;

12. session identifiers;

13. security events;

14. approximate location derived from IP address;

15. request duration;

16. upload or download technical events;

17. suspicious activity indicators.

Server logs are used for:

1. security;

2. debugging;

3. fraud prevention;

4. operational reliability;

5. legal compliance;

6. platform improvement;

7. abuse detection;

8. enforcement of the Terms of Use.

Server logs may be retained for a limited period unless longer retention is required for security, legal, fraud prevention, or dispute purposes.

21. Analytics Cookies

Based on the current ELVOAQ configuration, ELVOAQ does not currently use analytics tracking cookies.

This means ELVOAQ does not currently use third-party analytics providers such as Google Analytics, Plausible, PostHog, or similar behavioral analytics tools for general tracking.

However, ELVOAQ may still process basic technical logs, server logs, security logs, and operational data necessary to operate and secure the Platform.

If ELVOAQ later introduces analytics cookies, this Cookie Policy should be updated and the cookie banner should be configured accordingly.

Analytics cookies, if introduced later, may be used to understand:

1. page visits;

2. traffic sources;

3. product usage;

4. technical errors;

5. performance issues;

6. feature adoption;

7. browser and device information.

Where required by law, analytics cookies should not be placed before consent.

22. Marketing and Advertising Cookies

Based on the current ELVOAQ configuration, ELVOAQ does not currently use retargeting advertising cookies.

ELVOAQ does not use private vault content, asset records, proof documents, ownership records, uploaded documents, certificates, warranties, receipts, contracts, or private notes for behavioral advertising.

ELVOAQ may send optional marketing communications or product updates, but this does not mean that retargeting cookies are used.

If ELVOAQ later introduces marketing or advertising cookies, this Cookie Policy and the cookie banner should be updated before or at the time such technologies are deployed.

Marketing cookies, if introduced later, may support:

1. campaign measurement;

2. conversion tracking;

3. referral attribution;

4. advertisement performance measurement;

5. frequency control;

6. newsletter campaign analysis.

Where required by law, marketing cookies should not be placed before consent.

23. Embedded Content

ELVOAQ may include embedded content or third-party components, such as:

1. payment widgets;

2. support widgets;

3. security tools;

4. contact forms;

5. video content, if enabled;

6. scheduling tools, if enabled;

7. document viewers, if enabled;

8. captcha or bot protection tools;

9. external forms, if enabled.

Embedded content may set cookies or similar technologies controlled by third parties.

Where possible, ELVOAQ should avoid unnecessary embedded third-party tracking.

Where embedded content uses optional cookies, ELVOAQ should request consent where required by applicable law.

24. Third-Party Cookies

Some cookies may be placed by third-party providers used by ELVOAQ.

These may include providers for:

1. hosting;

2. cloud infrastructure;

3. payment processing;

4. authentication;

5. customer support;

6. email delivery;

7. security monitoring;

8. error monitoring;

9. bot protection;

10. consent management;

11. backup and technical operations;

12. document processing, if enabled;

13. AI-assisted infrastructure, if enabled.

Third-party providers may process cookie-related data according to their own privacy and cookie policies.

Some providers may act as processors on behalf of ELVOAQ. Others may act as independent controllers depending on their role, configuration, and applicable law.

Before publication, ELVOAQ should list the actual providers used.

Potential provider categories:

| Provider Category | Purpose | Cookie Category |

|---|---|---|

| Hosting provider | Platform hosting and delivery | Strictly necessary |

| Cloud infrastructure provider | System operation and reliability | Strictly necessary |

| Payment provider | Subscription checkout and payment security | Strictly necessary / payment |

| Support provider | Customer support chat or ticket support | Functional / support |

| Security provider | Bot detection and account protection | Strictly necessary / security |

| Consent tool | Cookie banner and preference storage | Strictly necessary |

| Email provider | Email delivery and communication support | Functional / communication |

25. Public Website Cookies vs Logged-In Platform Cookies

Cookies may be used differently depending on whether you are visiting the public website or using the logged-in ELVOAQ platform.

25.1 Public Website

The public website may use cookies for:

1. website operation;

2. security;

3. cookie consent management;

4. contact forms;

5. demo or trial access;

6. sign-up flows;

7. language or interface preferences;

8. support tools;

9. payment redirection, where applicable.

25.2 Logged-In Platform

The logged-in platform may use cookies for:

1. authentication;

2. secure sessions;

3. workspace access;

4. user permissions;

5. document upload workflows;

6. asset record workflows;

7. controlled sharing;

8. payment or subscription management;

9. security monitoring;

10. support and troubleshooting;

11. account settings;

12. demo and trial state;

13. AI-assisted workflow state.

Blocking strictly necessary cookies may prevent the logged-in platform from working correctly.

26. Cookies and Sensitive Customer Content

ELVOAQ is designed for valuable assets, proof documents, private records, and sensitive information.

ELVOAQ does not use cookies to sell or publicly expose private Customer Data.

ELVOAQ does not use cookies to build advertising profiles from:

1. private asset records;

2. ownership records;

3. uploaded certificates;

4. uploaded warranties;

5. uploaded receipts;

6. uploaded contracts;

7. insurance documents;

8. family records;

9. private notes;

10. confidential business documents;

11. proof documents;

12. uploaded files.

Where cookies are used inside the platform, their purpose should be limited to security, functionality, user preferences, payment support, controlled sharing, support, or technical operation.

27. Cookies in Emails

ELVOAQ may send service emails, legal emails, support emails, subscription emails, billing emails, security emails, and optional marketing emails.

Email systems may use limited technical technologies to:

1. deliver emails;

2. detect failed delivery;

3. protect against abuse;

4. support unsubscribe functionality;

5. maintain communication records;

6. measure delivery performance.

If optional marketing email tracking is used, such as open tracking or link tracking, this should be disclosed and managed according to applicable law.

You may unsubscribe from optional marketing emails at any time.

Service, legal, security, billing, and account emails may still be sent where necessary.

28. Cookie Retention Periods

Cookies may remain on your device for different periods depending on their purpose.

Typical retention periods may include:

| Cookie Category | Typical Retention |

|---|---:|

| Session cookies | Until browser session ends |

| Authentication cookies | Session or limited persistent period |

| Security cookies | Session to 12 months |

| Consent cookies | 6 to 12 months |

| Functional cookies | 6 to 12 months |

| Payment cookies | Session to 12 months |

| Support cookies | Session to 12 months |

| Controlled sharing cookies | Session or limited persistent period |

| Trial/demo cookies | Session to 12 months |

| Analytics cookies | Not currently used |

| Retargeting cookies | Not currently used |

Actual retention periods depend on the specific cookie, provider, configuration, and applicable law.

ELVOAQ should maintain a detailed cookie table with actual cookie names, providers, categories, purposes, durations, and first-party or third-party status.

29. Detailed Cookie List

Before publishing, ELVOAQ should complete the following table based on the actual website and platform configuration.

| Cookie Name | Provider | Category | Purpose | Duration | First/Third Party |

|---|---|---|---|---:|---|

| [Insert Cookie Name] | ELVOAQ | Strictly necessary | Authentication/session security | [Insert Duration] | First-party |

| [Insert Cookie Name] | ELVOAQ | Strictly necessary | Cookie consent preference storage | [Insert Duration] | First-party |

| [Insert Cookie Name] | ELVOAQ | Security | CSRF/session protection | [Insert Duration] | First-party |

| [Insert Cookie Name] | [Payment Provider] | Payment / strictly necessary | Secure checkout and payment fraud prevention | [Insert Duration] | Third-party |

| [Insert Cookie Name] | [Support Provider] | Functional / support | Customer support chat or ticket continuity | [Insert Duration] | Third-party |

| [Insert Cookie Name] | [Security Provider] | Security | Bot and abuse prevention | [Insert Duration] | Third-party |

| [Insert Cookie Name] | [Consent Tool] | Strictly necessary | Stores cookie choices | [Insert Duration] | First-party or third-party |

| Not currently used | Analytics provider | Analytics | ELVOAQ currently does not use analytics tracking | N/A | N/A |

| Not currently used | Advertising provider | Retargeting / advertising | ELVOAQ currently does not use retargeting advertising | N/A | N/A |

This table should not remain generic in the final published version. A real cookie scan should be performed and the table should be updated with actual cookie names.

30. Managing Cookie Preferences

You may manage cookies through:

1. the ELVOAQ cookie banner;

2. the ELVOAQ cookie customization panel;

3. a cookie settings or privacy preferences link, where available;

4. browser settings;

5. device settings;

6. privacy extensions;

7. operating system settings.

Most browsers allow you to:

1. view cookies;

2. delete cookies;

3. block third-party cookies;

4. block all cookies;

5. allow cookies from selected websites;

6. clear cookies after each session;

7. restrict cross-site tracking;

8. manage site permissions.

Blocking strictly necessary cookies may prevent ELVOAQ from functioning correctly.

31. Withdrawing Consent

Where ELVOAQ relies on consent for optional cookies, you may withdraw consent at any time.

Withdrawal of consent does not affect the lawfulness of processing based on consent before withdrawal.

After withdrawal, optional cookies should no longer be placed or read unless another legal basis applies or the cookie is strictly necessary for a service requested by you.

You may need to delete existing cookies from your browser if you want to remove cookies that were already stored before withdrawal.

ELVOAQ should provide a clear way to update cookie preferences, such as a Cookie Settings or Privacy Preferences link in the website footer.

32. Browser Controls

You can control cookies through your browser.

Depending on your browser, you may be able to:

1. delete existing cookies;

2. block future cookies;

3. block third-party cookies;

4. clear cookies when closing the browser;

5. control site-specific permissions;

6. restrict tracking technologies;

7. manage local storage;

8. use private browsing modes.

Browser controls may affect ELVOAQ functionality.

If you block all cookies, you may be unable to:

1. log in;

2. remain logged in;

3. access your workspace;

4. upload documents;

5. manage asset records;

6. complete checkout;

7. use controlled sharing;

8. access demo or trial features;

9. receive secure support functionality.

33. Do Not Track and Global Privacy Signals

Some browsers or browser extensions may send “Do Not Track,” Global Privacy Control, or similar privacy signals.

Because standards and legal obligations for such signals may vary by jurisdiction and technology, ELVOAQ may respond to such signals where required by applicable law or where technically feasible.

If ELVOAQ supports Global Privacy Control or similar mechanisms in the future, this Cookie Policy may be updated to explain how those signals are handled.

34. International Processing

ELVOAQ is operated from the Slovak Republic.

Cookie-related data may be processed in the European Union and, depending on the technical providers used, may also be processed in other countries.

This may include processing by providers for:

1. hosting;

2. cloud infrastructure;

3. payment processing;

4. customer support;

5. security tools;

6. email delivery;

7. consent management;

8. technical operations.

Where personal data is transferred internationally, ELVOAQ uses appropriate safeguards where required by applicable law.

More information about international transfers is available in the ELVOAQ Privacy Policy.

35. No Sale of Cookie Data

ELVOAQ does not sell cookie data.

ELVOAQ does not sell private vault content, asset records, proof documents, ownership notes, uploaded certificates, uploaded warranties, uploaded contracts, uploaded receipts, private notes, or sensitive customer-uploaded files.

Cookie-related data is used to operate, secure, support, and improve ELVOAQ according to this Cookie Policy and the Privacy Policy.

36. User Responsibilities

As a user, you are responsible for:

1. reviewing this Cookie Policy;

2. managing cookie preferences;

3. configuring browser privacy settings;

4. protecting your device;

5. protecting your browser profile;

6. logging out on shared devices;

7. clearing cookies where necessary;

8. using secure networks;

9. understanding that blocking cookies may affect functionality;

10. protecting downloaded or exported files outside ELVOAQ.

If you use ELVOAQ through a company, organization, family office, or workspace, internal administrator settings may also affect platform access, security, and user experience.

37. Changes to This Cookie Policy

ELVOAQ may update this Cookie Policy from time to time.

Updates may reflect:

1. legal changes;

2. regulatory guidance;

3. product changes;

4. new features;

5. changes in cookie use;

6. changes in payment providers;

7. changes in support tools;

8. changes in consent tools;

9. changes in security systems;

10. changes in hosting or infrastructure;

11. introduction of analytics tools;

12. introduction of optional marketing cookies;

13. changes in business operations.

The updated Cookie Policy will be posted on the ELVOAQ website or made available through the Platform.

If changes are material, ELVOAQ may provide additional notice where required or appropriate.

Your continued use of ELVOAQ after an updated Cookie Policy becomes effective means that you acknowledge the updated Cookie Policy.

38. Contact

For questions about this Cookie Policy or ELVOAQ’s use of cookies and similar technologies, contact:

Lukas Rajnic, trading as ELVOAQ

Sole trader established in the Slovak Republic

VAT: Not registered for VAT

Email: privacy@elvoaq.com

Legal: legal@elvoaq.com

Support: support@elvoaq.com

Website: www.elvoaq.com

39. Final Cookie Statement

ELVOAQ uses cookies and similar technologies to operate, secure, protect, and support the Platform.

Strictly necessary cookies help ELVOAQ provide login, account security, workspace access, payment flows, controlled sharing, consent storage, and core platform functionality.

Optional cookies, where introduced or enabled, should be clearly explained and subject to user choice where required by applicable law.

ELVOAQ currently does not use analytics tracking according to the current platform configuration.

ELVOAQ currently does not use retargeting advertising according to the current platform configuration.

ELVOAQ does not sell cookie data.

ELVOAQ does not use private vault records, asset records, ownership documents, proof documents, uploaded files, or sensitive customer content as advertising inventory.

ELVOAQ is built for users who value privacy, discretion, security, and structured control over important information. Our cookie practices should reflect that same standard.