Cookie Policy

This Cookie Policy explains how Film Permits Nepal uses cookies and similar technologies on its website. Film Permits Nepal is an independent, privately owned production-support service based in Kathmandu. We are not a government office, we do not issue permits, and this policy covers only the small set of technologies our own website relies on to function and to be measured. It sits alongside our Privacy Policy, which explains in broader terms how we handle any personal information you share when you contact us or request a document review.

We have deliberately kept our use of cookies modest. A production-support enquiry does not require behavioural advertising, cross-site tracking, or the kind of dense marketing technology stack many commercial sites carry. Our priority is that the site loads reliably, that any form you submit reaches us intact, and that we can understand in aggregate which planning guides are useful so we can improve them. Nothing on this page is designed to profile you as an individual for advertising purposes.

This document describes what cookies are, the categories we use, why each category exists, how consent works where it applies, how long typical cookies persist, and the practical steps you can take to review or remove them in your own browser. It also explains the limits of our knowledge: some cookies are set by third-party services we rely on, and those providers control their own technology and their own policies. Where that is the case we tell you plainly and point you to the right place. Because tools and providers change over time, the specific cookie names and durations described here are indicative and are confirmed against the live site during each review cycle rather than asserted as permanent fact.

What cookies are and why websites use them

A cookie is a small text file that a website asks your browser to store on your device. When you return to the site, or move between its pages, the browser sends that file back, which lets the site recognise the continuity of your visit. Cookies cannot run programs, read unrelated files on your computer, or carry viruses. They are simply a way for a website to remember short pieces of information between one page request and the next, because the underlying web protocol does not otherwise remember anything from moment to moment.

Cookies are commonly described by two characteristics. The first is who sets them. A first-party cookie is set by the website you are actually visiting, in our case the Film Permits Nepal domain. A third-party cookie is set by a different service whose code runs on the page, such as an analytics provider. The second characteristic is how long they last. A session cookie exists only until you close your browser, while a persistent cookie remains for a defined period, which may be measured in days, weeks, or months depending on its purpose.

Beyond cookies in the strict sense, websites use a few related technologies that behave similarly. These include local storage and session storage, which are browser features that hold small amounts of data, and pixels or tags, which are tiny invisible elements that help a service register that a page has loaded. Throughout this policy, when we say cookies we mean cookies and these closely related technologies together, because from a privacy standpoint they raise the same questions and deserve the same transparency.

We use cookies for three narrow reasons: to make the site work at a basic level, to keep your consent choice recorded so we do not ask repeatedly, and to measure in aggregate how the site is used. We do not use cookies to build advertising profiles, to follow you across other websites, or to sell any information about you. If our use ever broadens, this policy is updated first and your consent is sought where the law requires it before any new non-essential technology is activated.

The categories of cookies we use

We group the technologies on our site into a small number of categories so you can reason about them clearly. Categorisation matters because the rules that apply, and the choices available to you, differ by category. Broadly, essential cookies are treated differently from everything else, because a site cannot function without them, whereas analytics and any future non-essential cookies depend on your consent.

The first category is strictly essential cookies. These support core functions such as page navigation, security, load balancing, and remembering that you have made a consent choice. Without them, basic features would not work or would work unreliably. Because they are necessary to deliver a service you have actively requested, they do not require prior consent under most privacy frameworks, although we still disclose them here in the interest of transparency.

The second category is analytics and performance cookies. These help us understand, in aggregate and without identifying you personally, how visitors move through the site: which guides are read, where people arrive from, and where pages may be confusing or slow. This information shapes how we prioritise writing and revising our planning content. Analytics cookies are not essential, so on our site they are governed by consent where the applicable law requires it.

A third category, functionality or preference cookies, may be used to remember low-risk choices such as a language or display preference so you do not have to set them again. Where we use anything in this category, it is limited to improving your own experience and is never used to track you elsewhere.

We do not maintain an advertising or targeting category. We do not run behavioural ad networks, retargeting pixels, or social media tracking widgets that follow you after you leave. If a future service we adopt introduces any such technology, we will create a clearly labelled category for it, describe it on this page, and obtain consent before it operates. The absence of an advertising category is a deliberate design choice, not an oversight.

Strictly essential cookies in detail

Strictly essential cookies are the foundation that lets the website behave predictably. They tend to be invisible to visitors precisely because they are doing their job quietly. Typical examples on a site like ours include a session identifier that keeps your interactions consistent while you browse, a security token that helps protect forms against certain kinds of abuse, and a small record of your cookie consent decision so the consent banner does not reappear on every page.

These cookies are first-party wherever possible, meaning they are set by our own domain rather than an outside service. They generally contain no more than a random identifier or a simple flag, not your name, your production details, or anything you typed into a form. The information they hold is operational rather than personal in the everyday sense, although privacy law may still treat certain identifiers as personal data, which is why we disclose them.

Many essential cookies are session cookies that disappear when you close your browser. The consent-record cookie is a common exception, because its whole purpose is to remember your decision across visits, so it persists for a defined period before expiring and prompting the banner again. The exact lifetime of the consent cookie is set to a reasonable interval and is confirmed against the live configuration during review rather than asserted here as a fixed number, because platform defaults change over time.

Because these cookies are necessary to deliver the site you asked to see, most privacy frameworks allow them without prior consent. You can still block or delete them through your browser, as described later, but doing so may cause parts of the site to behave oddly. For instance, if you block the consent-record cookie, the banner may reappear on every visit, and if you block security-related cookies, some forms may refuse to submit. We mention this so that any inconvenience is understood as a side effect of blocking, not a fault in the site.

Analytics cookies and how we use aggregate data

Analytics cookies let us see how the website performs as a whole. The value to a planning-focused site like ours is practical: if we can tell that a particular guide on document preparation is heavily read but that visitors leave a related page quickly, that signals where our writing needs to be clearer. We use this feedback loop to decide which topics to expand, which explanations to simplify, and which planning tables to add.

The key characteristic of our analytics use is that it is aggregate. We are interested in patterns across many visits, not in reconstructing what a single named person did. Reputable analytics tools offer settings that reduce the identifiability of individual visitors, such as shortening or masking parts of the network address and limiting how long records are retained. Where such settings exist, our preference is to enable the privacy-protective options, and the exact configuration is confirmed during each review.

Analytics cookies are typically set by a third-party provider whose code runs on our pages. That means the provider, not us, ultimately controls the technology and operates under its own policy. We choose providers we consider reasonable, but we are honest that we do not control their internal systems. Where a provider offers a data-processing arrangement that constrains how our visitors' data may be used, we prefer providers who offer it, and which provider applies is confirmed against the live site rather than asserted as a permanent fact here.

Because analytics cookies are not essential, they operate on our site subject to consent where the applicable law requires it. If you decline analytics cookies, the site still works completely; we simply lose the aggregate signal for your visit. Declining does not degrade any feature, does not change what content you can read, and does not affect how we handle a support enquiry you later send us. Analytics consent and support enquiries are entirely separate matters.

Consent: when we ask and what your choice means

Consent is the mechanism that governs non-essential cookies. In practice this means that essential cookies load because they are necessary to deliver the site, while analytics and any future non-essential cookies wait for your decision where the law requires prior consent. The consent banner or notice you see on arrival is how we present that choice, and your selection is then remembered so you are not asked repeatedly during normal browsing.

When you accept, you are permitting the categories described in the notice to operate for the period until the consent record expires or until you change your mind. When you decline, non-essential categories stay inactive and the site continues to function on essential cookies alone. A neutral option, such as closing the notice without accepting, is treated conservatively, meaning we do not read your silence as agreement to non-essential cookies.

Consent is specific, informed, and revocable. Specific means it applies to defined categories rather than a vague blanket permission. Informed means this policy exists so your choice is made with the facts available. Revocable means you can withdraw or change your decision later, and withdrawing is intended to be as straightforward as giving consent in the first place. Withdrawing consent does not reach back in time to erase aggregate measurements already recorded, but it stops further non-essential cookies from operating going forward.

The precise design of the consent interface, including whether it appears as a banner, a settings panel, or both, depends on the consent tool configured on the live site and may evolve. What does not change is the principle: non-essential cookies should not run on your device before you have had a genuine opportunity to say no. If you ever believe the site set a non-essential cookie before you consented, we would like to know, because that would be a configuration issue we would want to correct promptly.

Third-party cookies and services we rely on

Some cookies on our site are not set by us directly but by third-party services whose technology we use to run the website. The most common examples are an analytics provider that measures aggregate usage and a hosting or content-delivery layer that helps the site load quickly and securely. When these services run on a page, they may set their own cookies under their own control, and their handling of any resulting data is governed by their policies, not ours.

We are transparent about the limits of our knowledge here. We can tell you which categories of third party we rely on and why, and we can describe the privacy-protective settings we prefer to enable. What we cannot do is give you a guaranteed, permanently accurate internal account of another company's systems, because we do not operate them and their configurations change. The specific providers in use are confirmed against the live site during each review rather than presented as fixed facts on this page.

Where a third party offers meaningful privacy controls, our preference is to use them. For analytics this may include address masking and shortened retention. For hosting and delivery it typically means the third party sets only operational cookies needed for security and performance rather than anything used for advertising. We select providers with these considerations in mind, while being candid that our influence is limited to choosing reputable services and configuring the options they expose.

If you want the fullest picture of a specific third party's cookies, the most reliable source is that provider's own cookie or privacy policy, which they keep current for their own product. We are happy to identify the relevant providers on request so you can read their policies directly. We treat this openness as part of being an independent, privately run service: we would rather point you to an authoritative source than paraphrase another company's practices and risk describing them inaccurately.

How long cookies stay on your device

Cookie lifetime varies by purpose, and understanding the difference helps you decide what to keep and what to clear. The two broad types are session cookies, which vanish automatically when you close your browser, and persistent cookies, which remain for a set period defined when the cookie is created. Neither type is permanent in the sense of lasting forever; even persistent cookies carry an expiry date, after which the browser discards them.

On our site, many operational cookies are session cookies, present only for the duration of your visit. Their whole role is to keep a single browsing session coherent, so there is no reason for them to outlive it. When you close the browser, they are gone, and a fresh visit starts a new session with new session cookies.

Persistent cookies on our site are limited to a few clear purposes, chiefly remembering your consent decision and, where used, a low-risk preference such as language. These are given a lifetime long enough to be useful but not indefinite, so that your choices are eventually re-confirmed rather than assumed forever. Analytics cookies set by a third-party provider also carry their own durations, defined by that provider, which is another reason we point you to the provider's policy for exact figures.

We deliberately avoid quoting precise day counts as permanent facts in this policy, because platform and provider defaults change and a number written here could quietly become wrong. The durations configured on the live site are what actually apply, and they are checked during each review cycle. If you want to know exactly how long a given cookie will persist at any moment, the most authoritative source is your own browser's cookie inspector, which shows the real expiry date the site actually set, described in the next sections.

Managing cookies in your browser

Your browser is the most powerful and reliable tool for controlling cookies, because it governs every website you visit, not just ours. Every mainstream browser includes settings to view the cookies currently stored, delete some or all of them, and block future cookies according to rules you set. These controls sit within the privacy or security area of the browser settings, though the exact wording differs between browsers and versions.

Common controls worth knowing about include the option to clear browsing data, which lets you delete stored cookies in one action, and the option to block third-party cookies while allowing first-party ones, which is a balanced choice many people prefer. You can usually also set the browser to warn you before accepting cookies, or to delete all cookies automatically each time you close it, which combines convenience with a clean slate on every session.

Most browsers also offer a private or incognito mode. In this mode, cookies set during the session are typically discarded when you close the private window, which is a simple way to browse without leaving persistent cookies behind. It is worth understanding that private mode mainly affects what is stored on your own device; it is not, by itself, a comprehensive anonymity tool, and it does not change how a site's server handles a request.

Because the steps differ across browsers, the most current guidance is the help documentation published by your browser itself, which is kept up to date as the interface changes. Look for a section on cookies or site data. If you use several browsers or devices, remember that cookie settings are specific to each one, so a choice made in a desktop browser does not carry over to a phone. Managing cookies at the browser level complements the on-site consent choice: the consent notice governs our site specifically, while browser settings give you a wider, device-level backstop.

Do Not Track, global privacy signals, and their limits

Some browsers can send a Do Not Track signal or a more recent global privacy control alongside each request, indicating a general preference not to be tracked. These signals express an intention at the browser level rather than enforcing a technical block, so what happens in response depends on how each website chooses, or is required, to interpret them. The landscape here is uneven, because there is no single universal standard that every site follows in the same way.

We aim to respect a clearly expressed preference against non-essential tracking, and because our site does not run behavioural advertising or cross-site tracking in the first place, the practical gap between honouring such a signal and our default behaviour is small. Our analytics use is aggregate and consent-governed, and we do not operate the kind of tracking these signals are primarily designed to stop. In that sense, a privacy-minded visitor is already close to the outcome these signals seek.

It is important to be candid about limits. A browser signal cannot compel a third-party provider's technology to behave differently, and the exact way any given signal is interpreted may depend on the consent tool and providers configured on the live site. We would rather set an honest expectation than imply a guarantee we cannot fully control across every component of the page.

If reliably suppressing non-essential cookies matters to you, the most dependable approach is to combine tools: decline non-essential cookies in our on-site consent notice, and use your browser's own settings to block third-party cookies and clear cookies on exit. This layered approach does not rely on any single signal being universally honoured. It puts the decisive control where it is strongest, on your own device, while our consent notice handles the site-specific choice.

Cookies and the forms you submit to us

When you use a form on our site, for example to request a document review or ask a planning question, it is worth understanding how cookies relate to that action, because the two are often confused. Cookies help the form function smoothly during your visit, for instance by maintaining a session and by supporting a security check that guards against automated abuse. These are operational, essential-type cookies, and they are not the same thing as the personal information you deliberately type into the form.

The details you enter, such as your name, your production, or a description of your locations, are submitted to us because you chose to send them, and they are handled under our Privacy Policy rather than this Cookie Policy. Cookies are a transport and continuity mechanism; the substance of your enquiry is the content you provide. Declining analytics cookies has no effect on your ability to complete and submit a form, and it does not change how we treat the information once it reaches us.

We encourage a simple discipline when using any web form, including ours: share what is needed for the review and avoid pasting highly sensitive material into a general enquiry field. If a document review requires confidential files, we would rather arrange a secure method than have sensitive attachments travel through channels not designed for them. This is about good handling of your information, and it is described more fully in our document-security and privacy materials.

Because form behaviour depends on the tools configured on the live site, the specific cookies a form sets are confirmed during review rather than asserted permanently here. The principle, however, is stable: the cookies around a form exist to make it work and keep it secure, not to profile you, and the meaningful information in any enquiry is what you consciously choose to send, governed by our broader privacy commitments rather than by this page.

Children, sensitive information, and cookies

Our website and services are intended for production professionals and organisations planning to film in Nepal, not for children. We do not knowingly direct our site at minors, and we do not use cookies to build profiles of any visitor, let alone a child. Because our cookie use is limited to essential operation and aggregate analytics, we do not create the kind of individual behavioural record that would raise heightened concerns for younger users.

We also design our cookie use so that it does not gather sensitive personal information through the cookies themselves. The essential cookies hold operational identifiers rather than personal details, and the analytics cookies are configured toward aggregate measurement. Sensitive information, in the meaningful sense, generally reaches us only when someone deliberately shares it in an enquiry or a document, and that is governed by our privacy and document-security commitments, not by cookies.

If you are responsible for a minor who has used a shared device to visit our site, the practical step is the same as for any site: use the browser's cookie controls to clear stored cookies and, if you wish, block future ones. Because our cookies do not carry a rich personal profile, clearing them is straightforward and has no lingering consequence beyond re-showing the consent notice on the next visit.

We mention this category not because our site poses a particular risk to children or handles sensitive data through cookies, but because a responsible policy should say plainly where it stands. Our position is conservative: minimal cookies, aggregate analytics, no behavioural profiling, and a clear separation between cookies as an operational mechanism and the deliberate sharing of information that our privacy materials cover in depth.

How this policy relates to our other policies

This Cookie Policy is one part of a small set of documents that together describe how Film Permits Nepal handles information. It focuses narrowly on cookies and similar technologies on our website. Broader questions about the personal information you share with us, why we hold it, how long we keep it, and what rights you have over it, are addressed in our Privacy Policy, which is the primary reference for personal data.

Where confidential production documents are involved, our document-security materials describe how files are received, stored, access-controlled, and eventually deleted. That is a distinct concern from cookies: a document review is a deliberate exchange of sensitive material, whereas cookies are a routine website mechanism. Keeping these documents separate helps each stay focused and accurate rather than blurring operational website behaviour with the handling of client files.

Our terms of service and our independent-service statements sit alongside these privacy documents. They make clear that Film Permits Nepal is a private production-support service, not a government office or permit issuer, and that we do not guarantee outcomes such as approval, timing, or access. None of the cookies described here change that relationship; they simply support the website through which we describe and coordinate our support work.

If any conflict ever appears between this Cookie Policy and another of our documents on the specific subject of cookies, this policy is the more specific reference for cookies and should be read as governing that topic, while the Privacy Policy governs personal data more generally. Where a question spans both, we aim to answer it consistently, and if you spot an inconsistency we would welcome a correction request so we can align the documents. Our corrections process exists precisely so that visitors can help us keep this material accurate over time.

Changes to this Cookie Policy

We review and update this policy as our website, our tools, and the applicable expectations evolve. Because we rely on third-party services for analytics and hosting, and because those services change their own technology, a cookie policy that is never revisited would gradually drift out of step with reality. Our approach is to treat this document as living, updated first when something changes, rather than as a fixed statement written once and forgotten.

When we make a substantive change, such as adding a new category of cookie or adopting a new analytics provider, we update this page before or as the change takes effect, and where the change introduces non-essential cookies we seek consent before those cookies operate. Minor edits, such as clarifying wording or correcting a description, may be made without a prominent announcement, but the intent is always that the page reflects what the live site actually does.

We deliberately avoid pinning this policy to specific cookie names, exact durations, or a fixed list of providers as if they were permanent, because doing so tends to create quiet inaccuracies as configurations change. Instead we describe categories and principles that remain stable, and we confirm the specific details against the live site during each review. This keeps the policy honest: it promises what we can reliably stand behind and points you to authoritative sources for the fast-changing specifics.

Your continued use of the site after an update means the current version applies to your visit, and where consent is required for non-essential cookies, that consent is sought afresh rather than assumed from an earlier version. If a change is significant enough to affect your choices, the consent notice is the mechanism through which you can review and reset those choices. We encourage you to glance at this page from time to time, particularly if you are a returning visitor who set preferences some time ago.

Questions, requests, and reporting a concern

If anything in this policy is unclear, or if you want to know which specific cookies and providers are active on the live site, you are welcome to contact us. As an independent, privately run service, we would rather answer a direct question than have a visitor guess. We can identify the categories of third party we rely on so that you can consult their own cookie policies for the authoritative detail we do not control.

We also welcome concerns and corrections. If you believe a non-essential cookie ran before you consented, that a description here is out of date, or that the consent notice behaved unexpectedly, telling us helps us fix a genuine configuration issue. We maintain a corrections process precisely so that reports like these are logged and acted upon rather than lost, and cookie behaviour is included in that process.

For requests that concern your personal information more broadly, rather than cookies specifically, our Privacy Policy sets out the appropriate route and the rights that may apply to you. Because cookies and personal data overlap but are not identical, directing a request to the right document helps us respond accurately. If you are unsure which applies, contact us and we will help route the question; there is no need to diagnose it yourself.

When you contact us about cookies, a short description of what you observed, which browser and device you used, and roughly when it happened, helps us reproduce and understand the issue. You do not need technical detail; a plain account is enough. We treat these messages as useful signal about how the site behaves in the real world, which no amount of internal testing fully replicates, and we are grateful when visitors take the time to tell us what they saw.

Category	What it does	Consent basis	How to control it
Strictly essential	Supports navigation, security, load handling, and remembering your consent choice	Necessary to deliver the site you requested; no prior consent required	Blockable via browser settings, though some features may then misbehave
Analytics and performance	Measures aggregate usage so we can improve planning guides; does not identify you individually	Runs subject to consent where the applicable law requires it	Decline in the on-site consent notice, or block third-party cookies in your browser
Functionality or preference	Remembers low-risk choices such as language or display, only where used	Improves your own experience; consent applied where required	Clear or block via browser; the preference simply resets
Advertising or cross-site tracking	Not used on this site	Not applicable; no such category is active	Nothing to disable, because we do not run it

Frequently asked questions

Does Film Permits Nepal use cookies for advertising?

No. We do not run behavioural advertising, retargeting pixels, or cross-site tracking widgets, and our site does not include an advertising cookie category. Our cookie use is limited to essential operation, aggregate analytics, and occasionally a low-risk preference such as language. If we ever adopted anything in the advertising category, we would create a clearly labelled section for it, describe it on this page, and seek your consent before it operated.

Will the site work if I decline analytics cookies?

Yes, completely. Declining analytics cookies does not remove any feature, does not change what content you can read, and does not affect how we handle a support enquiry you later send. The only difference is that we lose the aggregate measurement signal for your visit, which we use to improve our planning guides. Essential cookies still load because they are necessary to deliver the site you asked to see.

What is the difference between a session cookie and a persistent cookie?

A session cookie exists only until you close your browser, after which it is discarded automatically. A persistent cookie remains for a defined period set when it is created, then expires and is removed. On our site, many operational cookies are session cookies, while persistent cookies are limited to purposes such as remembering your consent decision. Even persistent cookies are not permanent, because every one carries an expiry date.

How can I see exactly which cookies this site has set on my device?

Your browser's built-in cookie inspector is the most authoritative source, because it shows the real cookies and their true expiry dates as the site actually set them. You can usually find this in the privacy or security area of your browser settings, often under site data or stored cookies. This is more reliable than any written list, since a document can drift out of date while your browser always shows the current reality.

Why does this policy not list exact cookie durations and provider names?

We rely on third-party services for analytics and hosting, and those services change their own configurations over time. If we pinned precise durations or a fixed provider list here as permanent facts, the page could quietly become inaccurate. Instead we describe stable categories and principles and confirm the specific details against the live site during each review. For the fast-changing specifics, your browser's inspector and each provider's own policy are the authoritative sources.

Who sets the analytics cookies, us or a third party?

Analytics cookies are typically set by a third-party provider whose code runs on our pages, which means that provider ultimately controls the technology and operates under its own policy. We choose providers we consider reasonable and prefer privacy-protective settings such as address masking and shortened retention where they are offered. We are candid that we do not control another company's internal systems, and we are happy to identify the current provider on request so you can read its policy directly.

How do I withdraw consent after I have accepted cookies?

You can change your decision through the on-site consent mechanism, which is designed to let you review and reset your choices as easily as you gave them. You can also clear cookies through your browser, which removes the stored consent record and causes the notice to appear again on your next visit. Withdrawing consent stops further non-essential cookies from operating going forward, though it does not erase aggregate measurements already recorded.

Do you respect Do Not Track or global privacy signals?

We aim to respect a clearly expressed preference against non-essential tracking, and because our site does not run behavioural advertising or cross-site tracking, the practical gap between honouring such a signal and our default behaviour is small. We are honest that a browser signal cannot compel a third-party provider's technology to behave differently in every case. For the most dependable result, combine declining non-essential cookies on our site with your browser's own settings to block third-party cookies.

Are cookies the same as the information I type into a form?

No, and it is a common confusion. Cookies are an operational mechanism that helps a form function and stay secure during your visit, such as maintaining a session and supporting a security check. The details you deliberately type, such as your name or production locations, are separate information submitted because you chose to send it, and it is handled under our Privacy Policy rather than this Cookie Policy. Declining analytics cookies has no effect on your ability to submit a form.

Does blocking cookies in my browser affect other websites?

Yes. Your browser's cookie settings apply to every site you visit, not just ours, so blocking or clearing cookies at the browser level is a device-wide control. Settings are also specific to each browser and device, so a choice made on a desktop browser does not carry over to a phone. This makes browser controls a powerful, wide-reaching backstop that complements the site-specific choice offered by our consent notice.

Is this site or its cookies intended for children?

No. Our website and services are intended for production professionals and organisations planning to film in Nepal, not for children, and we do not knowingly direct our site at minors. Our cookie use is limited to essential operation and aggregate analytics, so we do not build an individual behavioural profile of any visitor. If a minor has used a shared device to visit, clearing cookies through the browser is straightforward and has no lingering consequence beyond re-showing the consent notice.

What should I do if I think a cookie ran before I consented?

Please tell us. If a non-essential cookie appears to have operated before you had a genuine opportunity to decline, that would be a configuration issue we would want to correct promptly. A short account of what you observed, which browser and device you used, and roughly when it happened, helps us reproduce and fix it. We include cookie behaviour in our corrections process specifically so that reports like this are logged and acted upon rather than lost.

Does using private or incognito mode stop all cookies?

Private or incognito mode typically discards cookies set during the session when you close the private window, which is a simple way to avoid leaving persistent cookies behind. However, it mainly affects what is stored on your own device and is not, by itself, a comprehensive anonymity tool, nor does it change how a site's server handles your request. For stronger control, combine private mode with declining non-essential cookies and blocking third-party cookies in your settings.

Where should I go for questions about my personal data rather than cookies?

Our Privacy Policy is the primary reference for personal information: what we hold, why, how long, and what rights may apply to you. Cookies and personal data overlap but are not identical, so directing a request to the right document helps us respond accurately. If you are unsure which applies, contact us and we will help route the question. For confidential production documents specifically, our document-security materials describe how files are received, stored, and deleted.