Last updated: April 22, 2026. This Cookie Policy explains how InkMeld uses cookies and similar technologies on the website, what categories of technologies may be used, why they are used, how long they may remain on your device, and what controls you have.
This Cookie Policy applies to the InkMeld website at inkmeld.oakdev.app and related legal, support, and marketing pages that link to it. It should be read together with the Privacy Policy, which explains how we process personal data more generally.
If a conflict exists between this Cookie Policy and mandatory law, mandatory law controls. If a conflict exists between this Cookie Policy and a specific consent banner or feature-specific notice shown to you at the point of collection, the feature-specific notice controls for that feature.
Cookies are small text files placed on your device when you visit a website. Some cookies are deleted when you close your browser session, while others remain for a longer period until they expire or you delete them.
We also use the term "similar technologies" to include tools and storage methods that are not technically cookies but serve related purposes, such as:
Based on the website code reviewed on April 22, 2026, the InkMeld site includes Firebase Analytics scaffolding, but the current code only initializes website analytics if a complete Firebase configuration is supplied. In the current project state reviewed for this policy, the configuration is placeholder-only, and analytics initialization is skipped unless additional values are added in a deployment.
That means the actual cookies or similar technologies used on a live deployment can vary depending on whether optional analytics, security, hosting, CDN, or consent tooling is enabled. This policy is therefore written to cover both the website's present state and the categories of technologies that may reasonably be activated in normal operation.
These are technologies that are required for the website to function securely or correctly. They may be used to keep your session stable, preserve security state, prevent fraudulent requests, support navigation, remember a basic cookie preference, or maintain core infrastructure functions such as load balancing or bot protection.
Without these technologies, some parts of the website may not work, may fail to load correctly, or may become less secure. Where legally permitted, strictly necessary technologies do not generally require prior consent.
These may be used to remember choices you make, such as consent choices, display preferences, or other optional settings. If you disable these technologies, the website may still work, but it may not remember your preferences across pages or visits.
These may be used to understand how visitors use the site, which pages are visited, how long pages take to load, whether features are being used, where users encounter errors, and how the site can be improved. Depending on the deployment, this category may include tools such as Firebase Analytics or related website measurement services.
We aim to treat non-essential analytics technologies as optional and to seek consent where required by law.
These may be used to protect the site and its infrastructure from malicious traffic, automated abuse, request forgery, repeated attacks, scraping, spam, or other misuse. Security tools may be first-party or third-party and may involve cookies, local storage, request tokens, browser fingerprints permitted by law, or server-side telemetry.
If we later embed third-party services such as videos, maps, forms, chat widgets, payment widgets, or social media content, those services may set their own cookies or collect data directly from your browser. In that case, their own privacy and cookie notices may also apply.
Depending on the feature and deployment, we may use cookies and similar technologies to:
Where the law requires consent for non-essential cookies or similar technologies, we intend to rely on your consent before placing or activating them. Where a technology is strictly necessary for the security, transmission, or core operation of the website, we may rely on our legitimate interests and the relevant legal exemption that allows such necessary technologies without prior consent.
If analytics or similar optional tools are activated later, we may display a banner, consent tool, or other notice so that you can choose whether to allow them. Refusing non-essential technologies should not normally block access to the main informational parts of the site, although some convenience features may become limited.
The exact names can change over time as vendors update their products, but examples of the kinds of technologies we may use include:
Some of these may be first-party technologies that we control directly, while others may be provided by our hosting, analytics, consent, or infrastructure providers.
Different cookies and similar technologies may remain active for different periods:
We try not to keep browser-side identifiers longer than reasonably necessary for the purpose they serve. However, retention can vary depending on provider defaults, security needs, and legal requirements.
You can usually control cookies and similar technologies in several ways:
If you block or delete cookies, parts of the site may no longer function as intended. For example, preference choices may not be remembered and security or anti-abuse tools may behave differently.
If analytics, hosting, CDN, bot-protection, or similar providers are enabled, they may process information in the EEA, the United States, or other countries where they operate. Some of these providers may act as processors for us, while others may act as independent controllers for data they collect under their own terms.
Where required by law, we use or expect to use appropriate transfer safeguards for personal data associated with those technologies, such as adequacy decisions or standard contractual clauses.
Some cookies or similar technologies may be set directly by InkMeld or by infrastructure we control as the website operator. Others may be set or accessed by third parties acting on our behalf or, in some situations, for their own independent purposes under their own terms. Whether a provider acts as a processor, joint controller, or independent controller can depend on the specific product and implementation.
In practice, this means that not every technology on or around the site will be governed in exactly the same way. A hosting or security provider may use request-level identifiers to keep the site safe and available, while an analytics provider may use separate identifiers to measure aggregate usage trends. If a third-party service is embedded or linked, that third party may also collect information when your browser connects to it.
Not all browser-side or device-side tracking involves a traditional cookie file. Depending on the feature, the site or its providers may use local storage, session storage, indexed database storage, pixels, tags, scripts, request headers, software-development kits, cache entries, or server-side log records that help achieve similar operational, measurement, or security goals.
This policy uses the term "cookies and similar technologies" as a practical umbrella expression for those tools. Where the law draws a distinction between them, we aim to apply the appropriate rule to the specific technology in question. For example, browser-side storage may require consent in some circumstances even if it is not technically implemented as a classic HTTP cookie.
Server logs are also important to distinguish from browser cookies. A server log may record that a request happened, along with technical data such as the approximate time, IP address, user agent, or requested path, even if no persistent browser cookie is placed at all.
If we rely on consent for optional analytics, advertising, or similar technologies, you should be able to withdraw that consent later. Withdrawal normally affects future processing and does not necessarily erase information already collected before the withdrawal took effect, unless the law gives you a separate deletion right that applies.
To remember your choice, we may store a consent-state record or similar preference signal. Ironically, that means a small amount of storage may still be used to remember that you declined optional storage. Without such a record, the site might repeatedly ask for the same choice on each visit.
We may also keep limited server-side evidence of consent events, banner interactions, or preference changes for audit, compliance, dispute-resolution, and accountability reasons where permitted by law.
Different browsers and devices provide different privacy controls. Depending on the environment, you may be able to block third-party cookies, clear site data automatically, disable JavaScript, restrict cross-site tracking, use private browsing modes, or send privacy preference signals. Some mobile browsers and privacy tools also reduce identifier lifetimes or proxy certain network requests.
These controls are useful, but they are not always complete or uniform. A choice made in one browser usually does not automatically carry over to another browser, another device, another profile, or a separately embedded webview. If you use multiple devices, you may need to repeat your preference choices on each one.
Blocking or deleting cookies and similar technologies can improve privacy in some circumstances, but it can also affect usability, fraud controls, and reliability. For example, consent banners may reappear, forms may lose state, rate-limiting protections may become stricter, and embedded content may fail to load or repeatedly ask for permission.
If you experience broken behavior after changing browser privacy settings, the issue may not always mean that the site is malfunctioning; it may simply mean that a function designed to rely on browser-side storage can no longer remember prior choices or validate request continuity.
The InkMeld ecosystem may involve both app experiences and website experiences. If you open a legal page, support page, or purchase-related page from inside a mobile app, the page may appear inside an in-app browser or webview rather than your main device browser. Webviews can behave differently from full browsers with respect to cookie storage, consent persistence, autofill, password managers, and tracking-prevention features.
As a result, a preference or cookie state recorded in one environment may not automatically appear in another. For example, a consent choice made in your mobile browser might not carry over to a webview launched from an app, and a webview state might not persist once you return to the external browser.
A consent choice made on one page, subdomain, or browser context does not always automatically apply everywhere else. That depends on how the site is configured, whether the pages operate under the same technical origin, and whether a third-party service is embedded directly or merely linked out.
If you leave our site and visit a third-party site, that third party will generally apply its own cookie and privacy rules. Likewise, an embedded video, map, payment frame, or external widget may apply additional technologies when it loads, even if the surrounding InkMeld page has its own separate consent logic.
Some browsers offer a "Do Not Track" signal or similar privacy settings. Because the legal effect and technical interpretation of these signals has historically been inconsistent, the site may not respond to every such signal in a uniform way unless and until a specific legal framework requires us to do so for a given processing activity.
That said, where a legally recognized opt-out or privacy preference signal applies and our systems are configured to honor it, we may treat that signal as a request affecting future optional analytics, cross-context tracking, or related processing.
Websites often rely on content-delivery networks, edge caches, rate-limiting systems, web-application firewalls, or anti-bot protections that use short-lived identifiers or request analysis to keep the site available and safe. These technologies may be essential even when they do not look like traditional product features from the user's perspective.
Some of these protections may classify a browser or network session as risky based on technical patterns such as IP reputation, request frequency, malformed traffic, or unusual navigation behavior. As a result, privacy tools that heavily alter browser behavior can sometimes increase the likelihood of security challenges or degraded performance.
If the site later uses experimentation, performance measurement, or design-optimization tools, those tools may rely on cookies or similar storage to avoid showing the same visitor different interface variants on every page load, to understand whether a layout works, or to measure whether a support or legal page is understandable.
We would still try to classify those technologies according to the actual purpose they serve. Some may be strictly necessary for consistency or accessibility, while others may be optional analytics or optimization tools that require consent under applicable law.
If you are in Sweden and have questions about cookie rules under electronic communications law, the Swedish Post and Telecom Authority (PTS) is the supervisory authority in that area. If your concern relates more broadly to personal data processing, you may also have the right to complain to the Swedish Authority for Privacy Protection (IMY) or another competent supervisory authority.
We may update this Cookie Policy when our website, tools, or legal obligations change. When we do, we will update the "Last updated" date above.
If you have questions about cookies or similar technologies on the site, contact [email protected].