Cookie Policy
Last updated
Effective date: July 21, 2026
This Cookie Policy explains how Saras Holding ("Saras Holding," "ItemsInView," "we," "us," or "our") uses cookies and similar browser-storage technologies on itemsinview.com and itemsinview.app (collectively, the "Service"). It should be read with our Privacy Policy.
1. What cookies are
A cookie is a small text record a website asks a browser to store and return with later requests. Cookies can support authentication, security, preferences, analytics, or advertising, depending on how they are used.
ItemsInView currently uses only strictly necessary, first-party cookies needed to authenticate users, complete multi-factor authentication, maintain secure sessions, and protect the Service. We do not currently use advertising cookies, cross-site behavioral tracking cookies, or third-party analytics cookies.
2. Cookies currently used
| Cookie | Who receives it | Purpose | Typical duration |
|---|---|---|---|
iiv_account_session | Signed-in ItemsInView account holders | Authenticates the global account, maintains the server-side session, and supports authorized access and vault switching. | Up to 30 days, but may end earlier because of inactivity, sign-out, password reset, account action, or vault security policy. |
iiv_account_mfa_challenge | Users completing account sign-in | Temporarily identifies a sign-in that passed the password step and must complete multi-factor authentication. It is not a full authenticated session. | Approximately 5 minutes or until verification, cancellation, or replacement. |
iiv_super_admin_session | Authorized Saras Holding platform operators only | Authenticates access to the separate Super Admin Console and records completion of its required security steps. This cookie is not used for an ordinary Member or Vault Admin session. | Up to the applicable server-side session expiry and may end earlier because of sign-out, inactivity, reset, or administrative action. |
The Service may instruct a browser to delete obsolete cookies from earlier versions of ItemsInView (for example, a legacy iiv_vault_session cookie) by sending an expired cookie with a zero-second lifetime. This deletion instruction removes stale authentication state and does not create an active tracking identifier.
3. Cookie security and scope
Authentication cookies are configured with safeguards designed to reduce misuse:
- HttpOnly: browser scripts cannot read the cookie;
- Secure in production: the browser sends the cookie only over HTTPS;
- SameSite=Lax: reduces many cross-site request risks while allowing ordinary top-level navigation;
- Path=/: the cookie is available to the applicable ItemsInView host; and
- host-only: no broad
Domainattribute is set.
Because the cookies are host-only, itemsinview.com and itemsinview.app maintain separate browser-cookie state. Signing in on one domain does not necessarily sign you in on the other, even though this Policy covers both.
The raw session or challenge token is stored in the cookie. ItemsInView stores a one-way hash of that token on the server, so possession of the database value alone is not intended to create a usable browser session.
4. Similar technology: session storage
ItemsInView uses the browser's sessionStorage for a limited interface function:
| Storage key | Purpose | Duration |
|---|---|---|
coverage-alert-dismissed:<vault-address> | Remembers that a signed-in user dismissed the coverage-expiration alert for the current vault during the current browser-tab session. It contains a simple dismissal marker, not item or policy contents. | Until the browser tab/window session ends or the user clears site data. |
sessionStorage is separate from cookies and is not automatically sent with network requests. Rules applying to cookies may also apply to similar device-storage technologies in some jurisdictions.
5. Strictly necessary status and consent
The authentication and security cookies described above are essential to provide the signed-in Service requested by the user. Without them, ItemsInView cannot securely establish or maintain account and vault access. The session-storage dismissal marker supports the requested signed-in interface and lasts only for the tab session.
Where applicable cookie law provides an exemption for technologies strictly necessary to deliver a requested online service or protect its security, we rely on that exemption and do not request consent for these technologies. For that reason, ItemsInView does not currently display a cookie-consent banner.
If we introduce non-essential cookies or similar technologies—such as advertising, non-exempt analytics, persistent optional preferences, or third-party tracking—we will update this Policy and implement an appropriate consent or opt-out mechanism before using them where required.
6. Third parties and external links
ItemsInView does not currently embed third-party advertising or analytics scripts that set cookies through the Service. Our infrastructure providers may process technical request information on our behalf as described in the Privacy Policy, but the ItemsInView application does not intentionally expose third-party tracking cookies through its pages.
The Service may contain links to third-party sites, including authenticator-app pages or app stores. If you follow a link, the destination site may set its own cookies under its own policy. Saras Holding does not control cookies set after you leave ItemsInView.
7. Managing cookies and site storage
Most browsers allow you to view, delete, or block cookies and site storage. Consult your browser's settings or help documentation for instructions.
Blocking or deleting ItemsInView's essential cookies will not prevent access to public pages, but it will prevent or interrupt sign-in, multi-factor authentication, vault access, and other authenticated functions. Deleting session storage may cause a dismissed coverage alert to appear again during a new tab session.
You can also remove an active account cookie by using the Service's Sign out control. Server-side sessions may remain subject to revocation, expiry, and security records even after the browser cookie is removed.
8. Changes to this Policy
We may update this Cookie Policy when technologies, providers, law, or Service features change. The public page will show the latest update date. Material changes will receive additional notice or consent controls where required.
9. Contact us
Questions about our use of cookies or similar technologies may be sent to:
Saras Holding
11430 NW 5th St
Plantation, FL 33325
United States
Email: info@sarasholding.com