SITE POLICY / PRIVACY
Privacy notice.
This page explains the intended handling of information submitted through the Inham AI website. It must be reviewed against the actual hosting, email, logging, and retention configuration before the site is published.
Last updated: 10 October 2026 · Draft for configuration review
1. Information you submit
If you use the project enquiry form, the website asks for your name, agency name, work email, optional agency website, the systems involved, a workflow description, and optional project context such as timing, collaboration model, and referral source. Please do not send passwords, API keys, client records, CRM exports, or other sensitive credentials.
2. Why the information is used
The information is intended to help assess whether an enquiry fits the described lead-intake and CRM workflow service, clarify the requested outcome, and respond to the sender. It should not be used for unrelated purposes without an appropriate basis and notice.
3. How a submission is handled
The contact form submits to a server-side handler on this website. The handler is designed to validate the fields, apply basic anti-spam/rate-limiting controls, and send a notification using the hosting environment's configured mail service. This behavior depends on the deployed configuration and must be tested before launch. The final notice must identify any actual processors used for hosting and email delivery.
4. Hosting logs and retention
The hosting provider may process technical data such as IP addresses, request timestamps, and server logs as part of operating and securing the website. Exact log retention depends on the selected hosting configuration and provider policy and must be verified by the site operator. Enquiry details should be retained only as long as reasonably necessary for the stated purpose, subject to applicable requirements and any documented retention policy.
5. Cookies and analytics
The supplied website build does not include third-party analytics scripts or advertising pixels by default. If analytics, embedded media, scheduling services, or other third-party tools are added later, this notice should be updated to describe the actual tools and their data practices before activation.
6. Sharing and access
Enquiry information should be accessible only to people who need it to review and respond to the request. If details are shared with another processor or collaborator, the operator should confirm that the sharing is appropriate and transparently disclosed. This site does not ask users to submit credentials through the public form.
7. Security
The form uses server-side validation and basic anti-spam measures, but no website or communication channel can be represented as perfectly secure. Use a suitable secure process for any access details after a project has been scoped.
8. Your requests and contact
To ask about the information you submitted, request correction or deletion, or raise a privacy question, use the contact route provided on the Contact page. Before publication, the operator should add a verified privacy contact method and ensure it is monitored.
9. Regional requirements and updates
Privacy requirements depend on the operator, the people whose data is processed, and the markets served. The site operator should obtain appropriate legal guidance for applicable jurisdictions and update this notice when the form, hosting, analytics, retention, or business practices change.
10. Site owner checklist
- Confirm the operator/controller name and privacy contact.
- Confirm hosting provider and server-log retention.
- Confirm mail transport, recipient configuration, and any email processors.
- Decide how long enquiry messages are kept and how deletion requests are handled.
- Update this page before enabling analytics, cookies, or additional third-party tools.