1. The current website
The website does not use advertising pixels or third-party marketing analytics. Optional first-party conversion counts are disabled until you allow them through website privacy preferences. The application uses browser storage for your consent choice, workspace sign-in and a chosen appearance preference. Local storage is information saved by your browser for this site; it is a separate technology from cookies.
2. Sign-in storage
The workspace saves a session credential after sign-in and uses it to authenticate organization requests. Signing out removes it; rejected sessions are also removed. The credential expires according to the session settings, although a stored value may remain in the browser until removed. Clearing this storage signs you out of the console.
3. Appearance preference
If you choose a console theme, the application saves the choice to remember light, dark, or system appearance. The value remains until you change it or clear the site’s browser data. This preference is not used for advertising or cross-site tracking.
4. Optional usage counts and consent preference
The website saves your allowed or declined choice in first-party browser storage. Allowing counts sends only the event name, public page, capability category, time and a hashed abuse-control identifier. It does not send form values or patient information. Use website privacy preferences in the footer to withdraw permission at any time; future optional counts stop. Clearing site data removes the choice and returns optional counts to off.
5. Your controls
You can sign out of the console to remove the session credential and use your browser’s site-data settings to remove stored values for this domain. Browser controls can also block storage. Blocking authentication storage may prevent sign-in; removing the theme preference returns appearance to its default. These controls do not delete information already stored in an organization’s workspace or by a connected service.
6. Third-party destinations and hosting
The website loads typefaces from Google Fonts through network requests to Google’s font-hosting services. This is separate from the first-party browser storage described above. Following a link to a calendar service or another external website takes you to a service with its own storage and privacy practices. Hosting infrastructure may add security or routing technologies that are not part of this application code. The operator must verify the deployed website and update this notice for any such technologies.
7. Future changes
Any change to usage counts, embedded media, advertising or other browser technologies requires this inventory to be reviewed. Applicable notices, preferences, and consent controls must be implemented before technologies requiring them are activated. For questions about the current site, request a private follow-up through our contact page.