Cookie Policy

01What cookies are

Cookies are small values a website asks your browser to store and send with later requests. They can support sessions, request security, preferences or tracking. Local storage and session storage are separate browser features; their use should also be explained when a website relies on them.

A cookie’s name does not by itself establish its purpose. The behaviour of the application and any third-party scripts matters. This page describes the current public website rather than the separate applications we build for clients.

02Current first-party cookies

The Laravel application may issue a first-party session cookie and an XSRF-TOKEN cookie. The session cookie links requests to session state; XSRF-TOKEN supports protection against forged requests if a feature submits data. These are technical cookies, not advertising identifiers.

The current session configuration has a 120-minute lifetime. Session-cookie names can change with deployment settings; the local default is laravel-session. XSRF-TOKEN generally follows the configured session lifetime. Deployment settings and the cookies actually issued should be checked when the website is published or reconfigured.

03Analytics and advertising

The current website source does not include Google Analytics, advertising pixels or another visitor-tracking SDK. We therefore do not list a fictional analytics provider or display a consent choice for a tracker that is not installed.

If analytics or advertising technology is introduced, this page should name the tool, purposes, storage and retention. Any required notice and choice must be implemented for the actual behaviour before non-essential tracking starts. A policy paragraph alone does not implement a consent mechanism.

04Preferences and browser storage

The current navigation, card effects and animation pause control operate in the page; they do not save your selection in local storage or session storage. Your device’s reduced-motion preference controls whether animations run.

If we later save language, accessibility or other preferences, we will explain the values stored and how long they last. Client applications may have different storage behaviour and need their own notice.

05External websites and embedded services

A normal external link does not embed the linked website’s tracking script in this page. Once you open an external service, its own cookie and privacy settings apply.

If third-party videos, maps, chat widgets or social content are embedded in future, their loading and storage behaviour must be reviewed and described. The current public website does not use those embedded widgets.

The contact form loads Cloudflare Turnstile for spam protection. This verification service connects your browser to Cloudflare and is separate from advertising or website analytics. Blocking the verification script can prevent the form from being submitted; you can contact us by email instead. Cloudflare explains its technical processing in its Privacy Policy.

06Managing or removing cookies

You can inspect and delete cookies using your browser’s site-data or privacy settings and control whether it accepts future cookies. The steps differ between browsers and devices. Deleting a session cookie ends the associated session; blocking technical cookies may affect features that depend on them.

Browser controls are separate from any website choice offered for non-essential tracking. We do not promise that deleting browser storage also deletes project emails, invoices or server logs; those are handled under the Privacy Policy.

07Deployment changes and verification

Server middleware can issue cookies even when a page has no form. Cookie behaviour should be checked on the deployed domain, including expiry and the settings used for secure delivery. Local development settings do not establish the configuration of an AWS-hosted release.

A hosting change, added collection feature or new script can require an update to this notice. The date on this page identifies the reviewed website version, not a claim that every future deployment has the same settings.

08Questions about cookies

Email info@orionsuite.in if you see a cookie you do not understand or have a question about browser storage. Include the website address and cookie name, but do not send its value: session and security-cookie values can be sensitive.

For how OrionSuite handles enquiry information, project data and technical logs, read the Privacy Policy.