These Terms of Service set the general rules for accessing the Hozina Technologies website and using the online materials, tools, demonstrations and downloads made available through it. Product-specific terms and written service agreements may add to or replace particular provisions for the relevant product or engagement.

1. Agreement and acceptance

In these Terms, “Hozina”, “we”, “us” and “our” refer to the operator of the Hozina Technologies website and the relevant Hozina product or service. “You” means the individual accessing the website or, where applicable, the business or other organisation on whose behalf that individual acts. “Terms” means this document together with any applicable product-specific terms, order terms, licence terms, proposal, statement of work (“SOW”) or other written agreement.

By accessing or using the website, you agree to these Terms to the extent that acceptance is legally effective in the circumstances. Downloading, installing or using a desktop tool may also require acceptance of a separate end-user licence agreement (EULA) or an in-product notice. Buying or commissioning a service requires the applicable order, proposal or SOW to be accepted as stated in that document. If you do not agree, do not use the relevant website feature, download, product or service.

If you accept on behalf of a company or other organisation, you represent that you have authority to bind it. If you do not have that authority, you must not accept on its behalf.

2. Hozina operator and contact

“Hozina Technologies” is the brand name used for the website, software products and services described here. The exact contracting party for a paid product or service must be the person or legal entity identified on the relevant invoice, checkout, proposal or signed agreement. Those documents should identify the operator’s legal name and appropriate business contact details. A brand name alone does not establish whether the operator is a proprietorship, partnership, company or other legal form.

For general enquiries, contractual notices and legal or support communications, use the Contact Us page and identify the nature of your message. A legal notice or complaint should include enough information to identify the relevant product, service, order or project, without including passwords or unnecessary sensitive information. The Contact Us route must be monitored by the operator.

3. Eligibility and lawful use

You must be legally capable of entering into the relevant agreement under applicable law. If you use a product or service for an organisation, you must have authority to do so. You may use the website, downloads and tools only for lawful purposes and in accordance with these Terms, product instructions and applicable third-party terms.

You must not use Hozina services to violate another person’s rights, access systems or data without authority, distribute unlawful material, or carry out an activity prohibited by applicable law. Nothing in these Terms removes a right or protection that applicable law does not permit a contract to waive.

4. Website content, information and availability

We aim to keep website descriptions, feature lists, illustrations, prices where shown, documentation and availability information useful and current. Website content is provided for general information and may be updated, corrected, suspended or removed. Screenshots, mock-ups, roadmaps, examples, performance descriptions and demonstrations may be illustrative and may not represent the exact current release or a binding promise of a future feature.

Unless we expressly agree otherwise in writing, website information is not a binding offer to provide a particular service, deliverable, feature, release date, price or service level. A binding commitment is established by the applicable order, proposal, SOW, licence or other confirmed transaction documentation. We do not promise uninterrupted access to the website or that every page or download will always be available, compatible with every configuration, or free from errors.

5. Estimates, calculators and public demonstrations

Any time-saving calculator, estimator, scope-building tool, sample output, demo environment or project preview is intended to help with preliminary evaluation. Results depend on the information, assumptions and selections entered. Outputs are estimates, not guarantees of actual time, cost, savings, business results or technical feasibility.

Unless a separate notice says otherwise, public demonstrations are not production systems and must not be used to store real customer records, payment information, authentication secrets or confidential business data. Demo records may be fictional, reset, altered or deleted. Do not rely on a public demo as a backup, system of record or service with guaranteed availability.

6. Website intellectual property

Unless identified otherwise, the Hozina name, logos, mascots, product names, graphics, website layout, text, illustrations, software, source code, documentation and other materials are owned by or licensed to the relevant rights holder and are protected by applicable intellectual-property laws. These Terms do not transfer ownership to you.

You may access the website and use its public materials for their intended purpose. You must not reproduce, modify, republish, sell, publicly distribute, create derivative works from, remove ownership notices from, or commercially exploit Hozina materials except where expressly permitted by us or by applicable law. You must not use Hozina names or marks in a way that suggests sponsorship, certification or endorsement without written permission.

7. Downloads, licences and updates

A download is not a transfer of ownership of the software. Your rights to install, copy, use, transfer or redistribute a desktop product are governed by its applicable EULA, licence notice and any purchase or subscription terms. If no separate licence is presented, you receive only the limited permission needed to download and use the product for its intended lawful purpose, subject to these Terms, and no right to resell or redistribute it is granted.

We may issue fixes, security updates, changes or new versions, but we do not promise that updates will be released on a particular schedule or that every release will support every older configuration. You are responsible for checking compatibility, keeping your system updated, maintaining backups and reviewing release notes. Any separate licence or purchase terms govern duration, fees, activation, refunds and permitted installations.

8. Prohibited conduct

You must not, and must not help another person to:

• use the website, tools or services for fraud, harassment, unlawful surveillance, unauthorised access, or infringement of intellectual-property, privacy or other rights;
• upload malware, malicious scripts or content designed to compromise systems, disrupt services or expose data;
• probe, scan, reverse engineer, bypass access controls, interfere with security, or test vulnerabilities in Hozina systems without prior written authorisation, except to the extent a restriction is prohibited by applicable law;
• attempt to obtain source code, credentials, private data or restricted materials by deception or technical circumvention;
• circumvent licence limits, access controls, payment mechanisms or rate limits, or use automated methods that place unreasonable load on the website;
• misrepresent identity or authority, submit information you are not entitled to provide, or use Hozina materials to create misleading endorsements;
• use any product or service in a way prohibited by the product-specific section or applicable third-party licence.

9. Materials you submit

If you submit enquiry text, project requirements, feedback, files, sample data, screenshots or other materials, you remain responsible for them. You represent that you have the rights and authority necessary to provide them and to authorise the uses reasonably required to respond to your enquiry or deliver the service you requested.

You grant Hozina a limited, non-exclusive permission to host, copy, review and use submitted materials only as reasonably needed to respond to you, assess a project, provide support, perform an agreed engagement, secure the service, or meet legal obligations. This does not transfer ownership of your materials or authorise unrelated use, public disclosure or model training. Do not submit passwords, private keys, API tokens, payment-card credentials or unnecessary sensitive data through general contact forms.

10. Third-party services, links and open-source components

The website, desktop tools or services may refer to or interoperate with third-party websites, libraries, hosting providers, APIs, operating-system capabilities, payment providers or other platforms. A reference, integration or link does not by itself mean that Hozina owns, controls, endorses or guarantees that provider. Your use of a third-party service may be governed by its separate terms, licence and privacy notice.

Open-source and third-party components remain subject to their respective licences and notices. Where a component imposes obligations that apply to your use or distribution, those obligations continue to apply. Nothing in these Terms is intended to remove rights granted directly by an applicable open-source licence.

11. Privacy and information security

Our Privacy Centre explains the intended handling of website information and the four desktop tools. It should be read with the relevant product or service notice. Those notices describe designed behaviour and must be checked against the actual deployed website, installer, configuration and service provider arrangements. The privacy notice is not a promise that every product version or third-party service behaves identically.

You are responsible for securing your device, accounts, backups, network and credentials. No website, software or internet transmission can be guaranteed completely secure. Where a service processes data on your behalf or on a client's behalf, the applicable SOW and, where appropriate, a data-processing agreement governs the details of that processing.

12. Professional services and order of precedence

Website development, custom CRM development and workflow automation work is delivered only to the scope agreed in a proposal, order, SOW or service agreement. The scope should describe deliverables, milestones, dependencies, pricing, payment schedule, acceptance criteria, support, hosting responsibilities, change control and ownership or licence arrangements.

If documents conflict, the following order applies to the extent of the conflict: mandatory applicable law; a signed agreement or SOW expressly addressing the issue; the relevant paid product or service-specific terms; these general Terms; and general website descriptions. A specific written agreement may expressly set a different priority. A privacy notice governs privacy disclosures, not project scope or intellectual-property assignment.

13. Fees, payment, taxes and cancellation

Fees, billing currency, taxes, reimbursable expenses, due dates, milestone payments, late-payment consequences and any deposits will be stated in the applicable proposal, SOW, invoice or checkout before the relevant commitment. You are responsible for applicable taxes other than taxes on Hozina's net income where the law allocates them to Hozina. Work outside the agreed scope requires written approval and may incur additional fees.

Refunds, cancellation rights and withdrawal terms depend on the specific product, purchase flow, SOW and applicable law. These general Terms do not invent a universal refund promise or remove a statutory consumer right. Before accepting payment, Hozina should present the applicable refund and cancellation terms clearly at the point of sale or in the signed agreement. If the documentation is unclear, the parties should obtain written clarification before payment or work commencement.

14. Suspension and termination

We may restrict or suspend website access, downloads, a demo or product distribution where reasonably necessary to protect users or systems, respond to security risks, comply with law, address suspected abuse, or discontinue a feature. Where practicable, we will provide notice or an opportunity to remedy the issue. A service engagement may be suspended or terminated only as allowed by its agreement and applicable law.

On termination, permissions that depend on the terminated service or licence end as specified in the relevant agreement. Accrued payment obligations, intellectual-property rights, confidentiality obligations, lawful retention duties, disclaimers and provisions intended by their nature to survive will continue to the extent permitted by law. Termination does not erase rights or remedies that have already accrued.

15. Disclaimers and reliance

To the maximum extent permitted by applicable law, the website, general information, public demos and free tools are provided on an “as available” basis. We do not warrant that they will be uninterrupted, error-free, compatible with every environment, or suitable for every purpose. We do not promise a particular business outcome, cost saving, search result, file-recovery result, system integration or security outcome unless expressly stated in a binding written agreement.

You must independently verify important outputs and maintain appropriate backups. Nothing in these Terms excludes an express warranty made in an applicable signed agreement or any consumer right or legal protection that cannot lawfully be excluded or restricted.

16. Limitation of liability

To the maximum extent permitted by applicable law, Hozina will not be liable for indirect, incidental, special, exemplary or consequential loss, or for loss of profits, revenue, business opportunity, anticipated savings, goodwill, data or business interruption arising from use of the website, tools or services, where such loss is legally capable of being excluded. This does not exclude liability where the law does not permit it.

For a paid service engagement, and subject to mandatory law and any signed agreement providing otherwise, Hozina's aggregate liability arising from the relevant SOW will not exceed the fees paid or payable to Hozina under that SOW during the twelve months before the event giving rise to the claim. For a free website feature or no-fee desktop tool, any limitation is subject to mandatory statutory protections and the maximum amount permitted by applicable law. These limitations do not apply to liability that cannot legally be limited, and should be reviewed by qualified counsel for enforceability in the jurisdictions in which Hozina offers products and services.

17. Your responsibility for claims caused by your use

To the extent permitted by law, you are responsible for third-party claims, losses and reasonable costs arising directly from your unlawful use of the website, infringement of third-party rights by materials you provide, unauthorised access you enable, or material breach of these Terms. This does not make you responsible for losses to the extent caused by Hozina's own breach, negligence or other conduct for which responsibility cannot legally be transferred to you. Any broader indemnity must be stated clearly in the relevant signed agreement.

18. Changes to these Terms

We may revise these Terms to reflect changes to products, services, business processes or law. The updated text will show a revised “Last updated” date. Where law or an existing contract requires additional notice or affirmative acceptance, we will follow that requirement. A policy update does not retroactively authorise conduct that was unlawful or alter a signed SOW retroactively without the agreement or legal basis required.

19. Governing law and disputes

These Terms are governed by the laws of India, subject to mandatory conflict-of-law rules and non-excludable protections that apply to you. Disputes are subject to the jurisdiction of courts or forums competent under applicable law. Nothing here deprives a consumer of a forum or remedy that cannot lawfully be waived. A signed agreement may contain a valid dispute-resolution process for the relevant engagement, subject to applicable law.

20. General provisions

If any provision is held unenforceable, it will be limited or severed only to the extent necessary, and the remaining provisions will continue where legally possible. A failure to enforce a provision is not a waiver. You may not transfer your rights or obligations under these Terms without our prior written consent, except where applicable law permits otherwise. Hozina may assign its rights as part of a lawful business reorganisation or transfer, subject to applicable law and contractual obligations. These Terms do not create a partnership, employment, agency or joint venture relationship.

These Terms and any documents incorporated by reference describe the subject matter they cover. Any amendment to a signed service agreement must be made in the manner required by that agreement. Electronic records and acceptance may be used where recognised by applicable law.

21. Contact and legal references

Use the Contact Us page for questions about these Terms, a product, a purchase or a service engagement. Identify the issue and relevant order or version. This page is not individual legal advice and does not guarantee immunity from claims; the operator must ensure the actual product, service, contracts and website practices match these Terms.

These additional terms govern use of Hozina Clip, a clipboard history and snippet utility. They supplement the General Terms of Service and any EULA presented with the product.

1. Product function and licence

Hozina Clip is intended to help you manage clipboard history and user-created snippets. Subject to the applicable licence, you may use the product for its intended purpose on supported Windows devices. Do not resell, redistribute, sublicense or modify the software unless the applicable licence or written permission allows it.

2. Clipboard capture and sensitive information

When clipboard monitoring is enabled, the product may capture formats provided by Windows, including text, rich text/HTML, images or screenshots, and copied file paths. The documented design also records the executable name associated with a clipboard event. Clipboard content can include personal data, client information, passwords, authentication codes, API keys, private keys, financial or medical information and confidential business material.

You decide whether to enable monitoring and which applications to exclude. Do not use the product to capture information you are not authorised to access or retain. Pause monitoring before handling particularly sensitive content. This tool is not a password manager, enterprise data-loss-prevention system or guaranteed secret-detection tool.

3. Local storage and encryption

The documented design stores clipboard history, snippets, tags, folders, settings and associated records locally, including in an application data directory such as %APPDATA%\ProClipboardDock\. The documented build uses Windows Data Protection API (DPAPI) protection for selected payloads at rest. Storage paths, schemas and security features may differ by version. Local storage does not eliminate risk from malware, administrator access, compromised Windows accounts, physical access or compromised backups.

4. Network behaviour

The supplied product documentation describes the verified design as not using routine analytics, telemetry, crash uploads, cloud synchronisation, cloud AI requests or outbound network clients. This statement must be checked against the exact released executable and all bundled components. If an update, licensing, synchronisation, diagnostics or online feature is introduced, the notice and relevant product documentation must be updated before that behaviour is released.

5. Exclusions and secret detection

Where offered, excluded-application lists and local pattern matching may help avoid saving selected clipboard content. These mechanisms are heuristic: they may miss unknown, modified, encoded or unrecognised secrets and may incorrectly identify harmless text. You remain responsible for configuring them and for deciding whether clipboard capture is appropriate for your work.

6. Retention, purge and export

Available controls may let you pause capture, limit history by age or quota, remove unpinned records or purge local history. The options and exact deletion behaviour depend on the release. Exports, including JSON exports, may contain readable clipboard content, file paths and snippets and may not receive the same at-rest protection as the in-app database. Secure exported files yourself.

Clearing the application database or uninstalling Hozina Clip may not remove files exported elsewhere, operating-system artefacts, copies in backups or items shared with another application. Do not assume that deletion from the application will securely erase every copy.

7. User responsibilities and risk

Protect your Windows account and device, keep the operating system updated, maintain backups, inspect exports before sharing them, and do not rely on the application to identify all credentials or sensitive content. Hozina Clip is provided as a productivity utility, not a guaranteed archive or compliance control.

8. Product-specific disclaimers

Clipboard events, source-process identification, exclusions, encryption and retention depend on Windows behaviour, permissions, product settings and release version. Except where a binding licence or mandatory law provides otherwise, Hozina does not guarantee that every clipboard format will be captured correctly, that sensitive content will always be detected and discarded, or that local records can never be accessed by a person or process with sufficient device privileges.

9. Conflicts and contact

The General Terms apply except where this section or an applicable EULA expressly governs the subject differently. Mandatory law prevails. For product support, identify the Hozina Clip version and Windows version using the Contact Us page.

These additional terms apply to Hozina Clean, a utility for identifying duplicate files and reviewing large files. They supplement the General Terms of Service and any product EULA.

1. Product function and authorised use

Hozina Clean is intended to help users scan selected locations, compare files, identify possible exact duplicates, review large files and evaluate potential storage savings. You may scan only locations and files you are authorised to access and manage.

2. Local processing and stored records

The documented architecture processes selected file data locally to read metadata, compare file bytes, compute partial or full SHA-256 fingerprints, generate previews and calculate scan summaries. A local SQLite database, documented as %APPDATA%\DuplicateCleanerPro\cleaner.db for the described build, may contain file paths, identifiers, timestamps, hashes, scan history, counts, size estimates and preferences. Exact contents and paths may change between versions.

3. Network and telemetry

The supplied documentation describes a local-first build without network requests, telemetry, analytics, cloud synchronisation or remote file uploads. This is a version-specific technical statement and must be verified against the distributed installer, update mechanism, licensing components and bundled dependencies. A future network-enabled feature requires updated disclosures before release. Do not interpret this section as a promise about software that has not been audited.

4. File deletion and recovery limitations

Some actions may send selected files to Windows Recycle Bin or invoke other Windows file-operation mechanisms. Recoverability depends on the file system, volume, storage location, Windows configuration, permissions, network or removable storage, and the operation performed. Files may be permanently removed or overwritten in some circumstances. Hozina does not guarantee that all files are recoverable after removal.

Before removing files, confirm the full path, filename, size and selection. Maintain independent backups and test your backup restoration process. Do not delete files solely because they appear in a duplicate or large-file list. Applications, operating systems and business workflows may depend on files that appear redundant.

5. Accuracy of scans and storage estimates

Results depend on accessible folders, exclusions, permissions, file type, file changes during scanning, hashing and file-system behaviour. The tool may skip inaccessible or unsupported items or produce incomplete results. Hard links, compression, sparse files, cloud placeholders and storage allocation rules can cause estimated reclaimable space to differ from actual space reclaimed. Scan results are advisory and do not replace human review.

6. Exported reports and local database

CSV or JSON reports may reveal full file paths, Windows usernames, employer or client names, project titles, filenames, metadata, duplicate groups, scan locations and storage estimates. Exports are saved where you choose and are not automatically uploaded under the documented local-only design. Review them before sharing and protect them as confidential information where appropriate.

In-app controls may clear scan history or the hash cache. Removing app data or uninstalling the product may not remove exported reports, copies elsewhere, backups or operating-system records. Data-clearing controls are not a substitute for secure device disposal or organisational data-retention procedures.

7. User responsibilities

• Use only authorised folders, devices and storage locations.
• Back up important data before scans that may lead to file operations.
• Review and confirm each removal action rather than treating recommendations as commands.
• Protect exported reports and local app data from unauthorised access.
• Do not rely on Hozina Clean as a backup, forensic, legal discovery or records-retention system.

8. Product warranty and liability

Except for express promises made in an applicable signed licence or rights that cannot lawfully be excluded, Hozina Clean is not guaranteed to identify every duplicate, find every large file, calculate exact storage savings or recover a removed item. To the extent permitted by law, Hozina is not responsible for data loss caused by a user's file selection, deletion confirmation, unsupported storage configuration, lack of backup or operation contrary to product warnings. This does not exclude liability that applicable law does not permit Hozina to exclude.

9. Conflicts and contact

The General Terms and any EULA remain applicable. For support, include the application version and a description of the scan or file-operation issue, but do not send file contents or sensitive paths unless necessary and appropriate. Use the Contact Us page.

These additional terms govern Hozina Explorer’s file-management and productivity features. They supplement the General Terms of Service and any EULA.

1. Product function and permitted use

Hozina Explorer may provide local file browsing, previews, batch actions, workspaces, tags, activity history, disk analysis, an integrated terminal, optional Windows shell association, network-drive access and an embedded web viewer. Feature availability depends on the installed version and configuration. Use the application only for files, devices, network shares and accounts you are authorised to access.

2. File access and operations

Browsing or managing files may process filenames, paths, sizes, timestamps, contents needed for previews or comparisons, hashes, folder structure and metadata. Some operations can copy, move, rename, archive, extract or delete files. These actions may affect source files and other applications. Confirm the selected source and destination before operating, and maintain independent backups of important data.

Hozina Explorer is not a guaranteed backup tool, file-recovery tool, archival system or legal-discovery platform. Previews, disk analysis and activity information may be incomplete or change with the file system, access permissions and application version.

3. Local settings and activity records

The product may store preferences, workspaces, saved tabs, tags, folder colours, a recent-activity timeline, disk-analysis cache and other records locally. The documented storage path includes %APPDATA%\ModernExplorer\storage\ and related application storage, but exact paths and data contents may change between versions. These records may reveal work patterns or directory structures. Clear them through supported controls where available and protect your Windows account.

4. External web viewer and third-party websites

If you open a URL in the embedded web viewer, your device communicates with the selected website and its service providers directly. Those sites may receive your IP address, request metadata, cookies or information you submit, and are governed by their own terms and privacy notices. Hozina does not control their independent practices. Do not assume that opening a website inside Hozina Explorer makes it local or private.

5. Integrated terminal

The integrated terminal runs commands through the local operating-system command processor. Commands may read, modify, delete or transmit data and may run with the permissions of the relevant account or process. Commands obtained from the internet or third parties can be unsafe. Review commands before execution, understand their effects, and do not run commands you do not understand on a system containing important data.

6. Windows shell association and network drives

If you enable optional shell integration, the product may modify user-level Windows settings or registry entries so supported folder or drive actions open in Hozina Explorer. Review the confirmation before enabling it, and use the available restore function or current product instructions to revert the association. We do not warrant compatibility with every Windows configuration or third-party shell extension.

When connecting a network drive or share, Windows and the remote resource may process authentication details, connection metadata and access logs under their respective mechanisms. Hozina does not receive network credentials through the documented Windows network-drive mechanism; this statement is specific to that design and must be checked against the actual release.

7. Network, telemetry and updates

The supplied product summary describes core file-management functions as local-first without routine telemetry or automatic upload of file contents to Hozina. User-requested web browsing and terminal commands can nonetheless communicate with external systems. If a future updater, cloud feature, analytics or other network capability is added, the product notice must be updated. Technical statements apply only to the build that has been checked.

8. Deletion of local application data

In-app controls may clear supported history and preferences. The documented approach of removing the ModernExplorer folder under %APPDATA% may erase saved workspaces, tags, recent folders, local cache or undo information; use release-specific instructions before deleting app data. Removing app data or uninstalling Hozina Explorer does not remove source files, exported copies, backups, Windows system artifacts or records held by external websites.

9. User responsibilities and product limitations

You are responsible for confirming file actions, commands, external websites, shell registration and network destinations. No feature is a substitute for security review, independent backups or organisational access controls. Hozina does not guarantee that every file operation can be undone or that every third-party website or network resource will function correctly inside the application.

10. Conflicts and contact

The General Terms and any product EULA apply alongside this section. Where a term conflicts, mandatory law and the applicable EULA govern the software licence to the extent stated in that EULA. For support, identify the product version and relevant operation through the Contact Us page.

These additional terms apply to Hozina Search, a desktop search utility that indexes selected local folders and can extract document text when deep content indexing is enabled.

1. Product function and authorised indexing

Hozina Search is intended to help you find files, metadata and, where enabled and supported, text extracted from documents or source code. You decide which folders to include or exclude. Only index files, folders, devices and data you are authorised to access and process. The tool may not index encrypted, inaccessible, unsupported, corrupt, very large or changing files completely.

2. Local index and search information

The documented application may store filenames, directory paths, file sizes, timestamps, file types, selected metadata, extracted text, tokens or vocabulary records, previews or snippets, app paths, search-related cache, scan state and settings in a local SQLite index. Storage paths vary by release and may be associated with a Windows user SID or a folder under %LOCALAPPDATA%\HozinaSearch\Data\. File paths and indexed text can themselves be sensitive. Protect the Windows account and select index locations carefully.

3. Keyboard shortcut and local interface

The documented activation shortcut detects consecutive presses of the left or right Control key to open or focus the search window. The described implementation discards unrelated key events for this detection and is not designed to record general typed content or act as a keylogger. This is a description of the specified implementation, not a claim about any future or modified build. The optional browser interface is described as bound to loopback address 127.0.0.1, commonly on a local port. This reduces network exposure but is not an absolute security guarantee against malware, other local software or configuration changes.

4. Outbound network requests

The documented architecture describes two limited categories of outbound requests. The smart calculator may refresh exchange-rate data from https://open.er-api.com/v6/latest/USD, described as approximately every 12 hours when a refresh is due. That provider may receive ordinary connection metadata such as IP address, request time and user-agent. The documented request does not include search queries, document contents or the local index.

When the updater is triggered, it may contact the publisher’s update endpoint or CDN to retrieve a version manifest and validate a downloaded installer’s SHA-256 hash. The update provider may receive routine connection metadata, such as IP address, timestamp, requested resource and user-agent. Endpoints and behaviours may change between releases; the shipped version must match this disclosure.

5. What is not sent by the documented workflow

The supplied product description states that search queries, extracted document text, original document bodies, filenames and index contents are processed locally and are not sent to Hozina’s servers or the currency-rate provider by the described search workflow. This does not mean the product never communicates with external services: the exchange-rate and updater requests are exceptions. This clause is version-specific and must not be published as a verified fact until the actual release and bundled components have been tested.

6. Indexing controls, retention and deletion

Supported controls may allow you to add or remove indexed folders, rebuild or purge an index and manage exclusions. A file-change watcher may remove corresponding index records when it detects relevant changes, subject to product behaviour and permissions. Clearing the index removes app index records; it does not delete original files. Uninstalling the tool may not delete exports, backups, data outside the app data directory or records retained by external providers.

7. Results and reliability

Search results, previews and extracted text are a convenience feature, not a guaranteed archive or legal-discovery record. Results may be incomplete due to permissions, file type, exclusions, corruption, encryption, file size, resource limits or changes during scanning. Verify important information in the original file and location.

8. User responsibilities and disclaimers

Secure your device and local account, maintain backups of important files, review indexing locations and exclusions, and keep the product updated. Hozina does not guarantee that every file will be indexed, that all content extraction is exact, or that every search result is complete or current. The product is not intended to establish legal compliance or replace a regulated records-management system.

9. Conflicts and contact

The General Terms and any EULA apply alongside this section. For support, specify the Hozina Search version and describe the issue without sending sensitive document contents unless necessary and appropriate. Contact us through the Contact Us page.

These service-specific terms apply when Hozina agrees to build, configure, deploy or support a customer website. They supplement the General Terms and the applicable proposal, SOW or services agreement.

1. Scope and project documentation

Hozina will deliver the specific pages, components, features, integrations, migration tasks, deployment work, and documentation expressly identified in the accepted proposal or statement of work (“SOW”). General conversations, website examples, and preliminary demonstrations do not create deliverable commitments unless confirmed in writing. Where applicable to the project, the accepted SOW must identify: included pages and components; functional requirements and integrations; deliverable formats and source files; technical environment and deployment responsibilities; milestones and payment schedule; customer dependencies and approvals; acceptance criteria and review period; included defect-correction period; hosting, maintenance, and post-launch support arrangements; and ownership and licensing of custom deliverables. Not every item applies to every small project; material terms must be agreed in writing for each project.

2. Client materials and responsibilities

You must provide accurate requirements, approved content, branding assets, product information, access credentials, and feedback in a timely manner. You represent that you own or have permission to use all text, imagery, fonts, logos, video, data, and other materials supplied to Hozina. You are responsible for the accuracy and lawfulness of supplied content, the business claims made on your website, and any notices or permissions required for the site’s intended purpose.

Unless the accepted statement of work expressly provides otherwise, the customer controls the production hosting environment, domain, application accounts, and production data. Hozina does not provide managed server hosting by default. Projects are generally deployed to the customer’s own hosting account or server, as agreed in writing.

During authorised development, migration, testing, deployment, troubleshooting, or support, Hozina may require temporary access to systems or data relevant to the project. Depending on the agreed technical configuration, limited data may also be processed by approved third-party services, integration providers, logs, retry queues, backups, or support tools. Any hosting, storage, logging, backup, or other processing of customer information by Hozina must be consistent with the accepted project agreement and applicable data-handling terms. The parties must establish appropriate access controls, authorised purposes, retention requirements, credential management, and handover or deletion responsibilities for the project. At handover, the customer should rotate credentials shared during development, revoke temporary access that is no longer required, and confirm control of the production environment and its data.

3. Content, functionality and change requests

Features and requirements must be sufficiently described in the accepted SOW. New pages, revised requirements, new integrations, additional rounds of design, migrations, content entry, performance work, or modifications requested after approval require a written change request, additional fees, or an adjusted timeline. Hozina is not required to start out-of-scope work until the change request is approved in writing.

4. Testing and acceptance

The accepted statement of work must specify the acceptance criteria, customer review period, process for reporting reproducible defects, and procedure for resolving disputed acceptance.

The customer must review and test the agreed deliverables within the specified review period and provide a sufficiently detailed written description of any claimed defect.

A defect means a reproducible failure of a deliverable to meet an expressly agreed requirement. A request for new functionality, a material change in an approved design, a third-party change, or a modification outside the agreed scope is not automatically a defect.

The treatment of defects, delays in customer review, and any deemed-acceptance procedure must be expressly agreed in the project documents and remain subject to applicable law.

5. Third-party software, hosting and dependencies

A website may depend on hosting providers, domain registrars, content-management systems, plugins, APIs, email delivery services, payment gateways, CAPTCHA, analytics, cookies, web fonts, media embeds, or other third-party services. Unless expressly included in the accepted SOW, Hozina does not control their availability, pricing, terms, security, region, data retention, or future compatibility. Customer-paid subscriptions and usage charges must be identified in the SOW and remain the customer’s responsibility.

Hozina remains responsible for its own agreed implementation obligations. A third-party outage does not remove Hozina’s responsibility for work within its own reasonable control, but compatibility or performance guarantees exist only where express, measurable criteria have been agreed in writing. Security patches, backups, uptime monitoring, disaster recovery, 24/7 support, SEO rankings, load testing, accessibility audits, penetration tests, and ongoing maintenance are included only where expressly agreed in writing.

6. Legal compliance of the customer's website

Unless expressly included in the accepted statement of work, Hozina does not provide legal, tax, regulatory, or compliance advice and does not certify that a website satisfies every applicable legal requirement.

Where Hozina implements technical features based on requirements or legal specifications supplied by the customer or its professional advisers, the implementation does not constitute an independent legal certification.

The customer remains responsible for determining its applicable legal obligations, business disclosures, and the required notices, consents, and permissions for the website, subject to responsibilities expressly accepted by Hozina in writing and obligations that cannot lawfully be excluded. This provision does not excuse a failure to perform a compliance implementation that Hozina expressly accepted in the accepted statement of work.

7. Ownership and licences

Ownership and permitted-use rights for project deliverables must be expressly defined in the accepted statement of work or project agreement.

Unless the accepted statement of work expressly assigns ownership of specifically identified deliverables to the customer, Hozina retains ownership of its pre-existing intellectual property, general-purpose tools, reusable components, templates, libraries, generic code, methods, processes, and know-how.

Subject to full payment of all applicable fees, the customer receives a non-exclusive licence to use the final project deliverables for the purpose specified in the accepted statement of work. Any broader rights, including copyright assignment, exclusive rights, resale, redistribution, sublicensing, or source-code ownership, must be expressly agreed in writing.

Customer-provided materials remain the property of the customer or the relevant rights holder. Third-party and open-source components remain subject to their respective licences. Hozina cannot assign ownership of materials or components that it does not own.

Where the parties agree to assign ownership of specific bespoke deliverables, the accepted statement of work must identify the relevant deliverables, the rights being assigned, the applicable payment condition, and any components excluded from the assignment.

8. Access, security and handover

Each party must maintain administrative security, using separate user accounts, least-privilege permissions, secure credential exchange, and multi-factor authentication where available. Passwords, private keys, or API tokens must never be sent via general website contact forms.

The accepted SOW must state who controls hosting and production data, who maintains backups and updates, how access is revoked, and what handover materials are included. Where Hozina accesses personal data on the customer’s instructions, the parties must document that role and the required controls in the accepted SOW and, where appropriate, a data-processing agreement.

At handover, the customer must rotate credentials shared during development, revoke temporary access granted to Hozina, and confirm independent control of the production environment and its data.

9. Hosting, warranty and support

Each eligible customer receives up to three complimentary support requests during the first twelve months following the agreed project handover date, unless the accepted statement of work specifies otherwise. [BUSINESS CONFIRMATION REQUIRED: confirm eligibility criteria, start date, definition of request, and expiration rules].

Each support request covers one distinct question or issue relating to the delivered project. Hozina will review the request and confirm whether it falls within the included support scope. Work requiring a new feature, a material change, substantial redevelopment, third-party service intervention, or work outside the original agreed scope may require a separate written estimate and approval.

Complimentary support does not automatically include managed server hosting, continuous monitoring, operating-system administration, 24/7 emergency response, third-party subscriptions, or ongoing maintenance. Any additional support, maintenance, monitoring, or server administration must be agreed separately in writing before that work begins.

A separate defect-correction period, if any, applies only as expressly set out in the accepted SOW. Support does not include third-party outages, changes made by others, or emergency response outside the agreed service.

10. Completion, suspension and termination

Customer cancellation, fees for work completed up to termination, approved non-cancellable third-party costs, treatment of deposits and prepaid milestone fees, handover of paid work in progress, transfer of customer materials, return or deletion of information, and credential revocation follow the accepted SOW and applicable law.

Deposits and milestone payments represent compensation for allocated resources, scheduling, and completed phases; neither party may impose punitive cancellation charges without clear contractual agreement. If customer delay, missing credentials, or pending approvals prevent progress, milestones and timelines will be adjusted as the agreement permits.

On completion or termination, the parties must confirm delivery status, ownership/licensing position, account control, outstanding fees, backup verification, and access removal, subject to lawful retention and documented backup cycles.

11. Service-specific risk allocation

Website delivery depends on clear requirements, timely feedback, hosting configuration, third-party services, and ongoing maintenance.

To the extent permitted by applicable law and the accepted SOW, Hozina is not responsible for losses arising from inaccurate customer content, customer-directed configuration, unlicensed materials supplied by the customer, unsupported post-handover changes, or third-party service failures beyond Hozina’s reasonable control.

Exclusions and limitations apply only to the extent permitted by law and do not purport to exclude or restrict liability for gross negligence, wilful misconduct, fraud, or statutory consumer obligations that cannot lawfully be excluded.

12. Related documents and contact

The accepted proposal or SOW governs project scope, pricing, milestones, acceptance criteria, support, and ownership where it expressly covers those matters. The General Terms, Privacy Centre, and any agreed Data Processing Agreement also apply. In the event of a conflict, the order of precedence specified in Section 12 of the General Terms applies. Use the Contact Us page for service enquiries and identify the relevant project.

These service-specific terms apply to a custom customer relationship management (CRM) system and its agreed modules, integrations, migration and support. They supplement the General Terms and written project agreement.

1. Scope and written agreement

The accepted SOW defines included modules, entities, pipelines, workflows, roles, reports, integrations, migration sources, deployment targets, technical stack, milestones, and support. Features shown in mock-ups, conversations, or public demonstrations do not constitute deliverable commitments unless confirmed in writing. Customisation, changed business rules, additional integrations, and expanded migration scope require written change control and may incur additional fees.

2. Client's role and rights in CRM data

The customer determines the business purposes for which CRM personal data is collected and processed and is responsible for ensuring it has authority and an applicable lawful basis to process that information under applicable privacy laws. The customer must provide required notices to leads, customers, employees, and other individuals; maintain appropriate data quality and retention rules; and manage permissions, data-subject rights, access, correction, export, and deletion requests as required by law.

Do not import purchased, scraped, unverified, or confidential third-party data unless you hold the necessary legal rights and documented lawful basis. Avoid collecting unnecessary sensitive personal data in free-text fields or attachments. Hozina must follow documented customer instructions when accessing data, subject to applicable law and the agreed contract. This clause does not relieve Hozina of any statutory duties that apply directly to it as a processor, service provider, or independent controller for specific activities.

3. Access and processing instructions

Hozina will access or migrate live CRM data only where required by the project and authorised by the customer. Where Hozina processes personal data on the customer’s behalf, the parties must document data categories, processing purposes, authorised personnel, access periods, hosting environments, approved subprocessors [BUSINESS CONFIRMATION REQUIRED: confirm approved subprocessors], retention and deletion arrangements, security measures, incident notification protocols, and data-subject request assistance in the SOW and, where appropriate, a Data Processing Agreement. Synthetic, dummy, or anonymised records must be used for development and demonstrations wherever practicable.

Unless the accepted statement of work expressly provides otherwise, the customer controls the production hosting environment, domain, application accounts, and production data. Hozina does not provide managed server hosting by default. Projects are generally deployed to the customer’s own hosting account or server, as agreed in writing.

4. Demo and test environments

Public or shared demos are demonstrations, not production systems or permanent storage. They must use fictional sample data. Do not enter genuine customer records, personal identities, passwords, payment details, confidential attachments, or live production data into a demo environment unless the environment has been expressly approved, dedicated, and appropriately secured for that purpose. Demo records may be reset, altered, or removed without notice unless a written agreement provides otherwise.

5. Security features and responsibilities

Security features—including role-based permissions, audit trails, encryption at rest or in transit, multi-factor authentication, backup and restoration routines, secure exports, password policies, session timeouts, and vulnerability testing—are included only to the extent expressly specified in the accepted SOW and the implemented architecture. Hozina does not certify security compliance, perform penetration testing, or guarantee immunity from security compromises unless specifically contracted in writing.

Responsibility for operational security is divided: the customer remains responsible for user provisioning, access reviews, role assignments, account deactivation, credential management, local device security, and patching customer-controlled infrastructure, unless the SOW expressly assigns those tasks to Hozina. Production access must follow least privilege and be revoked when no longer required.

6. Integrations and third-party services

A custom CRM may connect to email, calendars, web forms, automation platforms, cloud storage, payment gateways, telephony, or external APIs. Such integrations can disclose data to the relevant third-party provider and are included only if the accepted SOW identifies them. Provider API changes, quotas, rate limits, outages, pricing revisions, regional data hosting, and retention policies may affect performance. The customer’s chosen provider terms apply to that provider’s independent processing. Hozina remains responsible for its agreed implementation, but cannot guarantee uninterrupted third-party service availability.

7. Testing, acceptance and data migration

The accepted SOW must specify acceptance tests, customer review periods, defect reporting procedures, and migration acceptance criteria. The customer must verify that workflows, user roles, reporting calculations, data mappings, imports, and exports meet agreed specifications before relying on the CRM in production. Migration depends on source-data quality, schema compatibility, duplicate records, file formats, and source-system access. Hozina does not guarantee perfect conversion of incomplete, corrupted, inconsistent, or unsupported source records. The parties must establish an agreed approach for identifying and resolving migration defects and data-mapping discrepancies.

The customer must maintain a verified backup of all source data prior to migration and validate migrated records. The customer must not decommission a previous system until operational readiness, data completeness, and system stability are confirmed in writing.

8. Hosting, backups and retention

Unless the accepted statement of work expressly provides otherwise, the customer controls the production hosting environment, domain, application accounts, and production data. Hozina does not provide managed server hosting by default. Projects are generally deployed to the customer’s own hosting account or server, as agreed in writing.

The contract must identify who controls the production environment, who performs backups, what backup frequency is included, and who is responsible for restoration testing. Hozina does not provide ongoing backups, disaster recovery, or server administration unless expressly included in an accepted SOW or separate support agreement. At project completion, temporary project files, credentials, and access will be returned, deleted, or revoked in accordance with the contract, subject to lawful retention requirements and documented backup cycles.

9. Ownership and reusable components

Ownership and permitted-use rights for project deliverables must be expressly defined in the accepted statement of work or project agreement.

Unless the accepted statement of work expressly assigns ownership of specifically identified deliverables to the customer, Hozina retains ownership of its pre-existing intellectual property, general-purpose tools, reusable components, templates, libraries, generic code, methods, processes, and know-how.

Subject to full payment of all applicable fees, the customer receives a non-exclusive licence to use the final project deliverables for the purpose specified in the accepted statement of work. Any broader rights, including copyright assignment, exclusive rights, resale, redistribution, sublicensing, or source-code ownership, must be expressly agreed in writing.

Customer-provided materials remain the property of the customer or the relevant rights holder. Third-party and open-source components remain subject to their respective licences. Hozina cannot assign ownership of materials or components that it does not own.

Where the parties agree to assign ownership of specific bespoke deliverables, the accepted statement of work must identify the relevant deliverables, the rights being assigned, the applicable payment condition, and any components excluded from the assignment.

10. Support and changes

Each eligible customer receives up to three complimentary support requests during the first twelve months following the agreed project handover date, unless the accepted statement of work specifies otherwise. [BUSINESS CONFIRMATION REQUIRED: confirm eligibility criteria, start date, definition of request, and expiration rules].

Each support request covers one distinct question or issue relating to the delivered project. Hozina will review the request and confirm whether it falls within the included support scope. Work requiring a new feature, a material change, substantial redevelopment, third-party service intervention, or work outside the original agreed scope may require a separate written estimate and approval.

Complimentary support does not automatically include managed server hosting, continuous monitoring, operating-system administration, 24/7 emergency response, third-party subscriptions, or ongoing maintenance. A change to a third-party API, client workflow, hosting provider, or business rule may require a change request and additional fees; however, issues resulting from a failure of Hozina to meet expressly agreed deliverable requirements during an applicable defect-correction period are not classified as chargeable changes.

11. Business decisions and service limitations

The custom CRM is a technical software tool for storing, managing, and presenting customer information; it does not guarantee a particular sales result, pipeline conversion rate, cash collection, or commercial outcome. The customer must verify important business outputs and maintain human oversight for decisions that materially affect individuals or business operations.

To the extent permitted by law and the SOW, Hozina is not responsible for decisions made on inaccurate source data, customer-configured permissions, unauthorised exports, or use outside agreed requirements, except to the extent the loss results from Hozina’s own breach or legal responsibility that cannot lawfully be excluded.

12. Related documents and contact

The accepted SOW, General Terms, Privacy Centre, and any agreed Data Processing Agreement apply together. Mandatory statutory protections prevail over conflicting terms. Contact Hozina via the Contact Us page and identify the project or environment involved.

These service-specific terms apply when Hozina designs, configures, tests, deploys or supports workflows and integrations between business systems. They supplement the General Terms and the applicable SOW.

1. Defined scope and integrations inventory

Hozina will design, configure, test, and deploy only the specific workflows and integrations set out in an agreed integrations inventory and workflow specification within the accepted SOW. Where applicable, the accepted SOW must identify: trigger and source system; destination system; data fields, schemas, and transformations; workflow logic, filtering, and branching; permissions and connected accounts; hosting arrangement and deployment environment; test scenarios and test data requirements; retry, error-handling, and fallback behaviour; duplicate-event and idempotency safeguards; monitoring, logging, and alerting commitments; human review and escalation rules; data retention and payload logging policies; and support and maintenance scope. Mention of n8n, Microsoft Power Automate, Google Workspace, Zapier, Make, REST/GraphQL APIs, or webhooks does not guarantee that every integration or platform feature is available. Integration feasibility depends on supported endpoints, account permissions, provider plan limits, and technical compatibility.

2. Client authority and lawful instructions

The customer must own or be authorised to administer all connected accounts, applications, and endpoints, and provide documented permission for Hozina to configure them. The customer is responsible for maintaining the lawful basis and authority to process and transfer data, providing required notices and consents, ensuring source-data accuracy, approving data destinations, and managing permissions granted to connected applications. Hozina will access data and connect systems solely under documented customer instructions and will not knowingly connect to a third-party account without documented authorisation or route personal information to an unapproved destination.

3. Data that may flow through workflows

Depending on configuration, workflows may process contact information, lead details, CRM records, spreadsheet rows, business documents, emails, attachments, calendar events, notifications, API payloads, webhook data, identifiers, execution logs, retry queues, timestamps, error messages, and technical diagnostics.

Where practicable, workflow logs should avoid retaining unnecessary personal or confidential content. Credentials, API tokens, private keys, and other authentication secrets must not be intentionally written to ordinary application logs. The parties must agree on appropriate payload redaction, access control, and retention for the selected automation platform. Hozina does not represent that every execution payload can always be completely masked if the underlying platform architecture or third-party node does not support payload redaction.

4. Third-party providers and data location

Data processed by automations may pass between web form services, CRM platforms, email providers, automation runtimes, cloud or on-premise infrastructure, and external APIs. Each provider applies its own processing terms, infrastructure location, logging, retention, and security controls. Data location depends on the customer’s account configuration, provider subscription tier, hosting setup, and configured endpoints. No data-residency, in-country storage, local-only processing, or jurisdictional compliance commitment applies unless the specific architecture has been evaluated and the requirement is expressly recorded in the accepted SOW.

5. Credentials, least privilege and security

Credentials, OAuth tokens, API secrets, private keys, and service-account permissions provide access to connected systems. The parties must use provider-supported OAuth or secure secret storage where available, establish dedicated service accounts where appropriate, apply least privilege, exchange secrets through an agreed secure channel, and rotate or revoke credentials when no longer needed, at handover, or following suspected exposure. The customer remains responsible for account ownership, credential security, and permission audits, unless the accepted SOW expressly assigns a specific credential-management service to Hozina.

6. Testing, logs, retries and duplicate actions

Before production use, the parties must agree on a test plan, test scenarios, synthetic payloads, error paths, retry logic, duplicate-event handling, logging, and rollback procedures. Automations may fail due to expired credentials, provider rate limits, API schema changes, service outages, invalid source data, network latency, or changed business rules. Automatic retry mechanisms can cause duplicate actions (such as repeated notifications, multiple webhook triggers, or duplicated database entries) unless the workflow and receiving systems are designed and configured with deduplication or idempotency safeguards.

Idempotency safeguards, deduplication, retry policies, rollback procedures, and manual review are implemented only where technically supported, agreed in the SOW, and appropriately tested. Hozina does not guarantee that duplicate execution or all data loss will always be prevented under all operating conditions.

7. Monitoring, service levels and human review

Alerts, monitoring dashboards, error queues, manual intervention, and ongoing performance reviews are included only if described in the accepted SOW. Unless expressly agreed in writing with measurable service levels, Hozina does not provide 24/7 monitoring, guaranteed execution, a specific uptime SLA, or immediate exception resolution. Where a paid monitoring or incident-response service is agreed, the SOW must specify operating hours, contact channels, coverage, and response targets.

The customer must maintain a manual fallback and human review where a missed, delayed, or repeated workflow action could cause financial loss or material harm. An automation must not be used to make high-impact, legal, or automated decisions about individuals without appropriate human oversight and safeguards. Each eligible customer receives up to three complimentary support requests during the first twelve months following project handover, subject to the applicable support terms. [BUSINESS CONFIRMATION REQUIRED].

8. Production data and change control

Synthetic, test, or anonymised data must be used during development and testing wherever practicable. If access to production data is required for debugging or live testing, the parties must agree on the scope, authorised users, access window, and cleanup procedures before access is granted. Changes to connected API schemas, third-party platforms, authentication methods, workflow logic, permissions, or business rules may disrupt workflow execution and require a formal change request and additional fees. The accepted SOW must identify which party controls workflow execution history, retry queues, logs, and backups.

9. Hosting, retention and project end

Unless the accepted statement of work expressly provides otherwise, the customer controls the production hosting environment, domain, application accounts, and production data. Hozina does not provide managed server hosting by default. Projects are generally deployed to the customer’s own hosting account or server, as agreed in writing.

Where self-hosted n8n or another automation platform is deployed on a customer-provided VPS or cloud server, the customer remains responsible for VPS hosting fees, operating-system administration, security patches, backups, and ongoing server maintenance, unless a separate written agreement specifically assigns a service to Hozina. At project end, workflows, credentials, test data, logs, and access permissions will be returned, removed, transferred, or disabled as agreed, subject to legal retention and technical constraints. At handover, the customer must rotate all credentials used during implementation and confirm control of the production environment.

10. Security incidents and cooperation

If Hozina becomes aware of a security incident affecting customer data within its direct control, it will assess the incident and cooperate with the customer in accordance with applicable law and the governing contract. The accepted SOW or Data Processing Agreement must specify notification contacts, communication timelines, information-sharing procedures, containment responsibilities, and the allocation of incident-response duties. No arbitrary notification deadline applies unless specified in the agreed contract or required by applicable law.

11. Ownership and no implied service level

Ownership and permitted-use rights for project deliverables must be expressly defined in the accepted statement of work or project agreement.

Unless the accepted statement of work expressly assigns ownership of specifically identified deliverables to the customer, Hozina retains ownership of its pre-existing intellectual property, general-purpose tools, reusable components, templates, libraries, generic code, methods, processes, and know-how.

Subject to full payment of all applicable fees, the customer receives a non-exclusive licence to use the final project deliverables for the purpose specified in the accepted statement of work. Any broader rights, including copyright assignment, exclusive rights, resale, redistribution, sublicensing, or source-code ownership, must be expressly agreed in writing.

Customer-provided materials remain the property of the customer or the relevant rights holder. Third-party and open-source components remain subject to their respective licences. Hozina cannot assign ownership of materials or components that it does not own.

Where the parties agree to assign ownership of specific bespoke deliverables, the accepted statement of work must identify the relevant deliverables, the rights being assigned, the applicable payment condition, and any components excluded from the assignment.

A workflow engagement does not imply a guarantee that a third-party API will remain available, that a platform vendor will not change pricing or terms, or that an automated process will eliminate all manual administrative effort.

12. Related documents and contact

The General Terms, accepted SOW, and any agreed Data Processing Agreement apply together and define the technical scope, fees, service levels, and data-handling responsibilities. Mandatory applicable law prevails over conflicting provisions. Use the Contact Us page to reach Hozina, identifying the workflow, platform, or project concerned.