VialRelay · Legal & privacy
Cookie Policy
The storage and external services identified in the website implementation.
- Version
- 1.0
- Approval status
- Awaiting company approval
- Publication / effective date
- Not published · No effective date
- Last updated
Prepared for company review. This version is not company-approved or an effective published policy. Factual and approval requirements remain outstanding.
1. Audit scope
The current application source does not install an analytics SDK, advertising pixel, marketing cookie or cookie-consent banner. This is a source audit, not confirmation that the production host injects no additional technologies. Production cookies, logs and scripts must be checked before final approval.
2. Cookies and authentication storage
The application does not explicitly set document cookies for public marketing pages. Cloud authentication support is configured to persist sessions in localStorage and refresh tokens when a session exists. The public Client Login page does not currently provide a working account sign-in. LocalStorage is browser storage, not a cookie.
Editor preview authentication may use brokered storage supplied by the hosting environment. It should not be confused with a customer account or a published client portal. No fixed cookie or token duration is asserted because the relevant production settings have not been verified.
3. Form protection
Contact and prepared industry/partner forms use a server-signed challenge held in page memory, a hidden honeypot, a minimum submission delay and server validation. Inquiry challenges expire after one hour. The server keeps accepted inquiries for duplicate matching and rolling per-email rate limits; this is not an advertising cookie.
Privacy-request intake uses its own purpose-bound challenge and private acceptance records. Its challenge is also kept in page memory and expires after one hour. Entered form values are not deliberately written to localStorage by these form components; browser autofill may retain information under your browser settings.
4. External providers
Google Fonts is loaded from Google-hosted resources and can receive normal connection metadata such as your IP address and browser headers. Font requests are not evidence that an analytics or advertising cookie is installed.
Instagram and LinkedIn links are not embedded social tracking widgets. Selecting a link leaves the website or attempts to open the corresponding mobile app, after which that service’s storage and privacy practices apply. Hosting and diagnostic behavior outside the application source must be separately verified.
5. Choices and duration
You can clear cookies and localStorage, adjust autofill and restrict storage in browser settings. Clearing authentication storage may remove an existing editor or authorized session. Blocking resources can affect fonts or other functionality.
No optional tracking consent interface is added on the basis of technologies that are not installed. If nonessential tracking is introduced, VialRelay must reassess applicable consent requirements and prevent consent-dependent tracking from starting before valid consent. Storage durations not determinable from current settings must be confirmed before publication.
6. Updates and questions
Technology changes require a fresh inventory and updates to this policy. Contact info@vialrelay.com for questions about cookies or browser storage. The Privacy Policy describes inquiry information and provider processing.