Disclaimer

This Disclaimer takes effect on 31 August 2026 and explains important limits of information, measurements, automation, connected services, and generated output available through Ignorre. Ignorre is a product and service brand operated by CX24 Digital Technologies Pvt. Ltd. (“CX24”).

This Disclaimer supplements the Terms and Conditions, Privacy Policy, and the Order or service-specific agreement that applies to a Customer. An express commitment in an accepted Order controls to the extent it conflicts with this general Disclaimer. Nothing here excludes a warranty, remedy, duty, or liability that applicable law does not permit CX24 to exclude.

A visible page, workspace, control, integration, record, workflow, metric, or plan does not by itself prove that a provider is connected, a feature is included in an Order, or an external operation completed.

• Recorded state reflects information stored by Ignorre. It may be a Customer entry, local workflow state, or earlier provider response and may not match current external state.
• Observed or measured state reflects a lookup or test limited by its source, target, scope, method, conditions, and timestamp.
• Calculated or recommended state is derived from available information and assumptions; it is not an authoritative provider response or guaranteed outcome.
• Provider-verified state reflects a successful check against the identified provider resource at the stated time. The provider or resource can still change afterward.
• Pending state means completion has not been confirmed. Unavailable or activation-required actions submit nothing and must not be treated as successful.
• Sample, preview, draft, sandbox, OTE, and production states serve different purposes. A test-environment result does not prove that a live registry, provider, payment, delivery, or publishing operation is enabled.

Domain and DNS evidence can be delayed, cached, incomplete, rate-limited, redacted, inconsistent, or ambiguous. The responsible registry and registrar-of-record make the authoritative decision for a domain operation.

• A search result does not reserve a name, create ownership, or guarantee registration, transfer, renewal, restoration, contact change, nameserver change, authorization code, or price.
• A domain shown as potentially available can become unavailable before a registry accepts the registration. A domain shown as unavailable can reflect a registry reservation, premium rule, policy restriction, unsupported TLD, data-source limit, or temporary response.
• RDAP, WHOIS, DNS, certificate, and public-web results are informational. Redaction or missing data must not be interpreted as proof of absence, ownership, identity, authority, safety, or wrongdoing.
• Registry, ICANN, registrar, dispute-provider, rights-protection, court, government, abuse, sanctions, and legal requirements can affect status and data handling independently of the Ignorre interface.
• Transfers, renewals, expirations, redemption, restoration, and deletion follow TLD-specific lifecycles. Reminders and automation reduce administrative effort but do not guarantee completion or recovery.

Domain prices can depend on TLD, registry classification, premium status, term, currency, tax, provider fee, redemption state, and timing.

• A payable offer exists only when the relevant commercial catalog or provider confirms a price and CX24 accepts the Order. A placeholder, historical, estimated, cached, or unsupported price is not an offer.
• A reseller, employee, or delegated administrator acts under separate authority. Its access does not prove domain ownership, registrant consent, accreditation, or authority beyond the permissions actually granted.
• Reseller branding, pricing, statements, and support commitments are the reseller’s responsibility unless an accepted agreement expressly makes CX24 responsible.
• A registry command may be immediate, irreversible, and externally chargeable. Customers must review the exact name, TLD, term, contacts, nameservers, renewal setting, and price before confirmation.

Infrastructure functions depend on provider systems, capacity, credentials, permissions, resource bindings, networks, software, Customer configuration, and Internet conditions outside CX24’s complete control.

• Provisioning, power state, reinstall, scaling, snapshots, backups, restores, certificate issuance, monitoring, and publishing can be delayed, rejected, unsupported, or fail after a request.
• A dashboard status or successful API response does not by itself prove end-to-end public availability, data integrity, recoverability, security, or correct application behaviour.
• DNS and DNSSEC changes can interrupt websites, email, certificate validation, and other services. Propagation depends on authoritative servers, resolvers, caches, TTL values, delegation, and third parties.
• A backup or snapshot is not a recovery guarantee unless the applicable Order states the coverage and it has been tested for the relevant resource. Customers should maintain independent copies proportionate to their risk.
• Service levels, response targets, resource guarantees, maintenance commitments, backup coverage, recovery objectives, and security features apply only when expressly stated in an accepted Order.

Mail delivery depends on sender authorization, message content, DNS, provider queues, recipient systems, reputation, filtering, policy, rate limits, and network conditions.

• A sent, accepted, queued, relayed, or delivered status has a specific technical meaning and does not necessarily mean that a human received, opened, read, trusted, or acted on the message.
• MX, SPF, DKIM, DMARC, MTA-STS, TLS reporting, certificates, and monitoring can improve security and evidence but do not guarantee delivery, inbox placement, reputation, encryption for every hop, or freedom from spoofing and abuse.
• Deliverability diagnostics are point-in-time observations and can differ across resolvers, networks, providers, recipients, and later tests.
• Customers remain responsible for lawful recipients, consent, suppression, message content, sender identity, anti-spam compliance, and appropriate handling of bounces and complaints.

Events, audits, rankings, recommendations, forecasts, scores, performance findings, and reports are decision-support tools based on the sources and measurement conditions available at the time.

• CX24 does not guarantee indexing, rankings, visibility, traffic, authority, backlinks, Core Web Vitals, accessibility, conversion, revenue, lead quality, or another business or technical result.
• Unknown, unsupported, or unmeasured values should remain unavailable rather than being interpreted as zero, success, failure, or a hidden estimate.
• First-party analytics can miss visitors, devices, blockers, consent choices, cross-device activity, private browsing, bots, attribution, and offline outcomes. It is not a complete or independently audited business record unless an Order expressly says so.
• Monitoring checks are samples from defined locations and times. A successful check does not prove uninterrupted availability, and a failed check does not always prove a full outage.

AI-generated text, code, metadata, designs, recommendations, analysis, summaries, and assistant responses can be inaccurate, incomplete, insecure, biased, outdated, inaccessible, or unsuitable.

• Review output for factual accuracy, functionality, security, licensing, intellectual property, accessibility, privacy, confidentiality, and legal compliance before relying on, sending, deploying, or publishing it.
• A confident or detailed response is not proof that its facts, citations, configuration, code, or conclusion are correct. Verify important matters against authoritative sources and the affected system.
• Do not use automated output as the sole basis for a legally significant decision about a person or for a high-impact production change without appropriate authority, testing, safeguards, and qualified human review.
• AI availability, model behaviour, retention, location, limits, and output can change with provider configuration. A disabled capability sends no prompt to a provider and produces no live provider result.

A website preview, template, generated project, source export, deployment plan, or publishing control is not proof that a public site has been safely deployed or is suitable for production.

• Generated or exported projects require independent review of dependencies, licenses, secrets, security, forms, payments, privacy, accessibility, content, SEO, performance, browser behaviour, and hosting configuration.
• A preview can differ from the deployed environment because of domains, DNS, certificates, environment variables, provider APIs, content, caching, browser support, and build settings.
• Customers must have rights to all text, images, marks, fonts, code, data, and other material used and must obtain any notices, consents, or professional review required for the published site.
• Publishing occurs only through an enabled and confirmed deployment capability. Saving a draft, generating source, or clicking an unavailable control does not publish anything.

A project brief, budget, timeline, message, attachment, milestone, staff assignment, status, or preview is part of a managed request-and-review workflow and is not an open freelancer marketplace.

• Submitting a brief does not create a statement of work, hiring relationship, delivery guarantee, fee, payment obligation, acceptance criterion, service level, or intellectual-property transfer.
• Binding scope, dates, fees, responsibilities, acceptance, warranties, and ownership arise only from an accepted Order or statement of work.
• Customers must review deliverables for accuracy, security, licensing, accessibility, privacy, compliance, and fitness for intended use. A delivered or approved workflow status does not replace specialist review where one is needed.

A legacy document expressly marked “SAMPLE RECORD — NOT PAYABLE — NOT A TAX INVOICE” is a non-commercial example preserved with its original provenance.

It is not a payment request, tax invoice, receipt, proof of payment, quote, contract, or evidence that a Service was ordered or delivered. It cannot enter production payment, revenue, collection, suspension, renewal, chargeback, or refund workflows. A separately identified production invoice must be supported by an accepted Order, usage record, renewal, statement of work, or other applicable agreement.

Registries, registry service providers, other registrars, hosting providers, payment and identity services, AI providers, search engines, websites, networks, and other third parties operate independently and can apply separate terms and privacy notices.

• An integration option, provider name, compatibility statement, or external link does not establish endorsement, accreditation, universal availability, or a contractual relationship for every Customer.
• CX24 cannot control or guarantee an independent third party’s content, systems, security, decisions, policies, availability, pricing, or acts, subject to any responsibility that cannot lawfully be excluded.
• Customers should evaluate third-party terms, privacy, security, data location, support, continuity, and suitability before enabling an integration or relying on external information.

Security indicators, diagnostics, checks, alerts, suggested configurations, and help content can reduce risk but cannot prove that a system is secure or free of vulnerabilities, compromise, malware, fraud, or abuse.

• A passed check covers only the tested condition, target, and time. It does not replace threat modelling, secure development, patching, access review, monitoring, penetration testing, incident response, or independent assessment appropriate to the risk.
• Applying a suggested DNS, email, server, access, or security change without understanding its scope can interrupt or expose a Service. Verify the resource, maintain recovery access, and test high-impact changes.
• Support and contextual help explain platform behaviour; they do not assume control of the Customer’s security programme or create a managed-security obligation unless an Order expressly says so.

Website content, domain information, analytics, reports, recommendations, generated output, configurations, calculators, and support guidance are not legal, tax, financial, investment, accounting, audit, compliance, cybersecurity, medical, or other regulated professional advice.

Obtain advice from a suitably qualified professional for decisions that require professional judgment, regulated advice, an independent opinion, or knowledge of your particular circumstances. No professional-client, fiduciary, employment, partnership, franchise, or agency relationship is created merely by using Ignorre or receiving general support.

CX24 works to provide secure and reliable Services, but software, providers, registries, networks, third parties, public data, and Customer configuration can fail, be delayed, or change.

• Except for an express commitment in an accepted Order, and to the maximum extent permitted by law, no guarantee is made that Ignorre, information, measurements, provider state, generated output, or a third-party service will be uninterrupted, error-free, current, complete, secure, or fit for a particular purpose.
• The warranty exclusions and liability limits in the Terms and Conditions apply to this Disclaimer. Repetition here does not enlarge those limits or remove any express remedy in an Order.
• Nothing in this Disclaimer limits fraud, wilful misconduct, a non-waivable consumer remedy, a statutory data-protection right, or another duty or liability that applicable Indian or other mandatory law does not allow the parties to exclude.
• If a statement in this Disclaimer is unenforceable, it is limited or severed only to the minimum extent needed and the remaining statements continue to apply.