Last updated: 2026-10-05 · Operator: SparkRelay Tech Services
Purpose. This document explains the cookies and similar technologies used by the MultiSigner service and website, why we use them, and how you can control them. It forms part of, and should be read together with, our Privacy Policy, our Encryption and Access Control document, and our Data Processing Agreement.
1. Purpose and Scope
This document applies to the MultiSigner electronic document signing service (the “Service”) operated by SparkRelay Tech Services (“Company,” “we,” “us,” or “our”), including the application available at app.multisigner.vip, our corporate website at multisigner.vip, and the pages where we host these legal documents.
It describes the cookies and similar technologies that are stored on, or read from, your device when you use the Service or visit our website, and it explains the choices available to you.
2. Summary
We use one strictly necessary cookie to keep you signed in (ms_session).
We store two preferences in your browser’s local storage: your language and your display theme.
We use no advertising cookies, no analytics or measurement tools, no social media pixels, and no cross-site tracking. We do not create user profiles for marketing, and we do not sell or share personal data for advertising purposes.
Because we only use technologies that are strictly necessary or set at your request, the Service does not show a cookie consent banner. If we ever introduce non-essential cookies, we will ask for your consent first.
The payment step takes place inside a secure checkout window operated by our Merchant of Record, Fungies Inc., which may set its own cookies (see section 6).
3. What Cookies and Similar Technologies Are
Cookies are small text files that a website stores on your device and reads back on later visits. They may be set by us (“first-party”) or by another domain whose content is displayed on the page (“third-party”).
Local storage and session storage are browser storage areas in which a website can save information without sending it on every request. Information stored there remains until it is deleted by the website or by you (local storage), or until you close the tab (session storage).
Pixels and similar techniques are invisible elements or code fragments used to record that a page or an email was opened. We do not use them.
4. Cookies Used by the Service
We use a single first-party cookie:
Name
Purpose
Category
Duration
Attributes
ms_session
Keeps you signed in during your session. It contains a signed JSON Web Token (JWT) that identifies your session; it does not contain your password or your documents.
Because it is HttpOnly, the session cookie cannot be read by scripts running in the page. It is required to use the Service: without it, you cannot sign in, sign documents, manage signing flows, or view your credit balance. No other cookie is set by the Service itself.
5. Storage Used in Your Browser
We keep two preferences in your browser’s local storage. They contain no personal data, are never transmitted to us or to third parties, and are stored only because you have chosen that setting:
Key
Purpose
Category
Retention
ms_lang
Remembers the interface language you selected (Spanish, English, German, or French).
Preference set at your request
Until you clear your browser storage
ms_theme
Remembers whether you chose the dark (default) or light theme.
Preference set at your request
Until you clear your browser storage
We do not use session storage, and we do not use these values to identify you, to build a profile, or to follow you across other websites.
6. Third-Party Content and the Payment Checkout
6.1 Payment checkout
Credit purchases are completed in a secure checkout window provided by Fungies Inc., our Merchant of Record, which is displayed as an embedded window (iframe) inside our application so that you do not leave the Service.
Fungies and its payment processor, Stripe, Inc., may set their own cookies or browser storage within that window in order to process the payment, keep the checkout secure, and prevent fraud. Those technologies are controlled by them, not by us, and their use is governed by their own policies.
If you select a payment method that is completed on the provider’s own website (for example certain bank-transfer or wallet methods), you will be redirected to that provider, which will apply its own cookies.
We do not receive your card details, and we do not set any cookie of our own for payment purposes.
6.2 Fonts and page styling
Our public website and these legal pages load two third-party resources to render the page: the Tailwind CSS runtime (cdn.tailwindcss.com) and Google Fonts (fonts.googleapis.com, fonts.gstatic.com).
Loading those resources means that the provider receives your IP address and standard browser information as part of the request. They are used only to display the page correctly; we do not use them to track you.
These resources do not set cookies on our domain.
7. What We Do Not Do
We do not use advertising, marketing, or retargeting cookies.
We do not use analytics or measurement tools (for example Google Analytics, Matomo, Plausible, or Hotjar), nor session-recording or heatmap tools.
We do not use social media pixels or plugins that follow you across other websites.
We do not use device fingerprinting, or any technique that identifies you by the characteristics of your device.
We do not track your activity across third-party websites, and we do not sell or share personal data for advertising.
We disable DNS prefetching in the browser (X-DNS-Prefetch-Control: off), so the links shown on the page are not resolved in advance.
8. Server-Side Data That Is Not a Cookie
For transparency, the following processing related to your activity relies on our servers rather than on cookies or browser storage in your device:
Technical logs: when you use the Service, our servers record technical data such as your IP address, browser user agent, and the date and time of requests, as described in our Privacy Policy.
Traceability of signing flows: for documents signed through a signing flow, we record the signer’s IP address, device information, and an approximate location (country, city, and coordinates) derived from that IP address on our servers. This is done to create an auditable record of the signature, and it does not rely on any cookie, browser geolocation, or GPS permission.
Acceptance video: when a signer voluntarily records a short acceptance video, the camera and microphone are used only after the browser asks for, and the signer grants, explicit permission. No recording takes place without that permission.
9. How to Control or Delete Cookies and Storage
Sign out of the Service to delete the session cookie immediately.
Browser settings: all major browsers let you view, block, and delete cookies and site data. Blocking or deleting the session cookie will sign you out and prevent you from signing in until it is set again.
Preferences: clearing your browser storage resets the interface language and theme to the defaults (Spanish and dark theme).
Third-party cookies: if you block all third-party cookies or content, the checkout window may not load, and some payment methods may be unavailable.
Do Not Track and Global Privacy Control: because we do not track you across websites, these signals do not change the way the Service behaves; they are honoured by design.
Incognito or private windows discard cookies and local storage when you close them.
10. Legal Basis
The ms_session cookie is strictly necessary to provide a service you have explicitly requested (an authenticated session), and therefore does not require consent under Article 5(3) of the ePrivacy Directive (2002/58/EC, as implemented nationally).
Where the GDPR applies, the session cookie is processed on the basis of the performance of our contract with you (Article 6(1)(b)) and our legitimate interest in keeping the Service secure and preventing unauthorized access and fraud (Article 6(1)(f)).
The language and theme preferences are stored at your request, and are used only to display the Service as you have configured it.
11. Changes to This Document
We may update this document to reflect changes in the technologies we use or in applicable law. The version in force is the one published on this page, with the “Last updated” date shown above. If a change is material, we will announce it on our website before it takes effect.
12. Contact
For questions about this document or about the cookies and similar technologies we use, please contact: