Dayrook · Operated by RadiantOS
Providers and Subprocessors
A provider’s role depends on the processing it performs. This page distinguishes services used by the public website from providers that may be relevant to a separately contracted customer deployment. A brand listing is not a claim that a particular vendor agreement or transfer safeguard has been executed.
1. Current website providers
| Provider | Website role and information | Location or boundary |
|---|---|---|
| Vultr | Hosting for the public marketing service; network requests and information needed to serve the website and route supported requests. | US production infrastructure. This is not a promise that every external service stays in the US or in an inquiry-selected region. |
| Cloudflare (including Turnstile) | Website delivery, proxying and security, including request and network information; Turnstile also uses technical signals to protect inquiry forms from automated abuse. | Global edge processing is not limited to the US origin. Provider processing follows its applicable privacy terms, including Turnstile terms; its role can include independent controller purposes. |
| PostHog | Optional consented website analytics: paths, interactions, click positions, visible-section time and browser/session information. Selected assessment categories and coarse pricing bands or option flags are included; contact details, free-text inquiry contents, URL query strings, session replay and advertising profiles are excluded. | US PostHog project. The browser’s inquiry-region selection does not change it. |
| Calendly | External walkthrough scheduling; information you enter there and booking information supplied to us. | Separate provider website and privacy practices. Our website analytics preference does not control it. |
The provider’s own terms identify its contracting entity and processing arrangements. We do not infer a legal entity, headquarters, complete processing-country list or transfer mechanism solely from its brand name.
2. Customer-service providers and integrations
The provider register for a customer service must be established for its actual order before Customer Personal Data is sent to a provider. It must identify the contracting entity, processing purpose, permitted data and location, authorization and applicable transfer protection. This website list is not an exhaustive or executed register for every customer deployment.
Depending on the services actually contracted and connected, the relevant providers may include hosting and storage, payment processing, transactional email, error monitoring, product analytics, customer-selected AI, or Microsoft and Google integrations. A provider you contract with directly may act independently rather than as our subprocessor. Availability in a product description does not establish that a provider is engaged for your data.
Ask the legal contact for the register applicable to the service you are considering. Do not send production personal data on the assumption that this general page has completed the necessary customer-specific authorization.
3. Authorization, changes and objections
For customer data we process on your behalf, the accepted DPA sets the authorization, advance-change notice, objection, downstream protection and responsibility rules. Posting a new provider name here does not replace a required direct notice or your contractual right to object.
For website information we handle as controller, the Privacy Policy explains purposes, disclosures, choices, retention and rights. We will update the applicable notice and obtain any required consent before materially changing an optional processing purpose.