What staysin your browser.
Effective date September 20, 2026 · Document version 2026-09-20
These pages remember your cookie and motion preferences. The dashboard stores what it needs to keep you signed in, and a note of two things you chose. This policy names every item on every address.
Three addresses carry Devexana in a browser: the pages you are reading at devexana.com, the Devexana Cloud dashboard at devexana.com/app, and the sign-in page Amazon Web Services operates for us. This policy says what each one puts in your browser, why, for how long, and who sets it.
1. What this covers
A cookie is a small file a site asks your browser to keep and send back on the next request. Session storage and local storage are two other stores the same browser keeps, which a page can read and write but which are never sent anywhere on their own. This policy covers all three, because the honest question is what a site keeps on your machine, not which mechanism it used.
It does not describe the Devexana software running on a customer’s own appliance. That is not a website and it keeps nothing in a visitor’s browser. What it holds, and what it never sends us, is in our Privacy Policy.
2. Your website preferences
The marketing pages set no advertising or analytics cookies. They store devexana.site.preferences.v1 in local storage on this domain. It remembers whether you allow Google Calendar and whether you prefer reduced animation. Devexana sets this preference after your choice; it remains until you change it or clear your browser storage.
Use to change either choice. Essential only keeps the calendar off. All product illustrations are served from this site.
3. The booking calendar
The booking calendar is served by calendar.google.com. When you select Show appointment times in the booking area or allow it in cookie settings, its frame loads on the home page and Google receives your browser’s request. Google may use its own cookies or storage under its own terms. Devexana does not receive those cookies.
Choose Essential only to keep the embed off, or open the booking page separately using the link beside it. The product films and campus illustration do not contact Google Maps.
4. The dashboard at devexana.com/app
Devexana Cloud is the web dashboard where a customer’s staff sign in to see the appliances their organization has registered. It sets no cookies. It keeps five items in the browser’s own stores, and the table below is all of them.
| Name | Type | Purpose | Duration | Party |
|---|---|---|---|---|
oidc.user:<authority>:<client id> |
Session storage | The signed-in session, including the tokens the dashboard attaches to each request it makes. | Until the tab closes. | First party, Devexana |
oidc.<state> |
Session storage | The state value and the PKCE verifier for one sign-in attempt, so the dashboard can tell that the reply it gets back answers the request it sent. | Seconds. Deleted when you return from the sign-in page. | First party, Devexana |
devexana.invite |
Session storage | An invitation code, carried across the sign-in redirect so a code you opened before signing in is still there when you come back. | Until it is redeemed, or the tab closes. | First party, Devexana |
devexana.org |
Local storage | Which organization you last looked at, so the dashboard opens on it next time. | Until you clear site data. | First party, Devexana |
devexana.cloud.columns.v1:<register> |
Local storage | Which columns you chose to show in a table. One entry per table. | Until you clear site data. | First party, Devexana |
None of these is a cookie, and none is sent anywhere by the browser on its own. The dashboard reads them and decides what to put in a request. No other site can read them, and they reach no other site.
The three session items die with the tab, which is why they are held there rather than in local storage: a signed-in session that outlives the tab is a session somebody else can find. The two local-storage items are preferences. Clearing them costs you a remembered organization and a column choice, and nothing else.
5. The sign-in page
Signing in sends you to devexana-login.auth.us-east-1.amazoncognito.com, a page Amazon Web Services operates for us under its Amazon Cognito service. While you are on that page it sets its own cookies, on its own address: a session cookie that carries you through the steps of signing in, and an anti-forgery cookie that ties the form you submit back to the page you were given.
We name the categories rather than the individual cookies because Amazon sets them, Amazon can change them, and a list we copied out today would be wrong the week Amazon changed one. They are strictly necessary: without them the page cannot complete a sign-in. They belong to amazoncognito.com, they cannot be read by devexana.com, and nothing stored by devexana.com can be read by them.
Section 5C of the Privacy Policy lists Amazon Web Services among the providers we use and says what it does for us.
6. What we do not do
On none of these addresses do we run analytics, advertising, cross-site tracking, or tracking pixels. There is no analytics cookie, no advertising cookie, no pixel, no tag manager, and no cookie or stored value that follows a reader from this site to another one. We do not sell or share what a browser does here, because we do not collect it.
On the dashboard that is a security position as much as a privacy one. The signed-in session sits in browser storage on devexana.com, and any script this site loaded could read it. Keeping the script list at nothing but our own is what keeps that list short, and adding a third-party snippet to this site would be a decision about customers’ signed-in sessions, not a decision about marketing.
7. How to refuse
Every browser can block cookies and site data, for one site or for all of them, in its own settings. Cookie settings also lets you turn off the Google Calendar embed and reduce animations.
- The marketing pages work with browser storage blocked; your preference will need to be chosen again on the next visit.
- The calendar frame loads only when allowed in Cookie settings, and blocking third-party cookies stops Google’s from being set. The booking page also opens in a tab of its own.
- The dashboard cannot keep you signed in without session storage. Blocking it does not fail quietly: the sign-in does not complete and you are returned to the sign-in page. Local storage is optional. Block it and the dashboard forgets your organization and your column choices between visits, and works in every other respect.
Clearing site data for devexana.com signs you out of the dashboard and clears your saved site and dashboard preferences. It does not delete your account or anything held about it.
8. How to contact us
Questions about this policy go to legal@devexana.com, or by post to DEVEXANA LLC, PO Box 1, Demarest, New Jersey 07627, marked for the attention of the privacy contact.
What personal information we hold, why, and how to see or correct it, is in our Privacy Policy. This policy is a companion to it, not a replacement for it. When either changes we publish the new version here with a new date on it.