Purchased scope
Mopbe means Making Operations Better. It is a software product, not a separate legal entity, and is part of the EVDATI All-in-One Business Ecosystem. It may be purchased and used as a standalone product/module or with separately identified EVDATI services. Buying Mopbe does not require purchasing the ecosystem or grant rights to unrelated products; buying another product does not include Mopbe unless the applicable agreement says so.
Cross-module access, synchronization, reuse or migration occurs only where technically implemented, purchased or otherwise authorized, consistent with customer instructions, permissions, configuration, applicable agreements and law. A shared EVDATI identity is a future architectural possibility, not a verified current Mopbe feature. Shared identity would not confer an entitlement to unpurchased modules. Same-entity internal processing is not an unrelated third-party disclosure; flows to other EVDATI entities or service providers must still be disclosed and lawfully safeguarded.
Current functionality
Local workflow guidance and deterministic operating calculations coexist with configured AI-assisted answers and PDF/photo invoice extraction. AI availability depends on configuration and provider availability. There is no verified Mopbe recruiting or autonomous employment-decision feature. Mentioning potential ecosystem functions does not activate them.
Inputs and outputs
Invoice/OCR extraction can omit, duplicate or misread items, taxes, discounts, fees, quantities, currencies and pack prices. Review material fields, matching and totals before saving or ordering; extraction is not an authenticated invoice or a guarantee of accuracy.
Food costs depend on entered prices, portions, units, yields, packaging and third-party inputs. Estimates and missing inputs must be reviewed. Calculations do not guarantee actual profitability. Inventory records require physical counts, reconciliation and controls; purchases are not proof of consumption.
Operational reports are not audited financial statements and are not automatically GAAP, IFRS or tax-accounting statements. Exchange references may be delayed; confirm transaction rates, tax treatment and records with appropriate professionals. Purchasing tools do not guarantee supplier availability, prices, quality or performance.
Customers are responsible for wage/hour, employment, payroll, benefits, discrimination, privacy and workplace obligations. Payroll execution, recruiting and assessments are not verified current Mopbe features. If separately purchased and implemented in an EVDATI module, those tools provide decision support, not final employment decisions or a transfer of employer responsibility. Human review and lawful notices, consents and accommodations remain required.
AI output and third-party integrations may be incomplete, inaccurate, biased, stale or unavailable. Review outputs before consequential decisions. Do not rely on the platform alone for emergency, food-safety, financial, employment or legal decisions.
Data processing
Customer retains ownership of its Customer Data, including recipes, invoices, vendors, products, inventory, operational and sales records, uploaded files and, where supported, personnel, applicant, scheduling and timekeeping information. Customer grants EVDATI a limited license to host, copy, transmit and process that data only as necessary to provide, secure, support and improve purchased services under the agreement, Privacy Policy, DPA and law. This is not a transfer of ownership or an unrestricted right to commercialize proprietary information.
Processing data to deliver requested AI functionality is distinct from permitted de-identified service improvement and from training generalized, internal or external AI models on identifiable or proprietary Customer Data. No unrestricted model-training license is granted. [AI TRAINING/DATA USE CONFIRMATION REQUIRED] before any such training program or representation about provider retention/training is approved.
Properly de-identified or aggregated information may be used for lawful analytics, benchmarking, security, capacity planning, research and platform or ecosystem improvement. It must not reasonably identify or permit reconstruction of a customer, individual, employee, applicant, proprietary recipe, trade secret or confidential vendor relationship. Identifiable or reconstructable information remains Customer Data and is subject to the agreement and retention requirements.
Provider behavior
The inspected AI processing requests set store:false. That setting alone does not prove zero retention, exclude abuse monitoring, or establish the customer’s provider-specific training settings. Review approved provider contracts and configuration. Avoid submitting unnecessary personal or confidential information in questions.
Human control
Review invoice candidates, product matches and amounts before saving. AI text does not itself authorize an order, payment, personnel decision or data modification. Permissions and confirmation controls continue to apply. Outputs may be similar for multiple users; no uniqueness, professional opinion or exclusive intellectual-property right is guaranteed.
Retention and remedies
Following expiration or termination, customers have up to 30 days to access and/or export available Customer Data, subject to law, security requirements, technical availability and any different written agreement. After that period, EVDATI is not obligated to retain data for retrieval unless legally required or expressly agreed. Customer Data will be deleted or properly de-identified from active production systems within 90 days, subject to legitimate legal, regulatory, tax/accounting, litigation-hold, dispute, fraud-prevention, security-investigation and contractual-enforcement requirements. Exception records remain protected, restricted to the justified purpose and reviewed for continued necessity.
Residual copies of Customer Data may remain temporarily in backup or disaster-recovery systems after deletion from active systems. Such copies are isolated from ordinary business use and are deleted or overwritten in accordance with our normal backup lifecycle, subject to applicable legal requirements. No specific backup-retention duration is represented here; the production lifecycle remains to be verified.
Termination of Mopbe alone does not automatically terminate another separately purchased EVDATI service. A broader account and shared data legitimately required for an active purchased service may remain in use under that service’s agreement. Mopbe-specific data no longer needed follows the retention policy. Ecosystem-wide termination applies only when the customer terminates that subscription, the agreement makes services inseparable, or cross-service termination for cause is legally permitted. Shared data is not destroyed merely because one module ends.
The executed service agreement governs applicable warranties, lawful limitations and remedies. Report harmful or incorrect output to support@evdati.com.