Disclaimer

What we don't promise

Every vendor lists what their product does. This is the other list — the limits, the shared responsibilities, and the things you should not assume.

Last updated 13 August 2026

1.Why this page exists

Authentication is a security boundary. If you are choosing infrastructure to sit on that boundary, the useful question is not what a vendor promises — it is what they decline to promise. This page is the second list.

Nothing here reduces the commitments in our Terms of Service. It sets out the limits of what Neuctra Authix does, so you can decide with the real picture rather than the marketing one.

2.No warranty

Neuctra Authix, its SDKs and its documentation are provided “as is”, without warranty of any kind. We do not warrant that the service will be uninterrupted, timely, secure or error-free, or that defects will be corrected.

We work to keep the service available and we monitor it, but there is no service level agreement and no uptime guarantee on any plan, including paid ones. Design your application to survive the API being unreachable.

3.Security is shared, not delegated

Using Neuctra Authix does not make an application secure. It handles a specific set of problems well and leaves the rest to you.

We handleYou still handle
Hashing passwords, issuing and verifying sessionsNot logging those sessions, not leaking them in URLs
Scoping publishable keys to the signed-in userKeeping secret keys off the client and out of your repository
Rejecting requests that exceed a plan limitValidating and sanitising what you store — the data API accepts any JSON
Enforcing ownership on every API requestYour own authorisation rules: who may see which screen, who may act on whose behalf
Rate limiting at the APIAbuse prevention in your product — spam signups, scraping, enumeration
Client-side guards are not security

A route guard or an auth gate controls what renders. It does not keep one user out of another's records — the API does that, on every request. Treat anything running in a browser or a mobile app as visible to the user, because it is.

4.Compliance is yours

Neuctra Authix holds no compliance certification. We are not SOC 2 or ISO 27001 certified, we have not been independently audited, and we are not a HIPAA business associate. We do not offer a signed data processing agreement as a standard product feature.

Do not store regulated data

Payment card numbers, health records, government identifiers and other special-category data do not belong in the Neuctra Authix data API. The API cannot detect them and applies no additional protection to them.

If you operate under GDPR, the UK GDPR, CCPA or a comparable regime, you are the data controller for your users. Meeting those obligations — lawful basis, notices, consent, responding to data subject requests — is your responsibility. See the Privacy Policy for how the roles divide.

5.Documentation, examples and estimates

  • Code samples are illustrations. They are written for clarity, not for production. They generally omit error handling, retries, input validation and logging. Read them, then write your own.
  • Documentation can lag the API. Where the two disagree, the API's actual behaviour is authoritative — tell us and we will fix the page.
  • Performance figures are indicative. Anything we publish about latency or throughput depends on your region, payload size, query shape and network. Measure with your own workload before committing to a design.
  • Plan limits are enforced as documented, but the practical capacity of an application built on Neuctra Authix depends on how it uses the API.

6.Not professional advice

Nothing on this website or in our documentation is legal, regulatory, financial or professional security advice. Descriptions of GDPR, HIPAA, PCI-DSS or any other regime are general context to help you ask the right questions, not an assessment of your situation. Consult a qualified professional about your own obligations.

8.Forward-looking statements

Buy what exists today

Anything we say about future features, roadmap items or planned improvements is an intention, not a commitment. Priorities change and planned work is sometimes dropped.

Make purchasing decisions on what the service does today, as described on the features page and in the documentation.

9.Contact

Questions about anything on this page: [email protected]. To report a security issue: [email protected] — please give us a reasonable chance to fix it before disclosing it publicly.

Operated by [registered company name], [registered address].