OrmiTech IT

Legal · Privacy

Privacy Policy

How OrmiTech handles account, business and customer information when you use our AI-assisted communication and automation platform.

This policy explains the information flows confirmed in the OrmiTech marketing website code. The separate dashboard, API and production infrastructure are not included in this repository, so product-specific collection and processing described in marketing materials cannot be verified here and must be confirmed by OrmiTech before this policy is relied upon.

1. Scope and roles

OrmiTech provides software for customer communication, AI-assisted replies, lead and order records, and workflow automation. A business using OrmiTech decides what information it collects from its customers and how it uses that information.

For account, website and service-operation information, OrmiTech handles information for its own purposes. For messages and customer records that a business connects or enters into the platform, OrmiTech generally processes that information to provide the service on the business's instructions. The business is responsible for its own privacy notice, permissions and responses to customer requests. The parties' exact legal roles depend on the applicable law and the processing involved.

2. Information we handle

Information handled by this website

The contact form requests a name, email, company, phone and message. Its API validates required fields and logs the selected topic and whether an email address or phone number was supplied, then returns a success response. This repository shows no connection that stores or delivers the message to a monitored inbox. Do not use the form for privacy requests or sensitive information.

The Google Analytics tag sends page-view information when the marketing site loads. The browser also requests some blog images directly from Cloudinary. Those requests expose ordinary connection data, such as an IP address, to the relevant provider. Hosting and server-log data are controlled outside the code available for this audit.

Separate product information not verified here

Marketing materials describe accounts, business workspaces, connected messaging channels, customer conversations, leads, orders, delivery details, AI prompts and outputs, and workflow activity. The separate app, API, databases and provider configuration are not present in this repository, so OrmiTech must verify whether and how those categories are collected, stored, shared or deleted before treating them as actual data flows.

3. How we use information

In this marketing-site code, confirmed purposes are to measure page views through Google Analytics and display editorial content, including remotely hosted images. The contact API validates the submitted fields and records limited submission metadata in its application log, but no delivery or persistence path is shown. Product purposes such as account operation, AI processing, messaging and workflow automation are described in marketing materials but cannot be verified from this checkout; OrmiTech must confirm the live product's actual use before relying on this policy.

4. AI and automated processing

When a business enables AI features, relevant instructions and conversation context may be processed to generate or suggest replies, identify intent, extract details or trigger configured workflows. The exact information used depends on the feature and the business's configuration.

AI output can be inaccurate, incomplete or inappropriate. Businesses should review and configure automated responses for their needs, and remain responsible for decisions and messages sent to their customers. The AI provider identities and their prompt, training and retention settings are not identified in this notice. OrmiTech must verify and disclose those details before processing customer information through AI features.

5. Connected platforms and service providers

OrmiTech describes integrations for Facebook Messenger, Instagram, WhatsApp Business and website chat. When such a channel is enabled in the product, the information and permissions depend on the channel and the business's connection. The exact Meta identifiers, message fields, permissions and access-token handling are not identified in this notice. OrmiTech must document them from the live integrations before processing channel data.

Two external providers are visible in this repository: Google Analytics, whose script loads on the marketing site without a consent interface, and Cloudinary, which hosts some blog images that load when a page containing them is viewed. A request for a hosted image or analytics script can disclose ordinary connection information such as an IP address and browser details to that provider.

This notice does not identify the providers used by the separate dashboard and API for infrastructure, AI, email, payment or support. OrmiTech must confirm and disclose the providers actually used. Meta and other channel providers separately process information under their own privacy terms. Their APIs, permissions and available features can change.

6. When information is shared

Information is made available to authorized members of the relevant workspace and to connected platforms or service providers as needed to provide the service. We may also disclose information when required by law, to address security or abuse, or as part of a proposed business transfer, subject to appropriate protections.

OrmiTech does not operate as the seller of a business customer's products, the customer's courier, or the payment merchant for the customer's sales. Order and delivery information handled through the software remains part of the business's relationship with its customer and providers.

7. Cookies, analytics and similar technologies

Google Analytics 4 is loaded on this marketing website and is configured to send page views. This repository has no cookie-consent interface or Google Consent Mode, so the tag can run before a visitor has made a choice. Google Analytics may set first-party cookies such as _ga and _ga_<container-id> and receives browser and page-view information. The separate dashboard is not covered by this website implementation audit.

The site owner should review whether consent or another choice mechanism is required for the jurisdictions and visitors served, then implement and disclose the resulting behavior. Browser settings can be used to manage or clear cookies.

8. Retention and deletion

We keep information for as long as needed to provide the service, maintain an active business workspace, address support or security needs, and meet applicable legal obligations. Retention can differ by information type and by the instructions of the business that controls customer records.

This project defines no product-data, log or backup retention periods or deletion schedule. The separate product's actual account lifecycle and retention behavior must be confirmed. No fixed deletion timing or backup-expiry period is promised here. A business customer should direct end-customer requests to the business that manages the relevant workspace.

Read the Data Deletion Instructions

9. Security

This notice does not make claims about specific authentication, access-control, encryption, hosting, backup or security-audit measures, or any certification. OrmiTech should describe only measures verified in the live product and its deployment. No monitored security-reporting contact is provided here; one must be published for security reports.

10. International processing

OrmiTech's connected platforms and service providers may process information in countries other than where you or your customers are located. The countries, transfer arrangements and safeguards depend on the providers and deployment used. Those details should be confirmed against the current production configuration.

11. Your choices and privacy requests

Depending on your location and applicable law, you may be entitled to request access to, correction or deletion of personal information, restriction of or objection to processing, portability, or withdrawal of consent. Rights and exceptions vary. Contact the business that controls the workspace for end-customer information; OrmiTech's role and response will depend on applicable law and its instructions or agreement with that business.

The marketing contact form is not shown by this repository to deliver messages to a monitored inbox, so it is not a verified privacy-request channel. No monitored privacy-request address is provided here. OrmiTech must publish a working privacy contact and request-handling process before directing people to submit access, correction, deletion or other rights requests.

12. Children's privacy

OrmiTech is designed as a business communication service and is not directed to children. Business customers must not use the service to collect information from children in a way that violates applicable requirements. If you believe information about a child has been submitted to an OrmiTech-powered business, contact that business. This website does not provide a monitored OrmiTech contact route for forwarding the concern.

13. Marketing communications

This marketing-site project contains no email or promotional messaging system. The separate product's practices for marketing, service and account messages could not be verified here and must be described by OrmiTech if those messages are sent.

14. Security incidents

An incident affecting information should be assessed and handled, including notices where required by applicable law or contract. No incident-response procedure or monitored security contact is identified here. OrmiTech must confirm its operational process and contact route.

15. Changes to this policy

We may revise this policy as the service or our practices change. The updated date appears above. If a change materially affects how information is handled, we will take reasonable steps to provide notice through the service or another appropriate channel.

16. Contact

A legal entity name, postal address and monitored privacy contact are not provided in this notice. OrmiTech must publish those verified details and a working contact channel before relying on this as its operational privacy notice.