Effective
This website and your questions
This policy describes information handling for the public iBi Nexus website at www.ibinexus.com and initial enquiries to the team. Contact info@ibinexus.com with privacy questions or requests about information you have provided. Separate notices or agreements may apply to client services.
Information you choose to provide
The online enquiry form asks for your email address, an optional name, a starting-point selection and a project description. The application adds the page path, submission time and an opaque enquiry reference. There are no attachment or marketing-enrolment fields. We use enquiry information to review your request, respond and discuss possible work.
Please leave out passwords, access keys, Social Security numbers, payment details, tax records, medical information and confidential client records. An initial enquiry does not establish a confidentiality agreement or an engagement.
How your enquiry reaches the team
When online sending is available, the Hostinger-hosted website application passes your enquiry through Microsoft Graph to the Microsoft 365 shared mailbox info@ibinexus.com. A sent copy is retained in Microsoft 365. Your email address is set as Reply-To so the team can respond. The form does not automatically send you a confirmation email or enrol you in marketing.
A submission confirmation means Microsoft accepted the message for processing. It does not guarantee inbox delivery or a response time. If online sending is unavailable, the page can prepare a local email preview. Preparing or copying that preview does not send it. Your email application sends only when you choose to send; your browser, clipboard and email provider may retain information under their own settings.
Website requests and providers
Hostinger delivers and operates the website, including its delivery and security services. Requests can involve network address, requested page, browser or device information, and request or diagnostic logs. Microsoft processes enquiry messages through Microsoft 365. These providers handle information as part of operating their services. We do not represent hosting requests as anonymous or promise a particular processing country.
Operational records and retention
The application does not create an enquiry-content database. It stores limited private operational metadata: keyed digests, a pseudonymous browser key, opaque references, timestamps and outcomes. These records support duplicate prevention, rate limits and investigation. They do not contain your message text, name, email address or raw IP address.
Duplicate records older than 24 hours are removed on a subsequent submission transaction. Rate-attempt records cover the prior hour and are cleaned on subsequent transactions. This is request-triggered cleanup, not a promise of scheduled deletion at an exact time. Application event logs record opaque references, times, outcomes and sanitized provider request identifiers.
Received mail, sent copies, hosting logs, backups and any later project records have separate lifecycles and can remain longer than application duplicate records. Retention takes account of reviewing and responding to enquiries, operating the services, subsequent agreed work and applicable recordkeeping needs. Contact info@ibinexus.com to ask about records relating to your enquiry or request their deletion; we review the request and any applicable obligations rather than promise an unimplemented automatic deletion period.
Access, security and your choices
Enquiry messages are available to the team through its shared mailbox and to the service providers involved in delivery. Server-side mail credentials are not included in browser code. HTTPS, input and origin checks, a fixed mailbox destination, and duplicate and rate controls help protect submissions. These measures cannot eliminate all security or delivery risks; initial enquiries are not suitable for sensitive records.
You can use direct email instead of the online form. You may ask for access, correction or deletion of information you provided by emailing info@ibinexus.com. We may need enough information to identify the relevant records and verify a request. Applicable law and recordkeeping obligations can affect how a request is handled. Do not include unnecessary sensitive information when making a request.
Website AI assistant
The public website assistant answers questions about published iBi Nexus services without an account or password. A separate passphrase-protected maintenance preview remains available to authorized reviewers. When enabled, the Hostinger application sends your question, bounded recent question context and approved website material to Cloudflare Workers, Workers AI and, when needed, AI Search. Answers can be incomplete or incorrect; check the linked pages. The assistant cannot send email, book meetings or act on your systems. Do not share sensitive information.
The public assistant uses a signed, HttpOnly, secure same-site cookie named __Host-iBiPublicAssistant, valid for up to two hours, to supply an opaque visitor identifier for rate limits. The maintenance preview has separate authorization (__Host-iBiAssistant) and conversation storage. The public assistant saves a bounded transcript and unsent draft in this tab's session storage under ibinexus.assistant.public.v1, for a fixed two-hour period. This supports same-tab navigation and refresh. A new tab normally starts fresh; browser session restoration may recover unexpired session storage. Closing a browser is not an absolute deletion guarantee. New conversation, locking the preview or detected expiry clears saved history. Blocked browser storage can prevent continuity. No permanent browser conversation profile is created.
Application operational storage contains opaque rate-limit identifiers, timestamps, concurrency leases and aggregate provider budgets, not conversation content or raw IP addresses. Failed access attempts are limited using separate private hosting state. Cloudflare and Hostinger process requests and can retain operational metadata under their own service practices; we do not promise zero platform logging, a particular processing country or a fixed provider retention period. The application does not routinely log transcripts or send them to email, CRM or analytics.
Examples and future features
The public engineering, workflow and AI examples use sample information. The public assistant is separate from these examples and appears across public pages when enabled. New data-processing features require disclosures reflecting their actual providers and handling before launch.
Updates and contact
We update this policy when website practices change and identify the effective date here. Email info@ibinexus.com with questions about this policy or your enquiry.
