Scope and operator
This page supports Redomon’s global B2B SaaS. The operator is based in Argentina; the service is not limited to the Argentine market. Applicable privacy and other mandatory laws depend on the relevant processing and jurisdiction.
Redomon is operated by Manuel García Nicastro, CUIT 20-50046009-2, La Plata, Argentina. Contact hello@redomon.com about cookies, local storage and similar technology. The privacy notice explains associated personal-data processing.
Storage on our pages
Our public website and workspace use necessary authentication, session and security storage and a local appearance preference. They do not use advertising trackers or cross-site advertising profiling. Product Analytics integrations on customers’ websites and applications are distinct from browser storage used to operate Redomon’s own pages; the customer selects its integration, identifiers and collection settings and supplies required notices and consent controls.
Authentication
Clerk’s authentication components may use first-party cookies and browser storage to establish and maintain a signed-in session, prevent misuse and support account flows. These are necessary to supply the authenticated service you request. Disabling them may prevent sign-in, organization switching or other account functions. This does not mean every cookie a vendor could offer is necessarily exempt from consent; only the actual necessary configuration is covered.
Security challenges
Cloudflare may use security or challenge cookies when needed to distinguish legitimate traffic and protect the service. Their presence depends on the active security configuration and requests. Server request logs and network metadata are distinct from storing a cookie and remain covered by the privacy notice.
Appearance preference
Redomon uses the first-party local-storage key redomon.theme.v1 when you choose light, dark or system mode. This preference has no automatic expiration for this key; it remains until overwritten or cleared. This remembers your requested presentation on the same browser and is not used to identify you for advertising. You can reset it through appearance controls or clear browser storage. It should persist only as needed to honor that choice or until you clear or reset it.
Provider-hosted flows
Polar-hosted checkout and customer-portal pages and provider-hosted authentication pages may use their own necessary payment, security and session technologies under their notices. We cannot describe an unrelated provider page as if it were cookie-free. Redomon should not load optional provider tracking on its own pages without the disclosures and choices applicable to it.
Consent and optional analytics
Necessary storage does not require opt-in where applicable law provides an exemption. A preference stored solely in response to your choice may qualify for the relevant user-requested functionality exemption; we will obtain consent if the actual implementation or local law requires it. We do not infer optional tracking consent from account registration, payment or continued browsing.
Optional analytics or other nonessential browser storage on our own pages requires a disclosure of provider, identifiers, purpose, first- or third-party status, duration and relevant transfers, with prior consent where required. A customer using Product Analytics is responsible for the corresponding inventory and consent on its own property. Rejecting or withdrawing optional consent must be as easy as granting it and must not disable unrelated core features. A cookie banner is not a substitute for stopping nonessential scripts before consent.
Browser controls
You can delete cookies and local storage in your browser’s site-data settings, block cookies or use private browsing. This may sign you out, remove appearance choices or interrupt checkout. Settings on one browser or device do not necessarily affect another.
Provider technology and changes
Provider cookie identifiers, scope and lifetimes depend on the authentication, challenge or checkout flow and its configuration. Refer to the provider’s notice and browser site-data controls for those flows, or contact us for assistance. A server-side event alone does not establish that consent is unnecessary; other privacy and electronic-communications rules may apply to the associated collection and identifiers.
Material changes will be reflected in the version date, with new consent obtained where legally required before activating new optional purposes.